By default, the SOAP driver files are installed on the Metadirectory server at the same time as the Metadirectory engine. The installation program extends the Identity Vault’s schema and installs both the driver shim and the driver packages. It does not create the driver in the Identity Vault (see Section 3.0, Creating a New Driver Object) or upgrade an existing driver’s configuration (see Section 4.0, Upgrading an Existing Driver).
If the SOAP driver files are not currently located on the server where you want to run the driver:
Install the driver files on an existing Metadirectory server, using the instructions in Preparing to Install the Engine, Drivers, and Plug-ins
in the NetIQ Identity Manager Setup Guide.
Install the Remote Loader (required to run the driver on a non-Metadirectory server) and the driver files on a non-Metadirectory server where you want to run the driver. See Installing and Managing the Remote Loader
in the NetIQ Identity Manager Setup Guide.
You must install the SOAP driver on a server that has HTTP access to the Web service with which the driver will communicate. This can be an existing Metadirectory server or a non-Metadirectory server that meets the system requirements for running the Remote Loader service (see System Requirements for the Remote Loader
in the NetIQ Identity Manager Setup Guide).