Previous Topic: Modify the Plug-in for an iPlanet Web Server

Next Topic: Verify the Clustered Installation

Start the WebLogic Cluster

After you configure managed nodes, you start the WebLogic cluster.

Note: If you are installing CA Identity Manager as part of an upgrade, you should now return to the Upgrade Guide to perform any final steps in the upgrade process.

If you are using WebLogic in production mode, the Identity Manager EAR may not auto-deploy the first time you start the application server after an install or upgrade. If this should occur, deploy the IdentityMinder.ear manually from the user_projects\applications folder.

To start the WebLogic cluster

  1. Start one of the SiteMinder Policy Servers that supports Identity Manager if you are using SiteMinder.

    Note: If you have a Policy Server cluster, only one Policy Server should be running while you create Identity Manager directories, create or modify Identity Manager environments, or change WorkPoint settings.

  2. Start the Node Manager on each managed node.
  3. Use the WebLogic Administration Console to start the managed nodes:
    1. Navigate to Environment, servers, managed node, control, start/stop.
    2. Repeat for each managed node in the cluster.

    Note: If errors stating that Identity Manager cannot connect to SiteMinder occur, set the -Djava.library.path in the Arguments field in the WebLogic console for each node in the cluster. The –Djava.library.path must be set to the directory that contains the SiteMinder library files. Make sure that this path is not overwritten by the default path.

  4. If you have already installed a SiteMinder Web Agent, start the Web Server where you installed the SiteMinder Web Agent and the application server proxy plug-in.