(v1) SAP IS (old)
Step 1. Create service instances on Your BTP tenant
Please note that the instructions below are meant to quickstart Your operations with Int4 Suite Cloud Version. Some decisions below, for example to use clientId and clientSecret options, might not be fit for Your organization. Please consult Your SAP Basis and Security teams before proceeding.
Also, take a look at official SAP Documentation for these services.
Create or validate existence of Services in Your BTP tenant
Depending on Your organization security settings and Your role You might or might not have access to perform the actions below. Consult Your SAP Basis and SAP Security teams for the best person and authorization settings for completing these steps.
Navigate to Instances and Subscription in Your BTP Tenant
Look for SAP IS related service instances. Process Integration Runtime plans needed are:
api
integration-flow
For these services, certain authorizations (roles) are needed:
api
AuthGroup_BusinessExpert
CatalogPackageArtifactsRead
CatalogPackagesRead
DataStorePayloadsRead
DataStoresAndQueuesRead
MessagePayloadsRead
TraceConfigurationEdit
TraceConfigurationRead
WorkspacePackagesConfigure
WorkspacePackagesEdit
WorkspacePackagesRead
WorkspaceArtifactsDeploy
integration-flow
ESBMessaging.send
If they don’t exist, they need to be created now.
Creation of service instance
Use the Create button for new service creation
Fill in the Service and Plan accordingly, provide a friendly name.
Select authorizations as described above.
Confirm creation of the instance.
Repeat the above steps for integration-flow service instance.
Create or use the access keys.
Once these service instances are created, or identified, we need access keys created.
Click on the three dots at the end of respective line, and choose Create Service Key option
Now provide the necessary settings, minimal is to provide a name for the new service key.
Once the service is created, please click the name of it and note the information, as it’s going to be necessary in the next step:
{
"oauth": {
"clientid": "sb-ad682a55-d5a1-49ec-8cf4-8e837353205b!b152182|it!b117912",
"clientsecret": "cde247c0-70cc-4803-831----xxxxxxxxxxxx",
"url": "https://int4-cloud-integration-cf-u0uxxxxxs.it-cpi018.cfapps.eu10-003.hana.ondemand.com",
"createdate": "2024-04-17T11:52:52.038Z",
"tokenurl": "https://int4-cloud-integration-cf-xxxxl6hs.authentication.eu10.hana.ondemand.com/oauth/token"
}
}
Key | Application |
---|---|
clientid | Needed for Communication System credentials |
clientsecret | Needed for Communication System credentials |
url | Communication System Host Name |
tokenurl | Communication System Token Endpoint |
Repeat the above steps.
Please note that the actions above need to be done twice, once for the api service and once for the integration-flow service.
Step 2. Create relevant Communication Systems
Communication system for the Management Endpoint
Host name, token endpoint, port should and client credentials should be derived from the configuration of instances created in Step 1. In this one, we use the “api” service.
Communication system for the Runtime Endpoint
Host name, token endpoint, port should and client credentials should be derived from the configuration of instances created in Step 1. In this one, we use the “iflow” service.
Step 3. Choose an Int4 environment or create a new one
Follow the general description for Int4 Environment Configuration to create or amend an environment
Step 4. Create communication arrangements
Create Arrangement for Scenario ID /INT4/COM_0001 - CPI Management
Assign the appropriate environment in the Additional Properties section.
Authorizations and services should populate automatically.
Create Arrangement for Scenario ID /INT4/COM_0002
Assign the appropriate environment in the Additional Properties section.
Authorizations and services should populate automatically.