Bringing up iManager 2.0.x after a Change of Server Hostname

Novell Cool Solutions: Tip
By Harshwardhan Pradhan

Digg This - Slashdot This Posted: 10 May 2006

Problem

If the administrator changes the hostname of the server where iManager 2.0.x is installed, iManager doesn't come up.

Solution

You need to edit certain Tomcat and iManager properties files to get iManager up and running.

Here are the steps to bring up iManager 2.0.x:

1. Change the following lines in var/opt/novell/tomcat4/webapps/nps/WEB-INF/PortalServlet.properties to reflect the new host-name:

System.DirectoryAddress=systst-lnx-160.blr.novell.com\:636
Custom_Backend_Renderer_Portal_Location=http\://systst-lnx-
160.blr.novell.com\:8080/nps

2. Change the following lines in /var/opt/novell/iManager/nps/WEB-INF/PortalServlet.properties to reflect the new host-name:

System.DirectoryAddress=systst-lnx-160.blr.novell.com\:636
INF/PortalServlet.properties:Custom_Backend_Renderer_Portal_Location=http\://systst
-lnx-160.blr.novell.com\:8080/nps

3. Change the following lines in /var/opt/novell/iManager/imanager20/configure.properties to reflect the new host-name:

PARAMETER_SERVER_WEB=systst-lnx-160.blr.novell.com
PARAMETER_SERVER_LDAP=systst-lnx-160.blr.novell.com

4. Restart Tomcat:

#/opt/novell/tomcat4/bin/dtomcat4 stop
#/opt/novell/tomcat4/bin/dtomcat4 start

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com