Upgrading to 7.1.0 SR1 interim fix 4 with side-by-side installation

The patch service that is used by Engineering Lifecycle Management is additive to replace internal components of the Engineering Lifecycle Management applications and it is necessary to reinstall them. The Engineering Lifecycle Management product team uses a Service Release (SR) as an alternative to an interim fix. It includes a refreshed installer. Administrators who are upgrading from an earlier release can use the refreshed installer. If an earlier interim fix version of 7.1.0 is already installed, a side-by-side installation is required.

Before you begin

  • Refer the documentation to ensure on any customization that you made to the start scripts, WebSphere® Liberty server, or configuration files are migrated correctly.
  • Create a test environment to test the migration.
  • Plan the backup and downtime for migration.

About this task

The installation process for Engineering Lifecycle Management 7.1.0 SR1 interim fix 4 is different than the regular interim fix process. Installation is done by using IBM® Installation Manager and existing configuration files are copied to the new Engineering Lifecycle Management installation.

Note: The side-by-side installation does not require any database update or re-indexing.

Engineering Lifecycle Management 7.1.0 SR1 interim fix 4 is a prerequisite for Engineering Lifecycle Management 7.1.0 interim fix 5 and later.

Procedure

Installing and migrating Engineering Lifecycle Management servers

  1. Install Engineering Lifecycle Management 7.1.0 SR1 interim fix 4 applications into a new package group.
    For distributed environment, install the recent version of applications that corresponds to the previously installed Engineering Lifecycle Management applications.
    Note: Ensure that you do not run the setup wizard after you have installed the applications.
  2. Start the Engineering Lifecycle Management applications and then stop them by using the server.shutdown.
  3. Migrate the existing configuration files.
    1. Copy Lifecycle Query Engine configuration files.
      Make sure that the following directories do not exist before you copy the Lifecycle Query Engine configuration files. Navigate to the directory where you just installed the version 7.1.0 SR1 interim fix 4 application. These directories must not exist in a fresh installation. If these directories exist, open a command prompt and enter the following commands to delete the directories:
      For Unix operating systems 
      rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/indexTdb

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/textIndex

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/shapeText

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/shapeTdb

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/historyText

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/historyTdb

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/versionTdb

      If prompted, confirm to complete the command.

      For Windows operating system 
      del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\indexTdb

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\textIndex

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\shapeText

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\shapeTdb

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\historyText

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\historyTdb

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\versionTdb

      If prompted, confirm to complete the command.

    2. Run the following commands to copy the configuration files to the new installation directory:
      For Unix operating systems 
      cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/indexTdb /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/indexTdb

cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/textIndex /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/textIndex

cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/shapeText /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/shapeText

cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/shapeTdb /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/shapeTdb

cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/historyText /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/historyText

cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/historyTdb /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/historyTdb

cp -R /opt/IBM/JazzTeamServer/server/conf/lqe/versionTdb /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/versionTdb

cp /opt/IBM/JazzTeamServer/server/conf/lqe/lqe.properties /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe

cp /opt/IBM/JazzTeamServer/server/conf/lqe/lqe.node.id /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe

cp /opt/IBM/JazzTeamServer/server/conf/lqe/lqe.key /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe

cp /opt/IBM/JazzTeamServer/server/conf/lqe/dbconnection.properties /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe

      If prompted, confirm to complete the command.

      For Windows operating system 
      xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\indexTdb D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\indexTdb

xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\textIndex D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\textIndex

xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\shapeText D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\shapeText

xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\shapeTdb D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\shapeTdb

xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\historyText D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\historyText

xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\historyTdb D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\historyTdb

xcopy /s D:\IBM\JazzTeamServer\server\conf\lqe\versionTdb D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\versionTdb

copy D:\IBM\JazzTeamServer\server\conf\lqe\lqe.properties D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe

copy D:\IBM\JazzTeamServer\server\conf\lqe\lqe.node.id D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe

copy D:\IBM\JazzTeamServer\server\conf\lqe\lqe.key D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe

copy D:\IBM\JazzTeamServer\server\conf\lqe\dbconnection.properties D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe

      If prompted, confirm to complete the command.

    3. Copy the Link Index Provider configuration files.
      Ensure that the following directories do not exist before you copy the Link Index Provider configuration files. Navigate to the directory where you just installed the version 7.1.0 SR1 interim fix 4 application. These directories must not exist in a fresh installation. If these directories exist, open a command prompt and enter the following commands to delete the directories.

      Run the following commands to clear any files:

      For Unix operating systems 
      rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/indexTdb
rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/textIndex
rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/versionTdb

      If prompted, confirm to complete the command.

      For Windows operating system 
      del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\indexTdb
del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\textIndex
del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\versionTdb

      If prompted, confirm to complete the command.

    4. Run the following commands to copy the configuration files to the new installation directory.
      For Unix operating systems 
      cp -R /opt/IBM/JazzTeamServer/server/conf/ldx/indexTdb /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/indexTdb

cp -R /opt/IBM/JazzTeamServer/server/conf/ldx/textIndex /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/textIndex

cp -R /opt/IBM/JazzTeamServer/server/conf/ldx/versionTdb /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/versionTdb

cp /opt/IBM/JazzTeamServer/server/conf/ldx/lqe.properties /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx

cp /opt/IBM/JazzTeamServer/server/conf/ldx/lqe.node.id /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx

cp /opt/IBM/JazzTeamServer/server/conf/ldx/lqe.key /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx

cp /opt/IBM/JazzTeamServer/server/conf/ldx/dbconnection.properties /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx

      If prompted, confirm to complete the command.

      For Windows operating system 
      xcopy /s D:\IBM\JazzTeamServer\server\conf\ldx\indexTdb D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\indexTdb

xcopy /s D:\IBM\JazzTeamServer\server\conf\ldx\textIndex D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\textIndex

xcopy /s D:\IBM\JazzTeamServer\server\conf\ldx\versionTdb D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\versionTdb

copy D:\IBM\JazzTeamServer\server\conf\ldx\lqe.properties D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx

copy D:\IBM\JazzTeamServer\server\conf\ldx\lqe.node.id D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx

copy D:\IBM\JazzTeamServer\server\conf\ldx\lqe.key D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx

copy D:\IBM\JazzTeamServer\server\conf\ldx\dbconnection.properties D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx

      If prompted, confirm to complete the command.

    5. Copy your JFS/text indices from the previous installation directory to the new installation directory.
      For distributed systems, you must copy files from the appropriate server.

      Run the following commands to clear the default indices directory in the new installation.

      For Unix operating systems 
      rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/jts/indices

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/ccm/indices

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/qm/indices

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/rm/indices

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/dcc/indices

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/relm/indices

rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/gc/indices

      If prompted, confirm to complete the command.

      For Windows operating system 
      del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\jts\indices

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\ccm\indices

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\qm\indices

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\rm\indices

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\dcc\indices

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\relm\indices

del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\gc\indices

      If prompted, confirm to complete the command.

    6. Run the following commands to copy the indices from the previous installation to the new installation.
      For Unix operating systems 
      cp -R /opt/IBM/JazzTeamServer/server/conf/jts/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/jts/indices

cp -R /opt/IBM/JazzTeamServer/server/conf/ccm/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/ccm/indices

cp -R /opt/IBM/JazzTeamServer/server/conf/qm/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/qm/indices

cp -R /opt/IBM/JazzTeamServer/server/conf/rm/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/rm/indices

cp -R /opt/IBM/JazzTeamServer/server/conf/dcc/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/dcc/indices

cp -R /opt/IBM/JazzTeamServer/server/conf/relm/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/relm/indices

cp -R /opt/IBM/JazzTeamServer/server/conf/gc/indices /opt/IBM/JazzTeamServer_NewInstall/server/conf/gc/indices

      If prompted, confirm to complete the command.

      For Windows operating system 
      xcopy /s D:\IBM\JazzTeamServer\server\conf\jts\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\jts\indices
xcopy /s D:\IBM\JazzTeamServer\server\conf\ccm\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\ccm\indices
xcopy /s D:\IBM\JazzTeamServer\server\conf\qm\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\qm\indices
xcopy /s D:\IBM\JazzTeamServer\server\conf\rm\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\rm\indices
xcopy /s D:\IBM\JazzTeamServer\server\conf\dcc\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\dcc\indices
xcopy /s D:\IBM\JazzTeamServer\server\conf\relm\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\relm\indices
xcopy /s D:\IBM\JazzTeamServer\server\conf\gc\indices D:\IBM\JazzTeamServer_NewInstall\server\conf\gc\indices

      If prompted, confirm to complete the command.

    7. If you are using Derby DB for any applications, you must copy the files in For Unix operating systems/opt/IBM/JazzTeamServer/server/conf/<context>/derby or For Windows operating systemD:\IBM\JazzTeamServer\server\conf\<context>\derby from the old installation directory to the new installation location.
      For example, to copy Derby DB files for Jazz® Team Server, you must copy the files in For Unix operating systems/opt/IBM/JazzTeamServer/server/conf/jts/derby from the old installation directory to the new installation location. For more information, see Copying derby database to new installation directory.
  4. If you are using Jazz Reporting Service, delete the following directories if they exist in Engineering Lifecycle Management 7.1.0 SR1 interim fix 4.
    For Unix operating systems 
    rm -r /opt/IBM/JazzTeamServer_NewInstall/server/conf/rs/db
    For Windows operating system 
    del /s D:\IBM\JazzTeamServer_NewInstall\server\conf\rs\db
    This is to make sure that the database folders are copied when you run the migration commands in Step 5.
  5. Run the configuration migration commands.
    By default, migration is not allowed when the old and new installs have the same release number. To allow these commands to work, an environment variable must be defined in the command shell.
    Note:
    • For Lifecycle Query Engine and Link Index Provider, you need to start and then shut down the new application server before running these commands to create the new profile instance.
    • If you are running on Windows and start the application server by using Windows Services, you need to update the service to refer to the new installation directory.
    • Set the DEFINE_INIT environment variable in each shell that the repotools command is run in. On a distributed environment, you need to set it on each system to run the migrate command.
    • If you have a custom context root for any application, include applicationContextRoot parameter with the value of the custom context root.
    • If you are upgrading for Standalone Liberty, you must use updateAppServerFiles parameter with the value no for all applications in the following commands.
    For Unix operating systems 
    cd /opt/IBM/JazzTeamServer_NewInstall/server
#
export DEFINE_INIT="-Dcom.ibm.team.repotools.commands.upgrade.enable.sameVersionConfigFileUpgrade=true"
#
repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=/opt/IBM/JazzTeamServer/server/conf 

repotools-gc.sh -migration_gc_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck 

repotools-ccm.sh -migration_ccm_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck 

repotools-relm.sh -migration_relm_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck 

repotools-dcc.sh -migration_dcc_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck 

repotools-qm.sh -migration_qm_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck 

repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=/opt/IBM/JazzTeamServer/server/conf ignoreJTSVersionCheck

# For RS
upgrade/rs/rs_upgrade.sh -oldApplicationHome /opt/IBM/JazzTeamServer/server/conf -ignoreJTSVersionCheck
    For Windows operating system 
    cd D:\IBM\JazzTeamServer_NewInstall\server
#
set DEFINE_INIT=-Dcom.ibm.team.repotools.commands.upgrade.enable.sameVersionConfigFileUpgrade=true
#
repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=D:\IBM\JazzTeamServer\server\conf

repotools-gc.bat -migration_gc_updateConfigurationFiles oldApplicationHome=D:\IBM\JazzTeamServer\server\conf ignoreJTSVersionCheck

repotools-ccm.bat -migration_ccm_updateConfigurationFiles oldApplicationHome=D:\IBM\JazzTeamServer\server\conf ignoreJTSVersionCheck 

repotools-relm.bat -migration_relm_updateConfigurationFiles oldApplicationHome=D:\IBM\JazzTeamServer\server\conf ignoreJTSVersionCheck 

repotools-dcc.bat -migration_dcc_updateConfigurationFiles oldApplicationHome=D:\IBM\JazzTeamServer\server\conf ignoreJTSVersionCheck 

repotools-qm.bat -migration_qm_updateConfigurationFiles oldApplicationHome=D:\IBM\JazzTeamServer\server\conf ignoreJTSVersionCheck 

repotools-rm.bat -migration_rm_updateConfigurationFiles oldApplicationHome=D:\IBM\JazzTeamServer\server\conf ignoreJTSVersionCheck 

# For RS
upgrade\rs\rs_upgrade.bat -oldApplicationHome D:\IBM\JazzTeamServer\server\conf -ignoreJTSVersionCheck
  6. Migrate WebSphere Liberty server configuration files.
    WebSphere Liberty server keystore is not automatically copied. Refer to the server.xml <keystore> node, location attribute for the keystore in use. Considering the default location and default keystore, use the following command:
    For Unix operating systems 
    cp -R /opt/IBM/JazzTeamServer/server/liberty/servers/clm/resources /opt/IBM/JazzTeamServer_NewInstall/server/liberty/servers/clm/
    For Windows operating system 
    xcopy /s /e D:\IBM\JazzTeamServer\server\liberty\servers\clm\resources D:\IBM\JazzTeamServer_NewInstall\server\liberty\servers\clm\resources

    For embedded WebSphere Liberty server deployments, the migration is done in Step 5. Hence, no further action is required.

    For stand-alone WebSphere Liberty server deployments, you must migrate the configuration files manually using the following steps.

    1. In the text editor, open JazzInstallDir/server/liberty/servers/clm/server.xml.
    2. Update the value in the <feature>jsp-2.2</feature> tag to 2.3 and <feature>servlet-3.0</feature> to 4.0.
      Below is the sample snippet with the updated values.
      <featureManager>
        <feature>monitor-1.0</feature>
        <feature>jsp-2.3</feature>
        <feature>servlet-4.0</feature>
        <feature>ssl-1.0</feature>
        <feature>appSecurity-2.0</feature>
        <feature>adminCenter-1.0</feature>
    </featureManager>
    3. Update the value for protocol version to 1.1.
      Below is the sample snippet with the updated values.
      <httpEndpoint id="defaultHttpEndpoint"
            host="*"
            httpPort="9080"
            httpsPort="9443"
            protocolVersion="http/1.1">
        <samesite none="JAZZ_AUTH_TOKEN,JSESSIONID,JazzFormAuth,LtpaToken2,X-com-ibm-team-foundation-auth-loop-avoidance,jfs-oauth-access-token*,jfs-oauth-access_token-secret*,jfs-request-token-*,JSA_AUTH_COMPLETE,JSA_SESSION_IDENTITY,JSA_CSRF*"/>
    </httpEndpoint>
  7. If you have customized settings within the server.startup.sh or server.startup.bat files that are located in the original installation directory, those changes need to be made in the new server.startup.sh or server.startup.bat files.
    You cannot simply copy the old script files to the new directory as this action breaks application logging due to changes required for the new version of log4j.

    If you updated the <ELMInstallLocation>\server\liberty\servers\clm\jvm.options file, this file needs to be copied to the new installation

    If you have database vendor JDBC drivers that need to be copied or referenced, the appropriate changes need to be made.

    When the SSL option is not selected and HTTP is used to run the Report Builder, changes in the Report Builder web.xml file will not be saved in the new environment after the upgrade. Re-create the same changes in the new Report Builder web.xml file.

Clustering addendum for installing Engineering Lifecycle Management 7.1.0 SR1 interim fix 4 side-by-side

This addendum provides additional steps that you must perform if you have set up the Engineering Lifecycle Management applications in a clustered environment and are performing a side-by-side installation or upgrade to IBM Engineering Lifecycle Management 7.1.0 SR1 interim fix 4.

  1. Stop all nodes of IBM Engineering Workflow Management and Engineering Test Management application clusters and then stop DCM.
  2. Migrate one node of each application cluster to 7.1.0 SR1 interim fix 4 by following the instruction from the Installing and migrating Engineering Lifecycle Management servers.
  3. Replicate Engineering Workflow Management to all nodes.
    You can replicate the Engineering Workflow Management application on all nodes in two ways.
    1. Install the Engineering Workflow Management application on all other nodes and only copy the teamserver.properties and server.startup files from the first node to the other nodes.
    2. Copy the entire installation directory from the first node to the other nodes. Do not forget to change the node IDs in the server.startup file on all nodes so that they all have unique IDs. For more information, see Replicate Engineering Workflow Management nodes.
  4. Replicate Engineering Test Management to all nodes.
    You can replicate the Engineering Test Management application on all nodes in two ways.
    1. Install the Engineering Test Management application on all other nodes and only copy the teamserver.properties and server.startup files from the first node to the other nodes.
    2. Copy the entire installation directory from the first node to the other nodes. Do not forget to change the node IDs in the server.startup file on all nodes so that they all have unique IDs. For more information, see Replicate Engineering Test Management nodes.
  5. Replicate node-specific identifiers and keystore from previous nodes.
    On each application node machine:
    1. The node identifier is mentioned as a value to the JAVA OPTION-Dcom.ibm.team.repository.cluster.nodeId in server.startup file. Copy the option and its value from server.startup of the older version node installation to its newer 7.1.0 SR1 interim fix 4 replica.
    2. Copy the keystore from older version installation for the node to its newer 7.1.0 SR1 interim fix 4 replica.
  6. Migrate Distributed Cache Micro service.
    1. For Unix operating systemsCopy the following files from /opt/IBM/ELM71/server/clustering/cache to /opt/IBM/ELM71_SR1/server/clustering/cache.
      • distributedCache.cfg
      • distributedCache.start.sh
      • distributedCache.stop.sh
      • client_keystore.jks

        If you have a custom keystore, copy that as well.

      Refer to the [REST-SslContextFactory] section in the distributedCache.cfg file to determine which keystore is in use.

    2. For Unix operating systemsCopy the following files from /opt/IBM/ELM71/server/clustering/ to /opt/IBM/ELM71_SR1/server/clustering/.
      • addNodeReg.sh
      • JASConfig.params
      If DCM runs outside of the default Jazz Team Server location, configure DCM in a nondefault location:
      1. Copy the latest DCM from Jazz Team Server 7.1.0 SR1 interim fix 4 installation (located in <SR1 Installation>\server\clustering directory), to the nondefault location you want it to run from.
      2. Follow the steps outlined in this document to complete the configuration.
    3. For Windows operating systemCopy the following files from C:\IBM\ELM71\server\clustering\cache to C:\IBM\ELM71_SR1\server\clustering\cache.
      • distributedCache.cfg
      • distributedCache.start.bat
      • distributedCache.stop.bat
      • client_keystore.jks

        If you have a custom keystore, copy that as well.

      Refer to the section [REST-SslContextFactory] in distributedCache.cfg file to determine which keystore is in use.

    4. For Windows operating systemCopy the following files from C:\IBM\ELM71\server\clustering\ to C:\IBM\ELM71_SR1\server\clustering\.
      • addNodeReg.bat
      • addNodeReg.ps1
      • JASConfig.params
      If DCM runs outside of the default Jazz Team Server location, configure DCM in a non-default location:
      1. Copy the latest DCM from Jazz Team Server 7.1.0 SR1 interim fix 4 installation (located in <SR1 Installation>\server\clustering directory), to the non-default location you want it to run from.
      2. Follow the steps outlined in this document to complete the configuration.
  7. Start DCM and then start the nodes. Verify whether cluster works fine.
    Note: Before you start DCM, make sure to stop all old nodes, old registered services and register and use newer services and nodes.

What to do next

If you've Jazz Authorization Server, you must upgrade your Jazz Authorization Server. For more information on upgrading Jazz Authorization Server by using Installation Manager, see Upgrading and enabling Jazz Authorization Server.

If you're upgrading IBM Engineering Lifecycle Optimization - Publishing 7.0.3 to IBM Engineering Lifecycle Optimization - Publishing 7.1.0 SR1 interim fix 4, follow the instructions from How to Upgrade IBM Publishing (PUB) Application to Version 7.1.0 SR1 - IBM Engineering Lifecycle Optimization - Publishing.