You can create connections to custom change management
or review systems, such as Bugzilla. Prior to creating a connection,
the repository administrator must have configured the server to use
a custom review process.
Before you begin
You must be a repository administrator or a community administrator
to add a new connection.
About this task
Users of the repository will use these connections to
map an asset or a forum topic to the external change management system
so that it is tracked.
Procedure
- Log in to the Rational® Asset Manager web
application.
- Open the Administration page and select the community you
want to edit.
- Open the Connections page.
- Under Change Management Connections, click New
connection.
- In the Choose Repository Type window, select the name of
the custom review process from the list and click OK.
- On the Repository Connection Details page, complete the
form with the details for your custom review process.
- Name: This is a name that you
provide for the connection. The name can include spaces and special
characters.
- Description: Optionally, you
can create a description of the connection. The description can have
spaces and special characters.
- Schema repository: This is the
database that is used to store and manage a group of schemas including
all versions of those schemas, and their associated user databases.
This list is populated from the list of connections set up in the Rational ClearQuest® Maintenance Tool on the server
machine. The name used for Schema repository should be
the same name configured on ClearQuest server. If a different
name is used, you will not be able to access the information from
the Rational Asset Manager server on the ClearQuest server.
- Database: This is the particular
database within the schema repository that you want to connect to.
- URL: This is where you specify
the fully qualified URL to the custom review process; for example, http://www.example.com/custom_review_process/.
- User name: This is the user ID
of a user who is authorized to access Rational ClearQuest. This user will be the one
who owns any requests opened in the external repository.
- Password: The user's password
for accessing Rational ClearQuest.
- Click OK.