As you import the driver configuration file, you will be prompted for the following information.
Driver name |
The actual name you want to use for the driver. |
Container |
The name of the Organization object under which SAP organizational information will be created. |
Active Users Container |
The name of the Organizational Unit object where Active users are placed. |
Inactive Users Container |
The name of the Organizational Unit object where Inactive users are placed. |
Active Employees Group |
The name of the Group object to which Active Employee users are added. To learn more about determining Employee status, refer to "Using the Relationship Query" on page 48. |
Active Managers Group |
The name of the Group object to which Active Manager users are added. To learn more about determining Employee status, refer to "Using the Relationship Query" on page 48. |
SAP Application Server |
The host name or IP address for connecting to the appropriate SAP application server. This is referred to as the Application Server in the SAP logon properties. |
SAP System Number |
The SAP system number on the SAP application server. This is referred to as the System Number in the SAP logon properties. |
SAP Client Number |
The client number to be used on the SAP application server. This is referred to as the Client in the SAP R/3 logon screen. |
SAP User ID |
The ID of the user this driver uses for the SAP system logon. This is referred to as the User in the SAP R/3 logon screen. |
SAP User Password |
The User password this driver uses for the SAP system logon. This is referred to as the Password in the SAP R/3 logon screen. |
SAP Language Code |
The language this driver uses for the SAP session. This is referred to as the Language in the SAP R/3 logon screen. |
Metadata File Directory |
The file system location in which the SAP Metadata definition file resides. By default, this is in the SAPUtils subdirectory of the driver's installation directory. IMPORTANT: This must be on the same system where the driver shim runs. |
IDoc File Directory |
The file system location in which the SAP HR IDoc files are placed by the SAP ALE system. IMPORTANT: This must be accessible to the driver shim process. |
Configure Data Flow |
Dataflow can be configured to one of the following options: - Bidirectional: SAP HR and eDirectory are both authoritative sources of the data synchronized between them.
- SAP-to-eDirectory: SAP is the authoritative source.
- eDirectory-to-SAP: eDirectory is the authoritative source.
|
Install Driver as Remote/Local |
Configure the driver for use with the Remote Loader service by selecting the Remote option, or select Local to configure the driver for local use. If Local is selected, you can skip the remaining parameters. |
Remote Host Name and Port |
Specify the host Name or IP address and port number for where the Remote Loader service has been installed and is running for this driver. The default port is 8090. |
Driver Password |
The driver object password is used by the Remote Loader to authenticate itself to the DirXML server. It must be the same password that is specified as the driver object password on the DirXML Remote Loader. |
Remote Password |
The Remote Loader password is used to control access to the Remote Loader instance. It must be the same password that is specified as the Remote Loader password on the DirXML Remote Loader. |
The additional driver parameters are set to default values during the import process, but they can be modified in iManager (by clicking the Driver Configuration tab on the driver object.)
Publisher Channel Only? (0=False) |
If you enter a non-zero value, SAP system connectivity and authentication are not required. You must, however, enter a Master HR IDoc parameter if a non-zero value is used. |
SAP User Language |
The two-character language abbreviation that the client uses. |
Character Set Encoding |
The character set encoding used to parse data from IDocs. If not specified, the driver uses the platform default encoding. If you incorrectly specify a character set, the driver initialization fails. |
Master HR IDoc |
The name of the IDoc type that is generated by the SAP ALE system to publish SAP HR database Master data modification. If not specified, the driver determines the revision of the SAP HR system and default to the standard IDoc type for that revision of SAP. This field is optional, unless a non-zero value is entered in the Publisher Channel Only field. |
(Optional) Address Subtype Code |
An enumerated configuration parameter that allows an administrator to specify which subtype of data the SAP Private Address infotype the driver synchronizes. |
(Optional) Communication Subtype Code |
An enumerated configuration parameter that allows an administrator to specify which subtype data of the SAP Communication infotype the driver synchronizes. |
Poll Interval (seconds) |
Specifies how often the driver polls for unprocessed IDocs. |
Publisher IDoc Directory |
Specifies the file system directory from which the publisher will read IDocs published by the SAP system. |
Future-dated Event Handling Option |
The processing of this option is determined by the Begin and End validity dates of the desired IDoc infotypes. There are four possible values for this parameter: 0 - Indicates that all attributes will be processed by the driver when the IDoc is available. A time stamp is set for each attribute that represents the validity period. 1 - Indicates that only attributes that have a current or past time stamp will be processed by the driver when the IDoc is available. Future-dated infotype attributes are cached in a .futr file to be processed at a future date. 2 - Indicates that the driver will blend options 1 and 2. All attributes will be processed, with a time stamp, at the time the IDoc is available. All future-dated infotype attributes are also be cached in a .futr file to be processed at a future date. 3 - Indicates that the driver will process all events at the time the IDoc is made available. All future-dated infotype attributes are cached in a .futr file to be processed again on the next calendar day. This continues until the attributes are sent for a final time on the future date. |