Introduction
Purpose
The document describes the high-level transport and configuration management process for R2 applications.
Scope
The transport process for the following applications will be covered in this document.
| Application | Type |
|---|---|
Ariba Sourcing | Brownfield system managed by Syensqo IT |
Ariba Cloud Integration Gateway | Brownfield system managed by Syensqo IT |
ICertis Contract Intelligence | Greenfield system managed by SyWay |
DocuSign | Brownfield system managed by Syensqo IT |
Integration Suite | Brownfield system managed by Syensqo IT |
Syniti | Greenfield system managed by SyWay |
ECC & PRS | Brownfield system managed by Syensqo IT |
Cloud Identity Services | Greenfield system managed by SyWay |
As part of release 2, no change or development is expected in the following systems and are considered out of scope for this document.
- Ariba Catalog
- Ariba Network
- Keelvar
- SAP Cloud Connector
- Convergence
- SuccessFactors
Transport Management
Ariba Sourcing
There are 3 Ariba Sourcing tenants for Release 2.
| Tenant | Description |
|---|---|
| Supplemental |
|
| Test |
|
| Production | Existing Syensqo Production tenant. |
Since Ariba Sourcing Supplemental Tenant is not linked with other tenants, a manual transport will be adopted.
- Changes (configuration, templates etc.) will be exported to files and uploaded to subsequent tenants.
- In scenarios where the object cannot be exported, changes will be manually replicated to the subsequent tenants.
Ariba Cloud Integration Gateway (CIG)
Ariba CIG has similar corresponding tenant for each Ariba Sourcing Tenant: Supplemental, Test and Production.
The following describes the transport process for Ariba CIG:
- Since Ariba CIG Supplemental tenant is not