By default, the SAP User 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 the driver shim and the driver configuration file. It does not create the driver in the Identity Vault (see Section 5.0, Creating a New Driver) or upgrade an existing driver’s configuration (see Section 6.0, Upgrading an Existing Driver).
The SAP User driver must be located on the same server as the SAP User application. If the driver is not on that server, you have the following options:
Install the Metadirectory server (Metadirectory engine and drivers) to the SAP server. This requires eDirectory to be installed on the server. See the instructions in Identity Manager 3.6.1 Installation Guide.
Install the Remote Loader (required to run the driver on a non-Metadirectory server) and the SAP User driver files to the SAP server. This assumes that you already have a Metadirectory server installed on another server in your environment. See Identity Manager 3.6.1 Installation Guide.
As part of the installation, select the Utilities option and install the SAP Utilities. This installs the SAP Java Connector Test utility that you can use to ensure that the driver has connection to the SAP system. If you’ve already installed the driver files but did not install the SAP Utilities, you can run the installation program again to install only the SAP Utilities.
The server where the SAP driver is installed must have the SAP Java Connector (JCO) client technology version 1.1x or 2.x to provide the driver with connectivity to the SAP system.
This JCO client is available to SAP customers and developer partners through SAP, and is provided for most popular server operating systems. You can download the JCO from the SAP Connectors site.