Installation and Upgrade Guides › Web Agent Installation Guide for Oracle iPlanet › Upgrade a Web Agent to 12.52

Upgrade a Web Agent to 12.52

This section contains the following topics:

Agent for Oracle iPlanet Upgrade Roadmap

How to Upgrade an Agent for Oracle iPlanet

Agent for Oracle iPlanet Upgrade Roadmap

The following illustration describes how to upgrade a CA SiteMinder® Agent for Oracle iPlanet to r12.5:

Flowchart showing the procedures for upgrading your SiteMinder Agent for Oracle iPlanet

How to Upgrade an Agent for Oracle iPlanet

Upgrading a CA SiteMinder® agent for Oracle iPlanet involves several separate procedures. To prepare for an upgrade of your agent, follow these steps:

Use one of the following diagrams to verify that you are in the proper step of the CA SiteMinder® upgrade process for an agent upgrade:
- Upgrade process from r6.x.
- Upgrade process from r12.0.
Create backup copies of any customized CA SiteMinder® files on your web server. Examples of files you could have customized after installing or configuring your agent include the following files:
- LocalConfig.conf
- WebAgent.conf
Gather information for the following CA SiteMinder® programs.
- Agent installation wizard.
- Agent configuration wizard.
If you are upgrading an agent on a UNIX/Linux operating environment, clear the LD_PRELOAD variable. Otherwise, continue with the next step.
Use one of the following procedures to upgrade your agent:
- Run the installation wizard for Windows operating environments.
- Run the installation wizard for UNIX/Linux operating environments.
If you are upgrading an agent on a UNIX/Linux operating environment do the following tasks (Otherwise, continue with Step 7):
- Source the agent environment script on the upgraded agent.
- Set the LD_LIBRARYPATH variable.
Use one of the following procedures to configure the upgraded agent:
- Configure your upgraded agent on Windows operating environments.
- Configure your upgraded agent on UNIX/Linux operating environments.
If you plan to use the Oracle iPlanet Administration console, apply the changes to your upgraded CA SiteMinder® configuration files.
Manually configure any nondefault Oracle iPlanet server instances.

Upgrade Process from CA SiteMinder® r6.x

An agent upgrade to 12.52 from r6.x occurs at stage three of the CA SiteMinder® upgrade process, as shown in the following illustration:

Graphic showing the first three stages of an r6.x agent upgrade process

Note: For more information about the CA SiteMinder® upgrade process, see the Upgrade Guide.

Upgrade Process from CA SiteMinder® r12.0

An agent upgrade to 12.52 from r12.0 occurs at stage two of the CA SiteMinder® upgrade process, as shown in the following illustration:

Graphic showing the first three stages of an r12.x agent upgrade process

Note: For more information about the CA SiteMinder® upgrade process, see the Upgrade Guide.

Ensure LD_PRELOAD Variable Does Not Conflict with Existing Agent

If you are upgrading or reinstalling a Web Agent on a Linux system, from the shell, set the LD_PRELOAD variable so that it points to a different location from any existing Web Agent installation directory. For example, if an existing LD_PRELOAD entry is set to:

LD_PRELOAD=web_agent_home/bin/libbtunicode.so

Before you reinstall or upgrade, set the variable to:

export LD_PRELOAD=

This entry sets the variable to a blank value.

Run the Installation Wizard to Upgrade your Agent on Windows

The installation program for the CA SiteMinder® agent installs the agent on one computer at a time using the Windows operating environment. This installation program can be run in wizard or console modes. The wizard and console-based installation programs also create a .properties file for subsequent installations and configurations using the unattended or silent method with the same settings.

For example, suppose the Agents in your environment use the same web server version, installation directory, Agent Configuration Object and Policy Servers. Use the installation wizard or console-based installation program for your first installation. Afterwards, you could create your own script to run the installation program with the .properties file the wizard or console-based installation program created.

Follow these steps:

Copy the CA SiteMinder® Web Agent installation executable file to a temporary directory on your web server.
Do one of the following steps:
- For wizard-based installations, right-click the installation executable file, and then select Run as Administrator.
- For console-based installations, open a command line window and run the executable as shown in the following example:
```
executable_file_name.exe -i console
```
Use the information that you gathered previously to complete the installation.

Run the Installation Wizard to Upgrade your Agent on UNIX/Linux

The installation program for the CA SiteMinder® agent installs the agent on one computer at a time using the UNIX or Linux operating environments. This installation program can be run in wizard or console modes. The wizard and console-based installation program also creates a .properties file for subsequent installations and configurations using the unattended or silent method with the same settings.

Follow these steps:

Copy CA SiteMinder® agent installation executable file to a temporary directory on your web server.
Log in as a root user.
Do one of the following steps:
- For wizard-based installations, run the installation executable file.
- For console-based installations, open a command-line window and run the executable as shown in the following example:
```
executable_file_name.exe -i console
```
Use the information from your agent Installation worksheet to complete the installation program.

Source the Agent Environment Script After an Upgrade on UNIX/Linux

The agent installation program creates an environment script in the following directory:

web_agent_home/ca_wa_env.sh

web_agent_home

Indicates the directory where the CA SiteMinder® Agent is installed.

Default (UNIX/Linux installations): /opt/ca/webagent

For most Apache-based web servers, source this script after doing any of the following tasks:

Running the agent configuration program.
Starting the web server.
Note: If you perform all the previous tasks in the same shell, only source the script once.

For the embedded Apache web server included with RedHat Linux, do one of the following tasks:

Source the script before starting the httpd service.
Source the script in the following file (instead of starting it manually each time):
/etc/init.d/htppd

Set the Library Path Variable Before Configuring your Upgraded Agent on UNIX/Linux

Set the library path variable on UNIX or Linux systems before running the agent configuration program.

The following table lists the library path variables for the various UNIX and Linux operating environments:

Operating System	Name of Library Path Variable
AIX	LIBPATH
Linux	LD_LIBRARY_PATH
Solaris	LD_LIBRARY_PATH

Set the value of the library path variable to the web_agent_home/bin directory.

web_agent_home

Indicates the directory where the CA SiteMinder® Agent is installed.

Default (UNIX/Linux installations): /opt/ca/webagent

Configure your Upgraded Agent on Windows

After gathering the information for your agent configuration, run the agent configuration program. This program creates an agent runtime instance for the web servers running on your computer.

This configuration program is wizard or console based, depending on the option you select. Running the configuration program in the wizard or console mode once creates a properties file. Use the properties file to run unattended configurations on other computers with same operating environment in the future.

Follow these steps:

Open the following directory on your web server:
```
web_agent_home\install_config_info
```
web_agent_home

Indicates the directory where the CA SiteMinder® agent is installed on your web server.

Default (Windows 32-bit installations only): C:\Program Files\CA\webagent

Default (Windows 64-bit installations only): C:\Program Files\CA\webagent\win64

Default (Windows 32-bit applications operating on 64-bit systems [Wow64]): C:\Program Files (x86)\webagent\win32
Use one of the following configuration methods:
- For a GUI-based configuration, go to Step 3.
- For a console-based configuration, go to Step 5.
Right-click the following executable, and then select Run as Administrator:
```
ca-wa-config.exe
```
Go to Step 8.
Open a Command Prompt window with Administrator privileges.
Navigate to the executable file listed previously, and then run it with the following switch:
```
-i console
```
Go to Step 8.
Follow the prompts shown in the configuration program. Provide the requested values from your agent configuration worksheet.
The agent runtime instance is created for your web servers.

Configure your Upgraded Agent on UNIX/Linux

After gathering the information for your agent configuration, run the agent configuration program. This program creates an agent runtime instance for the web servers running on your computer.

Follow these steps:

Open the following directory on your web server:
```
web_agent_home/install_config_info
```
web_agent_home

Indicates the directory where the CA SiteMinder® Agent is installed.

Default (UNIX/Linux installations): /opt/ca/webagent
Use one of the following configuration methods:
- For a GUI-based configuration, go to Step 3.
- For a console-based configuration, go to Step 5.
Run the following executable file:
```
ca-wa-config.bin
```
Go to Step 8.
Open a Command Prompt window with root privileges.
Navigate to the executable file listed previously, and then run it with the following switch:
```
-i console
```
Go to Step 8.
Follow the prompts shown in the configuration program. Provide the requested values from your agent configuration worksheet.
The agent runtime instance is created for your web servers.

Apply Changes to your Upgraded CA SiteMinder® Files with the iPlanet Administration Console

The Agent Configuration Wizard modifies the default obj.conf, and mime.types files that the Oracle iPlanet web server uses.

If you are using version 6.1 of a SunOne web server, and you plan to use the Oracle iPlanet Administration console, apply the changes to these files before using the console. If you do not apply the changes using the console first, the changes that are made for your CA SiteMinder® configuration could be corrupted. If you lose your configuration, run the configuration program again.

Note: The agent adds settings to the obj.conf file of the Oracle iPlanet web server when the Agent is configured to support an advanced authentication scheme. CA SiteMinder® does not remove these settings later. Edit the obj.conf file manually to remove any obsolete settings.

Follow these steps:

Log in to the Oracle iPlanet Administration Server console.
From the Servers tab, select the web server with the CA SiteMinder® agent installed and click Manage.
In the right corner of the dialog, click Apply.
A warning message about loading the modified configuration files appears.
Click Load Configuration Files.
Exit the console.
Restart the web server.
Optimize the Agent for Oracle iPlanet by tuning the shared memory segments.
The CA SiteMinder® changes are applied.

Manually Configure any Non-Default Server Instances for your Upgraded CA SiteMinder® Agent

The CA SiteMinder® Web Agent Configuration wizard only configures the default instance of your Oracle iPlanet web server. To configure a different instance of the Oracle iPlanet web server for CA SiteMinder®, manually edit the obj.conf file that is associated with that server instance. Examples of server instances that need manual configuration include:

Servers installed in a nondefault directory
Servers that you want to configure as a reverse proxy. We recommend configuring the reverse proxy using your Oracle iPlanet interface before adding the CA SiteMinder® settings to the obj.conf file.
Note: The CA SiteMinder® Agent Configuration wizard only modifies the default obj.conf file on the Oracle iPlanet (formerly Sun Java System) web server. To protect other instances or reverse proxy deployments with CA SiteMinder®, copy the CA SiteMinder® settings from the default obj.conf file to any respective instance_name-obj.conf files. For example, your web server created an obj.conf file when you installed it, but you later added a server instance named my_server.example.com. To protect resources on my_server.example.com with CA SiteMinder®, copy the CA SiteMinder® settings the wizard added from the obj.conf file to the my_server.example.com-obj.conf file.
Virtual servers on the same computer

Note: SunOne/Sun Java 7.0 web servers do not require these manual configuration steps.

Follow these steps:

Locate the directory of the server instance you want to configure.
Open the obj.conf file with a text editor.
Locate the following line:
```
<Object name="default">
```
Insert a new line below the previous one, and then add the following text:
```
AuthTrans fn="SiteMinderAgent"
```

Locate the following line:

AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"

Insert a new line below the previous one, and then add the following text:

NameTrans fn="pfx2dir" from="/siteminderagent/pwcgi" dir="web_agent_home/pw" name="cgi"
NameTrans fn="pfx2dir" from="/siteminderagent/pw" dir="web_agent_home/pw"
NameTrans fn="pfx2dir" from="/siteminderagent/jpw" dir="web_agent_home/jpw"
NameTrans fn="pfx2dir" from="/siteminderagent/redirectjsp" dir="web_agent_home/affwebservices/redirectjsp"
NameTrans fn="pfx2dir" from="/siteminderagent/certoptional" dir="web_agent_home/samples"
NameTrans fn="pfx2dir" from="/siteminderagent" dir="web_agent_home/samples"
NameTrans fn="pfx2dir" from="/siteminderagent/pwservlet" dir=web_agent_home/jpw"

web_agent_home

Indicates the directory where the CA SiteMinder® agent is installed on your web server.

Default (Windows 32-bit installations only): C:\Program Files\CA\webagent

Default (Windows 64-bit installations only): C:\Program Files\CA\webagent\win64

Default (Windows 32-bit applications operating on 64-bit systems [Wow64]): C:\Program Files (x86)\webagent\win32

Locate the following line:
```
NameTrans fn="ntrans-j2ee" name="j2ee"
```
Insert a new line below the previous one, and then add the following text:
```
PathCheck fn="SmRequireAuth"
```

Remove the following line:

NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Program Files/Sun/WebServer7.0/lib/icons" name="es-internal"

Locate the following line:

ObjectType fn="force-type" type="text/plain"

Insert a new line below the previous one, and then add the following text:
```
Service method="(GET|POST)" fn="SmAdvancedAuth"
```
Save the obj.conf file.
The Oracle iPlanet web server is manually configured.