Procedure
Input field |
Description |
Example |
RFC Station |
Name of the RFC destination for the LDAP gateway |
RFC-LDAP_3 |
LDAP Host name |
Computer on which the LDAP service is installed and the relevant port number |
hw1154 |
LDAP Port number |
389 | |
User name |
Logon data used to access the LDAP service |
Jackson |
Password |
????? | |
Parent node |
An LDAP service node, under which the address data is appended.
If a parent node is specified, the entries for basic nodes and replacement parent nodes have no significance. You should therefore only enter a parent node if you do not want to use the LDAP standard schema. |
|
Basic nodes |
The basic nodes of the LDAP service, under which the paths to the user data (e.g. cn=Jackson, ou=Sales) can be found. In addition, a replacement parent node which can be used if errors occur should be entered. For example, if the department entry is not maintained for an R/3 address, the node ou cannot be created. |
o=examplecompany, c=usa |
Replacement parent node |
o=examplecompany, c=usa | |
LDAP Version (2, 3) |
Current LDAP version |
3 |
Address type (1:company; 3:contact person) |
Address types to be exported |
3 |
Address number from |
Entry specifying which R/3 addresses should be copied (address type 1 for address numbers and type 3 for address and user numbers). |
5 |
Address number to |
||
User number from |
1 | |
User number to |
100 |
Result
The R/3 addresses are available as LDAP addresses. LDAP clients can access the LDAP service via the Internet or via an intranet to search for, display and maintain addresses, if the user has the required authorization.