CCM does not come online after installing a custom plugin
2 answers
This means that the installed plugin caused the deletion of some ccm files.
- All applications except CCM are up and running.
- The only change to the server is that the user deployed a custom plugin to CCM.
- Checking Jazz_home? It should be correctly defined in WAS.
- Look at /apps/IBM/JazzTeamServer5.0.2/server/conf/ccm/provision_profiles, NO file exists. In /conf/ccm/sites, there is only one folder, which is the custom plugin that user installed.
- In this case the client need to restore files in both folders.
-ensure the following folders exist in /ccm/sites/
==> enterprise-update-site
==> update-site
==> rtc-commons-update-site
==> js_user_role_condition_provider
CCM also has the following ini and site folder:
==> /ccm/provision_profiles/verify-profile.ini
==> /ccm/sites/verifier-update-site
Try to remove the WAS cache and try restart again:
Steps:
1. Stop WebSphere server
2. Navigate to the WebSphere temporary directory. The location of the
WebSphere's temp folder is...
<WebSphere Install Directory>\AppServer\profiles\<App Server
Name>\temp\<Node name>\<Server name>\
For example,
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/rpmcs11Node01/server1
3. Locate ccm_war and delete the folder
4. Start the server
All of this could be avoided by testing on another env first.
- All applications except CCM are up and running.
- The only change to the server is that the user deployed a custom plugin to CCM.
- Checking Jazz_home? It should be correctly defined in WAS.
- Look at /apps/IBM/JazzTeamServer5.0.2/server/conf/ccm/provision_profiles, NO file exists. In /conf/ccm/sites, there is only one folder, which is the custom plugin that user installed.
- In this case the client need to restore files in both folders.
-ensure the following folders exist in /ccm/sites/
==> enterprise-update-site
==> update-site
==> rtc-commons-update-site
==> js_user_role_condition_provider
CCM also has the following ini and site folder:
==> /ccm/provision_profiles/verify-profile.ini
==> /ccm/sites/verifier-update-site
Try to remove the WAS cache and try restart again:
Steps:
1. Stop WebSphere server
2. Navigate to the WebSphere temporary directory. The location of the
WebSphere's temp folder is...
<WebSphere Install Directory>\AppServer\profiles\<App Server
Name>\temp\<Node name>\<Server name>\
For example,
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/rpmcs11Node01/server1
3. Locate ccm_war and delete the folder
4. Start the server
All of this could be avoided by testing on another env first.
Comments
As I just answered your deployment is wrong and that causes the load process of the CCM server fail. Popular errors are typos in your provision profile or wrong content and structures in your site folder - missing site.xml or features/plugins.
-
Check the log file - this could indicate more what the problem is
- Delete the files you added when deploying and restart the test server
The test server should come up just fine.
You got the provision profile and the site wrong or there is some other issue in your deployment - assuming the extension works on Jetty.
See https://rsjazz.wordpress.com/2015/09/30/learning-to-fly-getting-started-with-the-rtc-java-apis/ especially
Cite:
If the extension works on Jetty, the worst that can go wrong deploying it on a real server is that the dependencies in the extension include libraries that are not available on the server. Other issues could be other dependency issues, missing provision profiles or typos in the profile or corrupt files. This would show in the log file during server start up. Check the RTC Server log (i.e. server/logs/ccm.log).
See https://rsjazz.wordpress.com/2015/09/30/learning-to-fly-getting-started-with-the-rtc-java-apis/ especially
Cite:
If the extension works on Jetty, the worst that can go wrong deploying it on a real server is that the dependencies in the extension include libraries that are not available on the server. Other issues could be other dependency issues, missing provision profiles or typos in the profile or corrupt files. This would show in the log file during server start up. Check the RTC Server log (i.e. server/logs/ccm.log).