How do I deploy new services to an existing jazz server?

Yeah, I followed those same steps during the early days of our project
when I wad doing tests on Tomcat. I started using the embedded jetty
bridge later instead once I found out about it and life's been a lot
easier for me.

If you're talking about actually deploying and not just "deploying and
testing", then I'm afraid that I don't have an answer for you.

Regards,
Rem

akmathur wrote:

I have created a service and want to deploy it to the server. What's
the best/recommended way of deploying this service. The on method I
have heard so far that I do not particularly like is

a) un-war the jazz.war file
b) place the service plugins in the appropriate location in this
extracted jazz.war
c) re-war the plugins back into jazz.war
d) put it back under tomcat/webapps folder for the server to
re-deploy
e) do make a backup of he existing jazz.war before starting this
process so you can go back to it.

I suspect there is a better way ... not?

I think the answer is that there is not a better way yet, but one is
planned. The buzzword for this is "provisioning WAR". It is mentioned
on this wiki topic (see subsection "Provisioning the Server"):

https://jazz.net/wiki/bin/view/Main/OneOhArchitecturalIssues

It is also mentioned in a line-item on the Repository team plan for the
second half of M3:

- Provisioning WAR - bring up in parallel rather than replacing mega-WAR
in M3. Exercise with Jetty tests and Web UI.

So when M3 is available (early October), check the New/Noteworthy for
mention of progress in this area.

Also, echoing Remy's reply, if you are more focused on development and
testing than actual deployment you may get good mileage from a Jetty
launch setup which is discussed on this wiki:

https://jazz.net/wiki/bin/view/Main/JazzServerRunAndDebug

Re: provisioning WAR:

The current work around provisioning is happening in Task 30196 ("Rework current Provisioning WAR to be in line with proposed admin changes") - feel free to subscribe and ask questions.