It's all about the answers!

Ask a question

How to: Deploy RTC follow up when CLM deployed on WAS?

Timur Markunin (6495166146) | asked Dec 25 '12, 5:28 a.m.
edited Dec 27 '12, 1:49 a.m.

I'm wondering if there are any differences in the RTC follow up deployment process between WAS and Tomcat?

Do we have any guidence for RTC follow up deployment on WAS?

-thanks in advance

Karl Weinert commented Dec 26 '12, 10:54 a.m.

Hi Timur  Can you provide a few more details on what you are trying to do.
Do you have a link to the instructions for Tomcat?
Also what version of CLM are you using?
Searching the information center for WebSphere brings up a number of help pages that might point you in the right direction.

Timur Markunin commented Dec 27 '12, 1:52 a.m.

Hi Karl! I'm trying to deploy RTC server-side extension (follow up) on WAS.

Tomcat part is described in RTC Extensibility workshop Lab 6 

I'm wondering if we have similar description for deployment on WAS?

-thanks in advance

One answer

permanent link
Ralph Schoon (63.3k33646) | answered Dec 28 '12, 12:46 p.m.
I am not aware of any difference in the deployment mechanism. Have you tried?

The only thing I am aware off is that is potential issues in rare cases if you try to use your own class loader. You would need to use the built in class loaders.  See Websphere documentation on classloaders.

Timur Markunin commented Dec 29 '12, 4:21 a.m.

 Hi Ralph,

I've tried to deploy the follow up in the same way as for Tomcat:
1. Copied provision profile to C:\IBM\JazzTeamServer\server\conf\ccm\provision_profiles
2. Copied update site to C:\IBM\JazzTeamServer\server\conf\ccm\sites
3. Restarted WAS

I do not see my new follow up in RTC client.

Any ideas how I could find the reason why it's not deployed? Any log files?

-thanks in advance

sam detweiler commented Dec 29 '12, 8:01 a.m.

You have to tell the server to reload the configuration after you make changes


then restart the server

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.