Cloud Inventory® Documentation

send feedback

❮ Previous Next ❯

Configure the SAP .NET Connector

The SAP .NET Connector transmits data among components and the SAP enterprise software. When configuring this connector, elements are specified, such as include the app server, system number, and system user name and password.

To configure the SAP .NET Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the SAP .NET Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
Select the Logon Type from the drop-down menu and complete one of the following options.
- If Single Logon is selected, complete the following fields.
  - For Application server, enter the name or IP address of the computer serving as a gateway host to the SAP system. The gateway host is the computer on which the gateway server runs and may be the same as the host computer. This value must be specified based on the particular configuration. For example, "10.255.255.255" indicates that 10.255.255.255 is the IP address of the computer.
  - For System number, enter the system number based on the enterprise configuration, for example, 00. If necessary, the basis administrator (enterprise system administrator) can provide this value.
- If Group Logon is selected, complete the following fields.
  - For Message server, enter the host name of the SAP system's message server (central instance).
  - For Message server service, enter the service name (as defined in etc/services) or the port number under which the message server is listening for load- balancing requests.
    Note:Usually this parameter can be omitted. By default RFC uses the service name “sapmsABC”, where ABC is the system ID of the SAP system.
  - For System ID, enter the SAP system's three-letter system ID.
  - For Logon Group, enter the logon group, from which the SAP system's message server shall select an app server.
For Client, enter the name of the enterprise environment to use when connecting to the SAP system.

Step Information

Note:Generally, only one environment is the production or "live" environment. There can also be other environments with access to other subsets of data, for example, for development and testing.
For User ID, enter user identification that the SAP system uses when managing profiles and permissions.
For Password, enter the SAP password of the user seeking to use the program. Entry in this field is hidden by asterisks, so the password is not readable.
For Supports Unicode, specify whether or not the installation of SAP supports Unicode.
For Log request/response documents, specify whether or not the request/response documents are logged to the Logging folder in the installation.

Step Information

Note:The document name format to which they are logged is SAP_(GUID).txt. (The GUID section will vary. This is a transaction ID which should be unique).
For Auto commit, select and complete one of the following options.
- If None is selected, then no calls are auto-committed by Mobile Enterprise Platform. The BAPIs called are responsible for committing data.
- If Per Function Call is selected, then all new functions that are registered will have an extra parameter for Auto commit that can be set when the function is called.
  - If parameter is set to 1 (true), then BAPI CommitWork is called immediately after the requested function is called. If a failure is detected, such as a communications failure, system failure, etc., then CommitWork is not called.
- If All is selected, then every call through the SAP .NET Connector will call CommitWork as if the Auto commit parameter was set to 1 (true). This, however, will not happen if an error is detected.
  - This option overrides any calls where the Auto commit parameter is set to 0.
For Language, select the logon language to be used. This setting is configured in SAP.
For Idle Time-out (seconds), enter the seconds for the idle time-out.

Step Information

Note:If a connection has been idle for more than the Idle Time-out seconds, it will be closed and removed from the connection pool. This setting is configured in SAP.
For Pool Size, enter the maximum number of RFC connections that this destination will keep in its pool as set in the SAP system.

Step Information

Note:More connections can be opened (until MaxPoolSize) is reached, but they are closed again immediately after usage. This setting is configured in SAP.
For Max Pool Size, use the parameter that is set in the SAP system.

Step Information

Note:In order to prevent an unlimited number of connections to be opened (which, from a certain point on, would cause the entire machine's performance to deteriorate dramatically). NCo will not open further connections for this destination when this limit is reached. This setting is configured in SAP.
For Trace, set a trace level for this specific destination or server. This setting is configured in SAP.
ABAP Debug can be used for R/3 systems with release 6.20 and above, where "external breakpoints" are not yet available.

Step Information

Note:The connections are opened in debug mode and the invoked function module can be stepped through in the debugger. This setting is configured in SAP.
For CPIC Trace Level, use this trace level for all destinations and servers, which do not define their own trace level. CPIC Trace Level is also used for writing traces in those deeper level layers of NCo, which are not directly related to a particular destination or server and consequently cannot use a destination/server trace level for their trace output. Select one of the following options.
- None/”0”: no tracing
- Level1/”1”: trace all function calls
- Level2/”2”: function calls and public API calls
- Level3/”3”: function calls, public API calls and internal method calls
- Level4/”4”: function calls, public API calls, internal method calls and network hex dump
Select Save.

There was a problem loading this topic

Mobile Enterprise Platform

Configure the SAP .NET Connector