A customer wanted to temporarily disable the already installed IBM Connections Content Manager (CCM) component. Here are the steps to do that:

  • On Deployment Manager, start WSADMIN client:cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
    ./wsadmin.sh -lang jython -user _websphere_admin user_ -password _password of wasadmin user_
  • Run the following commands on theWSADMIN console to checkout the LCC configuration file:execfile(“connectionsConfig.py”)
    LCConfigService.checkOutConfig(“/tmp”, AdminControl.getCell())
  • Disable the IBM Content Manager application by running the following commands on theWSADMIN console:LCConfigService.updateConfig(“ecm_files.enabled”, “false”)
    LCConfigService.updateConfig(“ecm_files.ssl.enabled”, “false”)
  • Check in the LCC configuration file again, synchronize all nodes and leave theWSADMIN prompt:LCConfigService.checkInConfig()
    synchAllNodes()
    exit
  • Restart all Connections clusters
  • If you want to enable the applications later again, use the same commands but change the value “false” to “true”.

After I did that, I sawe the following error messages in the SystemOut.log of the server where CCM was installed:

[codesyntax lang=”text”]

[/codesyntax]

The reason for that was, that there were still some unprocessed notification events in the queue which could no longer processed as the application has been disabled. To remove these events I ran the following commands:

  • On Deployment Manager, startWSADMIN client:cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
    ./wsadmin.sh -lang jython -user _websphere_admin user_ -password _password of wasadmin user_
  • Run the following commands on theWSADMIN console:execfile(“communitiesAdmin.py”)
    CommunitiesQEventService.clearQueuedEventsByRemoteAppDefId(“Library”)
  • The command returns the number of cleared events.

Now the error message should no longer be displayed.

IBM Connections: Disable IBM Connections Content Manager (CCM)
Tagged on:             

Leave a Reply

Your email address will not be published. Required fields are marked *