IBM Support

How to migrate ELM with Traditional WebSphere to WebSphere Liberty

How To


Summary

Starting in version 6.0.1, IBM Collaborative Lifecycle Management (CLM) is shipped with an embedded IBM® WebSphere® Liberty server. CLM is now known as IBM Engineering Lifecycle Management (ELM). ELM version 7.0 - 7.0.2 supports two application servers; WebSphere Application Server traditional and WebSphere Liberty.

The support of WebSphere Application Server is removed in ELM v.7.0.3. Due to this change, you must migrate ELM on WebSphere Application Server to WebSphere Liberty.

Objective

This technote provides high-level instructions on how to migrate ELM on WebSphere Application Server to WebSphere Liberty Profile.

Environment

  • IBM Collaborative Lifecycle Management (CLM) 6.x or IBM Engineering Lifecycle Management (ELM) 7.x
  • WebSphere Liberty

Steps

To migrate the applications hosted in WebSphere Application Server to WebSphere Liberty Profile, perform the following steps. The steps do not include component-specific WebSphere to Liberty Migration steps because there are parts of WebSphere Application Server configurations that do not exist or are not needed in WebSphere Liberty Profile.
You need to stop WebSphere Application Server before starting the Liberty instance.
Installation
  • Download and install a new instance of ELM in parallel with your existing installation. Ensure to select the option to install WebSphere Liberty Profile. This installation must be the same version as your current application version. The new installation deploys WebSphere Liberty Profile with most of the required settings pre-configured to run ELM applications. It is recommended that each application run on its own server or at least its own Liberty Profile (for process isolation). Each profile has its own JVM resources. For detailed installation instruction, refer to the Interactive Installation Guide.
ELM Configuration Files Migration
  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 (Liberty), replace the existing files.
Liberty Configuration files update
  • Although the embedded Liberty Profile comes with most of the required settings to run the ELM applications, there are the following settings that need to be configured manually:
User Registry
If your ELM WebSphere Application Server installation is configured to use LDAP as the user registry, perform the following steps:
  1. Start the Liberty server:
    1. Linux:
      Change directory to New_ELM_install/server
      Run the ./server.startup script
    2. Windows:
      Change directory to New_ELM_install/server
      Run the server.startup.bat script
       
  2. Follow the steps to configure LDAP connection in WebSphere Liberty.
    If your ELM WebSphere Application Server installation is configured to use the default internal user registry, you need to migrate the user records over to Liberty. Refer to 'Configuring a basic user registry for Liberty' for further details.
Certificate
  • The security certificate bundled with ELM applications is self-signed to localhost. If your ELM 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 WebSphere Liberty Profile.
  • The keystore file is located in New_ELM_install\server\liberty\servers\clm\resource
  • If you have IHS and use self-signed certificates for your ELM applications, perform the following steps to extract the certificate from the ELM Liberty installation and import it into IBM HTTP Server (IHS).  The example shown assumes that the host name, domain name, and port number for ELM WebSphere Liberty Profile installation is myelm.com:9443.
     
    Linux:
    1. From the server where ELM with Liberty is installed, execute:  
      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 certificate by using ikeyman:
      1. Select "Signer Certificates" from the drop-down
      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)

    Windows:
    1. Open a browser session from a machine where ELM on Liberty is being accessed
    2. Navigate to the Certificate Manager session, click Servers, select myelm.com:9443, click Export to extract the certificate into a certificate file (for example elm.crt)
    3. Open ikeyman within IBM HTTP Server directory (C:\IBM\HTTPServer\bin\ikeyman)
    4. Open the keystore referenced by your plugin-cfg.xml file (and enter the keystore password)
    5. Import certificate by using ikeyman:
      1. Select "Signer Certificates" from the drop-down
      2. Click "Add"
      3. Select "All Files"
      4. Select the newly created .crt file and click "Open"
    6. 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-----
For instructions on how to configure CLM/ELM on Liberty to run as Windows service, see CLM 6.x instructions and ELM 7.x instructions.
For instructions on how to configure Single Sign On (SSO) across WebSphere Liberty Profiles, see here.
For instructions on how to configure ELM on Liberty with TLSv1.2, refer to the "WebSphere® Liberty Profile" session in this technote.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYMRC","label":"Rational Collaborative Lifecycle Management"},"ARM Category":[{"code":"a8m50000000L3DPAA0","label":"ELM"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.6;and future releases"}]

Product Synonym

ELM

Document Information

Modified date:
07 June 2024

UID

ibm16513066

Page Feedback