Changing WebSphere Application Server installations and instances
This topic describes how to change Jazz® applications to a different WebSphere Application Server instance within the same environment. This may be necessary if you are installing a new version of the IBM® Engineering Lifecycle Management (ELM) on the same system or if an application is being moved to a different WebSphere Application Server profile or server instance.
Procedure
-
Perform the following steps on the original WebSphere Application
Server:
- Log on to the WebSphere Application Server Integrated Solutions Console at https://host name:9043/ibm/console/logon.jsp.
- Click Applications > Applications Types > WebSphere enterprise applications.
- Write down the security roles mapping of the jts_war, and if deployed, ccm_war, and qm_war applications to assist you with reapplying the mappings for the new WebSphere Application Server installation.
- Stop the ELM applications that are deployed on the server.
- Click Servers > Server Types > WebSphere enterprise applications.
- Click the server name to open it. The default server name is server1.
- Under Server Infrastructure, click Java and Process Management > Process definition.
- Under Additional Properties, click Java Virtual Machine.
- Under Additional Properties, click Custom properties.
- Record values for all settings, including JAVA_HOME, log4j.configuration, and if they exist, ORACLE_JDBC_DRIVER_FILE or SQLSERVER_JDBC_DRIVER_FILE.
- Record any other non-default settings in the WebSphere Application Server, including additional properties, Java™ memory allocations, security, virtual hosting, and authentication.
- Stop the original WebSphere Application Server.
-
Create a backup of the original WebSphere Application
Server
profile.
- Open a command prompt and change to the WAS_Profile/bin directory, for example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin.
-
Run the following command to back up the WebSphere Application
Server profile,
for example, ./backupConfig /root/was_backups/elm_oldWAS_profile.zip,
where ./backupConfig is the path for the backed-up profile.
Note: If necessary, you can restore the backed-up profile by running the ./restoreConfig command, for example, ./restoreConfig /root/was_backups/elm_oldWAS_profile.zip.
- Start the original WebSphere Application Server.
- Uninstall all Jazz applications and associated
settings.
- Log on to the WebSphere Application Server Integrated Solutions Console at https://host name:9043/ibm/console/logon.jsp.
- Click Applications > Applications Types > WebSphere enterprise applications.
- Uninstall the ELM applications that are deployed.
- Save the changes to the master configuration when prompted.
- Click Servers > Server Types > WebSphere application servers .
- Click the server name to open it. The default server name is server1.
- Under Server Infrastructure, click Java and Process Management > Process definition.
- Under Additional Properties, click Java Virtual Machine.
- Under Additional Properties, click Custom Properties.
- Delete the JAZZ_HOME and log4j.configuration entries.
- Save the changes to the master configuration when prompted.
-
Change any other settings that are no longer required for the original WebSphere Application
Server back to
the default.
For detailed information about the original settings, see Setting up WebSphere Application Server.
- Stop the original WebSphere Application Server.
-
Delete the temporary files for the Jazz applications on
the original WebSphere Application
Server instance
by removing the Jazz application-related contents from the wstemp and
temp directories in the profile. For example:
- C:\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp and C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp
- /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp and /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp
- Back up and remove the Jazz application-related
logs form the logs directory in the profile under profile_directory/logs, for
example:
- C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs
- /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs
- Back up the database.
- Derby: Make an archive copy of the following database directories, for
example:
install_dir/server/conf/jts/derby install_dir/server/conf/ccm/derby install_dir/server/conf/qm/derby install_dir/server/conf/rm/derby
- Db2®: See the Db2 database documentation for details. Here is an example
command:
db2 backup database {db-name} userdb2 backup database {db-name} user <userName> using <password> to <target-dir> COMPRESS
- For Oracle and SQL Server, see the vendor's documentation for details.
- Derby: Make an archive copy of the following database directories, for
example:
- Create a backup copy of the following Jazz
application information:
- Application configuration
files
install_dir/server/conf/jts/teamserver.properties install_dir/server/conf/ccm/teamserver.properties install_dir/server/conf/qm/teamserver.properties install_dir/server/conf/rm/teamserver.properties install_dir/server/conf/relm/teamserver.properties install_dir/server/conf/dcc/teamserver.properties install_dir/server/conf/lge/teamserver.properties install_dir/server/conf/ldx/teamserver.properties install_dir/server/conf/gc/teamserver.properties
- Application
indices
install_dir/server/conf/jts/indices install_dir/server/conf/ccm/indices install_dir/server/conf/qm/indices install_dir/server/conf/rm/indices install_dir/server/conf/relm/indices install_dir/server/conf/dcc/indices install_dir/server/conf/lge/indices install_dir/server/conf/ldx/indices install_dir/server/conf/gc/indices
- Log
settings
install_dir/server/conf/jts/log4j.properties install_dir/server/conf/ccm/log4j.properties install_dir/server/conf/qm/log4j.properties install_dir/server/conf/rm/log4j.properties install_dir/server/conf/relm/log4j.properties install_dir/server/conf/dcc/log4j.properties install_dir/server/conf/lge/log4j.properties install_dir/server/conf/ldx/log4j.properties install_dir/server/conf/gc/log4j.properties
- The JazzInstallDir/server/webapps directory that includes all the WAR files. These files will be needed when you set up WebSphere Application Server.
- The repository tools in the JazzInstallDir/repotools directory
- z/OS® only: @confPath@/jts/teamserver.properties
- z/OS only: @confPath@/jts/log4j.properties
- Application configuration
files
- After backing up the database and saving the files, continue with Setting up WebSphere Application Server and Deploying applications for the IBM Engineering Lifecycle Management on WebSphere Application Server.
For z/OS, see Configuring Jazz Team Server and the applications for the Engineering Lifecycle Management to use WebSphere Application Server on z/OS.
Note: Check all settings for the new WebSphere Application Server and installed Jazz applications against the settings recorded from the original WebSphere Application Server, including environmental variables, memory allocations, security, virtual hosting, LDAP and mapped application security roles. -
Make sure that the new WebSphere Application
Server is started
as well as all Jazz applications that were running in the
original WebSphere Application
Server
instance.
- Log on to the WebSphere Application Server Integrated Solutions Console at https://host name:9043/ibm/console/logon.jsp.
- Click Applications > Applications Types > WebSphere enterprise applications.
- Start the applications if they are not already started.
-
Perform a server reset for the Jazz
Team Server and
ELM
applications as shown in the following examples:
https://jts_server.mydomain.com:9443/jts/admin#action=com.ibm.team.repository.admin.serverReset https://ccm_server.mydomain.com:9443/ccm/admin#action=com.ibm.team.repository.admin.serverReset https://rm_server.mydomain.com:9443/rm/admin#action=com.ibm.team.repository.admin.serverReset https://qm_server.mydomain.com:9443/qm/admin#action=com.ibm.team.repository.admin.serverReset
Restart the WebSphere Application Server for the server reset to take effect.