Installation Guides › WebLogic Version › Installation on a WebLogic Cluster › How to Install CA Identity Manager on a WebLogic Cluster › Create a WebLogic Cluster › Configure Managed Nodes

Configure Managed Nodes

The CA Identity Manager installer installs JAR files on the Administration Server. These files are needed by the managed nodes, but they are outside the EAR and are not pushed to the nodes. Using this procedure, you copy the JAR files to each managed node and configure the JDBC drivers on each node.

Note: This procedure also applies after you have completely installed CA Identity Manager and you want to add more nodes.

To configure managed nodes

1. Copy the database JDBC drivers to all other managed nodes. Copy the sqljdbc.jar or ojdbc14.jar from …./tools/lib/jdbcdrivers/ to WL_HOME/server/lib/ on the node.
2. Log onto a node where you installed Node Manager.
3. If you have installed Node Manager as a Windows service, it must be disabled first as follows:
   1. Double-click Administrative Tools on the Control Panel.
   2. Double-click the Services icon.
   3. Double click BEA Products NodeManager.
   4. Click Stop.
   5. Click Startup type and select Disabled.
4. On the Admin Server, start WebLogic.
5. Open Weblogic Admin Server Administration console
   1. Navigate to Environment, Servers, Server, Server Start tab.
   2. Fill in Java Home with Sun JDK home location of the JDK shipped with the application server.

      For example: C:\bea\jdk160_05

   3. Fill in Java Vendor with Sun.
   4. Fill in Class Path with the fully resolved content of WEBLOGIC_CLASSPATH from commEnv.{cmd,sh} file shipped with the Application installation supplemented by WL_HOME\server\lib\ojdbc14.jar;WL_HOME\server\lib\sqljdbc.jar where WL_HOME is as set in commEnv.{cmd,sh} file shipped with the product.

      For example, in a WebLogic 9.2 installation:

      E:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;
      E:\bea\jdk150_12\lib\tools.jar;
      E:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;
      E:\bea\WEBLOG~1\server\lib\weblogic.jar;
      E:\bea\WEBLOG~1\server\lib\webservices.jar;
      E:\bea\WEBLOG~1\server\lib\ojdbc14.jar;
      E:\bea\WEBLOG~1\server\lib\sqljdbc.jar;
      

      For example, in a WebLogic 10.3 installation:

      C:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;
      C:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;
      C:\bea\JDK160~1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp.jar;
      C:\bea\WLSERV~1.3\server\lib\weblogic.jar;
      C:\bea\modules\features\weblogic.server.modules_10.3.0.0.jar;
      C:\bea\WLSERV~1.3\server\lib\webservices.jar;
      C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;
      C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.jar;
      C:\bea\WLSERV~1.3\server\lib\ojdbc14.jar;C:\bea\WLSERV~1.3\server\lib\sqljdbc.jar
      

   5. Fill in arguments with:

       -server -Xms768m -Xmx768m -XX:MaxPermSize=492m -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory
      

6. Open commEnv.{cmd,sh} file under WL_HOME\weblogic92\common\bin or WL_HOME\weblogic103\common\bin. At the end of the file, add the following:
   1. For Windows

      set IM_SM_PATH=%WL_HOME%\common\nodemanager\servers\<server>\stage\IdentityMinder\IdentityMinder.ear\library
      set PATH=%PATH%;%IM_SM_PATH%
      

   2. For UNIX

      IM_SM_PATH=${WL_HOME}/common/nodemanager/servers/<server>/stage/IdentityMinder/IdentityMinder.ear/library
      LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${IM_SM_PATH}
      export LD_LIBRARY_PATH
      

   Note: If IM_SM_PATH is already defined in this file, replace the definition with the Windows or UNIX definition from this step.

7. Log onto the next node and repeat this procedure.

More information:

Start the WebLogic Cluster