Select the options that apply to your environment to generate a customized guide to add one or more new applications to an existing .
To add additional () software packages to an existing , follow these steps:
You can add new IBM® Engineering Lifecycle Management (ELM) applications to an existing Jazz Team Server. If you have a Jazz Team Server with a subset of ELM applications installed and later on decide to add more ELM applications in the same environment, you can do so in two ways. Depending on what applications or features you already have installed, you might need to use the launchpad program, or the Modify feature of IBM Installation Manager. Follow the steps in this interactive guide to add new applications to an existing Jazz Team Server in your environment.
Before installing new applications into an existing , you must shut down the server.
cd JazzInstallDir\server
server.shutdown.bat
cd JazzInstallDir/server
./server.shutdown
Before you begin
* hard nofile 65536
* soft nofile 65536
* hard nproc 10000
* soft nproc 10000
ulimit -n 65536
ulimit -u 10000
Note: If you use these commands, start the Launchpad program or IBM Installation Manager from the same shell to inherit the modified limits. After these settings are applied, reindex the server to fix any corrupted server indexes by running the Jazz_Install_Dir/server/repotools-jts -reindex repotools command.
About this task
There are two ways to download and install applications. The first installation method is a web-based installation that includes a smaller download and connects to the internet during the installation to get the repository files. If you must install the server in an environment without internet access, use the second installation method: download and extract the repository files to a local computer to install the server.
If you do not have User Interface libraries installed on your server or just prefer to use the command-line installation method, you can use an response file to install . This method is also referred to as silent installation
.
There are two sample response files provided to install applications:
Procedure
Note: You must use the same user mode for (Administrator or Non-Administrator) as you previously selected when installing .
.\installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini
./installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini
.\userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini
./userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini
<data key='user.JazzFoundationServer.NoAppServer.WebApps.InstallLocation'
value='C:\tmp\silent-install\JazzTeamServer\server\webapps'/>
<data key='user.JazzFoundationServer.NoAppServer.WebApps.InstallLocation'
value='/tmp/silent-install/JazzTeamServer/server/webapps'/>
<!--
<offering id='com.ibm.team.install.jfs.app.rtc'/>
-->
<offering id='com.ibm.team.install.jfs.app.jrs' features='lqe,dcc'/>
If you are adding a feature to an existing installation, you must use the Modify feature of .
Before you begin
<offering id='com.ibm.team.install.jfs.app.jrs' features='lqe,dcc'/>
About this task
If you do not have User Interface libraries installed on your server or just prefer to use the command-line installation method, you can use an response file to install the features. This method is also referred to as silent installation
.
There are two sample response files provided to install features:
Procedure
.\installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini
./installc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini silent-install.ini
.\userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini
./userinstc -acceptLicense -showVerboseProgress -input silent-install-server2.xml --launcher.ini user-silent-install.ini
<data key='user.JazzFoundationServer.NoAppServer.WebApps.InstallLocation'
value='C:\tmp\silent-install\JazzTeamServer\server\webapps'/>
<data key='user.JazzFoundationServer.NoAppServer.WebApps.InstallLocation'
value='/tmp/silent-install/JazzTeamServer/server/webapps'/>
To add an application to an existing , you will use the QJTS70 LICPGM. For step-by-step instructions for new installations, see Installing and applications on IBM i.
If you are using the included Derby database, no additional setup is necessary. Proceed with the next step.
Note: Although a Derby database is included in the default configuration and requires no installation, this database is limited to 10 users. To enable more users, install a supported enterprise database such as Db2, Oracle, or SQL Server.
To create database tables, see Creating Db2 for z/OS database tables remotely.
By default, IBM Db2i database is setup and configured on your IBM i system. No additional setup is necessary. Proceed with the next step.
The products support IBM Db2 Enterprise Server Edition. For platforms that do not support Enterprise Server Edition, you can use IBM Db2 Workgroup Server Edition. You can obtain a trial download of one these Db2 editions or the free Db2 Express Server edition for deployments of 50 developers or fewer from ibm.com.
Before you begin
This procedure requires that the following prerequisites are met:
Procedure
db2 create database CCM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database QM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database RM using codeset UTF-8 territory en PAGESIZE 16384
db2 create database DCC using codeset UTF-8 territory en PAGESIZE 16384
Note: The database requires 32K pages.
db2 create database LQE using codeset UTF-8 territory en PAGESIZE 32768
The LQE database must have the MAXAPPLS increased to allow for concurrent connections in to process data if it is not set to AUTOMATIC. Increase the value to 300:
db2 update db cfg for LQE using maxappls 300
This means that the lock list must also be increased if it is not set to AUTOMATIC:
db2 update db cfg FOR LQE using locklist 20000
The transaction logs will also grow as data is processed in parallel. Increase the LOGFILSIZ to 20000:
db2 update db cfg for LQE using LOGFILSIZ 20000
Increase the number of primary and secondary transactions log files:
db2 update db cfg for LQE using logprimary 25
db2 update db cfg for LQE using logsecond 100
Note: The database requires 32K pages.
db2 create database LDX using codeset UTF-8 territory en PAGESIZE 32768
db2 create database GC using codeset UTF-8 territory en PAGESIZE 16384
db2 create database ENI using codeset UTF-8 territory en PAGESIZE 16384
db2 create database DW using codeset UTF-8 territory en PAGESIZE 32768
The data warehouse database must have the MAXAPPLS increased to allow for concurrent connections in to process data if it is not set to AUTOMATIC. Increase the value to 300:
db2 update db cfg for DW using maxappls 300
This means that the lock list must also be increased if it is not set to AUTOMATIC:
db2 update db cfg FOR DW using locklist 20000
The transaction logs will also grow as data is processed in parallel. Increase the LOGFILSIZ to 20000:
db2 update db cfg for DW using LOGFILSIZ 20000
Increase the number of primary and secondary transactions log files:
db2 update db cfg for DW using logprimary 25
db2 update db cfg for DW using logsecond 200
If you are creating the database with a user other than the user specified in the teamserver.properties file, you must grant DBADM authority to that user:
db2 connect to database_name
db2 grant dbadm on database to user user_name
db2 disconnect database_name
If you create all databases on the same database server, verify that the Max number of concurrently active databases is set to a number greater than the number of databases you created. If this value is lower than the number of active databases, you will get the SQL Code 1041 error.
To verify the value and increase the number if necessary, complete these steps:
db2 get dbm cfg
db2 update dbm cfg using numdb 32
db2stop
db2start
To create and set up an Oracle database, it is assumed that the user who is preparing the database has database administration authority over the database and that the database, tablespace storage, and appropriate storage configuration is created by a user with system administration authority.
Before you begin
Planning checklistsection of this document.
Restriction: Because of a defect in Oracle JDBC driver 12.1.0.2.0, this version of the driver cannot be used. For details, see repotools -createTables command fails with ORA-01000 on Oracle 12 on the IBM Support portal page.
The examples in this step are for one Oracle database with separate tablespaces and database users who are dedicated to each application.
alter system set open_cursors = 10000 scope=both;
alter system set open_cursors = 10000;
Procedure
CREATE BIGFILE TABLESPACE CCM
DATAFILE 'ORACLE_BASE/oradata/DB/CCM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE CCM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/CCM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE ENI
DATAFILE 'ORACLE_BASE/oradata/DB/ENI.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE ENI_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/ENI_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE QM
DATAFILE 'ORACLE_BASE/oradata/DB/QM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE QM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/QM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE RM
DATAFILE 'ORACLE_BASE/oradata/DB/RM.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE RM_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/RM_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE DCC
DATAFILE 'ORACLE_BASE/oradata/DB/DCC.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE DCC_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/DCC_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE LQE
DATAFILE 'ORACLE_BASE/oradata/DB/LQE.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE LQE_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/LQE_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE LDX
DATAFILE 'ORACLE_BASE/oradata/DB/LDX.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE LDX_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/LDX_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE GC
DATAFILE 'ORACLE_BASE/oradata/DB/GC.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE GC_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/GC_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
CREATE BIGFILE TABLESPACE DW
DATAFILE 'ORACLE_BASE/oradata/DB/DW.DBF'
SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;
CREATE TEMPORARY TABLESPACE DW_TEMP
TEMPFILE 'ORACLE_BASE/oradata/DB/DW_TEMP.DBF'
SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
In the Oracle Enterprise Manager Database Control, click Server > Tablespaces and verify that the tablespaces you created are displayed and accessible. Also ensure that the default Oracle tablespace named USERS already exist. If this tablespace does not exist in your Oracle database, create it.
After the tablespaces are created, a special Oracle user must be created for each application to use the Oracle database. For multiple Jazz servers that run on one Oracle database, an Oracle database user must be created for each application. The Oracle database user must be able to create database objects in its tablespace (either unlimited or with a space quota) with privileges to create session, table, procedure, and views.
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER CCM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE CCM QUOTA UNLIMITED ON CCM TEMPORARY TABLESPACE CCM_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO CCM_DB_USER;
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER ENI_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE ENI QUOTA UNLIMITED ON ENI TEMPORARY TABLESPACE ENI_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO ENI_DB_USER;
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER QM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE QM QUOTA UNLIMITED ON QM TEMPORARY TABLESPACE QM_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO QM_DB_USER;
To create a user for application tablespace and to grant the required permissions, enter the following commands:
CREATE USER RM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE RM QUOTA UNLIMITED ON RM TEMPORARY TABLESPACE RM_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO RM_DB_USER;
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER DCC_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE DCC QUOTA UNLIMITED ON DCC TEMPORARY TABLESPACE DCC_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO DCC_DB_USER;
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER LQE_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE LQE QUOTA UNLIMITED ON LQE TEMPORARY TABLESPACE LQE_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO LQE_DB_USER;
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER LDX_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE LDX QUOTA UNLIMITED ON LDX TEMPORARY TABLESPACE LDX_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO LDX_DB_USER;
To create a user for the application tablespace and to grant the required permissions, enter the following commands:
CREATE USER GC_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE GC QUOTA UNLIMITED ON GC TEMPORARY TABLESPACE GC_TEMP;
GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO GC_DB_USER;
To create a user for common data warehouse tablespace and to grant the required permissions, enter the following commands:
CREATE USER DW_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE DW QUOTA UNLIMITED ON DW TEMPORARY TABLESPACE DW_TEMP;
GRANT DBA TO DW_USER;
Note: The creation of the data warehouse on Oracle requires more permissions as compared to other databases. When you specify the database user in the connection spec for data warehouse, ensure that the database user has DBA permissions. You can change this permission after the data warehouse is created. For more information, see Completing the installation.
To create the data warehouse without DBA permissions, see this deployment wiki article.
In the computer that hosts the applications, create an environment variable named ORACLE_JDBC_DRIVER_FILE and point to the ojdbc8.jar JDBC driver. The location can vary depending on the Oracle product and operating system. You can download the supported Oracle JDBC driver from the Oracle website.
export ORACLE_JDBC_DRIVER_FILE =/Path_to_JDBC_driver/ojdbc8.jar
Before you begin
This procedure requires that the following prerequisites are met:
Procedure
Set up the SQL Server database by using the sqlcmd command line tool, which is provided with the SQL Server installation. You can also use a visual tool, such as SQL Server Studio Management.
Important: If you install applications either on the same computer or distributed platforms, a separate database and a database user who is associated with that database must be created.
CREATE DATABASE ccm
GO
CREATE LOGIN ccmDBuser
WITH PASSWORD = 'ccmDBpswd';
USE ccm;
exec sp_changedbowner 'ccmDBuser'
GO
ALTER DATABASE ccm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE ccm SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE eni
GO
CREATE LOGIN eniDBuser
WITH PASSWORD = 'eniDBpswd';
USE eni;
exec sp_changedbowner 'eniDBuser'
GO
ALTER DATABASE eni COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE eni SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE qm
GO
CREATE LOGIN qmDBuser
WITH PASSWORD = 'qmDBpswd';
USE qm;
exec sp_changedbowner 'qmDBuser'
GO
ALTER DATABASE qm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE qm SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE rm
GO
CREATE LOGIN rmDBuser
WITH PASSWORD = 'rmDBpswd';
USE rm;
exec sp_changedbowner 'rmDBuser'
GO
ALTER DATABASE rm COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE rm SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE dcc
GO
CREATE LOGIN dccDBuser
WITH PASSWORD = 'dccDBpswd';
USE dcc;
exec sp_changedbowner 'dccDBuser'
GO
ALTER DATABASE dcc COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE dcc SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE lqe
GO
CREATE LOGIN lqeDBuser
WITH PASSWORD = 'lqeDBpswd';
USE lqe;
exec sp_changedbowner 'lqeDBuser'
GO
ALTER DATABASE lqe COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE lqe SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE ldx
GO
CREATE LOGIN ldxDBuser
WITH PASSWORD = 'ldxDBpswd';
USE ldx;
exec sp_changedbowner 'ldxDBuser'
GO
ALTER DATABASE ldx COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE ldx SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE gc
GO
CREATE LOGIN gcDBuser
WITH PASSWORD = 'gcDBpswd';
USE gc;
exec sp_changedbowner 'gcDBuser'
GO
ALTER DATABASE gc COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE gc SET READ_COMMITTED_SNAPSHOT ON
GO
CREATE DATABASE dw
GO
CREATE LOGIN dwDBuser
WITH PASSWORD = 'dwDBpswd';
USE dw;
exec sp_changedbowner 'dwDBuser'
GO
ALTER DATABASE dw COLLATE SQL_Latin1_General_CP1_CS_AS
GO
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE dw SET READ_COMMITTED_SNAPSHOT ON
GO
In the computer that hosts the applications, create an environment variable named SQLSERVER_JDBC_DRIVER_FILE and point to the JDBC driver. The location of the driver varies depending on your installation.
SQLSERVER_JDBC_DRIVER_FILE =.:Path_to_JDBC_driver/sqljdbc42.jar
The clm_was_config.py script configures and sets up security options so that you can run applications in a WebSphere environment.
Before you begin
Ensure you have completed the following tasks:
Procedure
createJVMCustomProperty(jvm, "DB2Z_JDBC", "/etc/jazz/server/db2z", "")
createJVMCustomProperty(jvm, "ORACLE_JDBC_DRIVER_FILE", "C:\app\user\product\12.2.0\dbhome_1\jdbc\lib\ojdbc8.jar", "")
createJVMCustomProperty(jvm, "ORACLE_JDBC_DRIVER_FILE", "/opt/app/user/product/12.2.0/dbhome_1/jdbc/lib/ojdbc8.jar", "")
createJVMCustomProperty(jvm, "SQLSERVER_JDBC_DRIVER_FILE", "C:\MSSQL\jdbc\sqljdbc42.jar", "")
createJVMCustomProperty(jvm, "SQLSERVER_JDBC_DRIVER_FILE", "/opt/mssql/jdbc/sqljdbc42.jar", "")
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the conf directory.
cd WAS_Profile_Dir\bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/Jazz_Install_Dir/server/was/clm_was_config.py C:/Jazz_Install_Dir/server/conf
cd WAS_Profile_Dir/bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /opt/Jazz_Install_Dir/server/was/clm_was_config.py /opt/Jazz_Install_Dir/server/conf
cd WAS_Profile_Dir\bin
stopServer.bat server1 -user WAS_USER -password WAS_PASSWORD
startServer.bat server1
cd WAS_Profile_Dir/bin
./stopServer.sh server1 -user WAS_USER -password WAS_PASSWORD
./startServer.sh server1
Before you begin
About this task
uses J2EE container managed authentication for login and system permissions. For application server to work, you must configure a realm with the application server. The file-based user registry is useful for testing or evaluation, because does not support importing users or mapping user roles. For the full application functionality, including viewing system user roles and importing users, supports an LDAP realm.
Configure the federated repositories
Setting up groups and users
To be able to run , you need to define groups and users in the repository and map them to Jazz groups. Before installing any applications, you must create the user groups.
Note: In a distrubuted environment that the is not already setup, you must perform these steps on each application server.
Before you begin
Ensure you have completed the following tasks:
Procedure
-Xmx4g -Xms4g -Xmn1g
-Xgcpolicy:gencon -Xnocompressedrefs
-Xmx4g -Xms4g -Xmn1g
-XX:MaxPermSize=768M -XX:ReservedCodeCacheSize=512M -XX:CodeCacheMinimumFreeSpace=2M
-Xmx4g -Xms4g -Xmn1g
-Xgcpolicy:gencon -Xcompressedrefs
-Xgc:preferredHeapBase=0x100000000
Tip: If you need more heap size, then you can use the following setting, replacing {N} with the amount of memory to be used and {N/4} with 1/4 of the total memory. For example, if -Xmx is set to 8g, -Xmn should be set to 2g.
-Xmx{N} -Xms{N} -Xmn{N/4}
For only: The -Xmn value should be 33% of the -Xms value. For example, if the -Xmx size is 4gb, the -Xmn should be 1365m. The following Deployment wiki document contains useful information about sizing and tuning: Sizing and tuning guide for .
For only: If application pages become unresponsive as a result of memory issues, see this technote for troubleshooting.
In a distributed environment, when you are using a separate application server for each web application, you must add these custom properties for each instance of the .
To avoid problems, do not use spaces in file paths. You can use double quotation marks to enclose the path.
Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:///). For more information about Oracle Java Database Connectivity (JDBC) connections, see
Set up the database
step.
Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:///). For more information about SQL Server JDBC connections, see
Set up the database
step.
The settings that the startup_log4j.properties file contains are used at the early stages in the startup process to pass messages to the SystemOut.log file. After the early stages, each Jazz application switches to using the application-specific settings from the Jazz_Install_Dir/server/conf/app_context/log4j.properties file.
You can use clm_deploy.py or clm_deploy_distributed.py in a distributed environment to deploy application WAR files.
Before you begin
Ensure that , , and applications are installed prior to running the script.
Complete the following steps to map the security roles to your LDAP groups. Note that the groups must be setup on the LDAP server prior to completing this mapping.
The following example shows the role mapping for the application. Replace the values with the values from your LDAP server. You might need to contact your LDAP Administrator to obtain this information:
Note: Ensure that the JazzAdmins, JazzUsers, JazzGuests, and JazzProjectAdmins security groups do not have any spaces in their names.
RoleMapping = {
'ccm' : {
'JazzAdmins' : {
'mappedUser': None,
'mappedGroup': "cn=JazzAdmins,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
'JazzUsers' : {
'mappedUser': None,
'mappedGroup': "cn=JazzUsers,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
'JazzGuests' : {
'mappedUser': None,
'mappedGroup': "cn=JazzGuests,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
'JazzProjectAdmins' : {
'mappedUser': None,
'mappedGroup': "cn=JazzProjectAdmins,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
RoleMapping = {
'qm' : {
'JazzAdmins' : {
'mappedUser': None,
'mappedGroup': "cn=JazzAdmins,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
'JazzUsers' : {
'mappedUser': None,
'mappedGroup': "cn=JazzUsers,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
'JazzGuests' : {
'mappedUser': None,
'mappedGroup': "cn=JazzGuests,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
'JazzProjectAdmins' : {
'mappedUser': None,
'mappedGroup': "cn=JazzProjectAdmins,cn=members,o=ldap.server.com",
'AllowAccessToEveryone':'No',
'AllowAccessToAllAuthenticatedUsers':'No'
},
About this task
The clm_deploy.py script installs all application WAR files that are available in the webapps directory into a single node.
The clm_deploy_distributed.py script can be used to install any application WAR files that are available in the webapps directory, if you specify them in your command argument as a comma-separated list.
Note: The web archive applications must have a .war extension.
Procedure
To deploy applications on a single , complete this step:
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the webapps directory.
cd WAS_Profile_Dir\bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/Jazz_Install_Dir/server/was/clm_deploy.py nodeName server1 C:/Jazz_Install_Dir/server/webapps -config C:/Jazz_Install_Dir/server/was
cd WAS_Profile_Dir/bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /opt/Jazz_Install_Dir/server/was/clm_deploy.py nodeName server1 /opt/Jazz_Install_Dir/server/webapps -config /opt/Jazz_Install_Dir/server/was
To deploy applications in a distributed environment, complete this step:
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the webapps directory.
cd WAS_Profile_Dir\bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/Jazz_Install_Dir/server/was/clm_deploy_distributed.py nodeName server1 C:/Jazz_Install_Dir/server/webapps ccm,qm -config C:/Jazz_Install_Dir/server/was
cd WAS_Profile_Dir/bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /opt/Jazz_Install_Dir/server/was/clm_deploy_distributed.py nodeName server1 /opt/Jazz_Install_Dir/server/webapps ccm,qm -config /opt/Jazz_Install_Dir/server/was
To start the deployed applications, restart the application server. Replace server1 with the name of your application server:
cd WAS_Profile_Dir\bin
stopServer.bat server1 -user WAS_USER -password WAS_PASSWORD
startServer.bat server1
cd WAS_Profile_Dir/bin
./stopServer.sh server1 -user WAS_USER -password WAS_PASSWORD
./startServer.sh server1
Note: In a distrubuted environment you must deploy the application .WAR file on the dedicated application server.
Before you begin
Procedure
Depending on the applications that you installed, the following web applications might be available for deployment:
The following applications must have the same authentication methods for their users and use the same security group mapping as :
Procedure
These repository groups are associated with every Jazz implementation and must be mapped to a particular group that contains the authorized users. If you are using LDAP, these groups must be set up on the LDAP server prior to completing this mapping. If you are mapping these repository groups to individual users, select the repository group and click Map Users.
Note: If in the future there will be changes to the LDAP configuration level, you must remap the security roles to the user or repository group for and other installed applications.
If you are using version 9.x, you must update the JAX-RS settings before you can use the application:
A green arrow should appear that indicates the application is successfully started.
Note: The Converter application is supported only on Windows and Linux. For installation instructions on other unsupported platforms, see the
Delegated Configuration
section of Converter Application Configuration and Troubleshooting Guide.
For information about updating the profile, see Configuring the server on IBM i.
Configure your to use LDAP registry to authenticate users.
Before you begin
If you use LDAP for user management and you enable the option to not use case-sensitive user management, make sure that is also configured to allow user management that is not case sensitive. To configure the login property after you start the server, on the Advanced Properties page of the Administrative web interface, modify the Use case insensitive user ID matching property.
Procedures
In a distributed environment when you are setting up a new for your new application, you must copy the ldapUserRegistry.xml file from or any other srerver that is already configured for LDAP and use it in your new server.
Before you begin
If your new server has not been started yet and the JazzInstallDir/server/liberty/servers/clm directory does not exist, open a command prompt and enter the following command to create the server:
cd JazzInstallDir\server
server.startup.bat -create
cd JazzInstallDir/server
./server.startup -create
Procedure
You can now start the server.
cd Jazz_Install_Dir\server
server.startup.bat
cd Jazz_Install_Dir/server
./server.startup
Type the user ID of the functional user that will perform background tasks. automatically suggests a user ID that you can use, or you can click Browse and search for an existing one. The functional user ID does not have to exist in the external registry; if the user ID does not exist in the repository, it is automatically created.
Note: When Jazz Security Architecture single sign-on (SSO) is enabled in Jazz Team Server, the user interface differs. There is not a Consumer Secret field. After you complete the Application Name and Discovery URL fields, several fields are displayed. If the application also has Jazz Security Architecture SSO enabled, an Authorization Server Credentials section is displayed with the following fields: Authorization Server URL (read-only field), Administrator User ID, and Administrator Password. You must complete the latter two fields. If the application does not have Jazz Security Architecture SSO enabled, then the Consumer Secret and Re-type Secret fields are displayed. You must complete these fields.
You can use the registerApp repository tools command-line to register an application with an existing . With this method, you must provide a .properties file that contains all the required configuration parameters to register an application including the database connection parameters.
cd Jazz_Install_Dir\server
repotools-jts.bat -registerApp repositoryURL=https://hostname.example.com:9443/jts adminUserId=admin adminPassword=**** parametersFile=C:\app.properties
cd /opt/Jazz_Install_Dir/server
./repotools-jts.sh -registerApp repositoryURL=https://hostname.example.com:9443/jts adminUserId=admin adminPassword=**** parametersFile=/opt/app.properties
To learn about the registerApp repository tools command, see Repository tools command to register an application.
To configure the , see Configuring the connector.
For detailed instructions about activating configuration management and enabling project areas including a link to obtain an activation key, see Getting started for application administrators.
Note: Installation of is not supported on Windows platforms.
provides secure, rapid, bidirectional messaging for the Internet of Things (IoT) and mobile environments. is a high performance MQTT broker.
Procedure
To install a non-Dockerized version of , follow these steps:
Note: An IBMid is required to access these files. If you do not have an IBMid, you will be prompted to create one before you can download .
About this task
You can use the URL http://server:Port to connect to the Web UI. This task uses https://10.10.2.149:9087/ to connect to the Web UI. To use this URL, your Web UI container must be running on the host with IP address 10.10.2.149.
You must accept a certificate and server certificate before you can start using the Web UI. You must change both of these certificates if you move from a non-production to a production environment.
Procedure
Note: To prevent repeatedly having to accept certificates, you can replace the default certificate with your own appropriately signed certificate. For information about specifying your own certificate, see Changing the Web UI security certificate.
uses organizational configuration objects called hubs to define configuration policies.
Procedure
After you installed and configured , you must add the MQTT broker URI in the Advanced Properties section of the administrative Web UI:
Procedure
To learn about other configuration settings for multiple GCM instances, see Configuring multiple GCM instances.