Field | Description/Action |
Package | Package in which to create the connection. You must create the package using Designer before you use in this parameter. For information about creating packages, see webMethods Service Development Help for your release. Note: Configure the connection in a user-defined package rather than in the adapter's package. See Package Management for other important considerations when creating packages for Adapter for SAP. |
Folder Name | Folder in which to create the connection. |
Field | Description/Action |
Connection Alias | RFC connection name. This is the name by which the SAP system are known to Adapter for SAP developers, clients, and partners. Note: The Connection Alias must be unique for each connection. |
User Name | SAP default user for this RFC adapter connection. If no other SAP user name is provided during runtime then this SAP user account is used to execute the client request in the SAP System. Note: The default user of Adapter for SAP Connection is also used to execute lookups to the DDIC for RFC, BOR and ALE metadata. So, it is necessary to set an SAP logon user with the authorization to the following SAP standard function groups: RFC1, SDIF, SG00, and SRFC. It is a recommended best practice to set a technical SAP user account with the minimum necessary set of authorizations as the SAP default user. If the execution of an RFC adapter service requires additional access rights then the name of an SAP user with sufficient rights must be passed during runtime. |
Password | SAP password of the default user. |
Repository User Name | SAP repository user for this RFC adapter connection. If a repository user is provided, all meta data and repository lookups are executed with this user account. This field is optional. |
Repository Password | Password of the SAP user specified in the Repository User Name field. |
Client | Three-digit SAP client number. |
Language(optional) | SAP language code. This field is optional. If connecting to a version 3 SAP system, this is one character. For a version 4 or later SAP system, it is two characters. |
Field | Description/Action |
Load Balancing | ![]() ![]() |
Logon Group | Name of the group you want to login. |
Message Server Host | Host name or IP address of the message server. |
Message Server Service | Optional. Message server service or port number. Message Server Service can be used instead of the System ID field. |
System ID | Optional. System ID of the SAP system or SID. System ID field can be used instead of the Message Server Service field. |
Field | Description/Action |
Application Server | IP address or host name of the SAP system. |
System Number | SAP system number (00-99). |
Field | Description/Action |
External RFC Server | ![]() ![]() |
Program ID | Program ID of the external RFC Server |
Gateway Host | Gateway Host for accessing your RFC Server. Must be the IP- or DN-address of the Gateway the RFC Server is registered on. |
Gateway Service | Value corresponds to the system number of the RFC Server. The format is sapgwXXX, where XX is a value from 00 to 99. For example: sapgw07 or sapgw00s |
Repository Server | Value is the SAP server taken from the existing SAP system list. All repository lookups such as metadata lookups for structures and function interfaces are done there. This helps using third-party RFC Servers from Adapter for SAP as client. They can provide their functionality without being extended by a specific interface, for example: RFC_GET_FUNCTION_INTERFACE |
Field | Description/Action |
SNC Enabled | Determines whether this server should use Secure Network Communications (SNC). Possible Values are: ![]() ![]() |
SNC Quality of Service | SNC Quality of service, possible values: ![]() ![]() ![]() ![]() ![]() |
SNC Name | Your own SNC name if you do not want to use the default SNC name. This is the name you chose when generating a Personal Security Environment (PSE). |
SNC Partner Name | SNC name of the SNC partner (RFC server) or SNC name of the message server (Load Balancing). |
SNC Authentication | Select one of the following possible SNC authentication types: ![]() ![]() Note: At runtime, if a valid X.509 certificate is available in the current HTTPS Integration Server session, the X.509 certificate takes precedence over the credentials in the SNC PSE file. ![]() Note: At runtime, if a valid X.509 certificate is not available in the current HTTPS Integration Server session and the SNC mode is enabled, the credentials in the SNC PSE file is used for authentication. |
Field | Description/Action |
SAP Router String | SAP router string. The router string contains a substring for each SAP Router to set up a connection in the route: the host name, the port name, and the password, if one was given. For example: /H/127.0.0.1/H/, where H indicates the host name. The SAP router string is only needed if a firewall exists between the SAP System and Integration Server. For more information on configuring the SAP router, go to the SAP Service Marketplace at: http://service.sap.com/connectors. |
Field | Description/Action |
Use SAPGui | Run with/without/hide the SAP GUI between two RFC functions. Possible values are: ![]() ![]() ![]() |
RFC Trace | Enables the creation of RFC trace information for this client connection. Possible values are: ![]() ![]() For detailed information on using the RFC trace, see Logging and Monitoring. |
Log Transaction Status | Switch to save the processed logs. Possible values are: ![]() Tip: Setting this switch to Off reduces the amount of disk space needed and the time it takes to log the transaction status. It still allows you to check the current transaction status on Adapter for SAP. ![]() |
Store Message Body | Switch to store the message body of the incoming document to disk. Possible values are: ![]() Tip: Setting this switch to Off reduces the amount of disk space needed and the time it takes to persist the message body. It still allows you to track the message status on Adapter for SAP. ![]() |