How To
Summary
Installing the LDX application on stand-alone server to decouple the LDX from the JTS server.
In some circumstances, the resource needs of the LDX server can negatively impact the JTS when the LDX indices are large. Moving the LDX server might be the only option to improve JTS performance.
Objective
The following steps allow you to deploy LDX stand-alone server, by using the default ELM embedded liberty server. Which supersede the following article.
Installing Link Index Provider (LDX) on its own Server
Using this document the LDX application is deployed like any other ELM application.
Environment
Prerequisite:
IBM Installation Manager™ package installed, see jazz.net system requirement https://jazz.net/wiki/bin/view/Deployment/DeploymentInstallingUpgradingAndMigrating
IBM Installation Manager™ Repositories downloaded
https://jazz.net/downloads/workflow-management
Steps
Steps
1. Find "imcl" tool, and set IMCL_HOME with path to tool
Locate IBM Installation Manager™ home directory and set (IMCL_HOME) by adding the “\eclipse\tools\imcl” to the path.
Window™:
Set IMCL_HOME=C:\Products\IBM\InstallationManager\eclipse\tools\imcl
Linux®:
export IMCL_HOME=/opt/IBM/InstallationManager/eclipse/tools/imcl
2. Find repository file and navigate to the repository location
Navigate to the repository location of the ELM repository file to use for the installation. This example uses 7.0.1 repository, JTS-CCM-QM-RM-JRS-ENI-repo-7.0.1.zip
Windows™:
cd C:\Users\PhilippeChevalier\Documents\IM\repo
Linux®:
cd /elmspc
3. Run the IBM Installation Manager™ “ibmcl” to install LDX with following command parameters:
Windows™:
%IMCL_HOME% install com.ibm.team.install.jfs.app.jts com.ibm.team.install.jfs.app.ldx com.ibm.team.install.jfs.app.product-clm -installationDirectory C:/IBM/JazzTeamServer -repositories JTS-CCM-QM-RM-JRS-ENI-repo-7.0.1.zip -acceptLicense
Linux®:
$IMCL_HOME install com.ibm.team.install.jfs.app.jts com.ibm.team.install.jfs.app.ldx com.ibm.team.install.jfs.app.product-clm -installationDirectory /opt/IBM/JazzTeamServer -repositories JTS-CCM-QM-RM-JRS-ENI-repo-7.0.1.zip -acceptLicense
NOTE: Packages com.ibm.team.install.jfs.app.product-clm and com.ibm.team.install.jfs.app.jts cannot be removed from the installation scripts as it is a dependency to the LDX packages, step to clear the situation is documented later.
4. Review command output
Windows™:
C:\Users\PhilippeChevalier\Documents\IM\repo>%IMCL_HOME% install com.ibm.team.install.jfs.app.jts com.ibm.team.install.jfs.app.ldx com.ibm.team.install.jfs.app.product-clm -installationDirectory "C:/IBM/JazzTeamServer" -repositories JTS-CCM-QM-RM-JRS-ENI-repo-7.0.1.zip -acceptLicense
Installed com.ibm.team.install.jfs.app.jts_7.0.1000.RJF-SERVER-I20200604-1300-r701- to the C:/IBM/JazzTeamServer directory.
Installed com.ibm.team.install.jfs.app.ldx_7.0.1000.RJF-SERVER-I20200604-1300-r701- to the C:/IBM/JazzTeamServer directory.
Installed com.ibm.team.install.jfs.app.product-clm_7.0.1000.ELMB701-I20200604-2311-r701 to the C:/IBM/JazzTeamServer directory.
Linux®:
[root@vises1 clm]#$IMCL_HOME install com.ibm.team.install.jfs.app.jts com.ibm.team.install.jfs.app.ldx com.ibm.team.install.jfs.app.product-clm -installationDirectory /opt/IBM/JazzTeamServer -repositories JTS-CCM-QM-RM-JRS-ENI-repo-7.0.1.zip -acceptLicense
Installed com.ibm.team.install.jfs.app.jts_7.0.1000.RJF-SERVER-I20200604-1300-r701- to the /opt/IBM/JazzTeamServer directory.
Installed com.ibm.team.install.jfs.app.ldx_7.0.1000.RJF-SERVER-I20200604-1300-r701- to the /opt/IBM/JazzTeamServer directory.
Installed com.ibm.team.install.jfs.app.product-clm_7.0.1000.ELMB701-I20200604-2311-r701 to the /opt/IBM/JazzTeamServer directory.
5. Modify the $JAZZ_HOME, remove JTS and CLM Help war file from the clmServerTemplate directory
Windows™:
cd C:\IBM\JazzTeamServer\server\liberty\clmServerTemplate\apps
del -f clmhelp.war.zip jts.war.zip
rmdir /s /q clmhelp.war jts.war
Results:
Linux®:
C:\IBM\JazzTeamServer\server\liberty\clmServerTemplate\apps>dir
Volume in drive C is Windows
Volume Serial Number is A2B5-5FF2
Directory of C:\IBM\JazzTeamServer\server\liberty\clmServerTemplate\apps
10/14/2020 12:44 PM <DIR> .
10/14/2020 12:44 PM <DIR> ..
10/14/2020 10:56 AM <DIR> ldx.war
06/04/2020 01:03 PM 63,274,365 ldx.war.zip
1 File(s) 63,274,365 bytes
3 Dir(s) 391,954,374,656 bytes free
Linux®:
cd /opt/IBM/JazzTeamServer/server/liberty/clmServerTemplate/apps
rm -rf jts.* clmhelp.*
Results:
[root@vises1 apps]# ls
ldx.war ldx.war.zip
6. Navigate to the JazzTeamServer home and run the following command to create the ELM application server configuration
Windows™:
cd c:\IBM\JazzTeamServer\server
server.startup.bat -create
Results: The following directory is created and the ".../servers/clm" server is in place for startup
c:\IBM\JazzTeamServer\server\liberty\servers\clm>dir
Volume in drive C is Windows
Volume Serial Number is A2B5-5FF2
Directory of c:\IBM\JazzTeamServer\server\liberty\servers\clm
10/14/2020 12:58 PM <DIR> .
10/14/2020 12:58 PM <DIR> ..
10/14/2020 12:56 PM <DIR> apps
10/14/2020 12:56 PM <DIR> conf
10/14/2020 12:56 PM <DIR> dropins
06/04/2020 12:37 PM 1,763 jvm.options
10/14/2020 12:57 PM <DIR> logs
10/14/2020 12:56 PM 68 server.env
06/04/2020 12:37 PM 2,508 server.xml
10/14/2020 12:56 PM <DIR> workarea
3 File(s) 4,339 bytes
7 Dir(s) 391,677,751,296 bytes free
Linux®:
cd /opt/IBM/JazzTeamServer/server
./server.startup -create
Results: The following directory is created ".../servers/clm", means the server is created and in place for startup.
[root@vises1 clm]# pwd
/opt/IBM/JazzTeamServer/server/liberty/servers/clm
[root@vises1 clm]# ls
apps conf dropins jvm.options logs server.env server.xml workarea
At this point, the LDX server is ready for usage.
There are two types of action from this point on.
1. Move LDX from the JTS server, which this document does not address, use the following process to restore and existing server to this new installation.
Backing up and restoring Lifecycle Query Engine and Link Index Provider (LDX)
https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.6.1/com.ibm.team.jp.lqe2.doc/topics/t_lqe_backup.html
NOTE: The LDX Public URL will need to stay consistent from the original LDX deployment.
2. Run the JTS setup and complete the LDX distributed installation
Document Location
Worldwide
[{"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":"a8m0z000000CbOBAA0","label":"Jazz Team Server->Jazz Foundation Services"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
19 October 2020
UID
ibm16348196