ReleaseOwl Docs
  • ReleaseOwl Admin Guide
    • General Administration
      • User & Role Management
      • Project Management
      • Landscape Registration
      • Global Credential Management
      • Settings
      • Landscape Connectors
      • Parallel Landscape Configuration
      • Static Code Analysis
      • RO Agents
    • ALM Integrations
      • Jira
        • Jira Cloud
        • Jira On-Premise
        • Jira Automation Rules
      • Azure DevOps
      • ServiceNow
      • Freshservice Integration
    • Other Integrations
      • ReleaseOwl Callout Feature
      • DocuSign
    • Landscape Mapping
  • ReleaseOwl User Guide
    • Change Management
      • Backlog
      • Sprints
      • User Stories
      • Release Versions
      • User Story Dependency
    • Transport Management
      • On-Prem Environment Registration
      • Creation of Transports
      • Transport Validation and Analysis Reports
      • Transport Promotion and Pipeline Activity
      • Transport Management Actions
      • Transport of Copies
      • Retrofit & Conflict Resolution
      • gCTS
        • Build pipeline support for onPrem Fiori
    • SAP BTP
      • Administration
        • Credential Management
        • Cloud Environment Registration
      • Working with Build Pipelines
        • Static Code Analysis
        • Change Log Analysis
        • Download Artifact
        • Labels
      • GIT Ops
    • SAP API
      • Adminstration
        • Credential Management
        • Cloud Environment Registration
      • API Management
    • SAP CPI
      • SAP CPI Integration with ReleaseOwl
      • CPI Test Generator
      • CPI Management
        • Synchronize CPI Artifacts
        • Artifact Versions
        • CPI Artifact Comparison
        • Backup & Rollback
        • CPI Validation - CPILint
        • iFlow Unit Testing
        • Integration Advisor
    • SAP Analytics Cloud
    • SAP Datasphere
    • Working with Release Packages
      • Create Release Package with User Stories
      • Create Release Package with Transports
      • Release Package Validation with Transports
    • Working with Release Pipelines
      • Pipeline Tasks
        • Approval Task
        • Callout Task
        • Manual Task
        • User Story Status Task
        • Test Execution Task
        • Message Listener Task
        • GCTS Merge Task
        • GCTS Activate Task
        • GCTS Switch Task
        • Import via Toc Task
        • Transport Retrofit Task
        • Release Transport Task
        • DocuSign Approval
        • Validation Task
      • Use Cases
        • Automated Transport import along with Transport Promotion
        • Automated MTAR Deployments
        • Automated CPI Deployments
    • Test Automation
      • HCL OneTest
        • Test Configurations
        • Running Automated Tests with Release Pipelines
      • Tosca Integration
      • Integrating UiPath with ReleaseOwl
    • My Tasks
    • Multiverse
    • Utilities
      • ABAP Version Compare
      • gCTS Merge
Powered by GitBook
On this page
  • Prerequisites
  • Synchronize Integration Suite Artifacts
  • Sync History
  • Sort
  • Actions
  • Manage Environment Wide IFlow Configurations
  • Artifact Versions
  1. ReleaseOwl User Guide
  2. SAP CPI
  3. CPI Management

Synchronize CPI Artifacts

PreviousCPI ManagementNextArtifact Versions

Last updated 21 days ago

Prerequisites

  1. Begin by registering your SAP BTP credentials and the corresponding SAP Integration Suite environment within ReleaseOwl.

  2. Navigate to the Projects section and create a new project.

    • Project Type: Select SAP CPI.

  3. Once the project is created, add the registered environments to the project via Project Settings > Environment.

  1. Click Sync All Artifacts to fetch and display the available CPI artifacts within the selected project.

  2. Navigate to Build > SAP CPI Management and click on the actions button to view Sync Artifacts.

Synchronize Integration Suite Artifacts

  1. Click Sync Artifacts to fetch various artifacts like IFlows, Value Maps, Packages, Configuration parameters, etc. from the registered SAP CPI environment into ReleaseOwl.

  2. If there are changes made to the existing artifacts, the changes will also be updated.

  3. Click Sync Artifacts to sync the CPI artifacts.

Sync History

With this, you can view the history of all the artifact syncs that have occurred. Click Sync History, to view the CPI sync history of this project.

Sort

You can sort the artifacts as per your convenience. To sort them:

  1. Click the Sort icon.

  2. In the page displayed, choose an option and click OK.

Actions

Multiple actions can be performed on an artifact, based on the type of artifact. These actions include – View Test Cases, Comment , Configure, Deployment History, Versions and Download.

Manage Environment Wide IFlow Configurations

You can maintain configuration parameters for IFlows for each environment separately in ReleaseOwl. These will be updated accordingly during the deployment.

To configure an artifact:

1. Go to the required artifact, click Actions and choose Configure.

2. The following screen is displayed that will show various configuration parameters for the Integration Suite environments that are part of the landscape.

3. No changes can be made to Dev environment.

4. To make changes in any other environment, click the edit icon on the required name and make changes. Click Save.

Artifact Versions

1. To view the versions, go to the required artifact, click Actions and choose Versions.

  1. The following screen is displayed showing the user different versions of the artifact.

  1. Assign User Story option is used to link a specific version of an artifact (such as a configuration or integration flow) to a designated User Story.

  2. On clicking Assign User Story, the system will prompt you to:

  • Select a User Story from a searchable button.

  • Associate the current version of the artifact with the selected User Story, establishing a traceable link between the artifact version and the development requirement.

  1. Click Actions and choose either Download or Where Used List based on the requirement.