SAP EWM RFC Server

Registration Using Message Server

Select this checkbox if you want to set up the connection using a message server with load balancing instead of using an RFC gateway.

If you want to set up the connection using a message server, you need to specify the host name of the message server, the system ID, and the logon group. For a connection using an RFC gateway, you need to specify the gateway host name and the gateway service. The Management Console hides the entries that are not required, in accordance with your selection.

Program ID

The Program ID is used to identify the RFC destination in transaction SM59, from which PCo is to receive the requirements.

The Program ID must be unique and must be the same as that specified in the EWM system in transaction SM59 on the Technical Settings tab.

SAP Gateway Host

Specifies the host name of the RFC gateway. The connection is set up via the Gateway Host. This is the machine on which the gateway process runs.

You also need to specify the gateway host in the EWM system in transaction SM59 on the Technical Settings tab. You need to specify the gateway host if you do not want to set up the connection using a message server.

SAP Gateway Service

Specify either sapgw<SysNr> or the port number directly if the service is not defined in the service file.

SAP Message Server Host

Specifies the name of the message server if the connection is to be set up using load balancing.

SAP Logon Group

Here you specify the name of the logon group that is to be used for load balancing.

SAP System ID

The system ID of the SAP system to which you want to set up a connection.

SAP Router

The SAP Router makes it possible to connect through a firewall. Enter the SAP router parameters in the following format: /H/hostname//S/portnumber/H/

Number of Threads

Specifies the maximum number of parallel incoming RFC requests that the RFC server can process.

If you enter 5 for example, five users can send a request to the EWM system in parallel.

Compression

You use this checkbox to specify that table values larger than 8 KB are to be compressed in the RFC interface.

SNC

Enabled

If you select this checkbox, the Secure Network Communication component is enabled. For more information, see SNC Settings and, in the SAP NetWeaver documentation, see Secure Network Communications (SNC).

User SNC Name

SNC name of the user You also need to enter this name in the Business Suite system in transaction SM59 in the Partner field, for example, p:CN=D0XXXXX, O=SAP-AG, C=DE.

Server SNC Name

You enter the server name of the connected EWM system, for example, p:CN=UI3, O=SAP-AG, C=DE.

QoP (Quality of Protection)

Specifies the quality of protection (QoP) of the data transfer:

• 1 Only Secure Authentication (Digital Signature)

• 2 Protection of the Integrity of the Data (Digital Signature and Encryption)

• 3 Confidentiality of the Data (Digital Signature, Encryption, and User Authentication)

• 8 Default (Default Value Defined by the ERP System), profile parameter snc/data_protection/use.

• 9 Maximum Available (Maximum Value Supported by the Security Product), profile parameter snc/data_protection/max.

If the value is below the minimum required value (profile parameter snc/data_protection/min), it is increased automatically.

If the value is above the maximum available value (profile parameter snc/data_protection/max or maximum value of the external security product), the communication is terminated.

Library

Here you enter the full path and the name of the security library of a non-SAP product. This library is then used for the SNC communication.

If you use Single Sign-On (SSO), you do not need to enter anything here. You can use the path C:\Program\Files\SECUDE\Office\Security\secude\dll to access the SSO library. If in conjunction with SSO, the path differs from the standard path, enter this here.

Trace Settings

Enabled

If you select this checkbox, the Trace function is enabled. In this case, the RFC communication is traced in a file with this agent instance. The tracing file is stored in the current working directory of the PCo agent instance.

Level

States the trace level of the .Net Connector (NCo). The trace level is the degree of detail in which steps performed during message processing are traced by the system. The following settings are possible:

• Level 1

  With this setting, only the Remote Function Calls are traced.

• Level 2

  With this setting, the calls from public API Methods are also traced.

• Level 3

  With this setting, the calls from internal API Methods are traced in addition to the calls mentioned above.

• Level 4

  With this setting, the HEX Dumps are traced for the RFC log in addition to all calls previously mentioned.