It's all about the answers!

Ask a question

Changing the URI port number during WAS migration


Joseph Simon Arokiaraj (21414845) | asked Feb 21 '12, 12:00 p.m.
Hi All,

I have installed CLM on AIX and tomcat is made to run on the default port "443". Now we are doing the upgrade to WAS. WAS is running on the port "9443".

We added the port number 9443 to the teamserver.properties files exists under ccm,jts and qm directories and restarted the WAS.Erros raised in the jts.log.

Error:

2012-02-21 14:39:37,396 INFO uration.OverridablePropertyFileServerConfiguration - CRJAZ1363
I Loading the configuration from "file:///opt/IBM/JazzTeamServer/JazzTeamServer/server/conf/jts/teamserver.properties".
2012-02-21 14:39:38,192 INFO pository.service.internal.ServerDescriptionService - CRJAZ1779
I This server is configured as a JTS.
2012-02-21 14:39:38,193 INFO pository.service.internal.ServerDescriptionService - CRJAZ1971
I The server is configured with:
Public URI: "https://xxxx:9443/jts"
2012-02-21 14:39:38,553 INFO .repository.service.internal.rdb.ConnectionFactory - CRJAZ1365
I The server is attempting to connect to the following database: "thin:jts_owner/xxxxxxxx@//xxxx:xxxx/ctmpoc"
2012-02-21 14:39:38,909 INFO .repository.service.internal.rdb.ConnectionFactory - CRJAZ1364
I The connection to the following database was successful:
Db Product Name: Oracle
Db Product Version: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
Db URL: jdbc:oracle:thin:jts_owner/xxxxxxxx@//<server>:51521/ctmpoc
Jdbc Driver Name: Oracle JDBC driver
Jdbc Driver Version: 11.2.0.3.0
2012-02-21 14:39:43,004 INFO team.fulltext.service.internal.FullTextServiceImpl - CRJAZ8192
I: Fulltext Index Location: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/conf/jts/indices/workitemindex/fulltext_index
2012-02-21 14:39:43,005 INFO team.fulltext.service.internal.FullTextServiceImpl - CRJAZ8190
I: The fulltext index should point to an absolute directory but is currently set to 'conf/jts/indices/workitemindex'
2012-02-21 14:39:48,136 INFO com.ibm.team.repository.servlet.TeamServerServlet - CRJAZ2076
I Product Details:
Jazz Foundation - Core Libraries, Version 3.0.1 (RJF-I20110602-0017)

2012-02-21 14:39:48,142 INFO nternal.app.servlet.util.ServletDispatchingHandler - CRJZS0315
I Servlet Dispatching Enabled
2012-02-21 14:39:48,143 INFO nternal.app.servlet.util.ServletDispatchingHandler - CRJZS0318
I Servlet Loopback Disabled
2012-02-21 14:39:50,040 ERROR service.internal.discovery.ServiceRegistrationTask - CRJAZ1678
E Error during service contribution registration from https://<server>/ccm/scr

2012-02-21 14:39:52,708 WARN net.jazz.web.app.internal.about.AboutService - Unable to
get about:https://labaix14/ccm/application-about - Connection to https://labaix14 refused
2012-02-21 14:39:52,730 WARN net.jazz.web.app.internal.about.AboutService - Unable to
get about:https://xxxx/rm/application-about - Connection to https://xxxx refused
2012-02-21 14:39:52,748 WARN net.jazz.web.app.internal.about.AboutService - Unable to
get about:https://xxxx/admin/application-about - Connection to https://xxxx refused
2012-02-21 14:39:52,772 WARN net.jazz.web.app.internal.about.AboutService - Unable to
get about:https://xxxx/qm/application-about - Connection to https://xxxx refused
2012-02-21 14:40:44,243 INFO com.ibm.team.jfs - CRJZS5650
I Indices directory is /opt/IBM/JazzTeamServer/JazzTeamServer/server/conf/jts/indices
2012-02-21 14:40:44,441 ERROR com.ibm.team.jfs - CRJZS5677
E The index at "/opt/IBM/JazzTeamServer/JazzTeamServer/server/conf/jts/indices/_DzApIFF6EeGuTPLjOR0zZg/jfs-rdfhistory" was ind
exed with public url "https://xxxx/jts", but it is now set to "https://xxxx:9443/jts". Revert your public url or run t
he repotools command -reindex if the change is intended.


Could anyone please update me if you got any clue on my issue?

Cheers,
Jose

3 answers



permanent link
Anthony Kesterton (7.5k7180136) | answered Feb 21 '12, 4:27 p.m.
JAZZ DEVELOPER
Hi All,

I have installed CLM on AIX and tomcat is made to run on the default port "443". Now we are doing the upgrade to WAS. WAS is running on the port "9443".



Not sure about the other error messages, but are you able to switch port numbers this way? I would have thought that the port number is part of the URI - so this is equivalent to changing the server name. I am really not sure about this at all - so curious to know if this is true or not.

Is there any way to switch WAS to port 443 and see if that helps?

anthony

permanent link
Geoffrey Clemm (30.1k33035) | answered Feb 21 '12, 5:46 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The port number is part of the public URI, and in RTC-3.0, cannot be changed once information has been stored in the repository. (With RTC-4.0 server rename, you'll be able to make this change).

Cheers,
Geoff


Hi All,

I have installed CLM on AIX and tomcat is made to run on the default port "443". Now we are doing the upgrade to WAS. WAS is running on the port "9443".



Not sure about the other error messages, but are you able to switch port numbers this way? I would have thought that the port number is part of the URI - so this is equivalent to changing the server name. I am really not sure about this at all - so curious to know if this is true or not.

Is there any way to switch WAS to port 443 and see if that helps?

anthony

permanent link
Joseph Simon Arokiaraj (21414845) | answered Feb 23 '12, 4:59 a.m.
Hi Geoff/Anthony,

Thanks a lot for your quick reply.

I will try to configure WAS on port 443.

Cheers,
Jose


The port number is part of the public URI, and in RTC-3.0, cannot be changed once information has been stored in the repository. (With RTC-4.0 server rename, you'll be able to make this change).

Cheers,
Geoff


Hi All,

I have installed CLM on AIX and tomcat is made to run on the default port "443". Now we are doing the upgrade to WAS. WAS is running on the port "9443".



Not sure about the other error messages, but are you able to switch port numbers this way? I would have thought that the port number is part of the URI - so this is equivalent to changing the server name. I am really not sure about this at all - so curious to know if this is true or not.

Is there any way to switch WAS to port 443 and see if that helps?

anthony

Your answer


Register or to post 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.