Create One subaccount as Quality
DEV
Create Qua
Dev
Subscribe
3276989 - Check Configuration failed for Transport
Management Service in Cloud Integration tenant settings
Add content agent service and subscribe the free service and assign the roles.
Goto role collections
Add required Content agent service roles (Admini, import, export, read..)
Goto roles – content admin role -have above all roles
Add individual roles
Create the instance key and create service key
Oauth/token is missing
API Management
D1- API Management makes an API call to the Content Assembly Service
to inform about the transport.
D2 - Content Assembly Service then makes an API call to fetch the API
content from API portal workspace. The Content Assembly Service wraps
the API content for transport.
D3- The Content Assembly Service makes a second API call to push the
API content to the Transport Management service (TMS).
D4- The SAP Transport Management service makes an API call to the
Deploy Service. The Deploy Service calls the API Management in the
destination subaccount to import the package into the API Management
workspace .
Set Up API Portal Application | SAP Help Portal
Note
You should either have Integration Suite subscription or API
Management, API Portal tile visibility to set up the API Portal
application.
If you’re subscribing to the API Management, API portal in the
Cloud Foundry subaccount, either by using the Integration
Suite launchpad or the API Management, API portal standalone
tile, ensure that you don’t have an instance of starter plan created
in the same subaccount.
API Management capabilities from Integration Suite and API
Management subscriptions can’t coexist in a subaccount.
