The Administration console that is included with WebSphere® Application Server supports managing SSL certificates. You can connect to the console and find more information on using it at this location: http://hostname:12060/ibm/console.
If you are currently using Open SSL certificates and are upgrading your point product, see the procedures in Converting Open SSL certificates to IBM SSL. For more information on managing SSL certificates with WebSphere Application Server, see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp.
Some attributes in configuration files can be viewed or set as CM Server MBean parameters. See Setting available MBean attributes for more information.
Do not modify any CM Server configuration files other than those described in this user assistance. Some of the configuration options cannot be changed without adversely affecting the operation of CM Server.
If you enable WebSphere Application Server administrative security and deploy the ClearQuest Web component in a separate instance of WebSphere Application Server, you must update some properties in the file cqServerConn.properties.
To enable use of Rational ClearQuest by Rational ClearQuest Web clients and Rational ClearCase remote clients either for accessing ClearQuest databases or for accessing the ClearCase-ClearQuest UCM integration, you must install and configure Rational ClearQuest with the CM Server for ClearQuest Web feature on the CM Server machine.
When your CM Server host is running Windows, operations that are subject to Rational 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 may not have the Rational ClearCase permissions required to perform them.
You must provide approximately 100 MB of swap space per active Rational ClearQuest user. There must be sufficient physical memory to accommodate approximately ten percent of this swap space.
If Rational ClearQuest is not installed in the default location on the server, you must specify the location where Rational ClearQuest is installed by setting the ccrcUnixCqHome MBean value to the full path name to the directory where Rational ClearQuest is installed on the server. For more information about setting MBean values, see Setting available MBean attributes.
echo setting up DB2 environment . DB2-profile-path
On a CM Server machine where ClearQuest is installed (regardless of whether this is done to support accessing ClearQuest functionality from the Rational ClearQuest Web client or from the Rational ClearCase Remote Client), one required setup step is to create connections to the Rational ClearQuest schema repositories that are going to be accessed from a client or clients.