Facing issue during Segregation of RM application on separate server using reverse proxy for current CLM 6.0.5 Environment
![]()
Current Environment:
Server 1:
OS: RHEL 6.3
Application Server: WAS 8.5.5.2 Base profiles
CLM: 6.0.5 (All apps JTS, RTC, RQM, RDNG on same server using single (JTS) profile)
Server 2:
OS: RHEL 6.3
DB : DB2 10.5
RDNG performance is very slow that's why we need to segregate the RDNG on separate server using Reverse Proxy.
New Environment:
Server 1:
OS: RHEL 6.3
Application Server: WAS 8.5.5.2 Base profiles
CLM: 6.0.5 (JTS, RTC, RQM apps on server 1 using single JTS profile)
IHS 8.5.5.2
Websphere plug-in TB
Server 2:
OS: RHEL 6.3
Application Server: WAS 8.5.5.2 Base profiles
CLM: 6.0.5 (RDNG app on server 2 using RDNG profile)
Server 3:
OS: RHEL 6.3
DB : DB2 10.5
I have done following main steps:
1) I have installed IHS on main server and installed RM on new server on BASE RM profile.
Configured both profiles on IHS.
2) After that I stop the RM and converter application on first server and copied the RM folder on second server under
jazz_inst_dir/server/conf/RM (overwritten).
3) Then uninstalled RM and converter applications from first server's WAS profile.
4) But when I run setup and try to register RM using new scr, it is showing this message.
"The applications could not not be registered with Jazz Team Server : ID CRJAZ1726E
A friend or application with the URL"https://server........" is already configured. Each friend and application must have a unique root services or discovery URL.
com.ibm.team.repository.common.TeamRepositoryException".
I tried to find out the solution but couldn't find any solution. I would really appreciate if someone can help me in this regard. I need to close this issue as soon as possible.
Thanks in advance.
|
One answer
![]() There was a time sync issue between both servers old and new one. Sync the time between both servers, setup will detect RDNG application automatically.
|
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.