It's all about the answers!

Ask a question

Having a Jazz Test Server in WTP/RAD


Jose Miguel Ordax Cassa (2.4k2125100) | asked Nov 21 '09, 5:53 a.m.
Is there any way (and in such case, docs) about having a Test
Environment for Jazz Server so testing/debug could be easier and faster?

I am thinking about having a Test Server pointing to Tomcat or WAS where
Jazz/RTC is installed so we can control from the IDE the start/stop
process in normal/debug/profile modes easily.

I understand of course we won't have an automatic way to deploy the
server plug-ins as we have for Java EE apps, etc... in such tool. But we
could stop the server, export the plug-in to the server, and start the
server again and test.

Have you done this before?

Thanks in advance,

Chemi.

5 answers



permanent link
Jose Miguel Ordax Cassa (2.4k2125100) | answered Nov 22 '09, 3:38 p.m.
Well, I have done some advances in this topic i would like to share with
you, but still having some problems. I would appreciate any comment, tip
or experience you have found...

1.- I installed on top of RTC Client 2.0.0.1 WTP 3.0.4 from Ganymedes
Update Site using Help -> Software Updates...

2.- Then I added a Tomcat 5.5 Server pointing to RTC Server 2.0.0.1 (in
my case: D:\RTC SDK 2.0.0.1\jazz\server\tomcat) but DON'T start it now.

3.- Edit the new server properties and under Server Locations check Use
Tomcat installation (takes control of Tomcat installation)

4.- In the same editor, under General Information click Open launch
configuration and under (X)=Arguments, in VM arguments append these
ones: -Djava.awt.headless=true
-Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true
-DJAZZ_HOME=file:///D%3a/RTCSDK~1.1/jazz/server/conf
-Dcom.ibm.team.repository.tempDir=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
-Xmx700M (change paths by yours).

5.- In same editor, increase timeout to something like one minute and a
half... first time Jazz Server is started up will consume more time and
also when resetting the server to take a server component update.

6.- Edit Jazz Server file teamserver.properties (in my case, under
D:\RTC SDK 2.0.0.1\jazz\server\conf\jazz dircetory) and set
com.ibm.team.repository.db.jdbc.location property to an absolute PATH
(in my case D\:\\RTC SDK 2.0.0.1\\jazz\\server\\repositoryDB)

Now it is time to start and test the server. You should be able to start
the Jazz Server wihtin RTC from Server view and check the output in the
console view.

Note: I have done some tests successfully but I can't confirm I am
missing any step or I am going to have any side effect. But as I said,
currently it seems to work fine.

Now, it is time to develop and test. I won't detail all the steps
because they are detailed more or less in Wiki.

1.- Create a Plug-in project with all the extensions implemented.

2.- Create a Feature project including the previous Plug-in project.

3.- Create a Update Site project adding to it the previous Feature.

4.- Add a profile.ini file to Jazz Server pointing to your Update Site
(in my case it is D:\RTC SDK
2.0.0.1\jazz\server\conf\jazz\provision_profiles\test-profile.ini) with
following content:

url=file:/D:/RTC SDK 2.0.0.1/workspace/Jazz Tests Update Site
featureid=Jazz_Tests

Note: Jazz Tests Update Site is the name of my Update site project
within RTC.

5.- Add a link to the internal browser to
https://localhost:9443/jazz/admin?internal#action=com.ibm.team.repository.admin.serverReset
(it is used to reset Jazz Server so new updates to your development are
read)

Basically, with these steps done the cycle is:

1.- Perform a change in your plug-n

2.- Rebuild the update site

3.- Invoke the reset URL and press the button.

4.- Disconnect from RTC.

5.- Restart Jazz Server.

6.- Connect (or not) to Jazz Server and test your development.

Finally, what I was trying to test was a debug process. And honestly I
am very near but I have a problem. The steps to setup the debug support is:

1.- Edit tomcat properties from Server view. Under General Information
click Open launch configuration and under Source tab add your Plug-in
projects.

2.- Add a break point in your code.

3.- Start the server in Debug mode.

4.- Execute the feature you developed and the debug perspective will
open with your source code also opened and stopped in the breakpoint line.

But.... in my tests, RTC Client get blocked at this point so I can't
debug or do anything else. I have to kill RTC Client. :-(
Still investigating but I don't find the reason. I will open a new
discussion thread about this to see if anybody has a solution.

But if that is fixed, I think this could be a nice development
environment configuration. Comments? How do you develop/test?

Regards,

Chemi.

permanent link
Jose Miguel Ordax Cassa (2.4k2125100) | answered Nov 25 '09, 11:08 a.m.
It seems more productive the embedded Jetty as OSGi bundles
(https://jazz.net/wiki/bin/view/Main/JazzServerRunAndDebug)... :-)

So forget this path... although it could be nice to do a "real" test
including a remote server with its real feature installation.

Regards,

Chemi.

permanent link
Jose Miguel Ordax Cassa (2.4k2125100) | answered Nov 27 '09, 8:53 a.m.
A new set of videos have been published by Jean-Michel:
https://jazz.net/wiki/bin/view/Main/RTCSDK20_ProcessPreConditionExample#Videos

Not exactly the same scenario (it doesn't use WTP) but really near. And
it is a great source of information and very clear.

Thanks Jean-Michel!

permanent link
Jose Miguel Ordax Cassa (2.4k2125100) | answered Nov 30 '09, 5:53 a.m.
On 22-Nov-09 9:23 PM, Chemi wrote:
Finally, what I was trying to test was a debug process. And honestly I
am very near but I have a problem. The steps to setup the debug support is:

1.- Edit tomcat properties from Server view. Under General Information
click Open launch configuration and under Source tab add your Plug-in
projects.

2.- Add a break point in your code.

3.- Start the server in Debug mode.

4.- Execute the feature you developed and the debug perspective will
open with your source code also opened and stopped in the breakpoint line.

But.... in my tests, RTC Client get blocked at this point so I can't
debug or do anything else. I have to kill RTC Client. :-(
Still investigating but I don't find the reason. I will open a new
discussion thread about this to see if anybody has a solution.

Oh my god!
Problem was I was stopping the execution when saving a work item, and to
save the work item I was using the same RTC instance where I was
debugging... so it got locked because I stopped it in the debug, and the
debug got lock because I was uing the debugger from the RTC I had
stopped with the breakpoint. I feel stupid...

Well, now I can confirm I have a RTC Server development environment up &
running.

Regards,

Chemi.

permanent link
Jose Miguel Ordax Cassa (2.4k2125100) | answered Feb 16 '11, 2:38 a.m.
Hi, I have updated my dev environment for RTC 3.0 and these are the
modifications to the steps described in my previous post when using RTC
2.0 to get it running:

1.- Install RTC Client 3.0 and then, install WTP 3.1.1 from Galileo
Update Site on top of it.

2.- Add a WTP Tomcat 5.5 Server pointing to RTC Server 3.0 (in my case
at D:\RTC SDK 3.0\jazz\server\tomcat) but DON'T start it now.

3.- Edit the new server properties and under Server Locations check Use
Tomcat installation (takes control of Tomcat installation).

4.- In the same editor, under General Information click Open launch
configuration and under (X)=Arguments, in VM arguments append these
ones: -Djava.awt.headless=true
-Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true
-DJAZZ_HOME=file:///D%3a/RTCSDK~1.0/jazz/server/conf
-Dcom.ibm.team.repository.tempDir=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
-Djazz.connector.sslProtocol=SSL_TLS -Djazz.connector.algorithm=IbmX509
-Xmx700M
-Dlog4j.configuration=file:///D%3a/RTCSDK~1.0/jazz/server/conf/startup_log4j.properties
(Note: change paths by yours).

5.- In same editor, increase timeout to something like three minutes...
first time Jazz Server is started up will consume more time and also
when resetting the server to take a server component update.

6.- Edit Jazz Server files teamserver.properties (in my case, under
D:\RTC SDK 3.0\jazz\server\conf\jts and D:\RTC SDK
3.0\jazz\server\conf\ccm directories) and set
com.ibm.team.repository.db.jdbc.location property to an absolute PATH
(in my case D\:\\RTC SDK
3.0\\jazz\\server\\conf\\jts\\derby\\repositoryDB and D\:\\RTC SDK
3.0\\jazz\\server\\conf\\ccm\\derby\\repositoryDB).

Now it is time to start and test the server. You should be able to start
the Jazz Server wihtin RTC Client from WTP Server view and check the
output in the console view.

Note: I have done some tests successfully but I can't confirm I am
missing any step or I am going to have any side effect. But as I said,
currently it seems to work fine.

Hope this helps,

Chemi.

Your answer


Register or to post your answer.