Database
|
Data Items Needed
|
Description
|
Data
|
Comments
|
DB2
|
Names of databases
| |
|
|
Path
|
| |
|
URL including port number
|
Found in the teamserver.properties file typically as: com.ibm.team.repository.db.vendor, com.ibm.team.repository.db.jdbc.location and com.ibm.team.repository.db.jdbc.password
| |
|
Admin user account privilege and password for all databases
|
In the UNIX systems, get the password for the DB2 instance owner, which is typically the db2inst1 user.
| |
|
Location of where you can create a backup database.
| | | |
If using the datawarehouse, will need path name for database table space folder.
|
| |
|
If using the datawarehouse, type the login information for a functional user that will run the data collection jobs.
|
This user id must exist in your user registry. Note: The User ID that you enter for the functional user must be a different ID than the administrative user that you are currently using to configure the application.
| | |
Oracle
|
Names of databases
| |
|
|
Path
|
| |
|
URL including port number
|
| |
|
Admin authority for user account privilege and password for all databases
|
Must have 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.
| |
|
You must create a separate tablespace and database user who is associated with that tablespace for each application.
|
- CCM DB user id
- RQM DB user id
- RRC DB user id
| | |
If using the datawarehouse, will need path name for database table space folder.
|
| |
|
If using the datawarehouse, type the login information for a functional user that will run the data collection jobs.
|
This user id must exist in your user registry. Note: The User ID that you enter for the functional user must be a different ID than the administrative user that you are currently using to configure the application.
| | |
Microsoft SQL Server |
User ID and password for creating databases.
|
The user who creates the database table must be a member in the sysadmin fixed server role, or an owner of the database (dbo).
| | |
Names of databases
| | | |
Paths
| | | |
URLs including port number
| | | |
Admin authority for user account privilege and password for all databases
| | | |
You must create a separate tablespace and database user who is associated with that tablespace for each application.
|
- CCM DB user id
- RQM DB user id
- RRC DB user id
| | |
If using the datawarehouse, will need path name for database table space folder.
| | | |
If using the datawarehouse, type the login information for a functional user that will run the data collection jobs. |
This user id must exist in your user registry. Note: The User ID that you enter for the functional user must be a different ID than the administrative user that you are currently using to configure the application.
| | |
Application Server
|
|
|
|
|
WebSphere Application Server
|
URL, admin user account privilege and password.
| |
|
|
Path name to location of war files |
Found in WebSphereInstall/AppServer/profiles/profile/bin
| | |
User name and password with admin authority in the Integrated Solutions Console
| | | |
Name of application server which contain the war files prior to upgrade
| | | |
Name of application server to contain the war files once the upgrade is deployed
| | | |
Security roles mapped to jts_war
| | | |
Security roles mapped to ccm_war
| | | |
Security roles mapped to qm_war
| | | |
JAZZ_HOME |
Do the following steps from the Integrated Solutions Console to locate the information:
1. 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.
| | |
Tomcat
| Public URI |
As defined in the teamserver.properties file for com.ibm.team.repository.server.webapp.url
| | |
Database vendor |
As defined in the teamserver.properties file for com.ibm.team.repository.db.vendor
| | |
Database location |
As defined in the teamserver.properties file for com.ibm.team.repository.db.jdbc.location
| | |
Application home |
Full path to the RTC version 2 or CCM version 3 server configuration directory. The path must not contain any spaces. The default is /server/conf
| | |
Port numbers for the Jazz Team Server and CLM applications
| May be found in the server.xml file located at the path InstallDirectory/server/tomcat/conf |
|
|
Administrative ID and password. |
This ID and password must work in the previous version from which you are upgrading and reside in the tomcat-users.xml file.
| | |
User ID, name, password, and e-mail Address of the user who will have administrative access to the Jazz Team Server after the upgrade.
| This user must reside in the registry. | | |
Reverse Proxy Server
|
CLM Solution: |
URL, port number, context roots for all CLM applications:
|
See the following for more information:
https://jazz.net/library/article/744 and https://jazz.net/library/article/745
https://jazz.net/library/article/744
| | |
CCM |
Inbound client request URL to proxy server for CCM
| | | |
Forwarded client request URL from proxy server for CCM
| | | |
RM |
Inbound client request URL to proxy server for RM
| | | |
Forwarded client request URL from proxy server for RM
| | | |
QM |
Inbound client request URL to proxy server for QM
| | | |
Forwarded client request URL from proxy server for QM
| | | |
JTS |
Inbound client request URL to proxy server for JTS
| | | |
Forwarded client request URL from proxy server for JTS
| | | |
CLM Applications
|
| |
|
|
Jazz Team Server
|
Path for the installation directory of the Jazz Team Server package.
| | | |
Path for the new installation directory of the Jazz Team Server package.
| | | |
URLs for the server and each application, including port numbers and context root
|
Value found in teamserver.properties file for "com.ibm.team.repository.server.webapp.url". If this value is not set, it must be set using the administrative web interface.
|
|
|
ID and password with Admin privileges (JazzAdmin)
|
Provide the user ID, name, password, and e-mail Address of the user who will have administrative access to the Jazz Team Server
| |
|
Name
| | | |
Email
| | | |
Location of configuration files:
- teamserver.properties
- services.xml
- log4j.properties
- provision_profiles
|
Found in the path: Install Directory/conf/application
| | |
CM |
URL including port numbers and context root
| | | |
ID and password with Admin privileges
| | | |
RM |
URL including port numbers and context root
| | | |
ID and password with Admin privileges
| | | |
QM |
URL including port numbers and context root
| | | |
ID and password with Admin privileges
| | | |
RRDI |
URL including port numbers and context root
| | | |
ID and password with Admin privileges
| | | |
User Management
| | | | |
LDAP (General) | LDAP Registry Location |
See: http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_plan_identity_management.html for more information on LDAP parameters.
| | |
LDAP User Name
| | | |
LDAP Password
| | | |
Base User DN
| | | |
User Property Names Mapping
| | | |
Base Group DN
| | | |
Group Name Property
| | | |
Group Member Property
| | | |
Jazz to LDAP Group Mapping |
- JazzAdmins =[LDAP Group for Jazz admins]
- JazzUsers =[LDAP Group for Jazz users]
- JazzDWAdmins =[LDAP Group for Jazz Data Warehouse Admin]
- JazzGuests =[LDAP Group for Jazz guest] (Not used by Rational Quality Manager)
- JazzProjectAdmins =[LDAP Group for Jazz project admins]
See http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/c_plan_identity_management.html for more information. | | |
LDAP Local Group Realm for Tomcat
|
Path name and location of LDAP Local file
| | | |
Connection URL |
Obtain these three values from your LDAP Administrator. These values are from your LDAP directory.
See http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/t_config_ldaplicalgroup.html for more information.
| | |
User Base
| | | |
User Search
| | | |
License Management
|
| |
|
|
Floating license | Administrative user with a license |
If your Jazz Team Server application acted as a floating license server for multiple version 2 servers, you must reinstall your license keys.
| | |
Jazz Team Server that is the floating license server and has the Client Access License (CAL) keys installed. |
You will need the URL containing the fully qualified DNS hostname and port number. For example: http://floating-license-server:9443/jts where "floating-license-server" contains the DNS domain of the machine.
For more information: http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/tmanagefloatinglic.html
| | |
Jazz Team Server that assigns the floating Client Access License (CAL).
| This server points to the floating server. | | |
Client access license keys | URL with a fully qualified DNS host name including port number. The fully qualified host name includes the DNS domain reference of the machine on which the Jazz Team Server is installed. |
Example: https://[fully qualified hostname]:9443/jts/admin
For more information: http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.repository.web.admin.doc/topics/tmanagelicensekey.html
| | |
Location of the license activation key.
| | | |
The number of purchased licenses.
| | | |
Email Settings
| | | | |
|
SMTP server
| | | |
SMTP port
| | | |
SMTP user name and password
| | | |
Name and email address for the "From" field on email.
| | | |