Run the Installation in GUI Mode

Agent Guide › Installing and Upgrading the Agent › Install the SiteMinder Agent for IBM WebSphere › Run the Installation in GUI Mode

Run the Installation in GUI Mode

When performing a fresh install you can run the installation program for the SiteMinder Agent for IBM WebSphere using a graphical user interface on Windows and UNIX platforms.

The installation program and other required files can be downloaded from the Technical Support site.

To obtain the installation kit from the Support site

Click Technical Support.
Log in to CA Support Online.
Click Download Center.
Search the Download Center for the CA SiteMinder Agent for WebSphere installation kit for your operating environment.
Download the kit and extract its content to a temporary location.
Verify that all required files are present:
- ca-asa-wls-12.0-sp02.bat (Windows)
- ca-asa-wls-12.0-sp02.sh (UNIX)
- ca-asa-wls-install.jar

Notes for UNIX Installations

If you are planning to run the installation in GUI mode on UNIX, consider the following before you begin:

Running a GUI-mode installation or running the Configuration Wizard using the Exceed application can cause truncation of text in dialogs because of unavailable fonts. This limitation has no affect on SiteMinder Agent installation and configuration.
If you are installing the SiteMinder Agent over telnet or other terminal emulation software, you must have an X-Windows session running in the background to run the GUI mode installation. Additionally, set the DISPLAY variable to your terminal, as follows:
DISPLAY=111.11.1.12:0.0

export DISPLAY

If you try to run in GUI mode through a telnet window without an X-Windows session, the installer throws a Java exception and exits.
You can also run a command line installation from a console window.

To install the SiteMinder Agent using the graphical user interface (GUI) mode

Log in as the user who installed WebSphere. For example, if you installed as root, login as root.
Exit all applications that are running.
Open a command window and navigate to where the install kit is located
Enter the appropriate command for your operating system.
Windows:
```
ca-asa-was-12.0-sp02.bat
```
UNIX:
```
sh ca-asa-was-12.0-sp02.sh
```
Read the License Agreement. If you accept the terms, select the I accept the terms of the License Agreement option and click Next.
On the Choose Install Folder screen, specify a location for installing the SiteMinder Agent for IBM WebSphere and click Next. We recommend the following default location:
Windows: C:\Program Files\CA\smwasasa

UNIX: /CA/smwasasa

If you specify a folder that does not exist, the installer asks if you want to create it. Click Yes to create it; the installer creates a folder named smwasasa in whatever directory you specify.

The program installs the required files.
On the Choose WebSphere Folder screen, specify the installation location of the WebSphere Application Server and click Install. For example:
Windows: drive:\WebSphere\AppServer

UNIX: /opt/WebSphere/AppServer

The program installs the required files.

Note: If the location you specify is not present, the installation program displays an error message and asks you to reenter the information.
On the Host Registration screen, select one of the following:
- Yes, create trusted host — The installer invokes the Host Registration tool, smreghost, to register the unique trusted host name with the Policy Server and create the SmHost.conf file. Registering the system as a trusted host enables the SiteMinder Agent to establish a secure, trusted connection with the Policy Server.
  Create a Host Configuration Object in the Policy Server before registering a trusted host.
- No, use existing file — The installer invokes the smreghost tool to use an existing SmHost.conf file created for a SiteMinder Agent for IBM WebSphere to establish the connection between the trusted host and the Policy Server.
  Note: Specify this option only if you are reinstalling the SiteMinder Agent for WebSphere and the SmHost.conf file that you want to use was therefore created by the smreghost tool supplied with this release. The SiteMinder Agent for WebSphere is implemented using a pure Java SiteMinder Agent API and cannot use an SmHost.conf file created for another SiteMinder Agent to establish its connection to the Policy Server.
If you selected "Yes, create a trusted host" on the Host Registration screen, do the following:
1. On the FIPS Mode Setting screen, select one of the following options and then click Next:
  
  FIPS Compatibility Mode (Default)
  
  Specifies non-FIPS mode, which lets the Policy Server and the Agents read and write information using the existing SiteMinder encryption algorithms. If your organization does not require the use of FIPS-compliant algorithms, the Policy Server and the Agents can operate in non-FIPS mode without further configuration. If you do not want to use FIPS encryption, accept this default.
  
  FIPS Migration Mode
  
  Specifies FIPS-migration mode, which is used when you are upgrading an earlier version of SiteMinder to full-FIPS mode. The Policy Server and the Agents continue to use the existing SiteMinder encryption algorithms as you migrate your environment to use only FIPS 140-2 approved algorithms.
  
  FIPS Only Mode
  
  Specifies full-FIPS mode, which requires that the Policy Server and Web Agents read and write information using only FIPS 140-2 algorithms.
  
  Important! A SiteMinder installation that is running in Full FIPS mode cannot interoperate with, or be backward compatible to, earlier versions of SiteMinder that do not support FIPS, including all agents, custom software using older versions of the Agent API, and custom software using PM APIs or any other API that the Policy Server exposes. Relink all custom software using Policy Management APIs or any other API that the Policy Server exposes with FIPS-supporting versions of the respective SDKs to achieve the required support for Full FIPS mode.
2. On the Host Registration screen, enter the following information and click Next:
  - Policy Server IP Address—IP address of the Policy Server where you are registering the host
  - SM Admin Username—Name of the administrator permitted to register the host with the Policy Server
  - SM Admin Password—Password for the SM Admin account
  - Host Name—Unique name that represents the trusted host to the Policy Server. The name does not have to be the same as the physical client system you are registering; it can be any unique name.
  - Host Config Object— Name of the Host Configuration Object specified in the Policy Server.
  The installation program registers your unique trusted host name with the Policy Server. If your Policy Server is not running, an error message appears and you can register the trusted host later using the smreghost tool.
  
  If you have not patched the JVM Java Cryptography Extension (JCE) package for unlimited cryptography, host registration fails and the following error message appears:
```
Failed to enable any clusters. Registration has failed.
```
If you selected "No, use existing file" on the Host Registration screen, enter the location of a host configuration file (SmHost.conf) created for a SiteMinder Agent for WebSphere in the text box, or click Choose to browse for the file.
The default location of SmHost.conf is either:

ASA_HOME\conf\ (Windows)

or

ASA_HOME/conf/ (UNIX)
On the Agent Configuration screen, specify the name of the Agent Configuration Object that you created in the Administrative UI before installing the SiteMinder Agent. Click Next.
On the Install Complete screen, click Done to exit the installer.
The installation is complete.

More information:

Preconfigure the Policy Objects

Email CA Technologies about this topic