Moving the LifeCycle Manager Server

If you need to move the LCM server to a new server (because of upgrades or to increase performance etc.) use this procedure to ensure that correct information is copied from the source.

Note: Please note that moving the LCM Server is a fairly complex Administrator task, and it should be done with consideration and care.
  1. Install the LCM Server on the target server.
    Note: It is important to have the same LCM Server version installed on both source and target servers. If you plan to upgrade to a new version of LifeCycle Manager Server SW, install this on the target server and upgrade the source server before performing the steps below.
    Note: It is important to install the new server in the same path as the source.

    There is no need to supply information about LDAP configuration during the install, except if a local AD LDS instance is used for LDAP.

  2. Stop the LCM server on the target server.
  3. Copy the LDAP configuration section from lcm.properties on the source server to lcm.properties on the target server.

    (lcm.properties is found in ...\Infor\LifeCycle Manager\LCM-Server)

    Note: The path above is the default path. The path may differ depending on where your LifeCycle Manager Server was installed on the source server.
  4. Copy the hibernate.connection.password property value on the source server to lcm.properties on the target server.
  5. On the target server, start the LCM Server service.
  6. Start the LifeCycle Manager client and log-on to the target LCM Server. When verified, close the LCM client.
  7. On the target server, stop the LCM Server service.
  8. On the source server, stop the LCM Server service.
  9. Copy the following directories from the source server to the target server:
    • ...\Infor\LifeCycle Manager\LCM-Server\log
    • ...\Infor\LifeCycle Manager\LCM-Server\lcmdb
    • ...\Infor\LifeCycle Manager\LCM-Server\client
    • ...\Infor\LifeCycle Manager\LCM-Server\products
    • ...\Infor\LifeCycle Manager\LCM-Server\rss
    • ...\Infor\LifeCycle Manager\LCM-Server\war
    • ...\Infor\LifeCycle Manager\LCM-Server\grid (will only exist if a Grid is installed)
    • ...\Infor\LifeCycle Manager\LCM-Server\http
    • ...\Infor\LifeCycle Manager\LCM-Server\synch
    Note: The paths above are the default paths. The paths may differ depending on where your LifeCycle Manager Server was installed on the source server.
  10. On the target server, start the LCM Server service.
  11. Start LifeCycle Manager client and log-on to LCM server on the target server. Verify that all LCM Services configured on your LCM domain can now be seen in the client. The LCM Services will still be in status 'Stopped'. Close the LCM Client.
  12. Stop all LifeCycle Manager services by performing one of the following actions depending on the applicable platform:
    Platform Action
    Windows Stop the Windows Service LCM-Service:service_name.
    IBM i Stop the subsystem.
    AIX Run the command stoplcm as user lcm.
  13. Run the script updateCertificate located in the script folder of the LifeCycle Manager Service installation path. This script updates the keystore on the LCM Services. Running this script will prompt you for the new LCM Server IP address.
  14. Restart the LifeCycle Manager Service by performing one of the following actions depending on the applicable platform:
    Platform Action
    Windows Start the Windows Service LCM-Service:service_name.
    IBM i Start the service by using the script restartService.qsh.
    AIX Run the command startlcm as user lcm.
  15. Start a LCM Client and log-on to your new LCM Server. It should now be possible to administer your products again.
    Note: The source server can no longer be used to manage your products. There can be only one LifeCycle Manager master server.