Module 3 Lab 1 - Enhance the Account Process API

In Module 2, you implemented and deployed a SAP S/4HANA System API. In this module, you’ll modify an existing APi called the Account Process API to make use of the System APIs that you’ve created and deployed. In this lab, we’ll work on the following:

Create a new project in Anypoint Studio by using the example Account API from Exchange. In Anypoint Studio, click on the *Exchange icon in the menu bar.

Search for the account-papi API Example

Click Open

Once the example is loaded in Anypoint Studio, let’s take a look what is implemented so far.

We can see that two GET Methods are implemented

We already know that these two resources have been implemented in the underlying System APIs in the previous two modules. In this API, you can see that those System APIs are called by a Scatter-Gather scope which executes synchronously to retrieve Account information from Salesforce and SAP ECC.

Also have a look at the Transform Message component. Thanks to our standardized data model we do not require any further mapping. The Scatter-Gather scope is returning an object with the multiple payloads from within the scope.

In the DataWeave we simply navigate two hierarchies down by .. and flatten the output of the different indexes so one standalone array will be returned.

As a result, any further amendment of the Scatter-Gather using the same data model does not require any further configuration or scripting.

Navigate to the app.properties file under src/main/resources.

This file contains the properties for the Account API application. The project is configured to use two System APIs currently and we’ll be adding a third API for this lab.

You will also notice the following properties are currently blank:

These properties reflect the Client ID and Client Secret of a client application that will be calling the API instance. Instances that are protected by a client ID enforcement policy require client applications to provide a client ID and client secret. The client ID and client secret credentials are automatically created when the client application is registered in Anypoint Exchange. We’ll walk through the process of requesting access to an API instance and retrieving the client ID and client secret in Step 3.

Navigate back to the Anypoint Platform and open Runtime Manager.

Click and open the SAP S/4HANA System API. The Dashboard will show the hostname for the deployed application next to the Domain label.

For this hostname, we need to create a new property in the app.properties file named s4.host. Create the property and paste the hostname for the SAP S/4HANA System API into the file.

Add also these below properties inside the file.

sapecc.host=ws-sap-ecc-sapi-00.us-e2.cloudhub.io

sapecc.client_id=<ASK INSTRUCTOR>

sapecc.client_secret=<ASK INSTRUCTOR>

At the end,the app.properties file should look like the following screenshot below now. In the next step, we’ll be registering a client application to fill in the Client ID and Client Secret.

Now we have the hostnames setup in the file, let´s generate a Client ID and Client Secret for the SAP APIs in order to access our secured System APIs. Our secured System APIs require access control via a registered Client Application.

Navigate to Anypoint Exchange and locate the Salesforce-sAPI in Exchange.

In the Salesforce-sAPI page, click on Request access.

In the Request access window, select the first API instance under the API Instance field. And for the Application field, click on Create a new application.

Give your application a name (e.g. <initials> Application) and click on Create

Click Request access

Repeat the previous steps for the following API, and be sure to select the application (e.g. DJ Application) that you created instead of creating a new one for each.

Afterwards, you can access your application by navigating to the main Exchange page and click on My applications in the left-hand navigation bar.

Select the application that you created (e.g. DJ Application) and obtain the Client ID & Client Secret

On the left-hand side of the page, you can see to which APIs have been registered against this application and as you start making calls against these APIs, you will begin to see usage statics.

Take the Client ID and Client Secret and copy and paste them in to your app.properties file back in Anypoint Studio (overwrite the values).

Back in Anypoint Studio, navigate back to the application canvas and locate the two implemented flows

In the Mule Palette, click on Search in Exchange for your SAP S/4HANA System API. Add the <initials>-SAP-S4HANA-sAPI to your project.

Now your API has been added to your project and you can find it as an additional Module in your Mule Palette

Modify the get: accounts flow and add the Get accounts operation from the SAP S/4HANA API to the Scatter-Gather scope.

Next we need to configure the Get accounts operation. Click on the Get accounts operation that you just added to bring up the properties tab. Rename the Display Name to S4HANA and then click on the green plus sign next to the Connector configuration field.

Fill in the fields that match the properties in the table below.

Now we need to finalize the configuration by providing Client ID & Client Secret from our app.properties

Next, update the get: accounts/(accountName) flow. You’ll repeat most of the steps that we just ran through for the get: accounts flow.

You might notice that we still need to provide a value for the Account Name field. Similar to what you configured in Module 2 Lab 2, a variable has been created based on the API specification to contain tha account name that is passed into the API call.

Activate the formula field and type in vars.accountName

Now, you need also to modify the properties fields references for the SAP ECC API.

[NOTE: if in the SAP ECC connector configuration are present ${app.client_id} and ${app.client_secret}, you must change, inside 2 subflows, these properties. From ${app.client_id} to ${sapecc.client_id} and from ${app.client_secret} to ${sapecc.client_secret}. See below steps.]

Go to the get:\accounts:account-papi-config subflow and click on the SAP ECC connector. Change the fields properties as in the image below.

Do the same for the get:\accounts\(accountName):account-papi-config subflow.

You’ve successfully reused and modified an Account Proccess API from Anypoint Exchange. The API, which orchestrated data from Salesforce and SAP ECC now includes account data from S/4HANA as well.

In the next lab, we’ll take this newly created API and deploy it into CloudHub.

Click to continue on to Module 3 Lab 2