Skip to content

Commit

Permalink
Doc Fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
mayurmohan authored and LindaSieb committed Dec 20, 2022
1 parent 6f520ed commit c547de5
Show file tree
Hide file tree
Showing 3 changed files with 13 additions and 13 deletions.
8 changes: 4 additions & 4 deletions cmd/integrationArtifactTransport_generated.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

14 changes: 7 additions & 7 deletions documentation/docs/steps/integrationArtifactTransport.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,18 +2,18 @@

## ${docGenDescription}

With this step, you can transport Cloud Integration, capability of SAP Integration Suite content across various landscapes using SAP Content Agent Service.
With this step, you can transport Integration Packages from SAP Integration Suite across various landscapes using SAP Content Agent Service.

Cloud Integration provides content transport mechanism. SAP Content Agent service enables you to assemble the content from these content providers in MTAR format. Later, this content is either available for download or can be exported to the configured transport queue, such as SAP Cloud Transport Management. For more information on
configurations required for Cloud Integration, see [Content Assembly for SAP Integration Suite](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/8e274fdd41da45a69ff919c0af8c6127.html)
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](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/8e274fdd41da45a69ff919c0af8c6127.html)

To use the integrationArtifactTransport step, proceed as follows:

* [Create SAP Content Agent Service Destination](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/a4da0c26ced74bbfbc60e7f607dc05ab.html).
* [Create SAP Cloud Integration Destination](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/c17c4004049d4d9dba373d72ce5610cd.html).
* [Create Cloud Integration Destination](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/c17c4004049d4d9dba373d72ce5610cd.html).
* [Create SAP Cloud Transport Management Destination](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/b44463a657fa4be48ea2525b7eb6e7de.html).
* Transport Cloud Integration Content with CAS as explained in the blog [Transport Cloud Integration (CI/CPI) Content with Transport Management Service (TMS) and Content Agent service (CAS)](https://blogs.sap.com/2022/03/25/transport-sap-cloud-integration-ci-cpi-content-with-transport-management-service-tms-and-content-agent-service-cas/)
* integrationArtifactTransport step only supports Integration Package transport.
* 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)](https://blogs.sap.com/2022/03/25/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

Expand All @@ -31,7 +31,7 @@ Configuration example for a `Jenkinsfile`:
integrationArtifactTransport script: this
```

Configuration example for a YAML file(for example `.pipeline/config.yaml`):
Configuration example for a YAML file (for example `.pipeline/config.yaml`):

```yaml
steps:
Expand Down
4 changes: 2 additions & 2 deletions resources/metadata/integrationArtifactTransport.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
metadata:
name: integrationArtifactTransport
description: Integration artifact content transport using the SAP Content Agent service
description: Integration Package transport using the SAP Content Agent Service
longDescription: |
With this step you can trigger the integration artifact content transport using SAP Content Agent service and SAP Cloud Transport Management Service. For more information about the integration artifact content transport using SAP Content Agent service [here](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/8e274fdd41da45a69ff919c0af8c6127.html).
With this step you can trigger an Integration Package transport from SAP Integration Suite using SAP Content Agent Service and SAP Cloud Transport Management Service. For more information about doing an Integration Package transport using SAP Content Agent Service see the documentation [here](https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/8e274fdd41da45a69ff919c0af8c6127.html).
spec:
inputs:
Expand Down

0 comments on commit c547de5

Please sign in to comment.