Dynamic Connection

Use the Dynamic Connection activity to create dynamic connections at run time for invoking RFC/BAPIs, which include RFC/BAPIs as part of a transaction and also posting IDocs using the Post IDoc to SAP activity.

Note:  
  • The Dynamic Connection activity cannot be used to create dynamic connections for invoking RFC/BAPIs in load-balancing mode.
  • Dynamic Connection does not support third party library options property available in the SAP Connection shared resource.

General Tab

On the General tab, maintain a reference to the SAP Connection shared resource and configure the activity accordingly to either create a dynamic connection or close an existing dynamic connection.

The following table lists the configurations on the General tab of the Dynamic Connection activity:

Field Visual Diff Module Property? Description
Name Yes No Specify the name to be displayed as the label for the activity in the process.
SAP Connection Yes Yes Click to select an SAP Connection shared resource. The SAP Connection shared resource establishes connections between the plug-in and the SAP system.

If no matching SAP Connection shared resources are found, click Create Shared Resource to create one. For more information, see Creating and Configuring an SAP Connection.

Note: The SAP Connection shared resource is used to provide default settings for any connection parameters not defined in the input of the activity.

Terminate Connection Yes No Select this checkbox to terminate the dynamic connection when it is no longer required.

This checkbox is the same as the Context End checkbox in the Advanced tab of the Invoke RFC BAPI in SAP activity. When a dynamic connection with the selected Transactional checkbox is used, if you want to end the transaction, you must select both the Terminate Connection checkbox and Transactional checkbox instead of selecting the Context End checkbox.

Transactional Yes No Select this checkbox to enable the dynamic connection to be used with one or more RFC/BAPIs as part of a transaction.
Note:  
  • As part of the same ActiveMatrix BusinessWorks process, using a dynamic connection with RFC/BAPIs running as a transaction or non-transaction is not supported.
  • The Transactional checkbox is not applicable for the Post IDoc to SAP activity.

Description Tab

On the Description tab, enter a short description for the Dynamic Connection activity.

Input Tab

On the Input tab, specify detailed information for the dynamic connection you want to configure for invoking RFC/BAPIs.

The following table lists the input elements on the Input tab of the Dynamic Connection activity:

Input Item Data Type Description
sessionIDString Enter the session ID of the dynamic connection that is used for invoking RFC/BAPIs and for posting IDocs using Post IDoc to SAP activity.

The session ID has to be mapped when you are terminating an existing dynamic connection.

contextTimeoutLong Enter the timeout value in milliseconds for the activity to wait for the subsequent activity to be invoked.

The default value is 30000. This field is used only when the dynamic connection is used as part of a transaction.

This input element is the same as the Commit Expiry(ms) field on the Advanced tab of the Invoke RFC/BAPI activity, and can be overwritten by the Commit Expiry(ms) field.

Note:  
  • The module property of the long type cannot be left blank, and its value range does not include negative numbers.
  • If you set the value of this input item to negative numbers or zero, the default value of 30000 is used automatically at run time.

The following input elements are under the DynamicConnections node:
connectionTypeString Specify the type of the dynamic connection.

The value of this input element is not case-sensitive.

  • The value of 1 or dedicated indicates the dedicated connection.
  • The value of 2 or logon group indicates the SAP logon group connection.

appServerString Specify the SAP application server by using either the host name or IP address.
systemNumberString Specify the system number of the SAP system.
clientString Specify the client number of the SAP system.
userNameString Specify the user ID used to log on to the SAP system.
passwordString Specify the password for logging on to the SAP system.

The password attribute is part of the XSD schema. You have to define a module property as the password type, and map the defined module property to the password.

Note: This password is not required when you log on by using the SNC connection type.

systemNameString Specify the ID of the SAP system.

This field is required when using the connections of the logon group type.

msgServerString Specify the SAP message server used for load balancing.

This field is required when using the connections of the logon group type.

groupNameString Specify the name of the SAP logon group.

This field is required when using the connections of the logon group type.

codePageString Specify the character sets used by SAP and databases.

The default value is blank.

languageString Specify the language used to log on to the SAP system.

You can only specify a 1-character value for this field. If the value is not populated, the default value is E, indicating English.

rfcTraceString Specify whether to enable RFC trace as part of the connection.

  • To disable RFC trace, set value to 0, OFF, or false.
  • To enable RFC trace, set value to 1, ON, or true.

useSAPGUIString Specify whether to enable SAP GUI as part of the connection.

  • To disable SAP GUI from carrying out debugging of RFCs, set the value to 0.
  • To enable SAP GUI to carry out debugging of RFCs, set the value to 1.
  • To enable SAP GUI to carry out debugging of RFCs until used by an invocation of an RFC, set the value to 2.

ws_hostStringSpecify the valid host name of the machine where the SAP system exists.
ws_portIntegerSpecify the valid Port on which Web socket is configured for the SAP System.
tls_trust_allbooleanSpecifies whether to trust all TLS entities. By default, it is false.
tls_keystore_fileString

If the input parameter tls_trust_all is set to false, then the reference to the tls_keystore_file field must be configured accordingly, otherwise; you can ignore it.

tls_keystore_passwordString

If the input parameter tls_trust_all is set to false, then the tls_keystore_password field must be configured accordingly, otherwise; you can ignore it.

Output Tab

The Output tab displays the detailed information about the dynamic connection.

The following table lists the output elements on the Output tab of the Dynamic Connection activity:

Output Item Data Type Description
sessionIDString Displays the session ID associated with the dynamic connection.

This is the same session ID that is mapped to the input schema of the Invoke RFC/BAPI in SAP activity or posting IDocs in Post IDoc to SAP activity or the Dynamic Connection activity where the connection is being terminated.

CPIC_IDString Displays the CPIC ID associated with the dynamic connection as part of a transaction.

The CPIC ID is provided only for information purposes.

The following input elements are under the DynamicConnections node:
connectionTypeString Displays the type of the dynamic connection.

The value of this output element is not case sensitive.

  • The value of 1 or dedicated indicates the dedicated connection.
  • The value of 2 or logon group indicates the SAP logon group connection.
  • The value of 3 or snc indicates the SNC connection.

appServerString Displays the SAP application server specified by using either the host name or IP address.
systemNumberString Displays the system number of the SAP system.
clientString Displays the client number of the SAP system.
userNameString Displays the user ID used to log on to the SAP system.
passwordString Displays the password for logging on to the SAP system.
systemNameString Displays the ID of the SAP system.
msgServerString Displays the SAP message server used for load balancing.
groupNameString Displays the name of the SAP logon group.
snc_modeString Displays whether to enable SNC connectivity.
snc_partnernameString Displays the SNC name of the communication partner, which is an application server, if you set snc_mode to 1.
snc_qopString Displays the SNC quality of protection if you set snc_mode to 1.
snc_libString Displays the path of the crypto libraries on the machine where the ActiveMatrix BusinessWorks process is running.
snc_bSSO Displays whether to enable SSO.
snc_SSOrecvString Displays the string of the SSO logon ticket.
snc_x509String Displays the X.509 certificate that the SNC connection uses for authentication.
codePageString Displays the character sets used by SAP and databases.
languageString Displays the language used to log on to the SAP system.
rfcTraceString Displays the string to enable RFC trace as part of the connection.
useSAPGUIString Displays the string to enable SAP GUI as part of the connection.
ws_hostStringDisplays the websocket host for the SAP system.
ws_portIntegerDisplays the websocket port for the SAP system.
tls_trust_all BooleanDisplays whether the SAP system trusts all TLS entities.
tls_keystore_fileStringDisplays the TLS keystore file.
tls_keystore_password StringDisplays the TLS keystore password.
Note: The attributes having the prefix snc_ is available in the Output tab, but it should be ignored since Secure Network Communication is not supported in TIBCO Cloud™ Integration.

Fault Tab

On the Fault tab, you can find the error codes and error messages of the Dynamic Connection activity. For more information, see Error Codes.

The following table lists error schema elements on the Fault tab of the Dynamic Connection activity:

Error Schema Element Data Type Description
msgString Displays the error message
msgCodeString Displays the error code