Specifying the fully qualified domain name in express setup
I am following the instructions in the documentation to do an express setup using the Derby database.
(Installing > Configuring the server > Running express setup) I am running on Windows Server 2008 R2 virtual machine. Thus far, however, I have not been successful in specifying the fully qualified hostname that is required for configuring the database. I have experimented with adding a line to the Hosts file, but still no joy. Also tried variants of <computer name>, localhost, mylocalhost. Can anyone provide some guidance on constructing the fully qualified hostname? Thanks in advance! |
One answer
Ralph Schoon (63.1k●3●36●46)
| answered Mar 11 '13, 5:09 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Scott, I am not sure what your issue here is. Some thoughts around this.
CLM requires a stable public URI that is composed of the protocol, a logical name and optional a port. You can avoid the port if you change the server port to a well know ports such as 443 for https. See https://jazz.net/library/article/831 for a lot more guidance on this. A logical name is preferred over a machine dependent name. The reason simply is, it provides you with a way to move the servers to other machines later without violating company rules. A logical name would be clm.company.com rather than clm.servername.company.com. The server in question needs to be accessible by using the logical name (as example clm.company.com). So you would have to enter a new DNS entry for it in a company wide setup. If this is just a test system, as Derby suggests, you can instead add an entry like 127.0.0.1 clm.company.com to your host file. On another machine you would have to replace the 127.0.0.1 by the IP address of the real machine in this case. Once you have a logical hostname you just run the setup using this host name. for example https://clm.company.com/jts/setup or https://clm.company.com:9443/jts/setup and accept the public URI in the first step of your setup. |
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.
Comments
Hello Scott
Need more data to see what exactly the issue is.
--> Determine your host name: Choose a host name that is unlikely to change and that can be resolved through a DNS within your network.
This choice gives you the option to move the server to a computer with a different IP address and maintain a stable URI. Ensure that the host name is fully qualified.
Avoid using host names that cannot be resolved with a DNS: Avoid host names such as "localhost" or an IP address.
--> From the command prompt --> 'hostname' displays the current hostname.
Go to Start --> Right click on 'Computer' --> It should display a full computer name here.
If the FQDN is not displayed here, then this server machine is perhaps not part of a DNS.