This section presents the various step-by-step tasks that can be combined to cover all Core Driver installation scenarios. The tasks are grouped first into four basic categories:
NOTE: Be aware of the following:
Identity Manager 3.6.1 does not support NetWare. Therefore, if you wish to upgrade a Core Driver running in a NetWare environment, you will need to migrate to one of the other supported environments. See Migrating From NetWare for more details.
Some of the configuration tasks discussed briefly in this section are covered again in more detail in Section 6.0, Configuring and Administering the Core Driver
Core Driver installation on Linux and UNIX begins with one of the following tasks, depending on your scenario:
To install a new Driver Shim on Linux or Solaris:
From your installation media, locate and execute the appropriate self-extracting installer:
sh linux_x86_coredriver.bin
sh linux_x86_64_coredriver.bin
sh solaris_sparc_coredriver.bin
NOTE:The x86 (32-bit) installer is compatible with both 32-bit and 64-bit versions of Linux. To use the x86_64 (64-bit) installer with the 32-bit Identity Manager engine, you must first install and configure the 64-bit LDAP SDK (see Installing the LDAP Client SDK Libraries).
Accept the license, select your installation directory and proceed to install the product files.
The installer will next assist you in configuring the Driver Shim. You will be prompted for the Remote Loader password, which is used to encrypt driver network communications. Enter a password and remember it, as you will use it when configuring the driver in iManager.
You will then be prompted for a Driver Object password. This is used to access the driver object in eDirectory. This password will also be used when configuring the driver in iManager.
The next entry you are asked for is the eDirectory server/port, so the installer can retrieve an SSL certificate from eDirectory using your SSL-configured LDAP server. Enter the DNS name or IP address of the LDAP server that the Core Driver Shim will use to communicate with. Typically, this will be on port .
When prompted for an eDirectory admin name/password, enter the eDirectory administrator’s ID in LDAP dot format (example: , followed by the password.
NOTE: The installer must get a successful directory connection in order to proceed. Consult your eDirectory LDAP documentation for troubleshooting.
When prompted for an ASAM System Container Context, specify the distinguished name (DN) of the container in which the organizational unit ASAM System should be created. The driver will store configuration and synchronization information in this container. Enter the DN in LDAP dot format. Example: .
You are next prompted for information about the Core Driver, beginning with a descriptive name and the network port it will use (default 3451).
For the Core Driver network address, select a DNS name or IP address for the Core Driver. If your system has multiple addresses, use one which other systems (platforms) can use to communicate with the driver.
The installer will then create the eDirectory objects and indexes needed to completed the configuration.
Immediately after installation, you may need to change the port setting for the Core Driver’s built-in remote loader. This is especially likely if you are also using the standard remote loader that comes with Identity Manager, since both versions of the remote loader use 8090 as their default port setting.
The port setting for the Core Driver’s built-in remote loader resides in the fanout.conf file, which is located in /usr/local/ASAM/data/.
Edit the following line in fanout.conf to reflect the desired port:
-connection "ca=/usr/local/ASAM/keys/ca.pem port=8090"
NOTE:If you have a firewall, be sure to add the Driver's network port (default 3451) to its open ports list.
At the completion of this installation task, go next to Section 5.2.3, Setting Up the Core Driver in iManager.
Upgrading a driver running in Local mode on your Linux or Solaris eDirectory server is the most common upgrade scenario. Once upgraded, it will run as a Remote Driver, with both the Driver object and Driver Shim integrated on the same physical host.
To upgrade a Driver Shim that is running in Local mode in Linux or Solaris:
Stop the Core Driver object in iManager.
From your installation media, locate and execute the appropriate self-extracting installer:
sh linux_x86_coredriver.bin
sh linux_x86_64_coredriver.bin
sh solaris_sparc_coredriver.bin
NOTE:The x86 (32-bit) installer is compatible with both 32-bit and 64-bit versions of Linux. To use the x86_64 (64-bit) installer with the 32-bit Identity Manager engine, you must first install and configure the 64-bit LDAP SDK (see Installing the LDAP Client SDK Libraries).
Accept the license, select the same installation directory as your previous installation (usually this is /usr/local) and proceed to install the product files.
The installer will next assist you in configuring the Driver Shim. You will be prompted for the Remote Loader password, which is used to encrypt driver network communications. Enter a password and remember it, as you will use it when configuring the driver in iManager.
You will then be prompted for a Driver Object password. This password will also be used when configuring the driver in iManager.
The next entry you are asked for is the eDirectory server/port, so the installer can retrieve an SSL certificate from eDirectory using your SSL-configured LDAP server. Enter the DNS name or IP address of the LDAP server that the Core Driver Shim will use to communicate with. Typically, this will be on port .
When prompted for an eDirectory admin name/password, enter the eDirectory administrator’s ID in LDAP dot format (example: , followed by the password.
NOTE: The installer must get a successful directory connection in order to proceed. Consult your eDirectory LDAP documentation for troubleshooting.
When prompted for an ASAM System Container Context, specify the distinguished name (DN) of the container in which the organizational unit ASAM System resides. You can find this information on the Provisioning Status Details page using the Fan-Out Driver Web application plug-in in iManager. Enter the DN in LDAP dot format. Example: .
When prompted whether to create a new Driver or upgrade an existing one, enter to upgrade an existing Driver.
When a list of drivers displays, enter the number corresponding to the Driver you plan to upgrade.
The installer will then generate an updated configuration file and install indexes needed to completed the configuration. (You may receive a warning message regarding indexes since they will already exist.)
Immediately after installation, you may need to change the port setting for the Core Driver’s built-in remote loader. This is especially likely if you are also using the standard remote loader that comes with Identity Manager, since both versions of the remote loader use 8090 as their default port setting.
The port setting for the Core Driver’s built-in remote loader resides in the fanout.conf file, which is located in /usr/local/ASAM/data/.
Edit the following line in fanout.conf to reflect the desired port:
-connection "ca=/usr/local/ASAM/keys/ca.pem port=8090"
NOTE:If you have a firewall, be sure to add the Driver's network port (default 3451) to its open ports list.
At the completion of this installation task, go next to Section 5.2.3, Setting Up the Core Driver in iManager, which includes the task for upgrading a Core Driver configuration
If you are running a Fan-Out Driver in Remote mode, you can upgrade the Driver Shim on the Linux or Solaris system and eliminate the need to run the Novell Java Remote Loader.
To upgrade a Driver Shim that is running in Remote mode in Linux or Solaris:
Stop the Core Driver object and the Remote Loader instance for the current driver in iManager.
Still in iManager, open the , select the Fan-Out Driver instance and click . Make a note of the , and fields.
Because you no longer need the standard Novell Remote Loader, you may disable or remove it as follows, depending on whether you have other Remote Drivers:
If you’re running other Remote Drivers on the system, simply remove the Fan-Out Driver instance by selecting it in the Remote Loader Console and clicking .
If you aren't running other Remote Drivers on the system, open and run | ( on Windows Server 2008) to remove the Novell Identity Manager Connected System program.
From your installation media, locate and execute the appropriate self-extracting installer:
sh linux_x86_coredriver.bin
sh linux_x86_64_coredriver.bin
sh solaris_sparc_coredriver.bin
NOTE:The x86 (32-bit) installer is compatible with both 32-bit and 64-bit versions of Linux. To use the x86_64 (64-bit) installer with the 32-bit Identity Manager engine, you must first install and configure the 64-bit LDAP SDK (see Installing the LDAP Client SDK Libraries).
Accept the license, select the same installation directory as your previous installation (usually this is /usr/local) and proceed to install the product files.
The installer will next assist you in configuring the Driver Shim. You will be prompted for the Remote Loader password, which is used to encrypt driver network communications. Enter a password and remember it, as you will use it when configuring the driver in iManager.
You will then be prompted for a Driver Object password. This password will also be used when configuring the driver in iManager.
The next entry you are asked for is the eDirectory server/port, so the installer can retrieve an SSL certificate from eDirectory using your SSL-configured LDAP server. Enter the DNS name or IP address of the LDAP server that the Core Driver Shim will use to communicate with. Typically, this will be on port .
When prompted for an eDirectory admin name/password, enter the eDirectory administrator’s ID in LDAP dot format (example: , followed by the password.
NOTE: The installer must get a successful directory connection in order to proceed. Consult your eDirectory LDAP documentation for troubleshooting.
When prompted for an ASAM System Container Context, specify the distinguished name (DN) of the container in which the organizational unit ASAM System resides. You can find this information on the Provisioning Status Details page using the Fan-Out Driver Web application plug-in in iManager. Enter the DN in LDAP dot format. Example: .
When prompted whether to create a new Driver or upgrade an existing one, enter to upgrade an existing Driver.
When a list of drivers displays, enter the number corresponding to the Driver you plan to upgrade.
The installer will then generate an updated configuration file and install indexes needed to completed the configuration. (You may receive a warning message regarding indexes since they will already exist.)
Immediately after installation, you may need to change the port setting for the Core Driver’s built-in remote loader. This is especially likely if you are also using the standard remote loader that comes with Identity Manager, since both versions of the remote loader use 8090 as their default port setting.
The port setting for the Core Driver’s built-in remote loader resides in the fanout.conf file, which is located in /usr/local/ASAM/data/.
Edit the following line in fanout.conf to reflect the desired port:
-connection "ca=/usr/local/ASAM/keys/ca.pem port=8090"
NOTE:If you have a firewall, be sure to add the Driver's network port (default 3451) to its open ports list.
At the completion of this installation task, go next to Section 5.2.3, Setting Up the Core Driver in iManager, which includes the task for upgrading a Core Driver configuration.
Core Driver installation on Windows begins with one of the following tasks, depending on your scenario:
To install a Driver Shim on a Windows System:
From your installation media, run the following command:
fan-out\IDMCoreDrivers\Win\win_x86_coredriver.exe
This x86 (32-bit) executable is compatible with both x86 and x64 versions of Windows.
Accept the license, select your installation directory and proceed to install the product files.
The installer will next assist you in configuring the Driver Shim. You will be prompted for the Remote Loader password, which is used to encrypt driver network communications. Enter a password and remember it, as you will use it when configuring the driver in iManager.
You will then be prompted for a Driver Object password. This is used to access the driver object in eDirectory. This password will also be used when configuring the driver in iManager.
The next entry you are asked for is the eDirectory server/port, so the installer can retrieve an SSL certificate from eDirectory using LDAP. Enter the DNS name or IP address of an eDirectory server, and the LDAP secure port (default 636). In the console window that appears, enter to accept the certificate.
NOTE: If you are running both eDirectory and Active Directory on the Windows server, you may need to change the LDAP ports of either eDirectory or Active Directory so that they do not interfere with each other. See your product documentation for more information.
When prompted for an eDirectory admin name/password, enter the eDirectory administrator’s ID in LDAP dot format (example: , followed by the password.
NOTE: The installer must get a successful directory connection in order to proceed. Consult your eDirectory LDAP documentation for troubleshooting.
When prompted for an ASAM System Container Context, specify the distinguished name (DN) of the container in which the organizational unit ASAM System should be created. The driver will store synchronization information in this container. This is usually the top-level organization in the tree. Example: .
You are next prompted for information about the Core Driver, beginning with a descriptive name and the network port it will use (default 3451).
For the Core Driver network address, select a DNS name or IP address for the Core Driver. If your system has multiple addresses, use one which other systems (platforms) can use to communicate with the driver.
The installer will then create the eDirectory objects and indexes needed to completed the configuration.
Immediately after installation, you may need to change the port setting for the Core Driver’s built-in remote loader. This is especially likely if you are also using the standard remote loader that comes with Identity Manager, since both versions of the remote loader use 8090 as their default port setting.
The port setting for the Core Driver’s built-in remote loader resides in the fanout.conf file, which is located in C:\Novell\ASAM\data\.
Edit the following line in fanout.conf to reflect the desired port:
-connection "ca=/usr/local/ASAM/keys/ca.pem port=8090"
NOTE:If you have a firewall, be sure to add the Driver's network port (default 3451) to its open ports list.
At the completion of this installation task, go next to Section 5.2.3, Setting Up the Core Driver in iManager.
You can upgrade a driver running in Local mode on your Windows eDirectory server. The upgraded Driver will run as a Remote Driver, with both the Driver objects and Driver Shim on the same system.
To upgrade a Driver Shim that is running in Local mode in Windows:
Stop the Core Driver object in iManager.
From your installation media, run the following command:
fan-out\IDMCoreDrivers\Win\win_x86_coredriver.exe
This x86 (32-bit) executable is compatible with both x86 and x64 versions of Windows.
Accept the license, select the same installation directory as your previous installation (usually C:\Novell\ASAM) and proceed to install the product files.
The installer will next assist you in configuring the Driver Shim. You will be prompted for the Remote Loader password, which is used to encrypt driver network communications. Enter a password and remember it, as you will use it when configuring the driver in iManager.
You will then be prompted for a Driver Object password. This password will also be used when configuring the driver in iManager.
The next entry you are asked for is the eDirectory server/port, so the installer can retrieve an SSL certificate from eDirectory using LDAP. Enter the DNS name or IP address of an eDirectory server, and the LDAP secure port (default 636). In the console window that appears, enter to accept the certificate.
NOTE: If you are running both eDirectory and Active Directory on the Windows server, you may need to change the LDAP ports of either eDirectory or Active Directory so that they do not interfere with each other. See your product documentation for more information.
When prompted for an eDirectory admin name/password, enter the eDirectory administrator’s ID in LDAP dot format (example: , followed by the password.
NOTE: The installer must get a successful directory connection in order to proceed. Consult your eDirectory LDAP documentation for troubleshooting.
When prompted for an ASAM System Container Context, specify the distinguished name (DN) of the container in which the organizational unit ASAM System resides. This is usually the top-level organization in the tree. Enter the DN in LDAP dot format. Example: .
When prompted whether to create a new Driver or upgrade an existing one, click to upgrade an existing Driver.
When a list of drivers displays, select the Driver associated with the system you are upgrading.
The installer will then generate an updated configuration file and install indexes needed to completed the configuration. (You may receive a warning message regarding indexes since they will already exist.)
Immediately after installation, you may need to change the port setting for the Core Driver’s built-in remote loader. This is especially likely if you are also using the standard remote loader that comes with Identity Manager, since both versions of the remote loader use 8090 as their default port setting.
The port setting for the Core Driver’s built-in remote loader resides in the fanout.conf file, which is located in C:\Novell\ASAM\data\.
Edit the following line in fanout.conf to reflect the desired port:
-connection "ca=/usr/local/ASAM/keys/ca.pem port=8090"
NOTE:If you have a firewall, be sure to add the Driver's network port (default 3451) to its open ports list.
At the completion of this installation task, go next to Section 5.2.3, Setting Up the Core Driver in iManager, which includes the task for upgrading a Core Driver configuration
If you’re running a Fan-Out Driver in Remote mode, you can upgrade the Driver Shim on the Windows system running the Connected System portion of the Driver.
To upgrade a Driver Shim that is running in Remote mode in Windows:
Stop the Core Driver object and the Remote Loader instance for the current driver in iManager.
Still in iManager, open the , select the Fan-Out Driver instance and click . Make a note of the , and fields.
Because you no longer need the standard Novell Remote Loader, you may disable or remove it as follows, depending on whether you have other Remote Drivers:
If you’re running other Remote Drivers on the system, simply remove the Fan-Out Driver instance by selecting it in the Remote Loader Console and clicking .
If you aren't running other Remote Drivers on the system, open and run | ( on Windows Server 2008) to remove the Novell Identity Manager Connected System program.
From your installation media, run the following command:
fan-out\IDMCoreDrivers\Win\win_x86_coredriver.exe
This x86 (32-bit) executable is compatible with both x86 and x64 versions of Windows.
Accept the license, select the same installation directory as your previous installation (usually C:\Novell\ASAM) and proceed to install the product files.
The installer will next assist you in configuring the Driver Shim. You will be prompted for the Remote Loader password, which is used to encrypt driver network communications. Enter a password and remember it, as you will use it when configuring the driver in iManager.
You will then be prompted for a Driver Object password. This password will also be used when configuring the driver in iManager.
The next entry you are asked for is the eDirectory server/port, so the installer can retrieve an SSL certificate from eDirectory using LDAP. Enter the DNS name or IP address of an eDirectory server, and the LDAP secure port (default 636). In the console window that appears, enter to accept the certificate.
NOTE: If you are running both eDirectory and Active Directory on the Windows server, you may need to change the LDAP ports of either eDirectory or Active Directory so that they do not interfere with each other. See your product documentation for more information.
When prompted for an eDirectory admin name/password, enter the eDirectory administrator’s ID in LDAP dot format (example: , followed by the password.
NOTE: The installer must get a successful directory connection in order to proceed. Consult your eDirectory LDAP documentation for troubleshooting.
When prompted for an ASAM System Container Context, specify the distinguished name (DN) of the container in which the organizational unit ASAM System resides. This is usually the top-level organization in the tree. Enter the DN in LDAP dot format. Example: .
When prompted whether to create a new Driver or upgrade an existing one, click to upgrade an existing Driver.
When a list of drivers displays, select the Driver associated with the system you are upgrading.
The installer will then generate an updated configuration file and install indexes needed to completed the configuration. (You may receive a warning message regarding indexes since they will already exist.)
Immediately after installation, you may need to change the port setting for the Core Driver’s built-in remote loader. This is especially likely if you are also using the standard remote loader that comes with Identity Manager, since both versions of the remote loader use 8090 as their default port setting.
The port setting for the Core Driver’s built-in remote loader resides in the fanout.conf file, which is located in C:\Novell\ASAM\data\.
Edit the following line in fanout.conf to reflect the desired port:
-connection "ca=/usr/local/ASAM/keys/ca.pem port=8090"
NOTE:If you have a firewall, be sure to add the Driver's network port (default 3451) to its open ports list.
At the completion of this installation task, go next to Section 5.2.3, Setting Up the Core Driver in iManager, which includes the task for upgrading a Core Driver configuration.
You will use the Fan-Out Driver’s Web application to complete the Core Driver installation. This application resides in recent versions of iManager as a standard plug-in. If your version of iManager does not include the plug-in, you can install it from the software that comes with the Core Driver.
NOTE: In addition to iManager, you can use Designer, an application interface that comes with Identity Manager, for setting up and modelling large deployments of the Fan-Out Driver. A Fan-Out Driver application plug-in is included as part of the Designer installation. For more information on using Designer, see Section 6.4, Applications For Configuration.
After you have installed or upgraded a Driver Shim, the installation process continues in iManager with the following tasks, depending on your scenario:
If your version of iManager does not include the plug-in or if you are not familiar with iManager, you can refer to two additional topics at the end of this section before starting:
Use iManager to configure a Core Driver in the Identity Vault (eDirectory). To import a Core Driver configuration:
Login to iManager for your tree and select the task under on the left.
Keep the Driver Set selection and, if this is a new Driver Set, select the server in eDirectory where the Driver will run.
From the menu, select Fan-Out-IDM3_6_0-V1.xml. If this file is not available, select and select the file rules\Fan-Out-IDM3_6_0-V1.xml under the directory where the Driver Shim is installed (C:\Novell\ASAM by default).
Enter the following configuration fields. The installer will have filled in some of these fields:
: Enter a descriptive name.
: Choose the selection that corresponds to the activation you purchased. The Driver will operate in evaluation mode for 90 days if you don’t have an activation.
: Enter the DNS name or IP address and TCP port of your LDAP host.
: Enter the DNS name or IP address and TCP port used by the system where the Driver Shim runs.
: Enter an LDAP account that will be used to manage Driver information.
: Enter the passwords you entered when installing the Driver Shim.
Click and add your ASAM Master User.
Click and add the admin user, the ASAM Master User and other high-privilege users to the list.
Click to complete the import.
If you upgrade a Core Driver Shim, you also need to upgrade its configuration in iManager. To upgrade a configuration:
Login to iManager for your tree and select the task under on the left.
Select the Driver Set that contains the Driver to be upgraded.
Click to keep the Driver Set selection.
From the menu, select Fan-Out-IDM3_6_0-V1.xml. If this file is not available, select and select the file rules\Fan-Out-IDM3_6_0-V1.xml under the directory where the Driver Shim is installed (C:\Novell\ASAM by default).
On the next page, to the right of the field, select the driver you wish to upgrade from the drop-down box.
Enter the following configuration fields, consistent with your current installation. The installer will have filled in some of these fields:
: Choose the selection that corresponds to the activation you purchased. The Driver will operate in evaluation mode for 90 days if you don’t have an activation.
: Enter the DNS name or IP address and secure TCP port of your LDAP host.
: Enter the DNS name or IP address and TCP port used by the system where the Driver Shim runs.
: Enter an LDAP account that will be used to manage Driver information.
: Enter the passwords you entered when installing the Driver Shim.
On the next page, select and click .
Click to complete the import.
If necessary, apply any manual customizations.
NOTE: You must install the new version of the iManager Plug-in before using the Driver. See Installing the iManager Plug-In (If not Preinstalled).
If your installation of iManager does not display the Fan-Out Driver Configuration role (Roles and Tasks menu on the left), you can install the iManager plug-in manually.
To install the iManager plug-in:
Login to iManager as an administrative user.
Click the icon at the top.
Click under on the left menu.
Click above the list of plug-ins.
Select fan-out\iManagerPlugIn\FanOutWeb.npm from your installation media and click .
Check the box next to and click above the list of plug-ins.
Restart the Tomcat or Tomcat5 service on your iManager system, and exit and log back into iManager.
If the Fan-Out Driver Configuration role has not appeared, continue with the following steps.
Click the icon at the top.
Click under on the left menu.
Click the number under the column in the table.
Check the box next to and click above the list.
Click the icon at the top.
With the plug-in now installed, you can proceed to your next task.
NOTE: For additional information about using iManager with the Fan-Out Driver application plug-in, see Section 6.4, Applications For Configuration.
To use the iManager interface for setting up a Core Driver:
In iManager, select the task under .
Enter the DNS name or IP address and port of the system running the Driver Shim and click .
You may now use any of the items under and in iManager.
After the initial installation or upgrade of a Core Driver, other tasks that you may need to perform from time to time include the following:
If you have migrated your primary Core Driver from one system to another, you will need to physically copy the Certificate Authority files from your previous host system to your new host system. For example, in migrating from NetWare to another operating system, you must copy the Certificate Authority files from your NetWare system to your new system. These files are:
ASAM/data/CoreDriver/certs/ca_cert.pem ASAM/data/CoreDriver/certs/ca_key.pem ASAM/data/CoreDriver/certs/ca.pem
If you do not perform this migration, your new primary Core Driver system will generate a new Certificate Authority when it first starts up. This will invalidate any platform certificates that may have been signed using the previous Certificate Authority.
Both the Identity Manager Driver object and Driver Shim service must be running for the Core Driver to operate. To start the Core Driver:
In iManager, select the task under .
Select the Driver Set where the Driver is installed.
Click the status indicator (stop line) in the upper right corner of the driver icon, then click .
On the Driver Shim system, start the Fan-Out Driver as follows:
If the system is running Linux/UNIX, enter the following command:
/etc/init.d/asamcdrvd start
If the system is running Windows, open and run > . Start the Novell IDM Fan-Out Driver service.
To stop the Core Driver:
On the Driver Shim system, stop the Fan-Out Driver as follows:
If the system is running Linux/UNIX, enter the following command:
/etc/init.d/asamcdrvd stop
If the system is running Windows, open and run > . Stop the Novell IDM Fan-Out Driver service.
In iManager, stop the Driver in the Driver Set Overview.
The Driver Shim can be reconfigured in a number of areas, as itemized below.
NOTE: Always be sure to stop the Driver Shim before starting any of these reconfiguration tasks as described in Stopping the Core Driver.
To re-run the installer’s configuration wizard in Windows, open and run ( on Windows Server 2008). Click the button under . Then select from the dialog box that opens.
You can use the installer to create a new installation, create a new driver or upgrade an existing driver. Note that the installer doesn't remember previously configured fields, so you'll have to enter the fields like you did on the first-time install.
To change the Remote Loader and/or Driver Object passwords:
If the system is running Linux or Solaris, enter the following command and select menu item 1:
/usr/local/ASAM/setup/fandrv-config
If the system is running Windows, execute the following command from the installation directory (C:\Novell\ASAM by default):
bin\CoreDriver\asamcdrv.exe -sp
To retrieve a new SSL certificate from eDirectory:
If the system is running Linux or Solaris, enter the following command and select menu item 2:
/usr/local/ASAM/setup/fandrv-config
If the system is running Windows, execute the following command from the installation directory (C:\Novell\ASAM by default):
bin\CoreDriver\asamcdrv.exe -s
To install or remove the Driver Shim service in Windows, execute the following command from the installation directory (C:\Novell\ASAM by default) using either the installService or removeService parameter:
bin\CoreDriver\asamcdrv.exe -parameter
For scaleability, you can install secondary drivers to handle platform synchronization and password requests. A system can run only one Driver Shim. See Section 5.4, Performance Tuning for more information on specifying secondary drivers.
To install a secondary driver.
On the secondary Driver Shim’s system, follow steps 1-7 under one of the following tasks, depending on your operating environment:
NOTE:In step 7, be sure to specify the container that holds the ASAM System Container.
You will be prompted to create a new Driver or upgrade a Driver. Click to create a new Driver.
Specify a distinct name for the Driver as well as its port.
Select the Driver’s network address.
When you are prompted whether to make the new Driver primary, click to keep the Driver secondary.
Once the Driver Shim is installed, import a new Driver following the steps in Importing a Configuration for a Newly Installed Core Driver. Be sure to use the XML configuration file generated for the secondary Driver.
You can now run the secondary Driver as you would the primary Driver.
Depending on your configuration needs, you may decide to install a Driver Shim for a new primary driver.
NOTE: If the Core Driver you wish to make primary is already installed, you can use the menu task in iManager to do this.
Stop all Identity Manager Driver objects and Driver Shims. See Stopping the Core Driver.
Follow all the steps in the task, Installing Secondary Drivers, with the following exception:
In step 5, click to make the driver primary.
Start all Identity Manager Driver objects and Driver Shims. See Starting the Core Driver.