Novell Home

Can't get into iManager 2.5 after upgrading from NetWare 6.5 sp2 to OES NetWare and iManager 2.5

Novell Cool Solutions: Tip
By Peter J Strifas

Digg This - Slashdot This

Posted: 23 May 2005
 

What I found was a disconnect in the configurations of Apache2 and Tomcat. I had to make the following edits:

For Tomcat Configuration - In sys:\tomcat\4\conf there's a file called server.xml. In this file, there's a section for the SSL redirect. On my server port=9010 was redirecting to something other than 8443.

- <!--  Define a Coyote/JK2 AJP 1.3 Connector on port 8009   --> 
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="9010" 
minProcessors="5" maxProcessors="250" enableLookups="true" redirectPort="8443" 
acceptCount="10" debug="0" connectionTimeout="0" useURIValidationHack="false" 
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" /> 


Apache2 Configuration:
In sys:\apache2\conf there's an httpd.conf file. Check there's an include for 
iManager near the bottom of this file:
# NetWare iManager Config
Include sys:/tomcat/4/conf/nps-Apache.conf

and also check the Listen statement
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80
SecureListen 443 "SSL CertificateDNS"

On my server, the Listen statement was missing the 'SecureListen' component and in the autoexec.ncf file for my server, the ap2webup command was ahead of the MOUNT ALL command. I re-arranged that and iManager started working.


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

© 2014 Novell