It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,859
×10,877
×1,572
×11
×7

question asked: Aug 06 '21, 9:33 a.m.
question was seen: 812 times
last updated: Aug 24 '21, 9:10 a.m.

Related questions

EWM Custom Server Side plugin deployment issue

0
Ashish Kulkarni (21●4) | asked Aug 06 '21, 9:33 a.m.
edited Aug 06 '21, 9:40 a.m.

 Hello,


I have written custom service component (servlet) of kind "RAW_HTTP" with extension point as "com.ibm.team.repository.common.components".  Created a service provider with extension point as "com.ibm.team.repository.service.serviceProvider". This plug-in project gets deployed successfully on Eclipse Jetty Server. I can see my service net.jazz.rtcext.xxx.common.ITestService listed under https://localhost:7443/jazz/service as well as under https://localhost:7443/jazz/admin?internal=true#action=com.ibm.team.repository.admin.componentStatus.

However, when I deploy this service on the remote RTC server EWM 7.0.1 (as update-site), the service is listed only under https://localhost:9443/jazz/admin?internal=true#action=com.ibm.team.repository.admin.componentStatus. Service does not show up under https://localhost:9443/jts/service. I confirmed that there are no errors in https://localhost:9443/ccm/admin?internal=true#action=com.ibm.team.repository.admin.provisionStatus.

What could be the reason that service is readily available over eclipse Jetty Server but not on remote server through external deployment? Please help.



Comments
Ralph Schoon commented Aug 12 '21, 10:52 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

There is no actionable information. If there is a deployment problem, check with the EWM Extensions Workshop again and check the declaration values. Check the server logs for errors. 


The service needs to define a component and specify its ID to show up in the component view, provision status etc. 

There are many ways why the thing works in Jetty and not when you deploy them. For example if you have dependencies to client API or other unavailable packages. Check the server logs for errors at startup. Request a server reset to make sure provisioning happens again.

Be the first one to answer this question!

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.