Setting up WebSphere Application Server and deploying .WAR file for server monitoring

Use these instructions to deploy the CLM Server Monitoring .csm WAR file on WebSphere Application Server.

Before you begin

If the WebSphere Application Server that is hosting the CLM Server Monitoring feature is not in the same realm as the CLM applications that it is monitoring, you must perform these steps:
  1. Log in to the WebSphere Integrated Solution Console and click Security > Global security.
  2. Expand Java Authentication and Authorization Service and then click Application logins.
  3. Click WSLogin and then click
  4. Ensure that Use login module proxy is selected and use_realm_callback and use_appcontext_callback are set to true.
  5. Setup JAZZ_HOME and
    1. In the WebSphere Integrated Solutions Console, click Servers > Server Types > WebSphere application servers.
    2. Click the server name to open it. The default server name is server1.
    3. Under Server Infrastructure section, click Java and Process Management > Process definition .
    4. Under Additional Properties, click Java Virtual Machine.
    5. Under Additional Properties, click Custom properties.
    6. Click JAZZ_HOME and update its value to file:///CSM_Agent_Install_Dir/server/conf.
    7. Click log4j.configuration and update its value to file:///CSM_Agent_Install_Dir/server/conf/
    8. Save the changes to the master configuration when prompted.
  6. Map security roles to a user or repository group:
    1. In the WebSphere Integrated Solutions Console, click Applications > Application Types > WebSphere enterprise applications > csm_war.
    2. Under Detail Properties, click Security role to user/group mapping.
    3. Map the roles to the user or groups accordingly.
You must also import the CLM application server's certificate into the node default truststore:
  1. In the WebSphere Integrated Solutions Console, click Security > SSL certificate and key management.
  2. In the Related Items section, click Key stores and certificates.
  3. Click NodeDefaultTrustStore and then, in the Additional Properties, click Signer certificates.
  4. Click Retrieve from port and enter the connection information for the CLM application that you will be monitoring:
    • Host: CLM server host, for example,
    • Port: HTTPS port number, for example 9443
    • Alias: An alias for the server that you can remember
  5. After the required information is entered, click Retrieve signer information.

About this task

To configure Websphere Application Server, see Setting up WebSphere Application Server.

To deploy the csm.war application, see Deploying applications for the Rational solution for Collaborative Lifecycle Management on WebSphere Application Server.

video icon Watch videos

CLM playlist channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog