Migratable Target: Configuration: Migration
Configuration Options Related Tasks Related Topics
This page allows you to configure a migratable target, including specifying a preferred host server in the cluster and selecting candidate servers to use as a backup for services on this migratable target. You can also optionally provide the appropriate pre-migration and post-migration scripts to move a persistent store's data across migrated servers.
Name Description Name
The name of this migratable target.
The server member in the cluster that you prefer the migratable target to be active on.
Constrained Candidate Servers
Select server members in the cluster to use as a backup for services on this migratable target.
Pre-Migration Script Path
Specifies the path to the pre-migration script to run before a migratable target is actually activated. The script must be in the
Before the migratable target is activated, if there is a script specified, and Node Manager is available, then the script will run. Specifying a script without an available Node Manager will result in an error upon migration.
If the script fails or cannot be found, migration will not proceed on the current server, and will be tried on the next suitable server. This could be the next server in the candidate server list, or in the cluster, if there is no candidate server list.
Post-Migration Script Path
Specifies the path to the post-migration script to run after a migratable target is fully deactivated. The script must be in the
After the migratable target is deactivated, if there is a script specified, and Node Manager is available, then the sript will run. Specfiying a script without an available Node Manager will result in an error upon migration.
Allow Post-Migration Script To Run On a Different Machine
Specifies whether or not the post-deactivation script is allowed to run on a different machine.
Normally, when automigration occurs, the post-deactivation script will be run on the service's current location, and the pre-activation script on the service's new location. If the current location is unreachable for some reason, this value will be checked to see if it is safe to run it on the service's new machine.
This is useful if the post-deactivation script controls access to a networked resource and does not need any data from the current machine.
- Configure server migration in a cluster
- Configure JMS-related services migration
- Configure the JTA Transaction Recovery Service for migration