CLM Server Monitoring (DEPRECATED: CLM Server Monitoring is no longer supported and was dropped in version 6.0.3.)

10. In the Add Friend dialog add the information as it applies the JFS server you are adding:
Name: JFS
Root Services URI: https://localhost:9443/jts/rootservices
OAuth secret: secret
Re-type secret: secret
Trusted: checked

11. Click "Create Friend"

On successful completion the following message will appear then click next.



12. Authorize the provisional key. Click "Grant access for the provisional key". You may be asked to log into the JFS application at this point in order to grant access. Use the credentials for the JFS admin user.

13. Approve the request when asked. The "Consumer Name" is what the CSM server will be recognized as in the consumer list.
*If this fails or shows "Forbidden" just proceed to 14*

14. Once finished the friend will be added to Friends List:

15. Go to https://localhost:9443/jts/admin#action=com.ibm.team.repository.admin.configureOAuth .
Go to "Consumers (Inbound)". The CSM server consumer we just added should be listed there.
*If step 13 failed you may have keys to approve in the "Provisional Keys" section. Approve them by selecting "Approve" from the "Authorized" drop down and clicking "Save".*
Click the pencil beside the CSM consumer.

16. Edit Consumer Key Properties and add the JFS Admin user by selecting "Select User..."



and the consumer user added to the consumer list entry on the consumer page.

17. Go to the public IBM WAIT tool at https://wait.ibm.com/ and ensure that there is user name and password that will be use for this environment.

18. Go to https://localhost:10443/csm/admin#action=com.ibm.team.repository.admin.configureAdvanced advanced properties page.
WAIT Server: https://wait.ibm.com/
WAIT Server Email: The email address used in step 17
WAIT Server User: The user used in step 17
WAIT Server Password: The password used in step 17

19. Go to https://localhost:10443/csm/admin#action=jazz.viewPage&id=com.ibm.team.process.ProcessTemplateManagement and click "Deploy Predefined Templates"

20. Go to https://localhost:10443/csm/admin#action=com.ibm.team.process.manageProjectAreas and click "Create a Project Area" and create a new project called "CLM Server Monitoring"

• At a minimum, you will need to add a Jazz Admin user to the project (for JMX Connection User) along with any other users who you want to have access (and have a CSM User CAL).
  
  

• • The connection ID: JFS
  • The connection Name: JFS
  • The connection Type: Choose JSR160 because the application you are trying to monitor is deployed to Apache Tomcat.
  • Select the Jazz user that will be used to create problem records. The user must be assigned a CSM User CAL and be a Jazz Admin user
  • Set *Active": Checked
  • Enter the Host Name: localhost
  • Enter the Port: 1099

28. Click the domain of the activated connection. team.server./jts@9443

29. Ensure that the AllMonitorsEnabled and DiagnosticsEnabled check boxes are selected.

30. Copy/Paste the following rules XML into the Rules tab

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ruleSet>
<!-- Defaults -->
    <rule resourceType="service">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        </action>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
        </action>
    </rule>
    <rule resourceType="db_statement">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        </action>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
        </action>
    </rule>
    <rule resourceType="request">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        </action>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
        </action>
    </rule>
    <rule resourceType="http_client">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        </action>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
        </action>
    </rule>
<!-- Contributor service -->
    <rule resourceType="service" resourceName="com.ibm.team.repository.service.jts.contributor.internal.ContributorRecordUpdateRestService.service">
        <action name="problem">
               <test operator="GT" value="10000" attributePath="duration"/>
        </action>
    </rule>
    <rule resourceType="request" resourceName="/contributorRecords/">
        <action name="problem">
               <test operator="GT" value="10000" attributePath="duration"/>
        </action>
    </rule>
</ruleSet>

32. Go to JTS and run "All diagnostics" by going to https://localhost:9443/jts/admin#action=com.ibm.team.repository.admin.serverDiagnostics and click "Run All Diagnostics"

33. Go to the CSM dashboard at https://localhost:10443/csm/web/projects/CLM%20Server%20Monitoring#action=com.ibm.team.dashboard.viewDashboard

34. Wait for problems to appear in the viewlets. You can refresh the viewlets once in a awhile to see changes.

Related topics: Deployment web home, Deployment web home

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser