Configuring the Fan-Out Driver as a Remote Loader Driver

Document ID:3367789
Creation Date:06-Dec-2006
Modified Date:26-Apr-2012
- Micro Focus Products:
  Identity Manager

Environment

Novell Identity Manager Driver- Core Fan Out

Novell Identity Manager Identity Manager 3.0

Situation

There are some cases where for troubleshooting or other memory management reasons, it may be desirable to remove the Core Fan-out Driver from the NDSD Memory space on a Linux, Unix or Windows box. These instructions are for changing an existing Driver to Remote Loader mode. The installer for Fan-Out Driver 3.11 will create a new Driver automatically. To do this you must have the latest Fan-out Driver release and patches installed.

Resolution

To do this you must have the latest Fan-out Driver release and patches installed.
Install Remote Loader Components to Connected System
See your Identity Manager Administration Guide for details.
Create a directory for Remote Loader Components on Connected System
Recommended paths:
Linux/Solaris: /usr/local/ASAM/rdxml
Windows: C:\NOVELL\ASAM\RDXML
Edit Driver properties in Novell iManager:
- Under Driver Module, select the "Connect to Remote Loader" option.
- Set the Driver Object Password and make a note of it.
- Under Authentication, enter the following for "Remote loader connection parameters":
  hostname={eDir/IDM host} port={Remote Loader port}
  The default port is 8090, so a sample string would be:
  hostname=localhost port=8090
- Also under authentication, set the Remote Loader Password and make a note of it.
- Under Driver Parameters, click "Edit XML." In the new window, check the "Enable XML editing" box. In the edit box, inside of the and tags, enter the following XML text:
```
<
        definition display-name="Is Remote Loader:" name="isRemoteLoader" type="boolean">Is the Driver a Remote Loader Driver?true
```
  Click OK in both windows to save your changes.
- Driver Settings should reflect the operating system of the Connected System. This will affect the Debug Log File and Install Directory settings. Also, Debug to DSTrace and Log to DSTrace should be disabled on Linux and Solaris.

Create the Configuration File
Linux/Solaris:

Create a text file in the directory you created on the Connected System, e.g. fanout.conf.

Enter the contents of the file:

-description "Fan-Out Driver"

        -commandport 8000

        -connection "port=8090"

        -module /usr/local/ASAM/bin/CoreDriver/libasamcdrv.so

The logic in the rdxml control script requires the parameters being searched (i.e. '-module') to be the FIRST characters entered on the .conf line, otherwise the script will not find it's intended variable, and the control script startup fails.
The text should be left justified in the fanout.conf script, with no spaces or tabs.

Windows:

Start the Identity Manager Remote Loader Console application

Click the Add button to create a new instance.

enter a description in the Description box (e.g. "Fan-Out Driver")

Select {ASAM folder}\bin\CoreDriver\asamcdrv.dll for the driver.

Enter the Remote Loader and Driver Object Passwords that you specified for the driver in iManager.

Change other settings as desired (such as trace level) and click OK.
The above values are default values which can be changed if necessary. See your Identity Manager Administration Guide for more parameter information.

Secure the Remote Loader Driver (Linux/Solaris only)
The Remote Loader uses passwords to authenticate to IDM. Use the Remote Loader program to set these passwords.
Linux/Solaris: rdxml -config {config_file} -sp {Remote Loader password} {Driver Object password}
In the command above, substitute the passwords you specified when configuring the Driver in iManager.
Start the Remote Loader Driver
- Start the Driver engine component in iManager, as you would a normal Driver.
- Run the Remote Loader program on the Connected System:
  Linux/Solaris: rdxml -config {config_file} Windows: Select the Driver instance in the Remote Loader Console and click Start.
Stop the Remote Loader Driver (when needed)
- Linux/Solaris: rdxml -config {config_file} -u
- Windows: Select the driver instance in the Remote Loader Console and click Stop.
- You may then stop the Driver engine component in iManager.