Tip:
Highlight text to annotate it
X
If you tested with Snoop, when you request the setup process you will not be challenged to authenticate with your WebSphere admin user.
This is because there is a Single Sign-On (SSO) configuration applied to the application server.
You will also notice that express setup is no longer available when using an IBM HTTP Server configuration. This is because
the Derby database is no longer reachable from the HTTP server.
The first panel for the session is the introduction panel. Read all the information on each of these panels. If you have any doubt on the information,
pause the setup and confirm your configuration points. At this point, the public URI is derived from the browser
URL you use.
In this example, it is "clmserver.ibm.com" which is expected. Test the connection and review that the public URI is what you expect.
Click Next.
First step is to setup the Jazz Team Server (JTS) database.
Select the database vendor Oracle and leave the connection type as JDBC.
Using the sample connection string on this page, paste it in the JDBC location
and update the values that are pertinent to the database configuration. In this case, it will be "JTSUSER".
Modify the "localhost" to "oraexample.ibm.com" and update the database name to "CLM2012".
Then update the password field.
Test the connection.
Step 3 appears if the database connection is configured correctly and the database
is an empty database. Click the Create Tables button.
With time, the "Database tables created successfully" message occurs.
If you have an error message, you must stop the setup process at this point and try to correct the
error displayed on the page.
Move to the next page.
E-Mail Notification is not configured in this example. Click Next.
By default, setup uses the default URI to complete the context and SCR location for each of the applications.
This is why you must test the SCR locations: To make sure they are reachable. Otherwise, this page might fail because it cannot reach one or
another of the servers.
It is possible that the discovery URL is not the expected CLM server.
Make sure that the URL for each of the applications is specific to the URL you are targeting.
In this case, all the applications are in "clmserver". You can now register the applications.
Click Next.
Next configuration point is to setup the User Registry.
Choose LDAP.
In the first field for the LDAP registry location, place the "clmexample" server which is where the LDAP directory exists on port 1085.
The user name is taken from the WebSphere configuration "Bind distinguished name".
You can eventually use the Base distinguished name for some configurations points in the Setup Registry configuration.
The user name will be the Bind distinguished name. Use a fully qualified name.
Include the password.
For Base User DN, use the
Base distinguished name in the WebSphere configuration.
Also validate that the user ID maps with the UID in LDAP, the name to the CN, and the
email to the email. This attributes can change depending on your user registry.
Update the Base Group DN with the entry point to the LDAP directory tree. Review the Jazz Group Mapping.
The Group Member Property must be set to the attribute that defines the user to the groups in LDAP.
You can opt out of disabling ADMIN access, especially in a test system. This is not a recommended practice in a production system.
Next, activate one license. It can be a Rational Requirements Composer analyst or a Rational Quality Manager professional tester.
In this case, a Rational Team Concert developer license for the Jazz admin user.
Click Next.
This is the configuration for the Data Warehouse.
Select Oracle, as that database is used in this example.
Provide the JDBC URL for the JDBC Location field.
In this case, it will be "DWUSR"
on "oraexample.ibm.com" with database "CLM2012".
Note the Database Table Space Folder.
This folder exists not in the JTS environment, but on the database machine.
This path is a location for the creation of data files for the Data Warehouse itself.
Four data files are created and one temporary data file in this particular directory.
This directory must also exist on the Oracle database file system.
Keep the default "RPTUSER" as the user for the Data Warehouse.
Do no update any user ID information. In this example, you are using "OAuth" processes.
Once you have tested your database connection, you can now create the tables.
After some time, the database creation is complete. Click Next.
Next is the Cnange and Configuration Management (CCM) configuration point. As with the JTS database, copy the URI string
and update the password with the right values.
In this case, the JDBC location is now using the "CLM2012" database with the "CCMUSER" for the user and "oraexample.ibm.com"
as the database instance.
One you have the right value in place, test the connection to make sure the connection string is good.
The Create Tables button appears when you have confirmed a working connection to the database.
Once the database is complete, click Next.
This panel is for finalizing the CCM configuration. Finalization ensures
that the crossover communication between JTS and CCM applications are in working condition.
Next step is to configure the CCM Data Warehouse. In this context, you do not need to update the values.
Setup should prepopulate with the JTS data. Confirm the password.
Test the connection to the Data Warehouse for the CCM application in order to update the JTS properties
files for the CCM application.
When the test is complete, click Next.
Now to configure the Quality Manager (QM) application database. As with the previous
databases, update the JDBC location and password.
Use the same "CLM2012" database. The distinction is that you use "RQMUSR".
One you complete the test, create the tables.
Once the tables are created, click Next.
Begin the finalization process to make sure that the JTS and QM cross communication
between the two servers is working correctly.
Input the Data Warehouse password to make sure that the QM
application within the JTS properties has the right configuration to connect to the database.
Once you test the connection, click Next.
Now for the Requirements Management (RM)
application finalization. There is no database configuration. Just finalize the setup for RM, as it will utilize the JTS database.
Once this step is complete,
click Next. The next step is the finalization of
the Lifecycle Project Administration (LPA).
You might receive a message from the pop-up blocker in your browser.
This is because setup is trying to authenticate against all applications registered in the past steps.
If the pop-up is blocked, you will see an Authorize button. This button authorizes LPA
to authenticate against all repositories configured in past steps.
After dealing with any pop-up blocker issues, finalize the application setup.
Once finalization is complete, click Next.
This is the message that you succeeded in setting up your JTS environment.
Once complete, you can review you Jazz home for any specific area
that might be problematic.
Expand the home menu to see if all the applications are listed.
If you can see all applications, then JTS is able to work with those applications.
If you did not set NTP server, you will get a warning message. Otherwise, check for errors in the Diagnostics page.
This this case, there are none.
You can also try to import users from the LDAP registry.
In this example, a syncronization task has already occured. Users have been prepopulated.
This indicates that the LDAP configuration within JTS setup is successful.