Building the SAP call out to a synchronous system sample

All the files that are required to run the SAP call out to a synchronous system sample are supplied, but if you prefer to create the sample yourself, you can use the following instructions:

To build the adapter connection and message set:

1. Start the IBM Integration Toolkit.
2. Right-click in the Application Development view, and then click New > Adapter Connection.
3. In the Connector Import window, enter a name for your connector project. Click Next.
4. In the Connector Settings window, use the Browse buttons to locate your sapjco3.jar file and local files. Click Next.
5. In the Adapter Style window, select Inbound, click Next.
6. In the Configure Settings for Discovery Agent window, enter your details in any empty fields, such as Username, click Next.
7. Select the BAPIs that you want to implement in IBM Integration Bus. Select RFC (do not expand it by using the plus sign (+)). Select the Create or Edit filter button, which has three arrows on it.
8. Enter BAPI_CUSTOMER__*. Set the number of objects to receive to 100, which is important if you are using the wildcard character. Click OK.
9. Expand the RFC element, which prompts the wizard to connect to the SAP system and search for objects that match the filter that you created.
10. In the list of discovered objects, select four BAPIs:
    • BAPI_CUSTOMER_CHANGEFROMDATA
    • BAPI_CUSTOMER_CREATEFROMDATA
    • BAPI_CUSTOMER_DELETE
    • BAPI_CUSTOMER_GETDETAIL
    Press the up and down arrow keys to select the objects to import. These objects are displayed in the right pane. You might be asked whether you want to use SAP field names as attribute names, which is optional. Click Next.
11. In the Configure Objects window, ensure that Synchronous RFC is selected as the SAP Remote Function Call (RFC) type, click Next.
12. In the Service Generation and Deployment Configuration window, enter the missing details in any empty fields, such as RFC program ID, User name, and Password, click Next.
13. In the Publishing Properties window, create names for your Integration project, message flow, message set project, message set, and adapter. Click Finish.
14. You now have an Integration project and a message set project containing the message set for the import and export parameters of your BAPI, as well as an inbound adapter. If you have opted to start with a new message flow, drag the adapter onto the canvas of that message flow. This action creates an SAPInput node and a subflow that contains a branch that uses a RouteToLabel node for each BAPI that you have selected.

To build the message flow:

1. Open the message flow that was created when you ran the Adapter Connection wizard.
2. Locate your inbound adapter, which is in the message set that you created. Drag your inbound adapter onto the message flow canvas. This action creates an SAPInput node and a subflow that contains a branch for each BAPI that you selected in the previous stage, (BAPI_CUSTOMER_CHANGEFROMDATA, BAPI_CUSTOMER_CREATEFROMDATA, BAPI_CUSTOMER_DELETE, and BAPI_CUSTOMER_GETDETAIL).
3. Open the subflow. The subflow contains four branches that you navigate to by using a RouteToLabel node. Each of these branches has its own Output node, delete these Output nodes.
4. Add a Compute node after each Label node. Each branch corresponds to one BAPI, which is handled in a separate Compute node.
5. Add a single Output node and name it Reply. Connect all of the Compute nodes to the Output node.
6. In the main flow the subflow node now has two output terminals (Reply and Failure). Drag an SAPReply node from the palette and connect both of the subflow node output terminals to the Input terminal of the SAPReply node.
7. Write the ESQL for the Compute nodes. The names can be different to the ESQL that is provided in the sample, because if two discovered types have the same name, a unique number is added to the name. The ESQL that is provided in the sample can be used as the base.

Back to sample home