If you drag an XfA component to the workflow, you must first configure the connection to the required SAP system.
The drop-down menu on the left lists all systems that have already been created on the local machine. Use New to create a new system.
In the connection mask, you have the option of connecting to a single application server or to a message server using load balancing. In the first case, you must specify the host name and system number. In the second case, you must specify the message server, group, and SID. Client (e.g. 100 or 800) and language (e.g. DE or EN) must be specified as for SAP GUI logon.
For the authentication in the simplest case only username and password (Plain) are needed.
Other authentication methods are also supported, e.g. SNC SSO or Logon Tickets.
. Which RFC library is used is a matter of taste.
librfc32 has been discontinued by SAP and is officially no longer supported. However, it is more stable and uses less resources than the Netweaver library recommended by SAP.
The trace file specification can only be used by Support if requested to do so.
If some errors occur, debug logging (tracing) information may be required to analyze the issue. To activate tracing please follow those steps:
- Fill in a path (e.g. C:\Temp\Trace) in the field Trace Directory in the SAP connection Manager. To open the SAP connection manager, select the designer menu Server -> Manage Services. Select your SAP connection and click Edit.
- Reproduce the error. XML Files are created in the folder specified with the tracing information.
- Compress the folder to a zip file (e.g. Trace.zip) and sent it to our support.
- After reproducing the error delete the entry in the field Trace Directory since tracing is not needed anymore.
Please note that the debug logging usually should be activated by request of the support team. There are plenty of information that will be collected. This can decrease the capacity of your hard drives dramatically.