9 1:Changing the hostname of a Project.net Installation

From Pnet-Community

Jump to: navigation, search


[edit] Changing the hostname of a Project.net Installation

[edit] Introduction

If the hostname of your Project.net server ever changes you will need to make some adjustments within Project.net to match that change, for example, if you are setting up a virtual machine (VM) based upon an image of an existing Project.net server. In this case, there are some changes that need to be made once the new VM is running in order for Project.net to function correctly. These instructions detail those steps.

If you are not using a virtual machine and are just moving an existing server from one piece of hardware to another refer to these instructions.

[edit] Steps

When Oracle is installed it may save the hostname of the server in two configuration files, you will need to change those values if the database server is running on the system that just had its hostname changed.

  1. Look in $ORACLE_HOME/network/admin/listener.ora and $ORACLE_HOME/network/admin/tnsnames.ora for the reference to the database server (On most Linux installations $ORACLE_HOME is /usr/lib/oracle/xe/app/oracle/product/<Oracle version>/server). The server may be listed as 'localhost', by hostname or by IP address - if it is by hostname or IP address it needs to match the value for the existing system.
  2. If you need to change these two files, first stop the Oracle service.
  3. Edit and save listener.ora and tnsnames.ora to match the hostname or IP for the new server. Again, you do not need to change it if it is 'localhost' or if the hostname of the database server did not change.
  4. Restart the Oracle service.

There are four places you need to change the hostname in Project.net. Just follow these instructions:

  1. Follow the Customize system settings to change the siteHost value from the the old hostname to the fully qualified domain name (FQDN) of the new hostname.
  2. In Modify the default configuration change the defaulthost token to the same FQDN.
  3. For the non-default configuration, Create a custom configuration, add the FQDN to the list of "Supported Host Names', removing the old hostname from the list. Save your changes.
  4. Finally, look for the defaulthost token in this configuration and change it to the FQDN, only if it was set to the old hostname. If so, make the change and save it.
  5. Make sure everyone is logged out of Project.net, including the administrator.
  6. Restart Apache Tomcat service. If your server is a Windows system, use the Tomcat icon in the Windows taskbar, if it is a Linux-based system use the '/sbin/service tomcat5 restart' command.

Note: It will take a few minutes after it has come back up before you can get to the login page.

[edit] More Help

Personal tools