RTC 3.0 on Linux using DB2 and WebSphere - some tips
Hi,
We successfully implemented RTC 3.0 on a SUSE Linux using DB2 9.7 with WebSphere 7.0.0.9. I thought of sharing some of the tips that might help others doing the similar exercise:
---------------
If DB2 is locked up during the JTS setup, run following utility after stopping the WAS server:
srtia044:/opt/IBM/JazzTeamServer/server # ./repotools-jts.sh resetRepoLockId
srtia044:/opt/IBM/JazzTeamServer/server # ./repotools-ccm.sh -resetRepoLockId
---------------
If DB2 table creation from the command line is not successful then during JTS setup clicking "Create Tables" button does the work.
---------------
While registering the ccm application, the Web Page to configure Public URI was blank. To overcome this, we logged out and logged back in with the user ID that was created as part of the JTS setup (NOT the standard ADMIN user)
---------------
Manual unregistration of CCM application was required to reset the public URI for CCM. Referred to a post on this forum for manually preregistering CCM.
---------------
Before deploy , clean the WAS cache, remove all files from following dir (this path is for our installation), after stopping the WAS server:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp
After that, start the WAS server again.
---------------
Creation of new users:
Note: New users needs to be created in RTC which are same as WAS users but roles *cannot* be assigned to these users in RTC as the role is derived from WAS server itself eg JazzUsers. Hence the roles appears in RTC as Read-Only.
1. Login to WAS Admin Console
2. Go to Users & Groups, Manage Users, create a new user and add it in the appropriate group eg WAS_JazzUsers
3. Stop and start the WAS server.
4. Login to JTS as admin and create the same user.
---------------
We successfully implemented RTC 3.0 on a SUSE Linux using DB2 9.7 with WebSphere 7.0.0.9. I thought of sharing some of the tips that might help others doing the similar exercise:
---------------
If DB2 is locked up during the JTS setup, run following utility after stopping the WAS server:
srtia044:/opt/IBM/JazzTeamServer/server # ./repotools-jts.sh resetRepoLockId
srtia044:/opt/IBM/JazzTeamServer/server # ./repotools-ccm.sh -resetRepoLockId
---------------
If DB2 table creation from the command line is not successful then during JTS setup clicking "Create Tables" button does the work.
---------------
While registering the ccm application, the Web Page to configure Public URI was blank. To overcome this, we logged out and logged back in with the user ID that was created as part of the JTS setup (NOT the standard ADMIN user)
---------------
Manual unregistration of CCM application was required to reset the public URI for CCM. Referred to a post on this forum for manually preregistering CCM.
---------------
Before deploy , clean the WAS cache, remove all files from following dir (this path is for our installation), after stopping the WAS server:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp
After that, start the WAS server again.
---------------
Creation of new users:
Note: New users needs to be created in RTC which are same as WAS users but roles *cannot* be assigned to these users in RTC as the role is derived from WAS server itself eg JazzUsers. Hence the roles appears in RTC as Read-Only.
1. Login to WAS Admin Console
2. Go to Users & Groups, Manage Users, create a new user and add it in the appropriate group eg WAS_JazzUsers
3. Stop and start the WAS server.
4. Login to JTS as admin and create the same user.
---------------