How To Migrate Oracle iPlanet Web Server Virtual Server Settings To Oracle HTTP Server 11g

The iPlanet logo (Photo credit: Wikipedia)

This document is provided as a guideline for migrating Virtual Server settings from Oracle iPlanet Web Server (iWS) to Oracle HTTP Server 11g (OHS).

 iPlanet Web Server 7.0.x Configuration

 iWS configuration always contains a least one single default Virtual Server.  A Virtual Server settings can be found in the following ways,

A] The Admin CLI (wadm)

 The Virtual Server properties can be found by running the following wadm command:

/<server_root>/bin/wadm get-virtual-server-prop --user=<admin_user> --host=<serverhost> --port=<port> --ssl=true --config=<config> --vs=<vs>

For example:

#/opt/iplanet/bin wadm get-virtual-server-prop --user=admin --host=localhost --port=8989 --ssl=true --config=config1 --vs=virtual1
Please enter admin-user-password>
enabled=true
http-listener-name=http-listener-1
host=hosta.uk.oracle.com
document-root=../docs
default-object-name=default
name=java
object-file=virtual1-obj.conf

In order to get a list of all Configurations and Virtual Servers use the following wadm command: 

# /opt/iplanet/bin/wadm list-configs --user=admin --host=localhost --port=8989 --ssl=true
Please enter admin-user-password>
config1

# /opt/iplanet/bin/wadm list-virtual-servers --user=admin --host=localhost --port=8989 --ssl=true --config=config1
Please enter admin-user-password>
virtual1

2] You can examine the server.xml file directly, each Virtual Server is defined inside a block of <virtual-server></virtual-server> xml.

<virtual-server>
    <name>virtual1</name>
    <host>hosta.uk.oracle.com</host>
    <http-listener-name>http-listener-1</http-listener-name>
    <object-file>hosta-obj.conf</object-file>
    <document-root>../docs</document-root>
</virtual-server>

iPlanet Web Server 6.1.x Configuration

With iWS 6.1 the Virtual server configuration is stored directly in the server.xml. As it possible to have multiple Virtual Server Classes make sure the file is checked carefully.

<VS id="https-hosta.uk.oracle.com" connections="ls1" mime="mime1" aclids="acl1" urlhosts="hosta.uk.oracle.com">
            <PROPERTY name="docroot" value="/opt/iplanet/docs"/>
            <USERDB id="default"/>
            <SEARCH>
                <WEBAPP uri="/search" path="/opt/iplanet/bin/https/webapps/search"/>
            </SEARCH>
 </VS>

  

OHS 11g Configuration

OHS uses the standard Apache Virtual Host configuration.  

Virtual Server configurations are referred to as "Virtual Hosts" with OHS. By default OHS does not require a virtual host configuration to work as it will use the configuration wide settings.

1] To configure a Virtual Host edit the httpd.conf at a suitable location. Alternatively create a separate file and load it using an "Include" directive.  It is worth noting that the SSLrelated virtual hosts are usually placed within the ssl.conf file.

 An example of a name based Virtual Host.

NameVirtualHost *:80

<VirtualHost *:80>
    ServerAdmin webmaster@uk.oracle.com
    DocumentRoot "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/htdocs_virtual1"
    ServerName hosta.uk.oracle.com
    ServerAlias hostb.uk.oracle.com
   </VirtualHost>

An simple IP based Virtual Host.

<VirtualHost 192.168.0.1:80>
ServerAdmin webmaster@uk.oracle.com
DocumentRoot ${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/htdocs_virtual2"
ServerName hostc.uk.oracle.com
</VirtualHost>

2] Restart ohs

# opmnctl restartproc process-type=OHS