r2 - 2020-06-02 - 15:14:20 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentMonitoring > CLMServerMonitoring > CLMServerMonitoringAgent > CLMServerMonitoringAgentReset

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

Authors: TWikiUser, TWikiUser
Build basis: Products, editions, or versions that apply to the content. If no build basis applies to this content, set the build basis to None.


Why to reset a CLM Server Monitoring Agent


Alternatives to resetting a CLM Server Monitoring Agent


Remove the current installation and Install a new Server Monitoring Agent.

Instructions for resetting a CLM Server Monitoring Agent

Instruction example presumptions

  • Operating System is Linux (you may need to switch / to \, and otherwise change path information, and use repotools-csm.bat instead of sh ./repotools-csm.sh to correctly enter data on Window).
  • Hosting CLM Server Monitoring Agent on a standalone WebSphere application server at /opt/IBM/WebSphere/AppServer/AppSrv02 on server 1 with username admin and password password. (Your AppServer name may be AppSrv01 instead, a different server other than server1, and need a different username and password than listed in the example.)
  • /csm is the application path assigned to the CLM Server Monitoring Agent in WebSphere Application Server.
  • The HTTPS port is 9444 in WebSphere Application Server.
  • The in use server host name for WebSphere Application Server is lab4809.site.
  • Installation of CLM Server Monitoring Agent is in /opt/IBM/CSMAgent5.0.2 * Operating as a user with enough system priviledges for the listed instructions.

Note: you will need to reload any newer licenses as well, as the previous licensess with the product build may have expired previously. This is consistent with a new install of CLM Server Monitoring Agent 5.0.1 or 5.0.2.


  1. Issue the stop server command as appropriate for the WebSphere Application Server hosting the /csm application.
    • /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/stopServer.sh server1 -profileName AppSrv02 -username admin -password password
  2. In /opt/IBM/CSMAgent5.0.2/server/conf/csm/teamserver.properties change the following properties to these values.
    • com.ibm.team.repository.setup.completed.setup=false
    • com.ibm.team.repository.ws.allow.admin.access=true
    • com.ibm.team.repository.server.webapp.url=https\://lab4809.site\:9444/csm
  3. These are the commands to run, once the csm application server is shut down, for a windows install
    1. cd /opt/IBM/CSMAgent5.0.2/server
    2. sh ./repotools-csm.sh -resetRepoLockID
    3. sh ./repotools-csm.sh -dropTables
  4. restart the "/csm" host WebSphere application server using
    • /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin/startServer.sh server1 -profileName AppSrv02
  5. Once the server has reported starting successfully, use a browser to access https://example.website.site:9444/csm/setup.
    1. use Custom setup.
    2. Assure Configure Public URI (setup step 2) has its Step 1 (Configure Public URI) has a port number in the URI.
    3. On setup step (3) for the Database, Create Tables button will need to be used, because we dropped the original tables
    4. , Continue Setup as before until Finished.
  6. Continue CLM Server Monitoring configuration.

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: 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.