Extend Jetty by DOORS Next and Global Config?
Hi,
we have to develop the following:
- Server Extension which ...
- ... listens on Save button of EWM work item.
- ... reads linked ERM changesets.
- ... gets DOORS Next links from ERM changeset.
- ... does something with Requirements.
So here is our issue: Our current setup uses a jetty-based debug server as suggested in IBM Rational Team Concert 7.x Extensibility Workshop.
The jetty-based debug server has ...
- ... jazz context only (e.g., https://my.jetty:9443/jazz)
- ... /rm, /gc, /qm are missing
- ... hence, no cross-domain plugin testing and debugging is possible
Any ideas, how the debugging setup could look like when developing cross-domain plugins?
- E.g., Jetty could be extended by ERM DOORS Next and Global Config?
- E.g., Tomcat could be used for debugging and testing with full ELM installation?
- E.g., Liberty could be used for debugging and testing with full ELM installation?
Thanks in advance for any hints :)
-- Kerstin and Thomas
3 answers
The RTC Extensions Workshop is based on the EWM/RTC SDK. There are no SDK's available for any application other than EWM/RTC. The availability of the SDK and the ability to set up the plugin development environment in Eclipse with the SDK and the contained target platform make it possible to
- To run the EWM server on Jetty and debug your extension code
- To run the EWM server on any other supported application server and debug your extension code
"Jetty could be extended by....." makes no sense.
As far as I can tell, you should be able to install a full ELM on Liberty following the the extensions workshop, run the WorkshopSetup and follow the extensions workshop. You can setup your test data on that system. You can debug the RTC Extension on Liberty as shown in the Extensions Workshop 1.5__32 . This depends on the availability and the setup of the SDK. You can not debug DNG or any other of the applications because you do not have an SDK.
In a setup like the one above, or if you create a friends relationship from your Jetty EWM server to a DNG etc. server you can only debug RTC. The system however should be complete enough to test e.g. linking to DNG.
In a setup like the one above, or if you create a friends relationship from your Jetty EWM server to a DNG etc. server you can only debug RTC. The system however should be complete enough to test e.g. linking to DNG.
Comments
If an follow up action works on Jetty and it does not on Liberty, it is 99% due to a deployment issue. Plugin.xml missing, meta-inf missing. Generated with wrong Java, Plugin.xml incorrect, dependencies to client or not existing API. The CCM server log might provide hints.
You have client API in the server development workspace, if you are not careful, you pick that up in your dependencies. It would work in Jetty, but not in liberty. In Jetty it is surfaced by the workspace. In liberty it is unavailable. I found an old example of mine recently and discovered that I had such a case and did not realize since I did not test deploying that in liberty. Client API usually has .client. in the package name.
As explained in the extensions workshop you should be able to connect the Eclipse development client with the extension, connect debug to the liberty server, search for the server extension class and debug. Make sure your extension is correct and correctly deployed first.
Comments
Thanks a lot for the advices. Deployment on liberty works and our operation participant can be selected and tested.
However, when we started this thread we were hoping that there is another solution to debug/test on Liberty without going through the entire deployment process because this is very time-consuming during development. We were hoping for a debug/test solution similar to the Jetty approach but on our full ELM on liberty.