Running iManager in Standalone Mode without Apache Server
Novell Cool Solutions: Tip
By R Sathish
|
Digg This -
Slashdot This
Posted: 4 Dec 2003 |
If Apache HTTP Server-Tomcat integration fails, here's how to run iManager (Non-SDK Version) in standalone mode without integrating to Apache HTTP Server.
Update
Please note:
- The changes have to be undone for future Apache HTTP Server integration.
- PortalServlet.properties file will be generated after Configuration only. If the Custom_Backend_Renderer_Portal_Location property is not there, add it.
- Configure iManager for Non-SSL operation by commenting out the security-constraint section in $TOMCAT_HOME\webapps\nps\WEB_INF\web.xml. This section is the last section in web.xml.
- Edit 'Custom_Backend_Renderer_Portal_Location' property in $TOMCAT_HOME\webapps\nps\WEB_INF\PortalServlet.properties to include portnumber 8080 in URL.
EXAMPLE
Step 1
<!--
<security-constraint>^M
<web-resource-collection>^M
<web-resource-name>SSL-requiring Area</web-resource-name>^M
<url-pattern>/servlet/*</url-pattern>^M
</web-resource-collection>^M
<user-data-constraint>^M
<transport-guarantee>CONFIDENTIAL</transport-guarantee>^M
</user-data-constraint>^M
</security-constraint> -->^M<,
Step 2
Change
Custom_Backend_Renderer_Portal_Location=http\://127.0.0.1/nps
to
Custom_Backend_Renderer_Portal_Location=http\://127.0.0.1:8080/nps
If you have any questions you may contact Sathish at rsathish@novell.com
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com