Web Agent Guides › Web Agent Option Pack Guide › Installation Requirements and Considerations

Installation Requirements and Considerations

This section contains the following topics:

General Option Pack Installation Requirements

System Locale Must Match the Language of Installation and Configuration Directories

Components Required for CA SiteMinder® Federation

Components Required for eTelligent Rules

Version Compatibility

Environment Variables Added by the Installation

Java Virtual Machine Installation Error on Solaris can be Ignored (149886)

Web Agent Option Pack on JBOSS Requires Workaround

JBOSS 5.1.2 on Windows Requires Configuration Change (166151)

General Option Pack Installation Requirements

Before you install the Web Agent Option Pack, the following components are required:

Supported application server
For the supported application servers, see the Platform Support Matrix at the Technical Support site.

If you use ServletExec as your application server, apply the most current hot fixes. Federation Web Services requires these hot fixes to work with ServletExec. To obtain the hot fixes, go to the New Atlanta Communications web site.
A supported Java Development Kit (JDK).
This JDK is required even if you are using an application server that ships with a JDK or JRE.
For Linux operating platforms, be sure that the required Linux libraries are installed.

You can install the Web Agent Option Pack without the Web Agent. However, install the Web Agent before using federation.

Required Linux Libraries

Certain library files are required for components operating on Linux operating environments. Failure to install the correct libraries can cause the following error:

java.lang.UnsatisfiedLinkError

If you are installing, configuring, or upgrading a Linux version of this component, the following packages are required on the host system:

Red Hat 5.x:

compat–gcc-34-c++-3.4.6-patch_version.I386
libstdc++-4.x.x-x.el5.i686.rpm
libidn.so.11.rpm
ncurses

Red Hat 6.x:

libstdc++-4.x.x-x.el6.i686.rpm
libidn-1.18-2.el6.i686
libXext.i686.rpm
libXrender.i686.rpm
linXtst.i686.rpm
libidn.so.11.rpm
ncurses

Additionally, for Red Hat 6.x (64-bit):

All the RPM packages that are required for 64-bit Red Hat 6.x are 32-bit packages.

libXau-1.0.5-1.el6.i686.rpm
libxcb-1.5-1.el6.i686.rpm
compat-db42-4.2.52-15.el6.i686.rpm
compat-db43-4.3.29-15.el6.i686.rpm
libX11-1.3-2.el6.i686.rpm
libXrender-0.9.5-1.el6.i686.rpm
libexpat.so.1 (provided by expat-2.0.1-11.el6_2.i686.rpm)
libfreetype.so.6 (provided by freetype-2.3.11-6.el6_2.9.i686.rpm)
libfontconfig.so.1 (provided by fontconfig-2.8.0-3.el6.i686.rpm)
libICE-1.0.6-1.el6.i686.rpm
libuuid-2.17.2-12.7.el6.i686.rpm
libSM-1.1.0-7.1.el6.i686.rpm
libXext-1.1-3.el6.i686.rpm
compat-libstdc++-33-3.2.3-69.el6.i686.rpm
compat-db-4.6.21-15.el6.i686.rpm
libXi-1.3-3.el6.i686.rpm
libXtst-1.0.99.2-3.el6.i686.rpm
libXft-2.1.13-4.1.el6.i686.rpm
libXt-1.0.7-1.el6.i686.rpm
libXp-1.0.0-15.1.el6.i686.rpm
libstdc++.i686.rpm
compat-libtermcap.rpm
libidn.i686.rpm
ncurses

System Locale Must Match the Language of Installation and Configuration Directories

To install and configure a CA SiteMinder® component to a non-English directory, set the system to the same locale as the directory. Also, make sure that you installed the required language packages so the system can display and users can type localized characters in the installer screens.

For the details on how to set locale and required language packages, refer to respective operating system documents.

Components Required for CA SiteMinder® Federation

The following components are required for CA SiteMinder® Federation (Legacy and Partnership):

Policy Server
Application server or web server
Note: An application server with built–in web server, such as JBOSS, WebLogic or WebSphere, is required to deploy Federation Web Services. Alternately, a web server with an application server plug-in, such as ServletExec, can be used.
Web Agent Option Pack

Note: Refer to the Federation Release Notes for any known issues regarding federation features and the Web Agent Option Pack.

Components Required for eTelligent Rules

The following components are required for eTelligent Rules:

Policy Server
Web Agent Option Pack
The Web Agent Option Pack is required to support eTelligent Rules that contain POST variables.

Version Compatibility

If the Web Agent and Web Agent Option Pack are installed on the same server, they must both be the same version, including the Service Pack and CR version. However, the Web Agent Option Pack can operate with Policy Servers of different, but compatible versions. To learn which Policy Server versions the Web Agent Option Pack is compatible with, see the SiteMinder Platform Support Matrix.

Important! When different compatible versions of the Web Agent Option Pack and Policy Server are mixed, federation functionality is limited to that of the lesser of the two components. Thus, if the Policy Server supports a federation feature but the Web Agent Option Pack does not, a request that requires that functionality may be rejected or the functionality ignored. The same is also true if the Web Agent Option pack supports a feature and the Policy Server does not.

More information:

Mixed-Version Upgrade Considerations

Environment Variables Added by the Installation

The installation of the Web Agent Option Pack sets the following environment variables:

NETE_WA_OPACK = “INSTALLED”
NETE_WA_PATH = $NETE_WA_ROOT$$/$bin;$NETE_WA_ROOT$$/$bin$/$thirdparty;
$NETE_JRE_ROOT$$/$bin;$NETE_JRE_ROOT$$/$bin$/$server

Java Virtual Machine Installation Error on Solaris can be Ignored (149886)

Symptom:

You are doing a console mode installation of a CA SiteMinder® product on a Solaris platform. The following error message displays: "Unable to install the Java Virtual Machine included with this installer."

Solution:

Ignore this error message. The error is a third-party issue and it has no functional impact.

Web Agent Option Pack on JBOSS Requires Workaround

Symptom:

On a JBoss 5.1.2 server, system JARs are overriding application-specific JARs, such as those JARs for the Web Agent Option Pack.

Solution:

Prevent the Web Agent Option Pack XML API files from being overwritten by JBOSS system JARS.

Important! This workaround only applies to the version of JBOSS 5.1.x that the product supports.

Add the following filter package in two places in the war-deployers-jboss-beans.xml file:

<property name="filteredPackages">javax.servlet,org.apache.commons.
logging,javax.xml.parsers,org.xml.sax,org.w3c.dom</property>

The filter package allows the use of the Web Agent Option Pack XML API files instead of the JBOSS system files.

Follow these steps:

Locate the war-deployers-jboss-beans.xml file located in the directory:
/deployers/jbossweb.deployer/META-INF/

Find the following entry:

<property name="filteredPackages">javax.servlet,org.apache.
commons.logging</property>

Change the entry to:

<property name="filteredPackages">javax.servlet,org.apache.commons.
logging,javax.xml.parsers,org.xml.sax,org.w3c.dom</property>

This entry in the file is on one line.

Find the second instance of the entry in step 2 and replace it with the entry in step 3.
Add the filter package in both places in the XML file.
Save the XML file.

JBOSS 5.1.2 on Windows Requires Configuration Change (166151)

For JBOSS 5.1.2 on Windows, a configuration change is required to use the SAML 2.0 HTTP-Artifact profile for single sign-on.

Edit the war-deployers-jboss-beans.xml file.

Follow these steps:

Navigate to the following directory
jboss_install_home\jboss-as\server\default\deployers\jbossweb.deployer\META-INF\war-deployers-jboss-beans.xml
Change the property name entries in the file to:
<property name="filteredPackages">javax.servlet,org.apache.commons.
logging,javax.xml.parsers,org.xml.sax,org.w3c.dom</property>

Note: The <property name="filteredPackages"> entry occurs twice in the file. Make the same change in each place.