The administrator that starts the LDAP Connector requires authorization S_RZL_ADM with value 01.
1. Create an RFC destination of connection type T in transaction SM59.
We recommend that you use the following naming convention: LDAP_<server_name>. If you want to start multiple LDAP Connectors on one server, extend the name as follows: -<sequence_number>, that is LDAP_MYSERVERNAME-01
You must specify the name of the RFC destination in capital letters.
2. Select Registered server program as activation type.
3. Use the name of the RFC destination as the program ID.
4. Under Gateway Options, enter the gateway with which the LDAP Connector is to register.
We recommend that you use the gateway of the application server on which the LDAP Connector is to be started, where the Gateway Host = <application_server> and the Gateway Service = sapgw<system_number>.
5. Save your entries.
6. In the initial screen of the directory service maintenance (transaction LDAP), choose LDAP Administration а Connector, or the Connector pushbutton.
The system displays the Display “LDAP Connector (Maintenance View)” View: Overview screen.
7. Switch to change mode and select New Entries.
The system displays the New Entries: Details of Added Entries screen.
8. Enter the following data for the LDP Connector:
Name of the RFC destination defined for the LDAP Connector.
Name of the application server on which the LDAP Connector is to be started.
Enter the name in the format (for example, using entry help) that the server has in the rdisp/myname profile parameter (Note that this is case-sensitive). You can find this name in transaction SM51.
Target status of the CCMS monitoring, for example:
· Connector active
Only in this status can the connector be automatically selected by applications that cannot explicitly select an LDAP Connector, such as SAPoffice and the user master records synchronization.
· Connector inactive
· No CCCMS monitoring
Possible Trace Levels:
· Trace deactivated
The program start and all error messages are nevertheless always logged.
· Display function calls
· Function calls + flat parameters
9. Save your entries.
10. To start the Connector, choose Start Connector ().
The LDAP Connector is available and can be selected in the Connector field in the Directory Service Maintenance screen.
You can create additional command line parameters for the LDAP Connector using a configuration file, such as
· -o <maximum idle time>
You can specify the maximum idle time for an LDAP connection in minutes with this parameter. The connection is terminated after this time expires.
· -m <number of connections>
With this parameter, you can specify the maximum number of connections that the LDAP Connector can create.
When starting, the LDAP Connector checks whether the file "ldap_rfc.cfg" is in its working directory.
You can specify another file name (and if necessary, also another storage location) with the command line parameter "-cfg <filename>". If you have specified the configuration file explicitly in this way and cannot find the LDAP Connector, the LDAP Connector is terminated with an error message.
The configuration file contains the parameter names (without the initial hyphen) and optionally an initial value specified with an equal sign (=).
The LDAP Connector ignores empty lines and lines beginning with a number sign (#).
If the value contains spaces (for example, in the case of path specifications), enclose the entire value in double quotation marks (").
End the last line of the configuration file with a line feed.
The following example shows a configuration file that sets the option "-o" to the value 10 and configures the RFC option "-L" (path to the SNC library) with the specification of a filename:
# File: ldap_rfc.cfg
# Configuration file for the LDAP Connector (ldap_rfc[.exe])
# Connection outdate time (equivalent to command line option "-o")
o = 10
# Path to SNC library (option "-L")
L = "C:\Program Files\mysnclibrary.dll"
To check the activation of the LDAP Connector, view the logs in the trace files dev_<Name of the RFC destination>.trc using transaction ST11.