How to Hide port number from URL(jazz team server)
I am trying to hide the port number from the URL of jazz team server.
Accepted answer
You have to set the server or the proxy server up with the well known port 443 before you set up the server. If you have already set up the server you have to do a server rename. Stephane in the article Hide port number from URL did the setup of the server only after the changes and using the public URI root without port number.
2 other answers
You need to do a server rename on your Jazz environment. This uses a mapping file to redirect the public URI. It involves a minor performance hit as well. I would recommend opening a ticket with IBM support to make this happen.
Additionally, your environment will need a reverse proxy (such as IBM HTTP Server) in order to hide the port number. Please see this article.... http://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.3/com.ibm.jazz.install.doc/topics/t_config_reverse_proxy_ihs.html
Rather than going through the hoops involved in server rename you should investigate deploying a reverse proxy. With a reverse proxy properly configured your user base should be able to reach the application server without using a port number without making an invasive change to the application.
Comments
Hypothetical questions..isn't a server rename required along with a reverse proxy server? Without the server rename, clicking the links within CLM, for example clicking the app drop down list next the the home icon, would take the user to old URLs that include the port number correct? Only doing the server rename would completely remove the port number from all links that a users may click in CLM?
A server rename isn't required if to deploy a reverse proxy. You can use reverse proxy to hide the CLM server's public URI (and the fact that it includes a port number) from end users. Once users have reached the application server I doubt they care if the links don't match what the use to reach the home page and remember; Jazz.net uses a reverse proxy to expose the application server URI to the public.
Server rename is a potential point of failure and can also be costly. There are better ways and it should be avoided if possible.
The reverse proxy does not help AFTER the public URI was created with a port number encoded. You need to have the correct Public URI before or do a server rename, regardless if you use a reverse proxy or not.
But to change from a public URI with a port number exposed to a public URI that uses the well known port, a server rename is required.