Migration properties
These properties can be used only to migrate from a version 3 Transaction Server. Do not use them after your migration from version 3 to Red Hat® OpenShift® is finished.
The following table shows the migration properties. These properties are used to configure the newly
installed Transaction Server during the migration period. During this time, the new Transaction Server uses the older (version 3) Transaction Server as a backup when it is locating items. These variables configure
that operation.
| Property | Default value | Range | Description |
|---|---|---|---|
| migrationServer | none | N/A | The URL of the version 3 Transaction Server that serves as a backup item repository to the newly installed Transaction Server. If this property is left unspecified, migration backup is not enabled. |
| migrationPort | 2002 | N/A | The API port that is used by the version 3 Transaction Server. If you are planning to run both installations of Transaction Server on the same machine, consider switching the version 3 Transaction Server API port to a different port number. |
| migrationRmiPort | 1099 | N/A | The RMI port where the version 3 Transaction Server publishes its RMI interfaces. Usually this port is the same for both the newly installed and the version 3 Transaction Server installations. To distinguish between two servers that are running on the same machine, use the migrationClientInterfaceToken property. |
| migrationRmiClasspath | none | N/A | This property is a list of JAR files that are needed to allow the Transaction Server to communicate with the version 3
Transaction Server during the migration. The JAR file names in the list must be separated
by or colons. If this
property is specified, it must contain the txsvrcli.jar,
util.jar, txaccessors.jar, and
base_java_utilities.jar files that were copied from the
lib subdirectory of the version 3
Transaction Server. If this property is left unspecified, a version 3 Transaction Server is not used as a backup during migration. |
| migrationClientInterfaceToken | ClientRmiGateway | N/A | The RMI token that uniquely identifies the version 3 Transaction Server interfaces as published to the RMI registry. If two servers are running on the same machine, they need to have unique client interface tokens so their interfaces can coexist in the same RMI registry. |