Skip to content

Commit

Permalink
Reorganising content
Browse files Browse the repository at this point in the history
  • Loading branch information
ajmaradiaga committed Oct 3, 2023
1 parent ea52734 commit 5ba3a52
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions exercises/06-expose-integration-flow-api-management/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,17 +95,17 @@ Now that we've created the `Request_Employee_Dependants_v1` API, we can communic

At the moment we've set up an API (`Request_Employee_Dependants_v1`) in API Management that is a proxy for our integration flow. By doing this we can use API Management to add common API functionality to our API, e.g. secure the API, modify headers, transform message formats, or implement [rate limits](https://help.sap.com/docs/SAP_CLOUD_PLATFORM_API_MANAGEMENT/66d066d903c2473f81ec33acfe2ccdb4/bf441dc839034613b059cb508ad610f7.html?locale=en-US).

🧭 We've sent several messages to our integration flow via API Management. Take some time to check the message in Cloud Integration and explore the monitoring capabilities available to us in API Management (`Monitor > APIs`, Analyze section). You should see the successful and failed requests here. There is quite some information available to us here that can't be easily visualised in Cloud Integration and API Management gives us.
> 🧭 We've sent several messages to our integration flow via API Management. Take some time to check the message in Cloud Integration and explore the monitoring capabilities available to us in API Management (`Monitor > APIs`, Analyze section). You should see the successful and failed requests here. There is quite some information available to us here that can't be easily visualised in Cloud Integration and API Management gives us.
![API Management - Analyse section](assets/api-management-analyse.png)
<p align = "center">
<i>API Management - Analyse section</i>
</p>

The additional functionality can be set in API Management in the form of [Policies](https://help.sap.com/docs/SAP_CLOUD_PLATFORM_API_MANAGEMENT/66d066d903c2473f81ec33acfe2ccdb4/7e4f3e590f164996994cddc8e48bf7f5.html?locale=en-US). A policy is a program that executes a specific function at runtime, which is what allows us to add the extra functionality to our API.
> ![API Management - Analyse section](assets/api-management-analyse.png)
> <p align = "center">
> <i>API Management - Analyse section</i>
> </p>
## Examples of policies that we can apply to the Request_Employee_Dependants_v1 API

Additional functionality can be set in API Management in the form of [Policies](https://help.sap.com/docs/SAP_CLOUD_PLATFORM_API_MANAGEMENT/66d066d903c2473f81ec33acfe2ccdb4/7e4f3e590f164996994cddc8e48bf7f5.html?locale=en-US). A policy is a program that executes a specific function at runtime, which is what allows us to add the extra functionality to our API.

To communicate with the integration flow we need to send a Bearer token in the request headers. This Bearer token is obtained by first authenticating against the token server using the `clientid` and `clientsecret` we got from the [Cloud Integration runtime service key](../../prerequisites.md#create-sap-cloud-integration-runtime-client-credentials) that was created as part of the CodeJam prerequisites.

Although it is possible to create a service key and share the details with a new consumer of the service, this approach might not be ideal as an administrator will need to be involved whenever new/update credentials is required. It is not self-service, meaning we cannot use the Business Accelerator Hub Enterpise to manage our application/credentials.
Expand Down

0 comments on commit 5ba3a52

Please sign in to comment.