Skip to content

feedback from testing team #23048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 12, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ author_profile: https://github.com/Karunaharan

4. Choose **Edit** to start editing the integration flow.

Choose **Restore** at the bottom right corner to bring up the **Property Sheet**. Property sheet is the place where you define the parameters for each step in the integration flow.
Choose **Restore** at the bottom right corner to bring up the **Property Sheet**. Property sheet is the place where you define the parameters for every step in the integration flow.

<!-- border -->![Start editing the integration flow](3-1-edit-iflow.png)

Expand All @@ -78,7 +78,7 @@ In this step, you define your sender channel and sender adapter. In this case, w

### Add JSON to XML converter

Input to the integration flow is sent in JSON format. At a later point, you communicate to a web shop which is a OData service. You use the converter for this JSON to XML conversion. After the input is converted into XML, the message is sent as header information to the OData service to fetch the required product details.
Input to the integration flow is sent in JSON format. At a later point, you communicate to a web shop, which is a OData service. You use the converter for this JSON to XML conversion. After the input is converted into XML, the message is sent as header information to the OData service to fetch the required product details.

1. From the palette (the grey bar on the top containing integration flow steps), choose **Message Transformers > Converter > JSON to XML Converter**.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -49,9 +49,11 @@ In this step, you copy the endpoint address of the integration flow.

In this step, you define and expose an integration flow endpoint as an application programming interface

1. Choose **Design** > **APIs** > **Create** to create an API.
1. Choose **Settings** > **APIs** to provision the API Management capability. This provisioning might take a few seconds to complete. After the provisioning is complete, refresh your page.

2. On the **Create API** dialog, next to **Select**: choose **URL** and specify the following parameters:
2. Choose **Design** > **APIs** > **Create** to create an API.

3. On the **Create API** dialog, next to **Select**: choose **URL** and specify the following parameters:
>**IMPORTANT** : Paste only the endpoint URL till **`/http/products`** Otherwise, the scenario will not run appropriately.

| Parameter | Settings
Expand All @@ -65,33 +67,33 @@ In this step, you define and expose an integration flow endpoint as an applicati

Select **Create**.

3. On the landing page, choose **Resources** tab and then **Add**.
4. On the landing page, choose **Resources** tab and then **Add**.

<!-- border -->![Add resources](2-5-create-api-resources.png)

4. In field **Tag** enter **`Product Details`**, and in the field **Path Prefix** enter **`/details`**.
5. In field **Tag** enter **`Product Details`**, and in the field **Path Prefix** enter **`/details`**.

<!-- border -->![Add details](2-6-add-resources.png)

5. Under **Operations**, delete all tabs except the **POST** tab and choose **OK**.
6. Under **Operations**, delete all tabs except the **POST** tab and choose **OK**.

<!-- border -->![Add operations](2-7-save-resources.png)

The API Resource is displayed.

6. Choose **Deploy** to create and activate the API Proxy for your integration flow.
7. Choose **Deploy** to create and activate the API Proxy for your integration flow.

<!-- border -->![Deploy](009.png)

7. Choose the **POST** operation to display more details on the API. A default API definition in Open API specification format is also generated.
8. Choose the **POST** operation to display more details on the API. A default API definition in Open API specification format is also generated.

8. To update the generated API definition in Open API format, choose **Edit > Edit in API Designer**.
9. To update the generated API definition in Open API format, choose **Edit > Edit in API Designer**.

<!-- border -->![Edit API designer](010.png)

The API designer is opened.

9. In the editable section on the right part of the screen, make the following changes.
10. In the editable section on the right part of the screen, make the following changes.

Change **Payload** to **`productIdentifier`** and add a row as shown in the following screenshot.

Expand All @@ -103,13 +105,13 @@ In this step, you define and expose an integration flow endpoint as an applicati

Choose **Save**.

10. Choose **`RequestProductDetails`** and then the **Resources** tab.
11. Choose **`RequestProductDetails`** and then the **Resources** tab.

Choose the **POST** request. You notice the API changes, in particular, the request body contains now one element with a product identifier.

<!-- border -->![Resources Tab API Changes](014.png)

11. When you choose **Try Out** and then **Execute**, since no authentication details have been configured, you get an error message with error code 401 (not authorized).
12. When you choose **Try Out** and then **Execute**, since no authentication details have been configured, you get an error message with error code 401 (not authorized).

<!-- border -->![Error message](015.png)

Expand Down
15 changes: 15 additions & 0 deletions tutorials/cp-starter-isuite-api-management/rules.vr
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
[VALIDATE_4]
###Rule
multiple-choice

###Question
Which of the following values are mandatory to authorize the API client and to call an integration flow as an HTTP endpoint?

###Match
[X] clientid
[ ] roles
[X] clientsecret
[ ] url
[X] tokenurl

[VALIDATE_4]
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ You use *Cloud Integration* to design and deploy an integration flow. Then, you

>**WHERE TO START**:

> - **Are you new to SAP BTP Trial?** - skip the rest of the note and continue with the tutorial.
> - **Are you new to SAP BTP Trial?** - skip the rest of the note and continue with this tutorial.

> - You already have a SAP BTP trial account but new to SAP Integration Suite:

Expand Down Expand Up @@ -96,7 +96,7 @@ You use *Cloud Integration* to design and deploy an integration flow. Then, you

<!-- border -->![Assign Roles](3-6-Assign-Roles.png)

6. In the dialog that appears, select **Integration Provisioner**. Choose **Assign Role Collection**.
6. In the dialog that appears, select **Integration_Provisioner**. Choose **Assign Role Collection**.

<!-- border -->![Assign Role Collection](3-7-Assign-Role-Collection.png)

Expand All @@ -106,7 +106,7 @@ You use *Cloud Integration* to design and deploy an integration flow. Then, you



### Provision the capabilities
### Activate the capabilities

>**IMPORTANT**: Ensure that you unsubscribe from the standalone services (like Cloud Integration, or API Management) if you have already subscribed to them in the same subaccount. If the standalone subscription exists, you will be unable to activate respective capability via the Integration Suite.

Expand All @@ -117,7 +117,7 @@ You use *Cloud Integration* to design and deploy an integration flow. Then, you

<!-- border -->![Integration suite launchpad](4-1-isuitenewlaunchpage.png)

For this tutorial, you must select the **Design, Develop and Operate Integration Scenarios** and **Design, Develop and Manage APIs click** capabilities. Choose **Next**.
For this tutorial, you must select the **Build Integration Scenarios** and **Manage APIs** capabilities. Choose **Next**.

<!-- border -->![Add Capabilities](4-1-Addcapapbilities.png)

Expand Down