Federation Guides › Partnership Federation Guide › Getting Started with a Simple Partnership › Deploy the Federation Web Services Application on a Server › Deploy FWS on a WebLogic Application Server

Deploy FWS on a WebLogic Application Server

The following illustration shows a SiteMinder and WebLogic sample configuration. The illustration provides an example of how to deploy FWS in a sample federated environment.

In this environment, deploy the FWS application is on System 2 and System 5.

Important! Complete the deployment procedure for the Web Agent at the IdP and the SP.

After installing the software components on the systems in the illustration, deploy the FWS application. Deploy the application on System 2 for the asserting party and on System 5 for the relying party.

To deploy the FWS application

1. Set the LD_LIBRARY_PATH variable
2. Create a SmHost.conf file
3. Create a WebAgent.conf file
4. Modify the AffWebServices.properties file
5. Configure the WebLogic Reverse Proxy Plug-in
6. Deploy the FWS Application on WebLogic

Important! For the FWS application to work with WebLogic Server 8.1.4 or higher, review the weblogic.xml file in the WEB-INF directory. Verify that the prefer-web-inf-classes parameter is set to true. The weblogic.xml file is located in the following directory:

webagent\affwebservices\WEB-INF

The following code excerpt shows how to set the prefer-web-inf-classes parameter:

  <weblogic-web-app>
  <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
  </container-descriptor>
</weblogic-web-app>

If prefer-web-inf-classes is set to false, change the value to true.

Source the Environment Script on a UNIX Operating Environments

After you install the Web Agent Option Pack on a UNIX system, the installation program creates an environment script (ca-wa-opack-env.sh).

Source the environment script so the library path of the application server points to the location of the Web Agent Option Pack /bin directory.

Source the script by entering the following command at the command line:

. ./ca-wa-opack-env.sh

Setting the correct library path lets the option pack and the web or application server to work together.

After you source the script, the library path is set. The variable name for the library path differs depending on the operating system. Example of several library paths:

Solaris/Linux

LD_LIBRARY_PATH=/webagent_option_pack_home/bin

HP-UX

SHLIB_PATH=/webagent_option_pack_home/bin

AIX

LIBPATH=/webagent_option_pack_home/bin

Important! The application server startup script can reset the library path. Ensure that the path to the Web Agent Option Pack is the first entry in the path.

The path to the Web Agent Option Pack environment script points to one of the following locations:

• The installation directory of the web agent option pack. The default location is: /webagent_option_pack_home/bin.
• The installation directory of the web agent.

  If you install the option pack on the same system as the web agent, the script resides in the web agent directory. For any UNIX installation, the default location is /web_agent_home/bin.

Create an SmHost.conf File

The FWS application requires an SmHost.conf file. However, the Web Agent Option Pack does not install this file, so you must create it.

To create an SmHost.conf

1. Go to the directory /webagent_option_pack_home/bin
2. Run the smreghost.exe.

   For instructions on running smreghost.exe, see the Web Agent Installation Guide.

3. Put the SmHost.conf file in the following directory on Systems 2 and 5:

   /webagent_option_pack_home/config

Create a WebAgent.conf File

The FWS application requires the WebAgent.conf file. However, the Web Agent Option Pack does not install this file, so you must create it.

To create a WebAgent.conf file

1. Copy the WebAgent.conf file from System 1 to the following directory on System 2 and System 5:

   /webagent_option_pack_home/config

   webagent_option_pack_home

   Defines the installed location of the Web Agent Option Pack on System 2 or System 5.

2. Modify the WebAgent.conf file by:
   1. Setting the EnableWebAgent parameter to YES.
   2. Modifying other configuration parameters to suit FWS.

The following sample shows a WebAgent.conf file for the FWS application:

# WebAgent.conf - configuration file for the Federation Web Services Application
#agentname="agent_name, IP_address"
HostConfigFile="/webagent_option_pack/config/SmHost.conf"
AgentConfigObject="agent_config_object_name"
EnableWebAgent="YES"