Novell Home

My Favorites

Close

Please to see your favorites.

How to run iFolder 2.1 in protected memory

(Last modified: 13Jan2004)

This document (10082707) is provided subject to the disclaimer at the end of this document.

goal

How to run iFolder 2.1 in protected memory

fact

iFolder 2.1 Professional Edition

Novell NetWare 6.0

cause

iFolder 2.1 does not by default load its own instance of apache in protected memory on NetWare.  It will instead create an include statement on the default apache configuration file (ADMINSERV.CONF) and load in the kernal address space.

fix

These steps will outline how to setup another instance of apache that will be loaded in its own memory address on the server.  These steps are post install steps after installing iFolder 2.1 (or upgrading to iFolder 2.1).

1.  Unload the apache web server by typing NVXADMDN at the server console.

2.  In SYS:\APACHE\IFOLDER\SERVER locate the HTTPD.CONF file and open it with a text editor like Notepad or Wordpad.  Add the following information to their corresponding sections:

  • Listen <your IP address or DNS name>:port      ( i.e. LISTEN 10.10.1.1:51080)
  • Port <port number>   (i.e. PORT 51080)
  • ServerName <DNS NAME or IP Address>  (i.e. mcasey1.provo.novell.com)
  • Document Root "sys:/apache/ifolder/DocumentRoot"
  • <Directory "sys:/apache/ifolder/DocumentRoot"  (by default this will show as sys:/apache/htdocs)
  • SecureListen <your IP address or DNS name>:port "SSL CertificateIP" 
    • (i.e. "SecureListen 10.10.1.1:51443 "SSL CertificateIP

The last item that will need to be added will be added to the very bottom of the HTTPD.CONF file.  Its an include statement for the httpd_ifolder_nw.conf file.  Type the following line to the end of the HTTPD.CONF file:

include SYS:\Apache\iFolder\Server\httpd_ifolder_nw.conf 

3. Next, open SYS:\iFolder\Server\httpd_ifolder_nw.conf and verify that the ports listed in this configuration file match the ports listed in the HTTPD.CONF that was just created.  The only exception is the LDAP configuration sections that identifies the LDAP server's address and port.  Leave those as they were.

4.  Open the SYS:\apache\conf\adminserv.conf file.  At the end of the file right above the include statement for iFolder ("include SYS:\Apache\iFolder\Server\httpd_iFolder_nw.conf") there is a LISTEN and SECURELISTEN STATEMENT for iFolder.  These along with the Include statement will need to be remarked out.  For example: 

 #include SYS:\Apache\iFolder\Server\httpd_ifolder_nw.conf

#Listen 52080

#SecureListen 52443 "SSL CertificateIP"

5.  Under SYS:\SYSTEM find the STARTIFOLDER.NCF AND STOPIFOLDER.NCF.  Copy both files to SYS:\APACHE\IFOLDER\SERVER (rename the original files under the sys:\system directory or delete them).

Modify the STARTIFOLDER.NCF to read as followed:

LOAD ADDRESS SPACE = IFOLDER APACHE -f SYS:\APACHE\IFOLDER\SERVER\HTTPD.CONF

Modify the STOPIFOLDER.NCF to read:

UNLOAD ADDRESS SPACE = IFOLDER APACHE

6.  Verify that there is a search path defined to the iFolder server directory.  If there is not one then add it by typing the following at the system console (and adding it to the auotexec.ncf file):

SEARCH ADD SYS:/APACHE/IFOLDER/SERVER

7.  Load iFolder by typing STARTIFOLDER at the server console (also, reload the primary apache server by typing NVXADMUP).

If after following these steps you continue to experience problems logging into iFolder, refer to "Additional steps used to get iFolder running in protected memory ".

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10082707
  • Solution ID: NOVL89109
  • Creation Date: 30Apr2003
  • Modified Date: 13Jan2004
    • NovellNetWare

      Other

Did this document solve your problem? Provide Feedback