| Oracle® Access Manager Upgrade Guide 10g (10.1.4.0.1) Part Number B25354-01 |
|
|
View PDF |
| Oracle® Access Manager Upgrade Guide 10g (10.1.4.0.1) Part Number B25354-01 |
|
|
View PDF |
If your earlier Oracle Access Manager environment includes Sun (previously iPlanet) Web server that has been discontinued, you may use the example here to upgrade to a supported Sun Web server release.
|
Note: Specific release numbers are used only to illustrate the sequence of tasks. Refer to your vendor documentation for complete details about administering your directory server release. Specific details of the intermediate upgrade from earlier Oracle Access Manager releases to release 6.1.1 are outside the scope of this manual. Before you start upgrading from an Oracle Access Manager release earlier than 6.1.1, contact Oracle Support athttp://www.oracle.com/support/contact.html. |
The new Web server release should be in a separate area of the Windows 2000 file system. Be sure that the Web server 4.1 service is stopped and that the service control window is closed. Otherwise, the 4.1 service will be disabled and marked for deletion, and the new service will not be created. In this state, neither the 4.1 nor the 6.0 Admin Console can operate the server.
|
Note: This procedure provides details for only Windows 2000 and Sun Web server version 4.1 to 6.0 upgrades. This is an example only. For complete support information, see the Certify tab athttps://metalink.oracle.com |
To upgrade Sun (iPlanet) version 4.x Web Server to Sun version 6
Install a Sun Web server release 6 on the same Windows 2000 machine that is currently hosting iPlanet 4.1 and the earlier release of Oracle Access Manager.
Make a copy of the earlier magnus.conf and obj.conf files for future reference.
Stop Sun Web server 4 using either the Services Window or the Sun Web Server Administration Console, then close the service control window.
Open the Sun Web server 6 Administration Console, then click the Migrate Server link.
In the Sun 6.0 Admin Console, enter the Server Root for the Sun Web server 4 and click the Search button.
The list of server instances under the root node appears.
Select the instance you want to migrate, then click the Migrate button.
Select the Document Root option, then click Migrate. For example:
Use the new server's document root, Migrate
|
Note: If you choose the same document root as the old server, migration will create some incorrect entries in your configuration file. For example, if your Web server contains entries for WebGate, the server's document root will be changed to the WebGate directory and accessing the root usinghttp://server:port/ will show you a directory listing with webgate.dll as the only file. More details about correcting the document root are given later. |
The migration starts and status messages appear. The old configuration is assimilated into a newly created instance for Sun 6.0.
Close this browser window and continue with "Configuring the New Web Server Instance".
The following things need to be done manually:
You need to define the logs/access path in magnus.conf for the newly installed Web server instance, as described in the procedure here.
To configure the new Web server instance in magnus.conf
In the config directory of the migrated instance (6.0 instance area), locate the magnus.conf file.
Search for logs/access in magnus.conf; the path still refers to the old area.
In the magnus.conf, update the logs/access path appropriately.
For example, suppose your 4.1 area is D:\NSWS\Server4, and the 6.0 area is G:\iPlanet6WS, you need to make the following change:
From
Init fn=flex-init access="D:/NSWS/Server4/https-hostname/logs/access" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
To
Init fn=flex-init access="G:/iPlanet6WS/https-hostname/logs/access" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
|
Note: In this newly created 6.0 Web server, the access log location is defined as a variable in server.xml. For example: <VARS accesslog="G:/iPlanet6WS/https-hostname/logs/access" />. |
If you use this method to add this variable to server.xml, you would have to replace the line in magnus.conf as follows:
From
Init fn=flex-init access="D:/NSWS/Server4/https-hostname/logs/access" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
To
Init fn=flex-init access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
Continue with "Configuring obj.conf".
In the migrated obj.conf file (in the config directory), the document-root directives are all set improperly. For example, suppose the following section appears in the obj.conf file for your Web server 4.x instance before the migration. Note that the values of the various document-root(s) differ. For example, there is a document root for the Web server (D:/NSWS/Server4/docs) and others for individual objects, shown in bold:
Sample obj.conf 4.x before Migration to 6.0
NameTrans fn="NSServletNameTrans" name="servlet"NameTrans fn="pfx2dir" from="/servlet" dir="D:/NSWS/Server4/docs/servlet" name="ServletByExt"NameTrans fn=pfx2dir from=/ns-icons dir="D:/NSWS/Server4/ns-icons" name="es-internal" NameTrans fn=pfx2dir from=/mc-icons dir="D:/NSWS/Server4/ns-icons" name="es-internal"NameTrans fn="pfx2dir" from="/help" dir="D:/NSWS/Server4/manual/https/ug" name="es-internal"NameTrans fn="pfx2dir" from="/manual" dir="D:/NSWS/Server4/manual/https" name="es-internal" NameTrans fn=document-root root="D:/NSWS/Server4/docs" PathCheck fn=nt-uri-cleanPathCheck fn="check-acl" acl="default" ... ... <Object name="access_lost_pwd_mgmt"> NameTrans fn="document-root" root="G:/52/webpass/access/oblix/apps/lost_pwd_mgmt/bin"ObjectType fn="type-by-extension"ObjectType fn="force-type" type="text/html"Service fn="OBlost_pwd_mgmt_Service" method="(POST|GET)"</Object># Oblix Access Manager Objects #AMOBJECTS# Oblix WebGate Objects start #WGOBJECTS<Object name="access_web_gate"> NameTrans fn="document-root" root="G:/52/webpass/access/oblix/apps/webgate/bin"ObjectType fn="type-by-extension"ObjectType fn="force-type" type="text/html"Service fn="OBWebGate_Control" method="(POST|GET)"</Object>
During migration you were asked to choose to continue with the old document root or a new Web server document root. When you chose a new document root, a new location (for example, G:/iPlanet6WS/docs) is assigned to each document-root in the obj.conf file. Thus the section of the obj.conf file shown earlier would look something like this in the 6.0 release after migration.
Sample obj.conf after Migration to 6.0
NameTrans fn="NSServletNameTrans" name="servlet"NameTrans fn="pfx2dir" from="/servlet" dir="D:/NSWS/Server4/docs/servlet" name="ServletByExt" NameTrans fn=pfx2dir from=/ns-icons dir="D:/NSWS/Server4/ns-icons" name="es-internal" NameTrans fn=pfx2dir from=/mc-icons dir="D:/NSWS/Server4/ns-icons" name="es-internal" NameTrans fn="pfx2dir" from="/help" dir="D:/NSWS/Server4/manual/https/ug" name="es-internal" NameTrans fn="pfx2dir" from="/manual" dir="D:/NSWS/Server4/manual/https" name="es-internal" NameTrans fn=document-root root="G:/iPlanet6WS/docs"PathCheck fn=nt-uri-cleanPathCheck fn="check-acl" acl="default"……<Object name="access_lost_pwd_mgmt"> NameTrans fn="document-root" root="G:/iPlanet6WS/docs"ObjectType fn="type-by-extension" ObjectType fn="force-type" type="text/html"Service fn="OBlost_pwd_mgmt_Service" method="(POST|GET)"</Object># Oblix Access Manager Objects #AMOBJECTS# Oblix WebGate Objects start #WGOBJECTS<Object name="access_web_gate"> NameTrans fn="document-root" root="G:/iPlanet6WS/docs" ObjectType fn="type-by-extension"ObjectType fn="force-type" type="text/html"Service fn="OBWebGate_Control" method="(POST|GET)"</Object>
You use the next procedure to validate or correct these.
To configure the new Web server instance in obj.conf
In the config directory of the migrated instance (6.0 instance area), locate the obj.conf file.
Locate and verify the document roots point to the release 6 Web server instance.
|
Note: The following line in obj.conf may still refer to the old location:NameTrans fn="pfx2dir" from="/servlet" dir="D:/NSWS/Server4/docs/servlet" name="ServletByExt" In the newly created release 6.0 Web server, this entry is as follows: NameTrans fn="pfx2dir" from="/servlet" dir="$docroot/servlet" name="ServletByExt" when the variable document root is defined in server.xml, as shown in step 3. |
Locate and verify that the variable document root is defined in server.xml as follows.
For example
-<VSCLASS id="defaultclass" objectfile="obj.conf" rootobject="default"
acceptlanguage="off">
<VARS docroot="g:/iPlanet6WS/docs" /> -<VS id="https-hostname" connections="group1" mime="mime1"
urlhosts="lucerne.persistent.co.in" aclids="acl1">
<VARS webapps_file="web-apps.xml" webapps_enable="on" /> <USERDB id="default" database="default" /> </VS> </VSCLASS>
Alternatively, you can change obj.conf without updating server.xml by replacing the line from obj.conf by the following one -
NameTrans fn="pfx2dir" from="/servlet" dir="G:/iPlanet6WS/docs/servlet" name="ServletByExt"
Search the migrated obj.conf for any mention of the old install area (in this example, D:/NSWS/Server4) to ensure that the v 6.0 instance of the Web server does not refer to the old install area in any way.
For information about troubleshooting this process, see "Troubleshooting Sun Web Server Upgrades".
