M6 WAS DB2: jazz/setup page gives : A problem occurred whi
RHEL5, WAS 6.1.0.13, DB2, fresh install of M6.
Using Bluepages LDAP Tomcat comes up just fine, and the jazz/setup webpage reports that the DB connection is OK. If I shutdown Tomcat and start WAS instead, the jazz/setup webpage (Fast Path) displays a message "A problem occurred while loading User Registry settings." and the 'next' button is grayed out. If I use the "Custom Setup" link instead, it shows "Loading Database Connection settings..." Tried M5a .. the jazz/setup dialog works fine for both Tomcat and WAS. Any help appreciated |
7 answers
|
Yes, I've now reverted back to only one new Custom Property and the DB
connection remains in the green ! shawnlauzon wrote: FWIW, I did not have to add the configURL and log4j properties as |
|
I'm afraid I don't know what the provisioning server is for :-).
I only downloaded it because the Wiki page that Pravesh mentioned referred to it. I'm basically just trying to walk through the the new jazz/setup dialog. I have followed the Wiki instructions and my original DB connection problem has been resolved. On the next page of the "Custom Setup" I'm now seeing .. "Loading Email Notification settings..." I'll post a new message for that Thanks for getting back Richard Backhouse wrote: David, |
FWIW, I did not have to add the configURL and log4j properties as config properties; I set them as Generic JVM args and they work fine (no errors in the logs).
But big thanks for pointing out the extra provisioning setup necessary in WAS. |
David,
The only available Server SDK in M6 is now the provisioning one. (Now just called the JazzTeamServer-<tag>.zip) To install into WAS you must make sure that a system property is configured to point to the profile.ini found in the sdk. The profile.ini file itself must be modified such that it has an absolute path to the "jazz/server/update-site" directory found in the sdk. The "/ws" is just an example of where the profile.ini file had been copied to. For example. 1) Unzip the Server SDK into a directory called /M6 2) Modify the "url" property value in profile.ini to file:/M6/jazz/server/update-site 3) Add a custom property called "com.ibm.team.repository.provision.profile" to the WAS jvm setup that contains this value /M6/jazz/server/profile.ini You will need to make sure a com.ibm.team.server.configURL system property is set to point to your required teamserver.properties, however this is something that you should already have in place, perhaps set as a generic jvm property in the WAS configuration. If you want to have custom log4j properties then you can also add the log4j.configuration system property. Neither the com.ibm.team.server.configURL or log4j.configuration are required by the provisioning code. HTH Richard Jazz Web UI and Server Development David Ward wrote: Thanks for getting back |
|
OK .. a more careful reading of your note and that Wiki page would have
helped :-) When I include my actual absolute jazz/server path in the property values (duh) and edit the profile.ini as instructed, the problem goes away Thank you :-) David Ward wrote: Thanks for getting back |
|
Thanks for getting back
I grabbed the JazzProvisioningServer package (for M5a, M6 didn't seem to have one) and noticed that its profile.ini is the same as that provided by the M6 package (located in the jazz/server directory). In any case, I setup my custom properties to be identical to those shown on that Wiki page. That "/ws" syntax is new to me but I copied it verbatim anyway. Didn't seem to fix the problem, I'm afraid. I assume it's correct to remove the log4j and configURL Generic JVM properties and use the Custom Properties shown in the Wiki page ? Why does the first Custom Property shown start with "/ws/" and the other two use "file:/ws/" ? Cheers pravesh wrote: David, |
David,
The WAS setup documentation is wrong for M6. I had the same issue. You must add a custom property called "com.ibm.team.repository.provision.profile" for M6 running under WAS. See Wiki page below. https://jazz.net/wiki/bin/view/Main/JazzProvisionerSetupInWAS Additionally I had to add custom properties for com.ibm.team.server.configURL and log4j.configuration. These two properties used to be specified as Generic JVM arguements. |
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.