Creating accounts by using SAP ERP connector in Deploy Anywhere Flow Service

Create the account and connection details to use the SAP ERP connector in Deploy Anywhere Flow Service.

1. From the main navigation, go to Projects and select a project.
2. Click Integrations > Flow services. Next, click Deploy Anywhere Flow Service.
   The Flow Editor page appears.
3. Provide a name for the Deploy Anywhere Flow Service and save.
4. On the flow step, type the name of the connector such as SAP ERP and select Add Custom Action from the list.
   The Custom Action wizard is displayed.
5. On the Account page, provide the action name and description. Next select the default runtime to specify where the service runs such as cloud designtime or self-managed runtime. By default, the runtime selection on the Flow Editor page is considered. However, if you change the runtime in the Add account wizard, the connection is redeployed.
   Note: The runtime that is selected in the Default runtime field takes precedence during the connection redeployment.
6. In the Connect to account SAP® ERP field, select the account name by which the SAP system is known to SAP® ERP developers, clients, and partners.
7. Click the Add icon.
   The Add account wizard is displayed.
8. On the Account page, provide the following details to set the connection and click Next.
   • In the Connection alias field, enter the account name by which the SAP® system is known to SAP® ERP developers, clients, and partners.
   • In the User name field, provide the SAP default user for this account. If no other SAP username is provided at run time, then this SAP user account is used to run the client request in the SAP System.
     Note: The SAP default user is also used to run lookups to the DDIC for RFC, BOR, and ALE metadata. So, it is necessary to set an SAP logon user with the authorization to the mentioned SAP standard function groups: RFC1, SDIF, SG00, and SRFC. You can set a technical SAP user account with the minimum necessary set of authorizations as the SAP default user. If the execution of an RFC adapter service requires more access rights, then the name of an SAP user with sufficient rights must be passed at runtime.
   • In the Password field, enter the password of the SAP default user.
   • In the Client field, enter the three-digit SAP client number.
   • In the Repository user name field, optionally add a repository username.
     Note: If a repository user is provided, all metadata and repository lookups are run with this user account.
   • In the Repository password field, optionally enter the password of the repository user.
   • Optional: Enter the details in the SAP router string field. The SAP router string contains a substring for each SAP router to set up a connection in the route such as host name, port, and the password, if one is provided. For example, SAP router /H/127.0.0.1/H/ where H indicates the hostname. The SAP router string is needed if a firewall exists between the SAP System and webMethods Integration. For more information on configuring the SAP router, go to the SAP Service Marketplace at http://service.sap.com/connectors.
   • Optional: In the Language field, enter the SAP language code and in the Description field, provide the description of the connection.
   • Select Default runtime to specify where the service runs such as cloud designtime or self-managed runtime.
9. On the Action page, select the connection mode from the Connection Mode Setting Selection list such as Standard (Default) or Load balancing.
   If you select the Connection Mode as Standard, enter the SAP application server name in the Application server field and in the System number field enter the SAP system number (00-99).

   If you select the Load Balancing as a Connection Mode, you need to provide the following details:

   • In the Logon group field, enter the name of the group you want to log in.
   • In the Message server service field, enter the SAP message server service.
   • In the Message server host field, provide the hostname or IP address of the message server and the system ID in the System ID field.

   Note: The connection name must be unique across projects.
10. On the Logging page, configure the following fields:
    • RFC trace. The RFC trace field enables the creation of RFC trace information for this client connection. By default, it is disabled.
    • Log transaction status. The Log transaction status field is used to save the logs of processed transactions. When a transaction is created or updated, you can monitor it later in the transaction list. This option is enabled by default.
    • Store message body. The Store message body field is used to save the message content of the incoming documents. Like transaction logs, you monitor these messages in the transaction list after creation or update. This option is also enabled by default.
11. On the Advanced settings page, enable the connection pooling for a connection and click Next. By default it is disabled.
    • Minimum pool size - The minimum number of connection objects that remain in the connection pool always. When the connector creates the pool, it creates this number of connections. The default value is 1.
    • Maximum pool size - The maximum number of connection objects that can exist in the connection pool. When the connection pool is full, the connector reuses any inactive connections in the pool or waits for one to become available. The default value is 10.
    • Block timeout (ms) - The time is measured in milliseconds and defines how long webMethods Integration waits to connect to SAP ERP before giving up and displaying an error message. For example, you have a connection pool with a maximum of 20 connections. If 30 requests come at the same time, 10 of them wait in line. If you set the block timeout to 5000 milliseconds (5 seconds), those 10 requests wait for 5 seconds to get a connection. If the services take 10 seconds to finish and return the connection, the waiting requests fail and show an error because they waited too long. If you set the block timeout too high, it can cause delays and errors. One slow request can block others from being sent. Set the block timeout and maximum pool size in coordination to support bursts in processing.
    • Expire timeout (ms) - The time is measured in milliseconds and defines how long an unused connection stays in the pool before it closes and is removed. The default value is 1000 milliseconds. For example, to set it to 10 seconds, enter 10000. To keep connections open with no timeout, enter 0.
12. On the Synchronize page, the account is created, deployed, and validated on the self-managed runtime. Click Next.
    Note: The Synchronize page appears only when the self-managed runtime is set as the default runtime on the Account page during account creation.
13. On the Test and review page, verify the account information in the Overview section and test the connection. Click Enable and then click Done.