Perform a Custom Migration
1. On the 9.9 machine, open a command window or shell and go to the 9.9_Software AG_directory\IntegrationServer\bin\migrate directory.
2. Run the command migrate.{bat|sh}.
3. The utility asks for the full path to one of the following:
The old
Integration Server installation (for example, C:\
old_Software AG_directory\IntegrationServer or /opt/
old_Software AG_directory/IntegrationServer).
4. 9.6, 9.7, or 9.8 upgrade: If the old Integration Server installation has more than one server instance, the utility lists the instances and asks which instance to migrate.
The utility then asks for the name of a 9.9 server instance to be the target of the migration. If you want the utility to migrate to the 9.9 server instance that was created during installation, enter the name of that instance. If you want the utility to create a 9.9 instance and migrate to the new instance, enter a name that does not exist in the 9.9 installation.
If Wm packages exist on the old server instance, and the same Wm packages exist in the 9.9 package repository, the utility will install those Wm packages from the 9.9 package repository on the 9.9 server instance. If language packs exist in the package repository, the utility will install those language packs on the 9.9 server instance.
Note: | The migration utility can only install the ActiveTransfer Support package and the Application Platform Support package on the server instance that was created during installation. |
5. The utility asks whether to import migration settings. Enter N.
6. The utility asks whether to migrate custom packages. If you choose to migrate all custom packages, the utility migrates the following:
Custom packages.
The WmChemPayloads, WmPapinetPayloads, WmRNPips, WmFINMessages, and WmFIXMessages packages, if present. These packages contains IS documents for the corresponding eStandards Modules and the schemas for those documents.
If you choose to migrate selected packages only, the utility lists each of the packages above and asks whether to migrate it.
7. The utility asks whether to migrate Integration Server configuration files. If you choose to migrate selected configuration files only, the utility lists each configuration file and asks whether to migrate it. There are about 50 configuration files.
If you are using a cloned database with Integration Server 9.9, you must respond N to all prompts that list the Integration Server config\jdbc files. If you are using the live database with Integration Server 9.9, respond Y to these prompts.
If the Integration Server hosts Trading Networks, and you are using a cloned database with Trading Networks 9.9, you must respond N to all prompts that list the Trading Networks JDBC files TN.xml and pool_alias_name_in_TN.xml. If you are using the live database with Trading Networks 9.9, respond Y to these prompts.
8. The utility asks you to specify the behavior to use for new properties that have been added to Integration Server 9.9 and existing properties that have new defaults in Integration Server 9.9. If you choose to specify the behavior to use, the utility lists each property and asks whether to use new behavior or preserve existing behavior. You can also read about these properties in the Integration Server readme.
9. If the Integration Server hosts Wm packages, the utility asks whether to migrate the data (that is, configuration files) for those packages.
10. 9.5, 9.6, 9.7, or 9.8 upgrade: The utility asks whether to migrate custom jar files. If you choose to migrate selected custom jar files only, the utility lists each custom jar file and asks whether to migrate it.
11. If the Integration Server hosts Trading Networks, the utility asks whether to migrate Trading Networks information. If you enter Y, the utility asks the following:
a. Whether to migrate the Trading Networks configuration file. If you enter Y, the utility copies the configuration properties from the old Trading Networks installation directory, adds them to the new configuration properties in Trading Networks 9.9, and replaces the properties.cnf file in the 9.9_Software AG_directory\IntegrationServer\instances\instance_name\packages\WmTN\config directory.
Note: | If you have a cluster of Trading Networks instances, you must migrate the configuration file for each instance. |
b. Whether to migrate Trading Networks data. This migration maps the data in the Trading Networks database to the new table structure.
Note: | If you have a cluster of Trading Networks instances, the data is shared by all instances, so only migrate the data for one instance. |
c. Whether to migrate Trading Networks dashboard data. If you enter Y, the utility purges records from the dashboard tables and populates records from BIZDOC tables into dashboard tables. The dashboard tables include TransactionSummaryData, CustomAttributeVolumeValue, TransactionSuccessFailedData, SuccessFailedChartDocIdMap, and TransactionLateFAData.
12. The utility asks whether to export your settings. If you want to perform other migrations by importing the settings from this session, enter Y. If not, enter N.
