IBM Tivoli Federated Identity Manager, Version 6.2.1

Mapping the runtime to a Web server

About this task

When Tivoli® Federated Identity Manager runtime is deployed, it is automatically mapped to the default WebSphere® Application Server. In WebSphere cluster environments, WebSphere Application Server is usually deployed into a topology with a Web server such as IBM® HTTP Web server. In this case, a WebSphere plug-in has been installed and configured for the IBM HTTP Web server.

The IBM HTTP Web server performs the workload balancing across cluster members. This means that the Tivoli Federated Identity Manager runtime must be mapped to the Web server.

Procedure

  1. Log in to the WebSphere administrative console:
    http://your_host_name:9060/admin
  2. Navigate to Enterprise Applications -> ITFIM Runtime.
  3. The Configuration tab is displayed. In the Web Module Properties section, select the Virtual hosts link. A section titled Apply Multiple Mappings displays a table with a row entry for each Web module.
  4. Select the check box for each Web module. Ensure that all check boxes are selected.
  5. Accept the default entry of default_host in the Virtual host field for each Web module.
  6. A message box prompts you to save your changes. Click the Save link.
  7. The Save panel is displayed. Click the Save button.
  8. Return to Enterprise Applications -> ITFIM Runtime.
  9. The Configuration tab is displayed. In the Modules section, select the Manage Modules link. The Enterprise Application -> ITFIM Runtime -> Manage Modules page is displayed. At the top, you should see the title Manage Modules.
  10. Select the check box for each of the Web modules. For Tivoli Federated Identity Manager the list of modules can include, but is not limited to:
    • ITFIM-Runtime
    • ITFIM Security Token Service
    • ITFIM Information Service
    • TokenService
    • TrustServerWST13
  11. A scrolling window lists Clusters and Servers. Select both of the following entries:
    • The entry for your cluster. For example, cluster=fimCluster.
    • The entry for the Web server. For example, server=webserver1
  12. While both items are highlighted, click Apply. In the Module table, the definition for each server and cluster is added to the entry (in the Server column) for each of the Web modules that you selected.
  13. Click OK at the bottom of the page. A message prompts you to save your changes.
  14. Click the Save link. The Enterprise Applications → Save panel is displayed.
  15. Click Save.
  16. To finish configuring the Tivoli Federated Identity Manager runtime into a WebSphere cluster, continue with Enabling replication in a WebSphere cluster.


Feedback