Skip to content

Commit 0117709

Browse files
authored
name change (#23085)
1 parent 430d643 commit 0117709

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

tutorials/btp-integration-suite-nonsapconnectivity-usecase/btp-integration-suite-nonsapconnectivity-usecase.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author_name: Karunaharan V
88
author_profile: https://github.com/Karunaharan
99
---
1010

11-
# The Use Case for the Challenge
11+
# The Use Case for the Mission
1212
<!-- description --> Understand the integration problem that you're going to solve before you get started
1313

1414
## You will learn
@@ -31,12 +31,12 @@ SAP Integration Suite is available in simple service plans. To know more about t
3131
Using this integration scenario, you design and execute an integration flow that reads information from a third-party software. To accomplish the scenario, you use SAP Integration Suite, and in particular, its capabilities *Cloud Integration* and *Open Connectors*.
3232

3333
You use *Open Connectors* to
34-
- identify and establish connection to a third-party software
35-
- fetch data from the third-party software via APIs
34+
1. identify and establish connection to a third-party software
35+
2. fetch data from the third-party software via APIs
3636

3737
You use *Cloud Integration* to
38-
- design a custom integration artifact to fetch data from Open Connectors
39-
- deploy the integration artifact to a cloud-based runtime location
38+
1. design a custom integration artifact to fetch data from Open Connectors
39+
2. deploy the integration artifact to a cloud-based runtime location
4040

4141
Finally, use an open API platform like Postman to securely invoke the deployed integration artifact to see that you're able to fetch data from a third-party software using SAP Integration Suite.
4242

0 commit comments

Comments
 (0)