Shell scripts
You can use scripts provided with IBM® InfoSphere® Master Data Management Collaboration Server to perform many functions. These scripts are a powerful way to perform many functions quickly and efficiently.
Ensure that you do not use the following keywords in your
scripts. If any of the following keywords are used, your script may
fail to compile. These keywords are reserved in InfoSphere MDM Collaboration Server scripting
language:
- var
- function
- if
- else
- while
- for
- new
- return
- break
- continue
- true
- false
- null
- toInteger
- toDouble
- toString
- script_execution_mode=not_compiled
- script_execution_mode=compiled_if_available
- script_execution_mode=compiled_only
- script_execution_mode=java_api=
The following words are reserved as implicit variable names:
All script operation names are reserved as well.- item
- err
- val
- res
- category
- feed_doc_path
- cmsInstance
- cmsMetadata
- cmsReadOnlyAttribs
- abort_local.sh script
Use the abort_local.sh script to abort IBM InfoSphere Master Data Management Collaboration Server and all services from the command line. - analyze_schema.sh script
Use the analyze_schema.sh script to generate statistics of your Oracle and DB2® databases. - checkForCompileError.sh script
Use the checkForCompileError.sh script for automated checking of your scripts for compilation errors in the IBM InfoSphere Master Data Management Collaboration Server environment. - cleanup_cmp.sh script
Running the cleanup_cmp.sh script on an existing company in InfoSphere MDM Collaboration Server instance removes the company object itself from the InfoSphere MDM Collaboration Server database. Along with the company object itself, the script also removes all information in a company such as items and catalogs in the IBM InfoSphere Master Data Management Collaboration Server environment. - configureEnv.sh script
Use the configureEnv.sh script to configure your installation of IBM InfoSphere Master Data Management Collaboration Server. Running this script validates the env_settings.ini file and notifies you of any errors, generates build.properties and common.properties files, and generates the configuration for InfoSphere MDM Collaboration Server services. - copy_files_for_appsvr.sh script
Use the copy_files_for_appsvr.sh script to copy files for the IBM InfoSphere Master Data Management Collaboration Server appsvr service. This script is located in the $TOP/bin/copy_files_for_appsvr.sh directory. - create_appsvr.sh script
Use the create_appsvr.sh script to deploy a second appsvr service on the same server for vertical clustering in the IBM InfoSphere Master Data Management Collaboration Server environment. - create_cmp.sh script
Use the create_cmp.sh script to create a company for production deployment or a test company that you can use to test your installation and initial login to IBM InfoSphere Master Data Management Collaboration Server services. - create_pimdb.sh script
Use the create_pimdb.sh script to create a IBM InfoSphere Master Data Management Collaboration Server database in a production environment. - create_pimdevdb.sh script
Use the create_pimdevdb.sh script to create an IBM InfoSphere Master Data Management Collaboration Server database for use in a test or development environment. - create_schema.sh script
Use the create_schema.sh script to create the schema for your database. - create_vhost.sh script
Use the create_vhost.sh to create a virtual host to run a second appsvr service on the same server for vertical clustering in the IBM InfoSphere Master Data Management Collaboration Server environment. - db2_export.sh script
Use the db2_export.sh script, which can be found in the $TOP/src/db/scripts/backup directory, to export the IBM InfoSphere Master Data Management Collaboration Server schema. Running this script generates the SQL scripts required to create tables, indexes and sequences with their current values, and stores them in a tar file in the back up directory. - db2_fast_import.sh script
Use the db2_fast_import.sh script to import the contents of the tar file generated by running the db2_export.sh script into the database for a new IBM InfoSphere Master Data Management Collaboration Server environment. You can use this script to import the schema into the same or a different database under the same schema name or a different schema name. - drop_schema.sh script
Use the drop_schema.sh script to delete the IBM InfoSphere Master Data Management Collaboration Server schema. Before you issue the drop_schema.sh script, ensure that you stop InfoSphere MDM Collaboration Server. - envexpimpXMLValidator.sh script
Use the envexpimpXMLValidator.sh script to validate all the XML files contained in the environment files generated by the exportCompanyAsZip.sh script. The XML files are validated against the .xsd files of IBM InfoSphere Master Data Management Collaboration Server. - exportCompanyAsZip.sh script
Use the exportCompanyAsZip.sh script to export your company data model from the command line. You can import this data model in an IBM InfoSphere Master Data Management Collaboration Server target instance. - get_ccd_version.sh script
Use the get_ccd_version.sh script to get the version of the IBM InfoSphere Master Data Management Collaboration Server ccd. - get_params.sh script
Use the get_params.sh script to parse the argument list into named variables in the IBM InfoSphere Master Data Management Collaboration Server environment. - get_service_status.sh script
Use the get_service_status.sh script to get the status of individual IBM InfoSphere Master Data Management Collaboration Server services. - importCompanyFromZip.sh script
Use the importCompanyFromZip.sh script to import your IBM InfoSphere Master Data Management Collaboration Server data model from the command line. The data model is stored in a .zip file created by running the exportCompanyAsZip.sh script. - importRelationshipsAsCompany.sh script
Use the importRelationshipsAsCompany.sh script to import your IBM InfoSphere Master Data Management Collaboration Server data model. - indexRegenerator.sh script
Use the indexRegenerator.sh script to regenerate indexes for entities such as items and categories. If you change the index option for an attribute of the spec that is associated with the item or category after creating some other items or categories, then you must run this script to regenerate indexes. Regenerating indexes ensures that you get correct search results based on the changed attribute. You can use only one run_options combination at a time. However, you can use zero or more tuning_options together. - install_war.sh script
Use the install_war.sh script to replace the existing WebSphere® Application Server components when you deploy a second appsvr service in the IBM InfoSphere Master Data Management Collaboration Server environment. - load.sh script
Use the load.sh script to load the contents of a folder into a company. The format of the content should be the same as the format of the content that is created by extracting the file that is created by running the exportCompanyAsZip.sh script. - pimprof.sh script
Use the pimprof.sh script to start, and stop services, and to capture memory snapshots in the IBM InfoSphere Master Data Management Collaboration Server environment. - pimSupport.sh script
Use the pimSupport.sh script for collecting diagnostic information if you encounter any issues with IBM InfoSphere Master Data Management Collaboration Server and need to share data with the technical support team. - rename_cmp.sh script
Use the rename_cmp.sh script to rename a company code and company name in the IBM InfoSphere Master Data Management Collaboration Server environment. All users must log in with the new company code after this script is run. - rmi_status.sh script
IBM InfoSphere Master Data Management Collaboration Server runs using six key services, each of which run as a separate process on their own Java virtual machine, or JVM. The rmi_status.sh can be run to print a list of all the IBM InfoSphere Master Data Management Collaboration Server services which are currently running. In a non-clustered environment, there are six services. For a clustered environment, one service can have multiple processes and multiple entries. - run_job_template.sh script
Use the run_job_template.sh script to create scripts to integrate with an extender scheduler, such as Tivoli® Workload Scheduler, in the IBM InfoSphere Master Data Management Collaboration Server environment. The run_job_template.sh script is in the $TOP/bin directory. Ensure that you modify the values in this script and then issue the command to run the job. - start_local.sh script
Use the start_local.sh script to start IBM InfoSphere Master Data Management Collaboration Server and all services. - start_local_rmlogs.sh script
Use the start_local_rmlogs.sh script to start IBM InfoSphere Master Data Management Collaboration Server services and remove local logs. The start_local_rmlogs.sh script does the same job as the start_local.sh without the addition of removing logs. - start_rmi_and_appsvr.sh script
Use the start_rmi_and_appsvr.sh script to start IBM InfoSphere Master Data Management Collaboration Server RMI registry and appserver service. - stop_local.sh script
Use the stop_local.sh script to stop IBM InfoSphere Master Data Management Collaboration Server services from the command line. - svc_control.sh script
Use the svc_control.sh script to control individual IBM InfoSphere Master Data Management Collaboration Server services. - test_db.sh script
Use the test_db.sh script to verify the connectivity between IBM InfoSphere Master Data Management Collaboration Server and databases, and to check for JDBC and native client connections. - updateRtClasspath.sh script
There are two ways to update the classpath parameter in the env_settings.ini file.
Last updated: 21 Jul 2017