It's all about the answers!

Ask a question

Problems migrating for M5a to M6a on WebSphere and DB2


Adil Chahid (45524118) | asked Apr 30 '08, 7:48 p.m.
Hi all,
We tried to move our Jazz server and our RTC clients from Version M5a to M6a.
We thought that the upgrade operation went smoothely but here's what happened.
When we tried to access the Website using https://jazz-site/jazz/web we got the following error message: 404 ProxyServlet not found...
We were able to access the following url: https://jazz-site/jazz/setup and it displayed the setup page.
So we started the Custom setup wizard, to realize that we couldn't go further the second page: it was displaying DB2 as our database but we couldn't interact with the page anymore, excluding the Precedent button.


Here are the steps we followed for that migration:

1) ./repotools.sh -export toFile=/opt/backups/jazz/m5a/export_from_M5a.tar

2) We stopped the Jazz J2EE Application form the Websphere Application Server Administration Command (Version M5a) and we uninstalled it.

3) We stopped the Websphere process

4) We cleared the temporary files: rm -Rf /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/sael0109Node01/server1/jazz_war/

5) We decompressed the M6a archive

6) We manually adapted the teamserver.properties with the required data.

7) We created a new DB2 DB (as defined in teamserver.properties)

8) we did import the backed up data into the new db: ./repotools.sh -import fromFile=/opt/backups/jazz/m5a/export_from_M5a.tar

9) We started WebSphere

10) added the following JVM variables:
-Dcom.ibm.team.server.configURL=file:///opt/jazz/server/teamserver.properties -Dlog4j.configuration=file:///opt/jazz/server/log4j.properties -Djava.awt.headless=true -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true
-Dcom.ibm.team.repository.provision.profile=///opt/jazz/server//profile.ini

11) We deployed the war located under the webapp folder of the provided by default Tomcat installation in the M6a version of Jazz.

12) We associated the 4 groups to the 4 groupes defined in WAS

13) We completed the deployment

14) Edited web.xml in order to use the Basic Authentication instead of the Form Authentication:

<login>
<auth>BASIC</auth>
</login>

15) Finally Started the application

16) Accessed it and got the previously described error.


We did not install the Provisionning as described in this Wiki page: https://jazz.net/wiki/bin/view/Main/JazzProvisionerSetupInWAS

Here are the information about the installed WebSphere node:

Name IBM WebSphere Application Server - Express
Version 6.1.0.13
ID EXPRESS
Build Level cf130745.06
Build Date 11/13/07

and information about the installed JDK in WASD:
java full version "J2RE 1.5.0 IBM Linux build pxi32devifx-20071025a (SR6b)"

Did we missed some steps?
Is there a better way for importing the content of the teamserver.properties from one Milestone to another without manually editing it? We'll provide the teamserver.properties file if needed.

I thank you all in advance for your help!

2 answers



permanent link
Adil Chahid (45524118) | answered May 01 '08, 2:14 p.m.
Hi all,
I found the problem:

Initially this was the configuration:

-Dcom.ibm.team.server.configURL=file:///opt/jazz/server/teamserver.properties
-Dlog4j.configuration=file:///opt/jazz/server/log4j.properties
-Djava.awt.headless=true
-Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true
-Dcom.ibm.team.repository.provision.profile=file:///opt/jazz/server//profile.ini

I had to change the provisionning argument to:
-Dcom.ibm.team.repository.provision.profile=/opt/jazz/server//profile.ini

Thank you all for your time!
Cheers!

permanent link
Benjamin Chodroff (8985231) | answered May 07 '08, 5:01 p.m.
Just spent the day with this exact same problem. THANK YOU! Works now :)

Your answer


Register or to post 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.