How does one deploy a server extension?
Not sure if this is covered in the online documentation on Jazz.net, but I
was curious how one would go about providing a set of plugins to deploy along with the Jazz.war (or do we simply repackage Jazz.war with the new extensions)? |
7 answers
I am interested in finding how to do this as well.
aaakilov@us.ibm.com wrote:
|
As of the 0.5 release, you would need to repackage the WAR. There is work in progress to provide a better provisioning mechanism for extensions.
Note: if you have previously run the jazz.war before you repackage it, you would need to clear the directory <tomcat>/work/Catalina/localhost/jazz before you restart the server. Also, remove the <tomcat>/webapps/jazz directory. Ritchie Schacher Server development <aaakilov@us.ibm.com> wrote in message news:ev309p$l7m$1@localhost.localdomain... Not sure if this is covered in the online documentation on Jazz.net, but I was curious how one would go about providing a set of plugins to deploy along with the Jazz.war (or do we simply repackage Jazz.war with the new extensions)? |
is there a solution now in M4 or Beta2 to provide extensions to the jazz.war without repackaging it?
|
Yes, there is an alternative Server SDK available where it is possible
to add new server components. There is more information here : https://jazz.net/wiki/bin/view/Main/UsingJazzProvisioner akmathur wrote: is there a solution now in M4 or Beta2 to provide extensions to the |
Thanks for the post Richard. Will try this out.
|
Hi
I tried to use the provisioning server to deploy a server component, using the instructions on the wiki page (https://jazz.net/wiki/bin/view/Main/UsingJazzProvisioner) as suggested. However, my attempt hasn't been successful. More specifically, everything went well with the instructions until I did: $ ./repotools.bat -import fromFile=backup.tar The complaint I got is that my bundle "is invalid, it is not RESOLVED." Does anybody have any idea what's going on? Thanks for any insight and help! Annie |
It looks like the r4 doc is missing a step to edit the server.startup(.bat) script to point to the profile.ini. I changed it (as per the instructions in r3) and it worked...
Tim |
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.