Setting up Int4 IFTT with SAP Cloud Platform Integration

RFC Configuration

To enable interface testing on Cloud Platform Integration, runtime and management destination must be established - parameters SCI_DEST and SCI_DESTR (Global Parameters).

The connections might be set up automatically by Configuration Wizard (recommended) or setup manually as below:

Getting the right URLs for RFC destinations

NEO environment

Go to Subscriptions of your SAP Cloud Platform Cockpit on your tenant. There you will see two records, one with 'iflmap' suffix, one with 'tmn' suffix. Go to those links, and there you will find URLs necessary in SM59:
Runtime destination:

Management destination:

Alternatively, if you know the URL of your SAP Cloud Platform Integration, you can take it as "tmn" and add the second one where you replace "tmn" with "iflmap".

CloudFoundry environment

In Your instances and subscriptions BTP panel, please check the URL defined for the api and integration_flow plans in their credentials.

Use the URL for integration_flow plan for the runtime RFC. For management, use the one defined for the api plan.

Next steps

Go to your tenant, click a lock next to the URL in Chrome browser and choose 'Certificates.'

Download all certificates from the tree:

Now go to STRUST transaction where IFTT is installed. Finally, upload all certificates to anonymous SSL.

You will also need to upload your certificate to CPI tenant: STRUST → SSL server Standard → Own certificate → Export.

The exported file will need to be uploaded to the key store on CPI: Go to Overview → Keystore → Add.

Now in SM59, create two destinations with URLs found earlier, port 443 and credentials:

User credentials are a user from the tenant.

User roles

User used in RFC destination needs to have following roles in CPI:

ESBMessaging.send (iflmap/runtime)

For API / Management

In NEO

WebToolingCatalog.DetailsRead (tmn)
ESBDataStore.readPayload (tmn)
ESBDataStore.read (tmn)
WebToolingCatalog.OverviewRead (tmn)
AuthGroup.BusinessExpert (tmn)
IntegrationOperationServer.read (tmn)

In Cloud Foundry

AuthGroup_BusinessExpert
CatalogPackageArtifactsRead
CatalogPackagesRead
DataStorePayloadsRead
DataStoresAndQueuesRead
MessagePayloadsRead
TraceConfigurationEdit
TraceConfigurationRead
WorkspacePackagesRead

Int4 IFTT Dispatcher

Int4 IFTT uses its special iFlow called dispatcher, which needs to be deployed on the CPI tenant.

The iFlow is used to trigger test messages to destination iflows.

The dispatcher iFlow source file should be delivered with the installation package. Otherwise, please ask Int4 support for it.

The dispatcher will collect all requests from IFTT and route them to proper adapters. Thanks to the dynamic determination of the destination, users are not required to perform any additional configuration.

Remember that the HTTPS adapter in the dispatcher needs to be configured this way:

Since version 2.8.5 IFTT Dispatcher provides an additional SOAP endpoint. Int4 IFTT can be configured to use this endpoint using Global Parameter SCI_ASNC_D.
Using SOAP endpoint improves performance of CPI test runs.

Integration Suite HTTP Senders with Certificate Based Authorization

To be able to support HTTP senders with certificate based authorization set up on Integration Suite, the Cloud Integration own certificate needs to be added as a Key in the Process Integration Runtime Instance of BTP.

Certificate can be downloaded from the Key Store of Cloud Integration

Next it should be added as as a Key to the Instance of Process Integration Runtime to the integration-flow plan in BTP Cockpit.