The document describes the landscape and high-level transport process for R2 applications.
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 |
Out of Scope
As part of release 2, no changes is expected in the following systems and are considered out of scope for this document.
Detailed technical steps on how transports will be performed is also considered out of scope as the steps can be found in product documentations.
The following sections will cover the following the the applications in scope.
There are 3 Ariba Sourcing tenants for Release 2.
| Tenant | Description |
|---|---|
| Supplemental |
|
| Test |
|
| Production | Existing Syensqo Production tenant. |
Supplemental Realm will be repurposed release 4 after integration test (24-Nov). Hence there will be 2 transport paths for Ariba Sourcing
The following describes the transport process for Ariba Sourcing:
Ariba Sourcing and CIG tenants are provisioned together and integrated by SAP. Hence the landscape and transport path for Ariba CIG is the same as Ariba Sourcing.
The following describes the transport process for Ariba CIG:
ICertis landscape consists of 2 tiers.
| Tenant | Description |
|---|---|
| Non-PRD | Used for all R2 project activities (E.g., Development, Integration Test, UAT) |
| Production | During project phase, Production instance will be used to practice loading Production contract data loads. Before Go-live, data in Production will be cleared in preparation for Go-Live. |
Configurations and changes will be performed in non-PRD and transported to Production instance during project phase (to support data load) and ACO.
Promote Configurations (P2P) Tool will be used to transport changes from non-PRD to Production.
DocuSign landscape consists of 2 tiers.
| Tenant | Description |
|---|---|
| Non-PRD |
|
| Production |
|
Configurations and changes will be performed in non-PRD and transported to Production instance during ACO.
The following describes the transport process for DocuSign:
<TBD>