Running the Jazz Team Server setup wizard for Rational Engineering Lifecycle Manager applications

You will need to go through the configuration wizard for each Rational® Engineering Lifecycle Manager application you installed on a separate machine. For example, if you have installed Rational Engineering Lifecycle Manager and the Configuration Management application on one machine, and the Lifecycle Query Engine on another machine, you will run this wizard for both Jazz™ Team Server: https://RELM_fully_qualified_host_name:9443/jts/setup and https://lqe_fully_qualified_host_name:9443/jts/setup. The instructions in this topic use the Rational Engineering Lifecycle Manager JTS as the example, but the Lifecycle Query Engine can be configured in a similar way.

Before you begin

Procedure

  1. In a web browser open https://RELM_fully_qualified_host_name:9443/jts/setup
  2. Log into Jazz Team Server as ADMIN/ADMIN (case-sensitive)
  3. On the Setup page select Custom Setup and click Next.
  4. Read the Introduction page and click Next.
  5. On the Public URI page enter https://RELM_fully_qualified_host_name:9443/jts and check I Understand then click Next.
  6. On the Configure Database page, enter the information for your database. Derby is the default database, but DB2 and Oracle are also supported. Test the connection and then click Next.
  7. On the Email Notification page leave notification disabled and press Next
  8. On the Register Applications page, any application sharing the JTS should be pre-filled. Record the discovery URLs and functional user IDs. Any JTS-based applications installed on remote machines should be added to this list manually, and later you will set up a friend relationship between them as described in Configuring OSLC consumers. Click Register Applications.
    List of pre-filled applications to register.
    If the Lifecycle Query Engine is on a different Jazz Team Server, you will need to add it manually to the Rational Engineering Lifecycle Manager:
    • Application Instance: /lqe
    • Application Type: Lifecycle Query Engine
    • Discovery URL: https://[lqe_hostname]:9443/lqe/scr
    • Functional User ID: lqe_user
    You can also add this at a later time at this URL: https://relm_host_name:9443/jts/admin#action=com.ibm.team.repository.admin.registeredApplicationsSince DOORS® Web Access will always be remote from your Jazz Team Server, you will need to add it manually to the Rational Engineering Lifecycle Manager JTS:
    • Application Instance: DWA
    • Application Type: IBM Rational DOORS Web Access
    • Discovery URL: https://dwa_host_name:9443/dwa/public/scr
    • Functional User ID: rm_user
    You can also add this at a later time at this URL: https://RELM_fully_qualified_host_name:9443/jts/admin#action=com.ibm.team.repository.admin.registeredApplications
  9. On the Setup User Registry page, select to use Tomcat as your user database, and create a user ID and password.
    Selecting your user registry user ID
    Select the Disable default ADMIN access check box. This will disable the ADMIN/ADMIN user id and password you are using for this initial setup. If you choose not to select this, you should change the password as soon as the Jazz Team Server setup is complete. From the list of applications registered to this Jazz Team Server, select Rational Engineering Lifecycle Manager and any other application you want to be administered by this user ID.
    Selecting to administer applications
  10. On the /vvc Configure Database page select the database you will use for storing the Configuration Management application data, finalize the application, and click Next.
  11. On the /relm Configure Database page select the database you will use to store your Rational Engineering Lifecycle Manager data, finalize the application, and click Next
  12. The Summary page should look similar to the following; review the information then click Finish.

Results

You can test your newly created user ID at https://RELM_fully_qualified_host_name:9443/jts/admin

What to do next

Once you have configured your JTS server, there are some advanced settings that you must update:
  1. Open the administrative console at: https://RELM_fully_qualified_host_name:9443/jts/admin
  2. On the Server Administration home page click Server.
  3. Under Configuration > Advanced Properties look for the OAuth access token timeout field.
  4. Change the value to 86400 seconds and click Save.

Feedback