Event Driven Inbound Connections

This feature allows users to dynamically establish connections to the SAP system in an inbound adapter configuration. This feature provides flexibility to external systems and the following advantages accrue:

The inbound adapter configuration has to connect to the SAP system always, if the Request-Response Service or the Subscription Service services configured in the adapter configuration are not invoked frequently.
External systems can login with specific authorizations in the SAP system after authentication and execute RFC/BAPIs in the SAP system through the inbound adapter configuration with these authorizations.
The Request-Response Service and the Subscription Service services configured in the adapter make use of connections created dynamically.
A dynamic connection can be created in one of the following ways:
- Based on logon parameters defined at design time
- Based on logon parameters passed at run time when explicit logon occurs
If the inbound adapter configuration has set up the connection with a SAP system, the user ID and password are not required each time when it connects to other SAP systems under single sign-on using SNC.

Note: The SAP systems must establish a trust relationship in case of single sign-on using SNC.

Disabled Connection Pooling Inbound Configuration

In order to use a dynamic connection, you have to configure connection pooling by using the login parameters provided at design time. Any inbound adapter configuration can be configured to startup where connection pooling is disabled. Such an inbound adapter configuration does not establish any connections to the SAP system unless a call is required.

Once the call is completed, the connection to the SAP system is closed automatically.

After enabling a dynamic connection based on logon parameters defined at design time, the adapter configuration opens and closes connections on a per-message basis. The connection parameters for opening connections are picked up based on the connection references configured for the corresponding Request-Response or Subscription services.

To enable this feature, instruct the adapter configuration not to establish connections on startup by clicking the ConnectionPools tab of the Adapter for SAP Configuration editor for the specific configuration and selecting the Disable Connection Pooling check box in the Client Connection Pool Configuration panel for each of the configured Client connections. For more information about the ConnectionPools tab, see Client Connection Pool Configuration Reference.

Performing Explicit Logon for RFC/BAPIs

A Request-Response service can be enabled for explicit logon by passing the SAP connection information at the time of the RFC/BAPI transaction. The SAP connection information is passed to the inbound adapter configuration by using the DynamicConnection property available in the RFCCLOSURE class.

The RFCCLOSURE class is found in the Project_Name/AESchemas/ae/SAPAdapter40/classes/Classes directory in the TIBCO Business Studio project. Depending on the information provided on the connection, the connection to the SAP system can either be a Dedicated connection, a Logon Group connection, or an SNC connection.

Note: When the explicit logon feature is in use, the load balancing functionalities, RVCMQ,. and multiple instances of the adapter cannot be used.

If the logon operation is successful and a valid client connection to the SAP system is obtained through the inbound adapter service, a session ID is sent back in the reply to the calling system. The reply contains the session ID in its RFCCLOSURE class.

The external system invokes the RFC/BAPI with this session ID to be serviced by the inbound adapter service. Unless the session ID is used as part of a transaction, the connection to the SAP system is closed automatically.

If the external system requires a separate connection for each invocation, each invocation should be accompanied by the SAP connection information so the connection is created.

Enabling Single Sign-on Using SNC

You can set up connection with multiple SAP systems without providing the user ID and password by single sign-on, if the user ID already exists in those SAP systems and a trust relationship is established across the systems.

Note: Single sign-on only supports the RPC server of the inbound adapter configuration in the SNC dynamic connection.

To enable single sign-on, in the Input tab of the activity where you want to enable this feature, expand the _caret_userclosure_caret_ element and set the bTransactional property to 1.