It's all about the answers!

Ask a question

RTC Server and RTC Agent compatibility


vikas pujar (283) | asked Feb 07 '20, 2:14 a.m.

 Hi Team,


Scenario is that we have 

RTC Server 6.0.6 on installed on Linux and we have zD&T v10 where have Agent 6.0.1. 

Question is if these two are compatible. Can I run Builds on zD&T with Agent 6.0.1 and Server 6.0.6?

Vikas

Accepted answer


permanent link
vikas pujar (283) | answered Mar 06 '20, 4:46 a.m.

 All,


The issue is resolved now 

1) First issue was that zOS was not connecting to RTC server, the ports were opened (9443)
2) Second issue was that zOS was not able to resolve the DNS name of RTC Server , we used IP Address and it worked like https://10.111.429.12:9443/scm instead of https://rtcserver:9443/scm
3) For DNS name to work we need to add the entry of DNS name and IP Address in IPNODES member of TCPPARMS on zOS 

Hope this answer helps others who face similar issue

Ralph Schoon selected this answer as the correct answer

Comments
Ralph Schoon commented Mar 06 '20, 5:57 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You must never, ever, ever use a IP address with any production Jazz deployment. You must use a fully qualified domain name for that and it must be used from the beginning.

The URI e.g. https://elm.example.com/ is called a public URI root and plays a central role in the whole system Changing it requires a server rename process.
 
Otherwise you might corrupt your deployment. Fix you zOS system. 


vikas pujar commented Mar 09 '20, 11:35 p.m.

 Ralph, we have made update on zOS system to use URI only. Now we are able to access RTC using URI not IP.


Ralph Schoon commented Mar 10 '20, 2:49 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Great to hear you fixed it. 

5 other answers



permanent link
Ralph Schoon (61.4k33643) | answered Feb 07 '20, 4:20 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In general EWM/RTC supports N-1 compatibility.See link next line.

On the ELM download pages in getting started is a link to the System Requirements, which also contain related information.

In general I would your setup expect to work from the Jazz perspective.

permanent link
vikas pujar (283) | answered Feb 21 '20, 1:17 a.m.

 Thanks Ralph for the answer. I tested the build and it fails with below . Its says version compatability issue. Is it because RTC server is of version 6.0.6 and RTC Agent on zOS is 6.0.1?


BUILD FAILED
* com.ibm.team.repository.common.TeamRepositoryException: Error logging in to repository https://rtcserver.lnx:9443/ccm/.  Verify that the repository address and credentials to log in are correct.
* at com.ibm.team.build.ant.task.AbstractTeamBuildTask.initializeRepositoryManager(AbstractTeamBuildTask.java:565)
* at com.ibm.team.build.ant.task.AbstractTeamBuildTask.getTeamRepository(AbstractTeamBuildTask.java:338)
* at com.ibm.team.build.ant.task.AbstractTeamBuildTask.getTeamBuildClient(AbstractTeamBuildTask.java:294)
* at com.ibm.team.build.ant.task.StartBuildActivityTask.updateBuildResult(StartBuildActivityTask.java:153)
* at com.ibm.team.build.ant.task.AbstractPublisherTask.doExecute(AbstractPublisherTask.java:105)
* at com.ibm.team.build.ant.task.AbstractTeamBuildTask.execute(AbstractTeamBuildTask.java:974)
* at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
* at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
* at java.lang.reflect.Method.invoke(Method.java:620)
* at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
* at org.apache.tools.ant.Task.perform(Task.java:348)
* at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
* at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
* at java.lang.reflect.Method.invoke(Method.java:620)
* at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
* at org.apache.tools.ant.Task.perform(Task.java:348)
* at net.sf.antcontrib.logic.Switch.execute(Switch.java:138)
* at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
* at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
* at java.lang.reflect.Method.invoke(Method.java:620)
* at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
* at org.apache.tools.ant.Task.perform(Task.java:348)
* at org.apache.tools.ant.Target.execute(Target.java:357)
* at org.apache.tools.ant.Target.performTasks(Target.java:385)
* at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
* at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
* at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
* at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
* at org.apache.tools.ant.Main.runBuild(Main.java:758)
* at org.apache.tools.ant.Main.startAnt(Main.java:217)
* at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
* at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
* Caused by: com.ibm.team.repository.common.transport.HostUnknownException: CRJAZ1373E The following URL cannot be reached: /ccm/versionCompatibility?clientVersion=6.0.1. The network stated that the server is unknown and then returned the following error: rtcserver.lnx.
* at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1907)
* at com.ibm.team.repository.transport.client.RemoteTeamServer.executeWithAuthHandling(RemoteTeamServer.java:1544)
* at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1170)
* at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1119)
* at com.ibm.team.repository.transport.client.RestClientConnectionBase.executeMethod(RestClientConnectionBase.java:375)
* at com.ibm.team.repository.transport.client.RestClientConnectionBase.doMethod(RestClientConnectionBase.java:211)
* at com.ibm.team.repository.transport.client.RestClientConnectionBase.doGet(RestClientConnectionBase.java:144)
* at com.ibm.team.repository.transport.client.TeamRawRestServiceClient$RawRestClientConnection.doGet(TeamRawRestServiceClient.java:96)
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
* at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
* at java.lang.reflect.Method.invoke(Method.java:620)
* at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:254)
* at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:110)
* at com.ibm.team.repository.client.internal.RawRestServiceClientProxy$RestClientConnectionProxy.invoke(RawRestServiceClientProxy.java:121)
* at com.sun.proxy.$Proxy9.doGet(Unknown Source)
* at com.ibm.team.repository.client.internal.TeamRepository.fetchClientVersionJSONObject(TeamRepository.java:1701)
* at com.ibm.team.repository.client.internal.TeamRepository.access$0(TeamRepository.java:1698)
* at com.ibm.team.repository.client.internal.TeamRepository$5.run(TeamRepository.java:1769)
* at com.ibm.team.repository.client.internal.TeamRepository$5.run(TeamRepository.java:1)
* at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1327)
* at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)
* at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1322)
* at com.ibm.team.repository.client.internal.TeamRepository.checkServerVersionMatches(TeamRepository.java:1772)
* at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(TeamRepository.java:1520)
* at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:653)
* at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:627)
* at com.ibm.team.build.internal.scm.RepositoryManager.login(RepositoryManager.java:346)
* at com.ibm.team.build.ant.task.AbstractTeamBuildTask.initializeRepositoryManager(AbstractTeamBuildTask.java:563)
* ... 37 more
* Caused by: java.net.UnknownHostException: rtcserver.lnx
* at java.net.InetAddress.getAllByName0(InetAddress.java:1412)
* at java.net.InetAddress.getAllByName(InetAddress.java:1316)
* at java.net.InetAddress.getAllByName(InetAddress.java:1239)
* at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
* at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:111)
* at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
* at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
* at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
* at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
* at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
* at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
* at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
* at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
* at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1870)
* ... 65 more


Comments
Ralph Schoon commented Feb 21 '20, 4:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The error message does not seem to necessarily say that there is a version issue. The error message seems to say it can not log into the host or find the host

It explicitly says: Verify that the repository address and credentials to log in are correct.

Please note that in the post here there is additional stuff behind the ccm/ . Not sure that contributes. This can be just a connectivity issue. The version check page is only visible, because that is the first page a client is redirected.

My 2 cents.

permanent link
vikas pujar (283) | answered Feb 27 '20, 12:59 a.m.

 Thanks Ralph for the response. Yes I am also working with my admin team to check on the connectivity issues.


But want to understand the flow when perform build, does :

1) RTC Client first connect to RTC Server and then to RTC agent(zOS) ?
2) Does RTC Agent(zOS) should be able to connect to RTC Server? When I checked this connectivity is not there?
3) Does RTC Server need to talk to RTC agent ? We have opened port 5555 for RTC server to talk to RTC Agent on zOS

Any other thing or flow I am missing ? 


permanent link
Ralph Schoon (61.4k33643) | answered Feb 27 '20, 1:46 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 I don't know anything about the zOs side of RTC.


Comments
vikas pujar commented Feb 27 '20, 1:49 a.m.

No issues Ralph. appreciate all your answers :-)


permanent link
Verla Hiltz (111) | answered Mar 09 '20, 1:32 p.m.
edited Mar 26 '20, 3:44 p.m.

Hi...we have RPT 8.5.0.2 installed in our environment, with test agent 8.5.0.2 deployed on several servers.  I'm considering an upgrade of the RPT workbench to 8.5.1.  Will the 8.5.0.2 agents work with RPT 8.5.1? I'm trying to avoid coordinating multiple simultaneous upgrades, especially since upgrading the agents requires service requests with another team.



Comments
Ralph Schoon commented Mar 10 '20, 2:52 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

This is not a RPT forum. Please try to locate the forum and post ther. Good luck. 

Your answer


Register or to post your answer.