Jazz server under WebSphere Application servre

If you would like to have two Jazz servers use the same DB2 install, you
should create 2 DB2 databases. Copying your teamserver.properties file
and changing the DB2 database it points to is the right approach, and
yes, this is done pretty frequently in our testing. Make sure that your
new teamserver.properties file points to a unique database before
creating the new tables, and make sure that you second Jazz server setup
points to your new teamserver.properties file. Let us know if you run
into any problems.

Matt Lavin
Jazz Server Team


ghu wrote:

We successfully migrated our Jazz server from Tomcat to WebSphere
Apllication server 6.1.19. So we have WAS server1 run and invoke
jazz_war server and all works fine.

We then created a second WAS profile and a new DB2 database. We want
to try to see if we can configure the new instance of WAS profile to
install another Jazz server on the same server as a dev environment
to test some ideas before using them in the production instance.

We are not sure how to create the new Jazz table using the repotools
installed with the existing Jazz server. We don't want to mess up our
production database.

If we can pass this, we think we can just copy a few configurations
files like teamserver.properties and log4j.properties with the new
database info to a new directiory and configure the new WAS profile
to point to them, then install a new jazz_war.

Does this sound ok? Has anyone one tried this before? Please share
your thoughts and experiences.

Thanks, Matt

So if I have my original RTC installed under /opt/JazzTeamServer/ which contains two folders: server and repotools.
I just need to create a new folder server_test at the same level and copy files like teamserver.properties, repotools.sh, reporsitoryDB, jazz.war from
/opt/JazzTeamServer/server/ to
/opt/JazzTeamServer/server_test
and modify opt/JazzTeamServer/server_test/teamserver.properties to point to the new DB2 database
then run /opt/JazzTeamServer/server_test/repotools -createTables to create the Jazz tables.

After that, I should be able to install Jazz server in my second instance of WAS server and configure it to use the new Jazz files and database under /opt/JazzTeamServer/server_test?

I have to make sure as I don't want to mess up our production databse on the same box.

Actually it went pretty smooth with the creation part.
I created a new WAS profile with an admin account, then create a new DB2 database. Then run repootools to create Jazz tables by forcing it to point to the new teamserver.properties file in a new directory.

I was able to start the WAS admin console to configure and installed Jazz.war successfully. After starting Jazz servrer, I tried to run Jazz setup or go to the Admin UI using the same uid for accessing the WAS console, but failed because the uid is not authorized to access the admin UI, or not have the right role to access the server setup.

I then tried to go back to WAS admin console and configured LDAP authnetication but after restarting the server, I can't login with the admin account created during the new profile creation.

So I have two questions
1. Is there a way to at least go back and enable the admin acocunt access to WAS or I have to recreate a new profile?

2. There is an ADMIN/ADMIN acocunt coming with Tomcat installation and we used to access Jazz server. But now we are doing from WAS to WAS, what is the way to create a uid to access the new Jazz server installed in our new WAS profile?


2.

It seems you can only get responses from this forum with initial post :x

Anyway, just want to share with you that I made it work to run two instances of Jazz & WAS srevers on one Linux box and thanks for those who helped :lol:

Sorry for the lack of responses. The only excuse I can give is that we
are right at the end of our 1.0.1 release cycle and work is a little
hectic. I'm glad you figured out your problems even without help, and
perhaps if other people have questions like yours in the future you can
help us answer the questions quickly.

Matt Lavin
Jazz Server Team


ghu wrote:

It seems you can only get responses from this forum with initial post
:x

Anyway, just want to share with you that I made it work to run two
instances of Jazz & WAS srevers on one Linux box and thanks for
those who helped :lol:

I just setup a similar environment in Windows.

While reviewing the Jazz Advanced Properties (Jazz Web Admin UI) for the second instance (ports 9081/9444), I noticed a couple references to the default port values (9080/9443).

Specifically, com.ibm.team.repository.service.internal.webuiInitializer.ConfigPropertyInitializer and com.ibm.team.repository.servlet.internal.ServletConfigurationService have "URL HTTP Port" set to 9080 and "URL HTTPS Port" set to 9443.

I don't know the role of these properties, but plan on changing them to the new port values to be safe.

Are there other (less obvious) properties that need to be set to insure the 2 installations are cleanly partitioned?