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:
...
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.
...
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.
