a month ago - last edited a month ago
Dear SAP Experts,
We are currently defining the data layer modernization strategy for a client planning to rebuild their existing Pega-based case management and workflow solution on SAP Business Technology Platform (SAP BTP).
The main ask from Client is if SAP BTP offers the same or better functionality to rebuild a Workflow based Application with all the specification and implementation the client currently has available for the Pega-based application running on ASPIRE Version.
Since the underlying PostgreSQL database in Pega is tightly coupled with the Pega application and not directly accessible externally, we are proposing a staged extraction and migration approach using the Pega BIX tool.
Below is the detailed end-to-end data flow and migration approach we would like SAP to validate for compliance and supportability within the BTP ecosystem:
Proposed Data Flow
Source System (Pega Application):
Data to be extracted using Pega BIX tool in Database Schema output format.
Extracted data stored in Pega Cloud File Storage, as per standard Pega BIX process.
Staging Database Setup:
Files from Pega Cloud File Storage transferred securely (via SFTP or equivalent) to a Staging PostgreSQL Database, deployed within the same hyperscaler region where SAP BTP is hosted (e.g., AWS, Azure, or GCP).
This staging environment will be used for initial validation, transformation, and reconciliation of extracted data.
Migration to SAP BTP Data Layer:
Data from the Staging PostgreSQL DB will be migrated to the SAP BTP Hyperscaler Managed PostgreSQL service using native PostgreSQL utilities such as pg_dump, pg_restore, or pg_basebackup alongside psql (for data validation)
Target PostgreSQL DB in SAP BTP will act as the primary persistence layer for new SAP Build Process Automation (BPA) and SAP Build Apps-based workflow applications with CAP service as API interfaces to that persistency layer.
Clarification Needed
Can anyone please validate on the following points:
Whether this external data ingestion and migration pattern (Pega underlying PostgreSQL DB → Pega BIX tool → Staging PostgreSQL DB → Hyperscaler PostgreSQL in SAP BTP) is technically compliant and supported within SAP BTP guidelines.
Whether any additional services such as SAP Data Intelligence, SAP Integration Suite, or SAP Data Provisioning Agent for better orchestration or governance in this migration pattern is required or only using PostgreSQL native utilities like pg_dump/pg_restore/psql is enough.
BR,
Som
#Pega #SAPBTP #MigrateFromPegaToSAPBTP #HyperscalerPostgreSQLOption
Request clarification before answering.
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.