Jazz files for deployment on WebSphere
Deployment Instructions say the following files need to be moved to "a directory on the WebSphere machine...";
" ■The file JazzInstallDir/server/tomcat/webapps/jazz.war. ■The directory JazzInstallDir/server/update-site. ■The directory JazzInstallDir/server/conf. ■The default repository database in JazzInstallDir/repositoryDB. ■The repository tools in JazzInstallDir/repotools. ■The directory JazzInstallDir/server/license-update-site. ■The directory JazzInstallDir/server/nl1-update-site. ■The directory JazzInstallDir/server/nl2-update-site." However, I think that the workitemindex directory should also be relocated? Also, if I am using Oracle, do I really need to move the repositoryDB? Thanks, Bill |
2 answers
|
I have RTC working with Oracle and now want to deploy this in WebSphere. I have moved the appropriate files per instructions. However, I have a question about some entries I have in teamserver.properties.
do I really need this entry any more? com.ibm.team.repository.db.jdbc.location=/opt/IBM/WebSphere/jazzfiles/repositoryDB Does this entry need to change for WebSphere? user authentication will be LDAP from Websphere... com.ibm.team.repository.user.registry.type=TOMCAT Does Floating License server need to change with WebSphere deployment? com.ibm.team.repository.licenseService.floatingLicenseServerURI=http\://localhost\:9080/jazz Thanks, Bill |
I have RTC working with Oracle and now want to deploy this in WebSphere. I have moved the appropriate files per instructions. However, I have a question about some entries I have in teamserver.properties. Hi Bill Are you using the Oracle Teamserver.properties example file in the same directory as you found teamserver.properties? This should contain the basic correct settings. The floating license server could stay the same if your http port is staying the same . I would edit this setting via the WebUI (Admin->Server->License Key Management) as this will help you test the connection too. anthony |
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.