Manually Migrating Individual Components

Individual scripts for each component migration are also available in the $MQ_HOME/bin/migration folder. If you want to migrate an individual component, you can run each script separately.

Component Usage

Database Migration

$MQ_HOME/bin/migration/DatabaseMi-gration.bat/sh

Note: If you migrate database by using the script, then you must install the database client for the database that you are migrating.

Use this utility to migrate the database from the previous version to the new version.

DatabaseMigration -path DBProviderName DatabaseName UserName Password ServerName

Where

  • path can be: -93_931, -92_931, -91_931, and -90_931

  • DBProviderName can be: ORACLE or SQLSERVER,

  • ServerName is database-instance-name or database-ip. If you installed the Oracle database, then ServerName is not required.

For PostgreSQL: DatabaseMigration -path DBProviderName PGHome HostName Port DatabaseNameUserName Password

Where DBProviderName is PostgreSQL.

Configuration Migration

For MDM: $MQ_HOME/bin/migration/ConfigValuesMergeUtil.sh/bat

Use this utility to migrate ConfigValues.xml from the previous version to the new version.

<ConfigValuesMergeUtil> -path -prop <version XML configuration file> -xmlin <Source configuration XML file> -xmlout <Output configuration XML file>

Where,

  • path can be: -93_931, -92_931, -91_931, and -90_931
  • <version XML configuration file> is the previous version of ConfigValues.xml with an absolute path
  • <Source configuration XML file> is the new version of ConfigValues.xml
  • <Output configuration XML file> is the absolute path to an user ConfigValues.xml file. For example, $MQ_HOME/config/Migration_Config_Values.xml.

    After migration, back up the new ConfigValues.xml file, and then rename the Migration_Config_Values.xml file to ConfigValues.xml to use it.

  • Copy the hibernate3.jar file from new $MQ_HOME\lib\external\hibernate to new $MQ_HOME\lib\external of the latest version.
For GDSN: $MQ_HOME/plugins/gdsn/version_number/bin/gdsnxmlPropMergeUtil.bat (when merging MDM and GDSN Configuration)

<gdsnxmlPropMergeUtil> -GDSN -prop <9.1 MDM XML configuration file> -xmlin < 9.1 GDSN configuration XML file> -xmlout <Output configuration XML file>

Configuration Directory Migration

  • Indexer Configuration: $MQ_HOME/bin/migration/CopyConfigDirFiles.bat/sh.
  • Cache Configuration: $MQ_HOME/bin/migration/CacheConfigMergeUtil.bat/sh.
  • The Indexer configuration refers to the IndexerConfig.xml file. This is an optional file, migrate if needed.

    The utility copies specific files from the old Config directory to the new Config directory based on migrateConfigFolderFiles.prop configuration.

  • The utility upgrades the CacheConfig.xml file in the Config directory. The CacheConfig.xml file includes setup and configuration of Apache Ignite cache.
  • <CopyConfigDirFiles.bat> -<path>: It prompts for the previous version $MQ_HOME.

Where path can be: -93_931, -92_931, -91_931, and -90_931

<CacheConfigMergeUtil> -<path> -prop <version CacheConfig file> -xmlin <Source CacheConfig XML file> -xmlout <Output CacheConfig XML file>" Where,

  • <path> can be: -93_931, -92_931, -91_931, and -90_931
  • <versionCacheConfig XML file> is the previous version of CacheConfig.xml with an absolute path
  • <Source CacheConfig XML file> is the new version of CacheConfig.xml
  • <Output CacheConfig XML file> is the absolute path to an user CacheConfig.xml file.

For example, $MQ_HOME/config/Migration_Cache_Config.xml.

After migration, back up the new CacheConfig.xml file, and then rename the Migration_Cache_Config.xml file to CacheConfig.xml to use it.

FileWatcher Migration

$MQ_HOME/bin/migration/fileWatcherMergeUtil.bat/sh

This utility allows you to migrate the FileWatcher.xml file from the previous version to the new version.

fileWatcherMergeUtil -<path> -prop <old FileWatcher file> -xmlin <new FileWatcher file> -xmlout <Output FileWatcher file>

Where <path> can be: -93_931, -92_931, -91_931, and -90_931

<old FileWatcher file> is the previous version of FileWatcher.xml with an absolute path.
<new FileWatcher file> is the new version of FileWatcher.xml .
<Output FileWatcher file> is the absolute path to the FileWatcher.xml file of a user. For example, $MQ_HOME/config/Migration_File_Watcher.xml.

After migration, back up the new FileWatcher.xml file, and then rename the Migration_File_Watcher.xml file to FileWatcher.xml and use it.

Common Directory Migration

$MQ_HOME/bin/migration/CopyCommonDirFiles.bat/sh

 This script replaces standard files from 9.x versions to 9.3.1.

CopyCommonDirFiles -<path>

Where <path> can be: -93_931, -92_931, -91_931, and -90_931
  • It prompts for new $MQ_COMMON_DIR (Current version $MQ_HOME/common)
  • It prompts for previous $MQ_COMMON_DIR (Previous version $MQ_HOME/common)

    Note: Previous $MQ_COMMON_DIR is updated during migration to a new version. You must use this $MQ_COMMON_DIR

Work Item Migration

$MQ_HOME/db/databasename/migration/Migrate901_91/ createAndMigrateWIAttributes.sql

Run the createAndMigrateWIAttributes.sql script only if you are migrating from the 9.0.x version or previous version.

Run the script to migrate the values of work item attributes from the WorkItemDetail table to the WorkItemAttribute table.

When the value of an attribute is changed through work item modification, the value in the WorkItemAttribute table is updated. The table is used for sorting of work items based on configured attributes.

Execute the script on a particular enterprise.

Repository Index Migration for PostgreSQL

(Required only if you are migrating from 91 to 93)

Repository table contains unique index, which includes the PRODUCTIDEXT column. The PRODUCTIDEXT column can have NULL values.

PostgreSQL allows duplicate nulls in the unique columns. Therefore, you need to update the unique indexes on the repository table.

For every repository table, remove index Repository_Table_Name_IDX99 and create two new indexes based on the following new indexes:

Copy
CREATE Unique index MCT_34522_IDX99_1 on MCT_34522(CPRODUCTID, CPRODUCTIDEXT, CMODVERSION) WHERE CPRODUCTIDEXT IS NOT NULL;

Copy
CREATE Unique index MCT_34522_IDX99_2 on MCT_34522(CPRODUCTID, CMODVERSION) WHERE CPRODUCTIDEXT IS NULL;

Rules Migration

$MQ_HOME/bin/migration/MigrateRules.bat./sh

This utility adds new rules and new default template to the existing organization, and it adds the new process selection rule. You can also migrate custom processes, forms, maps, and rulebases.

  • Ensure that tibjms.jar is available at $MQ_HOME/lib/external

  • Ensure that the TIBCO MDM server is up before running this utility. Also ensure that the OLD_MQ_HOME variable is set.

  • Ensure that you have provided organization ID in %MQ_HOME%\bin\migration\orglist.txt and orglist-processSelection.txt.
  • The organization IDs are procured from the ID column of the ORGANIZATION table.

The following parameters are mandatory:

  • -addNewProcessSelectionRules: Adds new process selection rule to the existing organization as defined in orglist-processSelection.txt.
  • -addDefaultTemplate: Adds new default template existing rule in organization as defined in orglist-processSelection.txt.
  • -addNewRules: Adds new rules to the existing organization as defined in org.list.
  • -migrateRulesActions: Migrates rules.
Caution: Ensure that you run all utilities from the directories in which they are present (such as $MQ_HOME/bin/migration); do not run it from remote locations by providing the absolute paths.

For example, do not run a script from a remote directory by providing $MQ_HOME/bin/migration/scriptname.sh. Instead navigate to the $MQ_HOME/bin/migration directory and then run scriptname.sh.