Add Server Domain in RTC 3.0.1
I've a team concert server (RTC 3.0.1) with a non friendly url ofr the user (rtc.domain.com:9443) and i don't know if is possible to add a domain like rtc.namecompany.com in WAS server.
I've readed something about it is not possible in RTC server but I don't know if is possible in the WAS server.
Thanks and regards
I've readed something about it is not possible in RTC server but I don't know if is possible in the WAS server.
Thanks and regards
Accepted answer
Hi Ramon,
1. Since RTC 4 it is possible to rename public URI: https://jazz.net/library/article/1081
2. If you are not going to migrate to RTC 4, you can simply add mapping to your dns server.
Let us know if it helped for you.
Best regards,
Krzysztof Kazmierczyk
1. Since RTC 4 it is possible to rename public URI: https://jazz.net/library/article/1081
2. If you are not going to migrate to RTC 4, you can simply add mapping to your dns server.
Let us know if it helped for you.
Best regards,
Krzysztof Kazmierczyk
Comments
Hy Krzysztof,
First of all thank you for your response.
One question more about use DNS, when I navigate using web client, which uri is show it when I click one link?
Do you recommend add domain uri or could be a problem?
Regards,
Ramón
Hi Ramon,
There will be shown link to the entry set as public uri. If you want to see the uri in nicer form than you have already, then you need to consider changing public uri.
2 other answers
Hello Ramón,
For a new install of RTC where the public uri has not been set yet, the following options are available
1. When setting up WebSphere, there is the option during profile creation to set the transports to use the hostname/port of your choice
1a.Or if the profile is already created, then you should be able to modify the host:port that the server instance is listening on
2. Use a proxy server in front of the appserver
https://jazz.net/library/article/745/#mozTocId438966 1
For a new install of RTC where the public uri has not been set yet, the following options are available
1. When setting up WebSphere, there is the option during profile creation to set the transports to use the hostname/port of your choice
1a.Or if the profile is already created, then you should be able to modify the host:port that the server instance is listening on
2. Use a proxy server in front of the appserver
https://jazz.net/library/article/745/#mozTocId438966 1