* integrationArtifactTransport Command * CodeReview Fix * CodeReview Fix * codereview fix * Update documentation/docs/steps/integrationArtifactTransport.md Co-authored-by: Srinikitha Kondreddy <srinikitha.kondreddy@sap.com> * Update documentation/docs/steps/integrationArtifactTransport.md Co-authored-by: Srinikitha Kondreddy <srinikitha.kondreddy@sap.com> * CodeReview Fixes * CodeReview FIxes * CodeReview Fix * Doc Fixes * Update documentation/docs/steps/integrationArtifactTransport.md Co-authored-by: Linda Siebert <39100394+LindaSieb@users.noreply.github.com> * Doc fixes * Doc Fixes * CodeReview Fixes * Doc Fixes Co-authored-by: Linda Siebert <linda.siebert@sap.com> Co-authored-by: Srinikitha Kondreddy <srinikitha.kondreddy@sap.com> Co-authored-by: Linda Siebert <39100394+LindaSieb@users.noreply.github.com>
2.5 KiB
${docGenStepName}
${docGenDescription}
With this step, you can transport Integration Packages from SAP Integration Suite across various landscapes using SAP Content Agent Service.
SAP Integration Suite provides the ability to transport its content to other services. SAP Content Agent service enables you to assemble the content from various content providers (including SAP Integration Suite) in MTAR format. Later, this content is either available for download or can be exported to a configured transport queue, such as SAP Cloud Transport Management. This step, integrationArtifactTransport, only supports transporting Integration Packages from SAP Integration Suite. For more information on configurations required for SAP Integration Suite, see Content Assembly for SAP Integration Suite
To use the integrationArtifactTransport step, proceed as follows:
- Create SAP Content Agent Service Destination.
- Create Cloud Integration Destination.
- Create SAP Cloud Transport Management Destination.
- Transport Cloud Integration Content with SAP Content Agent Service as explained in the blog TMS – Transport SAP Cloud Integration (CI/CPI) Content with Transport Management Service (TMS) and Content Agent Service (CAS)
- integrationArtifactTransport step only supports Integration Package transport
Prerequisites
${docGenParameters}
${docGenConfiguration}
${docJenkinsPluginDependencies}
Example
Configuration example for a Jenkinsfile
:
integrationArtifactTransport script: this
Configuration example for a YAML file (for example .pipeline/config.yaml
):
steps:
<...>
integrationArtifactTransport:
casApiServiceKeyCredentialsId: 'MY_API_SERVICE_KEY'
integrationPackageId: MY_INTEGRATION_PACKAGE_ID
resourceID: MY_INTEGRATION_RESOURCE_ID
name: MY_INTEGRATION_PACKAGE_NAME
version: MY_INTEGRATION_PACKAGE_VERSION