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

Run the Installation in Console Mode on UNIX

When performing a fresh install on UNIX platforms, you can run the installation program for the SiteMinder Agent for IBM WebSphere from the console.

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

To obtain the installation kit from the Support site

1. Click Technical Support.
2. Log in to CA Support Online.
3. Click Download Center.
4. Search the Download Center for the CA SiteMinder Agent for WebSphere installation kit for your operating environment.
5. Download the kit and extract its content to a temporary location.
6. 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

To install the SiteMinder Agent for WebSphere by running the installation script in a UNIX console

1. Login as the user who installed WebSphere. For example, if you installed as root, login as root.
2. Exit all applications that are running.
3. Open a command shell and navigate to where the install kit is located
4. Enter the following command:

   sh ca-asa-was-12.0-sp02.sh -i console
   

   The -i console option interactively runs the installation from a console.

5. Read the License Agreement. If you accept the terms, enter Y and then press Enter.
6. In the Choose Install Folder section, specify a location for the SiteMinder Agent for IBM WebSphere installation, and then press Enter.

   We recommend the following location:

   /opt/smwasasa

7. Enter Y, then press Enter to create or confirm the installation location for the SiteMinder Agent.

   The program installs the required files in the SiteMinder Agent install location.

8. Specify the installation location of the WebSphere Application Server. For example:

   /opt/WebSphere/AppServer
   

   The program installs the required files in the WebSphere install location.

9. When the Host Registration prompt appears, select one of the following numbers:
   • 1—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 Administrative UI before registering a trusted host.

   • 2—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 the 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.

10. If you entered 1 at the Host Registration prompt (to create a new trusted host), do the following:
    1. When prompted to select a FIPS mode, select one of the following options:
       • 1—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.

       • 2—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.

       • 3—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. When prompted, enter the following information:
       • 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, a message appears and you can register the trusted host manually later.

       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.
       

11. If you entered "2" at the Host Registration prompt (to use an existing trusted host), enter the location of the host configuration file (smhost.conf) created for a SiteMinder Agent for WebSphere.

    The default location of the file is:

    ASA_HOME/conf/

12. Supply the name of the Agent Configuration Object that you created for the SiteMinder Agent.
13. At the installation complete prompt, press Enter to exit the installer. The installation of the SiteMinder Agent for IBM WebSphere is complete.

More information:

Preconfigure the Policy Objects