IBM Security Access Manager for Enterprise Single Sign-On, Version 8.2.1

Installation overview

Learn about the installation packages and installation prerequisites for each product component.

IMS Server installation

When you run the installer, it unpacks the IMS Server applications and configuration files into the designated installation folder. The installer also offers to deploy the IMS Server application files into the designated WebSphere® Application Server environment. The installer supports installation on both WebSphere Application Server Base and WebSphere Application Server Network Deployment editions.

Prepare the server hosts for the IMS Server and make sure that the software prerequisites are installed and configured before you run the IMS Server installer.

Figure 1. An example of a load balanced farm of IMS Servers with an IP load balancing infrastructure. Figure shows an example of a load balanced farm of IMS Servers with an IP load balancing infrastructure.

Figure shows an example of a load balanced farm of IMS Servers with an IP load balancing infrastructure.

For high availability configuration, prepare the IP load balancing infrastructure. The IP load balancer can be either a hardware or software load-balancer. The IP load balancer must route traffic from any client back to the same member host in the server farm.

AccessAgent installation

The AccessAgent installation package comes in the form of MSI and EXE files, and some configuration files.

The configuration files indicate the location of the IMS Server, whether a GINA replacement is required, and a few other installation options.

You can do a push-installation of the MSI and configuration files on the target Windows workstations and servers through typical software distribution systems. For example: Microsoft Active Directory Group Policy Object (AD GPO) and Tivoli® Provisioning Manager.

You can also use an application provisioning software like Tivoli Provisioning Manager. AccessAgent is installed silently with the required "language" support added as an MSI option. Reboot the computer after completing the installation.

Alternatively, you can download the installation package to individual target machines and manually install it from there. You must have Administrator rights on the computer to do this option. If you use the EXE installer, you are prompted to select the language for AccessAgent during the installation process.

If you want to enforce strong authentication, you must install the required third-party drivers and libraries before you install AccessAgent.

Note: Do not remove deploymentscript.vbs directly. Keep preremove and postcopy sub. Comment out the content of these two subs instead. Otherwise, it causes installation error.

AccessStudio installation

The AccessStudio installer is an InstallShield-generated MSI file that is intended for Administrators. You can install AccessStudio manually on the Administrator user workstation.

You must install AccessAgent and Windows .NET Framework 2.0 before you install the AccessStudio. An error is displayed if either of these prerequisites are missing at the time of installation.

Feedback