9.3 Clustering the Remote Loader

The Remote Loader is an additional feature of Identity Manager that extends the Identity Manager functionality across applications. It allows a few Identity Manager drivers to connect to external applications without having the Identity Vault and the Identity Manager engine installed on the same server as the application.

NOTE:For clustering the Remote Loader, you need not cluster the Identity Manager engine.

9.3.1 Installing and Configuring the Remote Loader on Cluster Nodes

Install the Remote loader on all the cluster nodes.

For installing the Remote Loader, see Installing the Remote Loader in the Identity Manager 4.0.2 Framework Installation Guide.

For configuring the Remote Loader, see "Configuring the Remote Loader" in the Identity Manager 4.0.2 Remote Loader Guide.

9.3.2 Configuring the Remote Loader Resources

IMPORTANT: Copy the shim configuration to the /etc/opt/novell/dirxml/rdxml location and disable the Remote Loader service startup.

  1. Select Connection > Login.

  2. In the left pane, select Resources, then click Add > Primitive and enter a unique ID for the resource.

  3. Select Primitive and enter a unique ID for the group, then specify values for the following fields:

    • Enter a unique ID for the resource IP address.

    • From the Class list, select the resource agent as ocf

    • Select heartbeat from the Provider list.

    • Select IP Address from the Type list, then click forward.

    • Switch to the Instance Attributes tab, select the unique ID that you have specified, then click Edit to add the virtual IP address of eDirectory.

    • Click Ok, then Apply.

    • Select Primitive and specify the unique ID for the rdxml service.

    • From the Class list, select the resource agent as lsb.

    • From the Type list, select rdxml, then click Forward.

    • Click Ok, then Apply.

    • Click Cancel if you do not want to add more sub-resources to a group.