ENABLING CORBA ON ENTERPRISE SERVER

(Formerly CONFIGURING WEB NAMING)

Revised: 12/12/97 - Mike S. Lee, Technology Evangelist
Created: David Huntley, Technology Evangelist
This Netscape TechNote explains how to configure a web server to support Web Naming.
Products and Versions: Enterprise Server 3.01 (or 3.0f) with WAI-Patch #P85416) and newer.

WEB SERVER REQUIREMENTS

When a CORBA server uses the register()function, the Web Naming service utilizes an HTTP "Put" command to store the IOR (Interoperable Object Reference) on the web server.  In order for your web server to support this functionality, it must meet four pre-requisites:
  1. Enterprise Server must be upgraded to at least Enterprise Server 3.0f (or 3.01) with the WAI-Patch #P85416.
  2. WAI-Management must be ON, to allow for use of CORBA from Enterprise Server
  3. Web publishing must be ON, to allow for HTTP "Put" command
  4. Web Naming (Naming Service) security must be configured to give write access to the iiopnameservice configuration style

ENABLING CORBA ON ENTERPRISE 3.x

The following sections show how to enable these features using the Enterprise 3.x server.
  1. Enable WAI-Management.  This will enable the use the CORBA.
  2. Enable Web Publishing.  This will enable the use of the Put command.
  3. Configure Web Naming (Naming Service) Security. This will enable read/write from the Naming Service.
I. ENABLE WAI-MANAGEMENT
  1. From the Administration Server, enable WAI-Management by turning Enable WAI Services to "Yes" as in the following diagram.  Then, press the "OK" button, save and apply your change.

II. ENABLE WEB PUBLISHING

  1. From the Administration Server, turn the Web Publishing state to "On" as in the following diagram.  Then, press the "OK" button, save and apply your change.

III. CONFIGURE WEB NAMING SECURITY

  1. From the Administration Server, go to the Configuration Styles -> Edit Styles and select iiopnameservice configuration style.  Click on Edit this style button.
  1. Click on the Restrict Access link.  Under section A, click on the Edit Access Control button.
  2. Next, you must enable access control, and set the permissions to the Name Service so that:
    3. In setting the access control rules, you must make sure that the "Users/Groups" field is always set to "anyone."  This is because the Web Naming service isn't set-up to pass user authentication information to the server.  Ex: The figure below shows how you would set the access control rules so that any machine in the 132.32.3 subnet can register a name, and any machine anywhere can resolve one.  For more information on using wildcards in access control rules, press the Help button on the Access Control Rules dialog.
  3. Afterwards, press the "Submit" button, save and apply your changes
TN-CORB-01-9709                                
Copyright © 1997 Netscape Communications Corporation