r4 - 2020-06-02 - 15:25:48 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentMonitoring > CLMServerMonitoring > CLMServerMonitoringQuickStart

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

constantchange.png Authors: Boris Kuschel (BorisKuschel)
Build basis: Collaborative Lifecycle Management 5.0 M4 only

CLM Server Monitoring Quick Start

Warning WARNING: DO NOT USE. REFERENCE ONLY! This page is now under reconstruction and does not represent how to quick start with CLM5.0.1 and later, nor any other version but 5.0M4 and should not be used otherwise until this reconstruction is complete Warning

These instructions will help you get a learning environment running. It consists of a JFS/JTS Server and a CSM Agent server.

1. Download the 5.0 M4 Jazz Foundation Server and CLM Server Monitoring Agent (Web Install) installation package from: https://jazz.net/downloads/jazz-foundation/milestones/5.0M4

2. In the launchpad click "Install Jazz Foundation Server" and complete the install of the JFS/JTS server.

3. Modify the server.startup script for JFS found in /server/server.startup by uncommenting the following section:


   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote=true"
   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=1099"   
   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false" 
   JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false" 

Microsoft Windows:

   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote=true
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=1099
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.ssl=false
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.authenticate=false
4. Launch JFS by running the /server/server.startup script 5. Finish running through the JFS setup at https://localhost:9443/jts/setup according the instructions as found in the infocenter for JTS https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/roadmap_form.html

6. In the launchpad click "Install CLM Server Monitoring Agent" and complete the install of the CSM server.

7. Launch CSM by running the /server/server.startup script

8. Finish running through the CSM setup at https://localhost:10443/csm/setup according the instructions as found in the infocenter for JTS (yes, JTS) https://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/roadmap_form.html
*Assign a CSM User Client Access License to the administrator you create in setup.*

9. Go to the CSM Administration page at https://localhost:10443/csm/admin#action=com.ibm.team.repository.admin.friends . Then click the "Add..." link on the right.


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).

21. Click "Save."

22. Assign the "Team Member" role to any users assigned to the project.

23. Click "Save."

24. Go to https://localhost:10443/csm/web/projects/CLM%20Server%20Monitoring#action=com.ibm.team.dashboard.viewDashboard to access the project you created.

25. Select JMX Connections -> Create-> Create Connection.

26. Complete the connection information:
    • 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

27. Click "Save".

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"?>
<!-- Defaults -->
    <rule resourceType="service">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
    <rule resourceType="db_statement">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
    <rule resourceType="request">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
    <rule resourceType="http_client">
        <action name="problem">
               <test operator="GT" value="4000" attributePath="duration"/>
        <action name="javacore">
               <test operator="GT" value="10000" attributePath="duration"/>
<!-- 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"/>
    <rule resourceType="request" resourceName="/contributorRecords/">
        <action name="problem">
               <test operator="GT" value="10000" attributePath="duration"/>

31. Click "Save".

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:

Additional contributors: TWikiUser, TWikiUser

Topic attachments
I Attachment Action Size Date Who Comment
Pngpng Selection_543.png manage 95.1 K 2014-03-25 - 20:56 UnknownUser  
Pngpng Selection_545.png manage 4.0 K 2014-03-25 - 20:57 UnknownUser  
Pngpng Selection_547.png manage 24.2 K 2014-03-25 - 21:14 UnknownUser  
Pngpng Selection_569.png manage 42.1 K 2014-03-25 - 21:01 UnknownUser  
Pngpng Selection_570.png manage 23.5 K 2014-03-25 - 21:09 UnknownUser  
Pngpng Selection_571.png manage 42.9 K 2014-03-25 - 21:17 UnknownUser  
Pngpng Selection_573.png manage 35.5 K 2014-03-25 - 21:30 UnknownUser  
Pngpng Selection_574.png manage 28.0 K 2014-03-25 - 21:34 UnknownUser  
Pngpng Selection_575.png manage 33.9 K 2014-03-25 - 21:35 UnknownUser  
Pngpng Selection_576.png manage 29.3 K 2014-03-25 - 21:41 UnknownUser  
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.