This topic describes how to configure and customize Rational
Change Management Server (CM Server).
CM Server is installed with a default configuration that is suitable
for most sites. Some sites might need to modify the CM Server configuration
after installation to accommodate various host-specific or site-specific
requirements. For example:
- Changing the HTTP port numbers
- Changing the logging defaults
- Configuring access to CM Server from another WAN server that functions
as a proxy
- Configuring secure sockets
The WebSphere Application Server administrative console supports
managing SSL certificates. Connect to the console and find information
about using it at the following URL:
http://host_name:12060/ibm/console
If you are using Open SSL certificates and are upgrading your point
product, see Converting Open SSL certificates to IBM SSL. For information
on managing SSL certificates with WebSphere® Application
Server, see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp.
You can customize the CM Server by setting available MBean attributes.
See Setting available MBean attributes.
Attention: Do not modify any CM Server configuration files
other than those described in the help. Modifying some configuration
options can adversely affect the operation of CM Server.
Configuring CM Server to use ClearQuest
You
must install and configure ClearQuest with the CM Server for ClearQuest
Web feature for ClearQuest Web clients and ClearCase Remote Clients
(CCRC) to access databases. You must also create connections to schema
repositories by using the Maintenance Tool.
When using the
Maintenance Tool on a CM Server host that is running on Windows, follow
these rules to ensure that ClearQuest Web client and CCRC users can
access all schema repositories for which connections were created:
- Only run the Maintenance Tool from a local user account that is
part of the local admin group. Do not use a domain user account to
run the Maintenance Tool.
- Run the Maintenance Tool from the same user account each time
you create a connection.
Restrictions
The following restrictions
apply to the CM Server host.
- On Windows:
- When the CM Server host is running on Windows, operations that
are subject to ClearCase permissions checking are not supported when
run from within Rational ClearQuest hooks. These operations run with
the identity of the local system account (NT AUTHORITY/System), which
might not have the required ClearCase permissions.
- On the UNIX system and Linux:
- You must provide approximately 100 MB of swap space per active
ClearQuest user. There must be sufficient physical memory to accommodate
approximately ten percent of the swap space.
If ClearQuest is not
installed in the default location on the server, you must specify
the location where ClearQuest is installed by setting the ccrcUnixCqHome MBean
value. For more information about setting MBean values, see Setting available MBean attributes.