Configuring the Money that Matters sample environment

As an administrative user, configure the Money that Matters sample environment, so that you can complete the tasks in the Money that Matters lifecycle scenario tutorial.

Before you begin

You have installed the Money that Matters sample project. For more information, see Installing the Money that Matters sample.

Assigning licenses to sample users

About this task

Sample users are created without assigned licenses. Assign each user a license, as described in the following table.
Note: You can automatically assign licenses by using a custom sample script. License identifiers are: com.ibm.rqm.tester and com.ibm.team.rtc.developer.

Primary users in the Money that Matters lifecycle scenario tutorial.

User ID Name Email Password Permissions License

bob

Bob

bob@jkebanking.net

bob

JazzUsers

Analyst

marco

Marco

marco@jkebanking.net

marco

JazzUsers

Developer, Quality Professional

deb

Deb

deb@jkebanking.net

deb

JazzUsers

Developer

tanuj

Tanuj

tanuj@jkebanking.net

tanuj

JazzUsers

Quality Professional

rebecca

Rebecca

rebecca@jkebanking.net

rebecca

JazzUsers

Developer

build

build

build@jkebanking.net

build

JazzUsers

Build System

Secondary users in the Money that Matters lifecycle scenario tutorial. Assigning client access licenses to these users is optional.

User ID Name Email Password Permissions License

ursula

Ursula

ursula@jkebanking.net

ursula

JazzUsers

Analyst

curtis

Curtis

curtis@jkebanking.net

curtis

JazzUsers

Contributor (any type)

tammy

Tammy

tammy@jkebanking.net

tammy

JazzUsers

Quality Professional

sally

Sally

sally@jkebanking.net

sally

JazzUsers

Analyst

al

Al

al@jkebanking.net

al

JazzUsers

Design Manager

Optional setup for developer exercises

About this task

This section describes how to start the Jazz™ Build Engine and set up an Eclipse environment.

Procedure

  1. Two build engines are automatically created and owned by the JKE Banking (Change Management) project area. The two build engines are jke.dev.engine and jke.production.engine. As the build user, start the Jazz Build Engine, so that you can run builds. For example, start the Jazz Build Engine with the following arguments: jbe.exe -repository https://MY_SERVER_ADDRESS:9443/ccm -engineId jke.dev.engine -userId build -pass build For more information, see Starting and stopping the Jazz Build Engine.
  2. Set up Eclipse client environments for the Deb user.
    1. Open the Eclipse client.
    2. Specify a path for the Deb user sandbox. For example, specify C:\workspaces\deb.
    3. Connect to the repository and the JKE Banking project area. For more information, see Connecting to repositories and project areas.
  3. Repeat step 2 for the Rebecca user.

Optional setup for architect exercises

About this task

This section describes how to set up your Rational® Software Architect environment for the architect exercises.

Procedure

  1. Open the Rational Software Architect client
  2. Specify a path for Al’s workspace. For example: c:\workspaces\al.
  3. Connect to a server project to establish a connection to the repository. For example: https://host-name:9443/dm. Connect to the JKE Banking (Design Management) project area.
  4. Click Window > Open Perspective > Other... and select Work Items (select Show all if you do not see Work Items). Select Always enable activities and don't ask me again and click OK.
  5. Follow steps under 2 to use the Team Concert Eclipse Client.
  6. Close the Rational Software Architect client

Optional setup for tester exercises

About this task

This section describes how to set up an environment to perform the tester exercises.

Procedure

  1. If you plan to link builds to test execution results Configure Rational Team Concert as your build provider.
  2. Enable the automatic unblocking of test cases:
    1. Log on to the Administration page of the Jazz Team Server. In a web browser, navigate to https://fully qualified hostname:9443/qm/admin.
    2. Click Advanced Properties.
    3. In the RQM Change Management Integration section, update the User Name and User Password fields with the administrative user name and password.
    4. In the Delay field, type 120. The default value is 500 seconds.
    5. Click Save.
  3. Before you run the sample application, set the system PATH environment variable to include the folder where the java.exe file is located. You can use the same folder that you used in the -vm option in the jbe command when you started the Jazz Build Engine.

video icon Watch videos

CLM playlist

Jazz.net channel

User Education channel

learn icon Learn more

CLM learning circle

Agile learning circle

Learning circles

ask icon Ask questions

Jazz.net forum

developerWorks forums

support icon Get support

Support Portal

Deployment wiki

Support blog