IBM Support

How to perform a side-by-side installation to deploy the IBM Engineering Lifecycle Management 7.0.2 SR1 (iFix015) and 7.0.1 SR1 (iFix018)

How To


Summary

This document explains how to upgrade an existing Engineering Lifecycle Management 7.0.2 deployment to 7.0.2 SR1 (iFix015) and 7.0.1 deployment to 7.0.1 SR1 (iFix018)

In order to provide a complete upgrade and remediation of Apache log4j security vulnerabilities for the IBM Engineering Lifecycle Management applications, a side-by-side installation is required. The process outlined in this document upgrades all instances of Apache log4j used in IBM Engineering Lifecycle Management to version 2.17 or higher and remove all older versions previously installed.

Environment

These instructions apply to currently supported versions of Rational Collaborative Lifecycle Management and IBM Engineering Lifecycle Management applications.
The currently supported versions and their related fix installs are:
  • 7.0.2 - All fix levels through iFix014
  • 7.0.1 - All fix levels through iFix017
The installation process for Engineering Lifecycle Management 7.0.2 SR1 (iFix015) and 7.0.1 SR1 (iFix018) is different than the regular interim fix process. Installation is performed 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 updates or reindexing.
Future interim fixes for Engineering Lifecycle Management 7.0.2 SR1 and 7.0.1 SR1 are to be installed the way interim fixes are traditionally deployed. Future interim fixes are only compatible with Engineering Lifecycle Management 7.0.2 SR1 (iFix15) and 7.0.1 SR1 (iFix018). They are not compatible with earlier versions of ELM. You must move to the SR1 release to use future interim fixes.

Steps

Steps to migrate
1. Preparation
  • Review the steps in this document and the corresponding product documentation.
    • Assemble documentation for any customizations you made to the start scripts, WebSphere Application Server profiles, WebSphere Application Server Liberty, or configuration files.
    • Create a test environment to test out the migration.
    • Plan the backup and downtime for the migration.
2. Installation
  • Install the fixed version of the applications into a new package group, but do not run the setup wizard after the installation. For distributed configurations, install the fixed version of the applications that correspond to the previously installed applications.
    • NOTE: Do not run the setup wizard after the installs are completed.
    • NOTE: If you are using DerbyDB for any applications, you need to copy those files from the old installation directory to the new installation location.
3. Stop the running application servers by using either server.shutdown or server.shutdown.bat
4. Migrate existing configuration files
  • A. Copy the Lifecycle Query Engine (LQE) configuration files
    • Ensure the following directories do not exist before copying the LQE configuration files.  Navigate to the directory where you just installed the version 7.0.2 application. In a fresh installation, these directories should not exist. Alternatively, you can open a command prompt and enter the following commands to delete the directories.
      • Linux 
        • rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/indexTdb
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/textIndex
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/shapeText
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/shapeTdb
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/historyText
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/historyTdb
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe/versionTdb
          • If prompted, confirm to complete the command.
      • Windows 
        • del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\indexTdb
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\textIndex
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\shapeText
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\shapeTdb
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\historyText
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\historyTdb
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\lqe\versionTdb
          • If prompted, confirm to complete the command.
    • To copy the configuration files to the new installation directory, enter the following commands: 
      • Linux 
        • 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.
      • Windows 
        • 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.
  • B. Copy the Link Index Provider (LDX) configuration files
    • Ensure the following directories do not exist before copying the LDX configuration files.  Navigate to the directory where you just installed the version 7.0.2 application. In a fresh installation, these directories should not exist. Alternatively, you can open a command prompt and enter the following commands to delete the directories.
    • Verify by running these commands to clear any files.
      • Linux 
        • rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/indexTdb
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/textIndex
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx/versionTdb
          • If prompted, confirm to complete the command.
      • Windows 
        • del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\indexTdb
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\textIndex
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\ldx\versionTdb
          • If prompted, confirm to complete the command.
    • To copy the configuration files to the new installation directory, enter the following commands:
      • Linux 
        • 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.
      • Windows 
        • 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.
    • If you are using Derby DB for either LQE or LDX, ensure that you copy those files as well
  • C. Copy your JFS/text indices from previous installation directory to the new installation directory. 
    • For distributed systems, go to the appropriate server and copy the files.
    • To clear the default indices directory in the new installation, open a command prompt and enter the following commands:
      • Linux 
        • rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/jts/indices
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/ccm/indices
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/qm/indices
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/rm/indices
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/dcc/indices
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/relm/indices
rm -rf /opt/IBM/JazzTeamServer_NewInstall/server/conf/gc/indices
          • If prompted, confirm to complete the command.
      • Windows 
        • del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\jts\indices
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\ccm\indices
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\qm\indices
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\rm\indices
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\dcc\indices
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\relm\indices
del /s /f D:\IBM\JazzTeamServer_NewInstall\server\conf\gc\indices
          • If prompted, confirm to complete the command.
      • To copy the indices from the previous installation to the new installation, open a command prompt and enter the following commands:
        • Linux 
          • 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.
        • Windows 
          • 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.
5.  Run the configuration migration commands
  • By default, migration is not allowed when the old and new installs have the same release number. To enable these commands to work, an environment variable must be defined in the command shell.
  • Note: For LQE and LDX, you need to start and then shut down the new application server before running these commands to create the new profile instance.
  • Note: If you are deployed on WebSphere Application Server to host the applications, refer to the extra instructions in this document for extra arguments for the commands listed here.
  • Note: 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.
  • Note: You must 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.
  • Note: If you have a custom context root for any application, include applicationContextRoot parameter with the value of the custom context root.
  • Linux 
    • 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
  • Windows 
    • 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.  For Liberty deployments, replicate port and SSL configurations by copying server configuration file and the referenced keystores
  • Linux: 
    • cp /opt/IBM/JazzTeamServer/server/liberty/servers/clm/server.xml /opt/IBM/JazzTeamServer_NewInstall/server/liberty/servers/clm/
      • If prompted, confirm to complete the command.
    • 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: 
      • cp -R /opt/IBM/JazzTeamServer/server/liberty/servers/clm/resources /opt/IBM/JazzTeamServer_NewInstall/server/liberty/servers/clm/
  • Windows:  
    • copy D:\IBM\JazzTeamServer\server\liberty\servers\clm\server.xml D:\IBM\JazzTeamServer_NewInstall\server\liberty\servers\clm
    •  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: 
      • xcopy /s /e D:\IBM\JazzTeamServer\server\liberty\servers\clm\resources D:\IBM\JazzTeamServer_NewInstall\server\liberty\servers\clm\resources
        • When prompted, enter "D" to complete the command.
7. Customized parameters
  • If you have customized settings within the server.startup.sh or server.startup.bat files located in the original installation directory, those changes will 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 will break 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 will 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. You must re-create the same changes in the new Report Builder web.xml file.
If the applications are deployed on WebSphere Application Server
Add the following argument to the migration commands:
  •  updateAppServerFiles=no 
    • By default, this option is set to yes to update the Tomcat configuration files when migrating to Liberty. Set this parameter to no if you are using WebSphere Application Server.
Redeploy the application WAR files
  1. Back up the WebSphere Application Server profile
    • Open a command prompt and change to the bin folder of the WebSphere Application Server profiles directory. 
      • For example, cd D:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin or /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
      • Enter the following command. 
        • If WebSphere Application Server security is turned on, you must also supply the user name and password. Make sure that the directory path to the compressed file exists.
        • Linux
        • backupConfig Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password
        • Windows
        • backupConfig.bat Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password
  2. Stop and update the previously installed applications from the WebSphere Application Server
    • Make sure the server is started and then log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp.
      1. Click Applications > Application Types > WebSphere enterprise applications.
      2. Click the Enterprise Applications link and then stop and update the following applications:
        • jts_war
        • clmhelp_war
        • ccm_war
        • qm_war
        • rm_war
        • converter_war
        • relm_war
        • lqe_war
        • ldx_war
        • dcc_war
        • rs_war
        • gc_war
      3. Select the application you want to update and click Stop. After the application stops, select it again and click Update.
      4. Select the "Replace the Entire Application" option, choose Local File System and locate (browse) the .war you want to install.
      5. When you are prompted to save the changes to the master configuration, save them.
Update the JAZZ_HOME and configuration location custom properties
  • Log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp.
    1. Click Servers > Server Types > WebSphere application servers.
    2. Click the server name to open it. The default server name is server1.
    3. Under Server Infrastructure section, click Java and Process Management > Process definition.
    4. Under Additional Properties, click Java Virtual Machine.
    5. Under Additional Properties, click Custom properties.
    6. Click JAZZ_HOME and update its value to file:///New_install_dir/server/conf. 
    7. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_NewInstall/server/conf.
    8. Change the property name "log4j.configuration" to "log4j2.configurationFile", and change the value to the New_install_dir location and the file name to "startup_log4j2.xml" replacing "startup_log4j.properties"
      • For example,
        • Linux: file:///opt/IBM/JazzTeamServer_NewInstall/server/conf/startup_log4j2.xml
        • Windows: file:///C:/PROGRA~1/IBM/JazzTeamServer_NewInstall/server/conf/startup_log4j2.xml
    9. Click lqe.config.location and update its value to file:///New_install_dir/server/conf/lqe
      • For example,
        • Linux: file:///opt/IBM/JazzTeamServer_NewInstall/server/conf/lqe
        • Windows: file:///C:/PROGRA~1/IBM/JazzTeamServer_NewInstall/server/conf/lqe
    10. Click ldx.config.location and update its value to file:///New_install_dir/server/conf/ldx
      • For example,
        • Linux: file:///opt/IBM/JazzTeamServer_NewInstall/server/conf/ldx
        • Windows: file:///C:/PROGRA~1/IBM/JazzTeamServer_NewInstall/server/conf/ldx
    11. When prompted, save the changes to the master configuration.
Update the JRS shared library classpath
  • In WebSphere Integrated Solutions Console navigation pane click Environment > Shared libraries.
    1. Click the JRS shared library name in the list to open it.
    2. In the Classpath field, update the path to the new installation directory. 
      • For example,
        • Linux: /opt/IBM/JazzTeamServer_NewInstall/server/conf/rs/WAS_SharedLibrary
        • Windows: D:\IBM\JazzTeamServer_NewInstall\server\conf\rs\WAS_SharedLibrary
    3. Click Apply and then Save directly to the master configuration.
Stop WebSphere Application Server
  • Open a command prompt and change to the <WebSphere>/AppServer/profiles/AppSrv01/bin directory.
    1. Enter the following command:
      • Linux
      • stopServer server1 -user admin_userid -password admin_password
      • Windows
      • stopServer.bat server1 -user admin_userid -password admin_password
Clean up the WebSphere Application Server temp directories
In a distributed topology, you must complete this step on each application server that hosts the applications.
  1. Remove the application-related contents from the following directories in the profile:
    • <WebSphere>/AppServer/profiles/AppSrv01/temp
    • <WebSphere>/AppServer/profiles/AppSrv01/wscache
    • <WebSphere>/AppServer/profiles/AppSrv01/workspace
Clean up the logs directory
In a distributed topology, you must complete this step on each application server that hosts the applications.
  1. Remove the application-related log files from the following logs directory in the profile:
    • <WebSphere>/AppServer/profiles/AppSrv01/logs
  2. Clear the class cacheRun the following command
    • Linux 
      • <Websphere>/AppServer/profiles/AppSrv01/bin/clearClassCache.sh
    • Windows 
      • <Websphere>/AppServer/profiles/AppSrv01/bin/clearClassCache.bat
  3. Start WebSphere Application ServerOpen a command prompt and change to the <WebSphere>/AppServer/profiles/AppSrv01/bin directory.
    • Enter the following command:
    • Linux
    • startServer server1
    • Windows
    • startServer.bat server1
Upgrade Jazz Authorization Server
If you used the IBM Installation Manager to install Jazz Authorization Server, use the Update feature to upgrade your Jazz Authorization Server.
Before you begin
  1. Stop the Jazz Authorization Server before performing the update.
  2. Make a backup copy of the entire Jazz Authorization Server installation directory and rename it to /opt/JazzAuthorizationServer_OLD.
  3. Ensure that you have a discoverable repository location set in the Installation Manager Preferences window.
    1. In Installation Manager go to File > Preferences and click Add Repository.
    2. Browse for a local .zip file or online link that contains the Jazz Authorization Server offerings repository.config file.
    3. To ensure you can connect to the repository location, click Test Connections.
    4. To close the Preferences window, click Apply and then OK.
Procedure
  1. In IBM Installation Manager click Update.
  2. Select the Jazz Authorization Server package and click Next on all panels until you reach the Summary page.
  3. Review the summary information and click Update to start the upgrade process.
  4. If you are using DerbyDB for Jazz Authorization Server, complete the following steps:
    1. Copy the asDB folder from the backup you created earlier /opt/JazzAuthorizationServer_OLD/derby/asDB and place it in the /opt/JazzAuthorizationServer/derby/asDB replacing the existing asDB folder.
  5. Copy the listed configuration files from the old installation directory (/opt/JazzAuthorizationServer_OLD/wlp/usr/servers/jazzop) to the new installation directory:
    • server.xml
    • appConfig.xml
    • ldapUserRegistry.xml
    • localUserRegistry.xml (if used)
    • Server certificate keystore (Default file name: ibm-team.keystore)
  6. Restart the Jazz Authorization Server.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPRJQ","label":"IBM Engineering Lifecycle Management Base"},"ARM Category":[{"code":"a8m0z000000CbPJAA0","label":"Jazz Team Server-\u003EUpgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYMRC","label":"Rational Collaborative Lifecycle Management"},"ARM Category":[{"code":"a8m0z000000CbPJAA0","label":"Jazz Team Server-\u003EUpgrade"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.6"}]

Document Information

Modified date:
12 December 2022

UID

ibm16588059

Page Feedback