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

Network deployment (clustered)

The Network Deployment consists of multiple WebSphere® Application Servers in a cluster, where the IMS Server is managed as a single domain by the Deployment Manager.

Figure 1. Example of IBM Security Access Manager for Enterprise Single Sign-On in a two node network deployment cluster for high availability
The diagram shows an example of the IMS Server in a two node WebSphere Application Server cluster.

Use a network deployment (cluster) to sustain a high availability environment. The web servers are deployed on the same application-tier host. A load balancer is at the front of the deployment. Alternatively, the web servers and application servers can be deployed on separate hosts. A network deployment scenario is typically used for medium to large-scale deployments.

You might want to add additional application servers to an existing network deployment scenario for any of the following reasons:
  • To build redundancy into your product deployment (high availability).
  • To restore an application server that failed.
  • To have deployments that support higher volume of requests or support more users.

Implementation overview

The following list is an overview of how to do a network deployment.
  1. Check and comply with the requirements.
  2. Install and configure the required middleware.
    1. Prepare the database server. If you are using DB2® or Oracle, create the IMS Server database.
    2. On Host A, install WebSphere Application Server.
    3. On Host A, install the WebSphere Update Installer.
    4. On Host A, install the WebSphere Application Server fix packs.
    5. On Host A, create a deployment manager profile and custom server profile.
    6. On Host B, install WebSphere Application Server.
    7. On Host B, install the WebSphere Update Installer.
    8. On Host B, install the WebSphere Application Server fix packs.
    9. On Host B, create a custom server profile.
    10. On Host A and B, install the IBM® HTTP Server.
    11. Install the IBM HTTP Server fix packs.
    12. Create a cluster. Add Host A and Host B as cluster members.
    13. Start the WebSphere Application Server profile.
  3. Deploy the IMS Server applications in the WebSphere Application Server.
  4. Verify the IMS Server deployment on the WebSphere Application Server.
  5. To implement biometric support, install the Native Library Invoker (NLI) resource adapter.
  6. Configure the IBM HTTP Server.
  7. Configure the IMS Server.
  8. Restart the WebSphere Application Server.
  9. Configure your single sign-on authentication environment. See the IBM Security Access Manager for Enterprise Single Sign-On Configuration Guide.
  10. If you want to create reports, install IBM Cognos® Business Intelligence or Tivoli® Common Reporting.
Parent topic: Planning for the IMS Server deployment

Feedback