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 to Migrate Script Name and Location Description Usage
Database Migration $MQ_HOME/bin/migration/DatabaseMigration.bat/sh Use this utility to migrate the database from the previous version to the new version. 
DatabaseMigration -path DBProviderName DatabaseName Username Password Server Name

Where path can be: -83_92, -90_92, or -91_92 
Where DBProviderName can be: ORACLE or SQLSERVER

Configuration Migration
  • For MDM: $MQ_HOME/bin/migration/ConfigValuesMergeUtil.sh/bat
  • For GDSN: $MQ_HOME/plugins/gdsn/version_number/bin/gdsnxmlPropMergeUtil.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: -83_92, -90_92, or -91_92 

  • <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.

      (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 ActiveSpaces cache. 
<CopyConfigDirFiles.bat> -<path>
Where path can be: -83_92, -90_92, or -91_92 
<CacheConfigMergeUtil> -<path> -prop <version CacheConfig file> -xmlin <Source CacheConfig XML file> -xmlout <Output CacheConfig XML file>"
Where,
  • <path> can be: -83_92, -90_92, or -91_92
  • <versionCacheConfig file> is the previous version of CacheConfig.xml with an absolute path
  • <Source CacheConfig XMLfile> is the new version of CacheConfig.xml
  • <Output CacheConfig XML file> is the absolute path to an user CacheConfig.xml file.
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.

Prerequisites:

  • 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.
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: -83_92, -90_92, or -91_92
Common Directory Migration $MQ_HOME/bin/migration/CopyCommonDirFiles.bat/sh This script replaces standard files from 8.x versions to 9.1. 
CopyCommonDirFiles -<path>
Where <path> can be: -83_92, -90_92, or -91_92
  • 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 9.1 version. You must use this $MQ_COMMON_DIR

Golden Bundle Migration [Optional] $MQ_HOME/db/databasename/migration/Migrate83_90/fixRelationshipGoldenBundle.sql Using this script, you can use the golden bundle feature for the existing records. To enable the golden bundle feature, set the value of the Record UI golden view configuration property to true in Configurator. The property enables link to view golden version of records and bundle. By default, the value is set to false.

The script ensures that the relationship between the golden copies is established and also the relationship between the latest version and the golden copy version.

Copy the fixRelationshipGoldenBundle.sql script to any database tool and execute as a script. Or

If the database client is installed, navigate to the $MQ_HOME/db/database/migration/Migrate901_91 and connect to the database, and then run the fixRelationshipGoldenBundle.sql script using the appropriate command based on the database. For example: Oracle@fixRelationshipGoldenBundle.sql

Synchronization Migration [Optional] $MQ_HOME/db/databasename/migration/Migrate83_90/alterForSelfOutputMaps.sql

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

Run the script for the following:
  • to support out-of-the-box self relationships between output maps for the existing metadata
  • to add self related output maps to the repository that contains self active relationships because the relationships mentioned in the synchronization workflow are no more supported.
Execute the script on the latest version database because by default the script works for all enterprises and repositories. You can execute the script on a particular enterprise by uncommenting the following condition in the WHERE clause and providing an organization ID:
Remove -- to uncomment the condition and replace organization ID by removing #. 
WHERE c.type = 'OUTPUTCATALOG' -- AND c.sourceorganizationid = #
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.
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.