Migrating Engineering Lifecycle Management from WebSphere Application Server to WebSphere Liberty server

Engineering Lifecycle Management version 7.0.0 - 7.0.2 supports two application servers; WebSphere® Application Server and WebSphere Liberty server. The support of WebSphere Application Server is no longer available in Engineering Lifecycle Management starting with version 7.0.3. Due to this change, you must migrate Engineering Lifecycle Management on WebSphere Application Server to WebSphere Liberty server. You must migrate from WebSphere Application Server to WebSphere Liberty server before you upgrade to Engineering Lifecycle Management version 7.0.3

Download and install a new instance of Engineering Lifecycle Management in parallel with your existing installation. Ensure to select the option to install WebSphere Liberty server Profile. This installation must be the same version as your current application version. The new installation deploys WebSphere Liberty server Profile with most of the required settings preconfigured to run Engineering Lifecycle Management applications. It is recommended that each application run on its own server or at least its own WebSphere Liberty server Profile (for process isolation). Each profile has its own JVM resources.

Stop the WebSphere Application Server before starting the WebSphere Liberty server instance.

The task does not include component-specific WebSphere Application Server to WebSphere Liberty server migration steps because there are parts of WebSphere Application Server configurations that do not exist or are not needed in WebSphere Liberty server.

Migrating Engineering Lifecycle Management configuration files

  1. Stop the WebSphere Application Server.

    If you have your server setup as a service, ensure to disable automatic startup. Once the migration from WebSphere Application Server to Liberty completes, you might want to remove the application server service. See instruction in step 4 from here.

  2. Back up your databases.
  3. Copy the entire content of the OLD_ELM_install\server\conf\app directory (used by WebSphere Application Server) to the New_ELM_install\server\conf\app directory (WebSphere Liberty server), replace the existing files.

Liberty Configuration files update

Although the embedded Liberty Profile comes with most of the required settings to run the Engineering Lifecycle Management applications, there are the following settings that need to be configured manually:

User Registry

  1. If your Engineering Lifecycle Management WebSphere Application Server installation is configured to use LDAP as the user registry, perform the following steps:
    1. Start the Liberty server:
      • Change the directory to New_ELM_install/server

        Run the ./server.startup script

      • Change the directory to New_ELM_install/server

        Run the server.startup.bat script

    2. Follow the steps to configure LDAP connection in IBM® WebSphere Liberty. If the Engineering Lifecycle Management WebSphere Application Server installation is configured to use the default internal user registry, you must migrate the user records to WebSphere Liberty server. See, 'Configuring a basic user registry for Liberty'.
    Certificate
    • The security certificate that is bundled with Engineering Lifecycle Management applications is self-signed to localhost. If your Engineering Lifecycle Management installation on WebSphere Application Server uses a certificate from a well-known or corporate-trusted certificate authority, you must import these certificates into the keystore that is used by the IBM WebSphere Liberty Profile.
    • The keystore file is located in New_ELM_install\server\liberty\servers\clm\resource
      • The file name for CLM 6.x is ibm-team-ssl.keystore
      • The file name for Engineering Lifecycle Management 7.x is ibm-team-ssl.p12
      • For instructions on how to import certificates into the WebSphere Liberty server Profile keystore, see Receive Certificate and Add it to Keystore
    • If you have IHS and use self-signed certificates for your Engineering Lifecycle Management applications, perform the following steps to extract the certificate from the WebSphere Liberty server installation and import it into IBM HTTP Server (IHS). The example that is shown assumes that the hostname, domain name, and port number for WebSphere Liberty server Profile installation is myelm.com:9443.
    1. Run the following command on the WebSphere Liberty server server where Engineering Lifecycle Management is installed:
      openssl s_client -connect myelm.com:9443
    2. From the output, copy the certificate only (see the sample certificate at the end of this document). Be sure not to include spaces or any other text.
    3. Create a certificate file (for example elm.crt) by pasting the copied text in a text editor and saving the file.
    4. Open iKeyman from IBM HTTP Server directory (/opt/IBM/HTTPServer/bin/ikeyman).
    5. Open the keystore referenced by your plugin-cfg.xml file (and enter the keystore password).
    6. Import the certificate by using iKeyman.
      1. Select Signer Certificates from the list.
      2. Click Add.
      3. Select All Files.
      4. Select the newly created .CRT file and click Open.
    7. Restart IHS (/opt/IBM/HTTPServer/bin/apachectl stop/start/restart).
    1. Open a browser session from a machine where Engineering Lifecycle Management on the WebSphere Liberty server is being accessed.
    2. Navigate to the Certificate Manager section, click Servers, and then select myelm.com:9443.
    3. Click Export to extract the certificate into a certificate file (for example elm.crt).
    4. Open iKeyman within IBM HTTP Server directory (C:\IBM\HTTPServer\bin\ikeyman).
    5. Open the keystore that is referenced by your plugin-cfg.xml file and enter the keystore password.
    6. Import the certificate by using iKeyman.
      1. Select Signer Certificates from the list.
      2. Click Add.
      3. Select All Files.
      4. Select the newly created .CRT file and click Open.
    7. Restart IHS (C:\IBM\HTTPServer\bin\apachectl stop/start/restart).Sample certificate:
      -----BEGIN CERTIFICATE-----
      MIIDGTCCAgGgAwIBAgIEFInHnjANBgkqhkiG9w0BAQsFADA9MQswCQYDVQQGEwJ1
      czEMMAoGA1UEChMDaWJtMQwwCgYDVQQLEwNjbG0xEjAQBgNVBAMTCWxvY2FsaG9z
      dDAeFw0xNzA1MTMxMDA5MzdaFw0xODA1MTMxMDA5MzdaMD0xCzAJBgNVBAYTAnVz
      MQwwCgYDVQQKEwNpYm0xDDAKBgNVBAsTA2NsbTESMBAGA1UEAxMJbG9jYWxob3N0
      MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAl5hSpIR+gmyX8t8Cei02
      b9GilUqkdfpWZ5kkJaRmJraLKdPlLMPhEEuIfYEb2cKl3livGMVUfZkxgXLNL7rN
      UOemBaDb882R66sAJ1MZOYAQ976QGRY59hnGiXcX2d7KndCqXmtF7qw6BPS6R7nX
      6nog4P7tMjV1XFY6N6aN5OL6URBaPwf+7EDWPIF7vVlSDM6CFOAWHqt8HjyeGMPO
      Rcnmwg21+NhcUwT467mneEWyavgevdNcfRLm9FOjdwRGZnCnqhcjDKkd9yRyjI8h
      QS2IFPRQVWLPVRQJxDBKBU66k7xhv68bpW4sdkVni26UPzoxQrXNVjETGFxWxfaJ
      QQIDAQABoyEwHzAdBgNVHQ4EFgQUdEkGyXMjCHunNJi3aHAxdIzpYn4wDQYJKoZI
      hvcNAQELBQADggEBAI+A7EffStJJC8+wKbulLaesqOED1eml9JY6kqL7ltMI0HEG
      WRGbYNK0htHmQtzOaHM8gAHd5X5RxHZhOhbaTQ+CH2C4b0MJ+gl9hJGIvt28yiW2
      tS4s/Dt1IJ8Cy7/Xz84YJ1VPn4oFy36lJTGgSM+Bg6aItbbx9vNOflDf8C6tyZbg
      ujMxF2o6BBeKCdBM+Aft164l2uFmVBGIgYQv2aWBNTmxirr72mZnLgo8vGUqc/nA
      1T/CJIz8dq6byclfiOjCBkqDr4XlcXtbD6yjdlRqTusiJ17iZvlNPpoYoGGjqS9z
      JhKmsi2mxWzz7a5ZgsdiK6u+1sn/55MWAabz23I=
      -----END CERTIFICATE-----