Migrating the SSM for an application

A cluster administrator, or the consumer administrator for the consumer associated with the IBM® Spectrum Symphony application can migrate the SSM for an application in two ways: from one host to another, so that the SSM starts on the other host; or to the same host, so that the SSM starts on the local host. To migrate the SSM, run the soammigrate command.

• To migrate the SSM for the application, from one management host to another, so that the SSM starts on the other host, run:

  soammigrate app start application_name [-f] [-s simReconnectionTimeout] [-r resReq] [-u user_name] [-p password]

  For example, to migrate the SSM for application ABC, so that the SSM starts on the other host, run:

  soammigrate app start ABC

  To migrate the SSM for application ABC, and specify that SSM should release all resources in it before starting on the other host, specify the -s option with a value of 0, as such:

  soammigrate app start ABC -s 0

  For detailed about this command, see soammigrate.

  Note: Depending on your application profile configuration, running the soammigrate command for migrating SSM from one management host to another, affects running workload in two ways:

  If the SOAM version in your application profile is configured to the same version of IBM Spectrum Symphony as you have installed (for example, your application profile is configured for IBM Spectrum Symphony 7.1.2, and you have IBM Spectrum Symphony 7.1.2 installed), then any running workload is never interrupted and remains running. The service instance manager sends the results to the new SSM after migration. The SSM that is being migrated can keep its existing allocated resources throughout the migration process; resources are still deserved and still required.

  If the SOAM version in your application profile is configured to with a value of latest version, then the SSM starts using the latest version of IBM Spectrum Symphony that you have installed. Running workload will be interrupted; however both recoverable and unrecoverable sessions can be used with the new SSM after migration, and all workload is re-dispatched after migration.

• To migrate the SSM for the application so that the SSM starts on the local host, you can use the soammigrate command with the -r local option, or use the cluster management console by following the steps in Updating your IBM Spectrum Symphony application to use the new version.