Question
Knowledge Expert
IN
Last activity: 26 Jan 2024 12:19 EST
Deployment strategy/runbook/instructions for process fabric hub and connector to higher environments
Hi All,
We are working on configured PPF hub and connector in our Enterprise applications in lower environments.
As per the documentation provided by pega we have successfully configured the hub and connector in lower environments and able to test the functionalities
How do we move it to higher environments like QA or UAT and to PROD? Should we register applications in PPF in higher env's directly or is there any other way we can move as instances?
We need a deployment strategy/runbook from pega for PPF which provides the best practices/things to take care, etc w.r.t to deployment
Thanks
Jayachandra
Accepted Solution
Updated: 26 Jan 2024 12:19 EST
Pegasystems Inc.
IN
It is recommended to register applications on QA/UAT/Prod environments directly.
- As realtime data can get published once the sync is in progress.
- It is not advisable to sync Prod data into non-prod environments.
Process Fabric also throws a warning/error when syncing data from non-prod environments if Hub is on Prod environment.
Please keep in mind that based on the no of assignments/cases in the registering application, there could be load on the Queue processor infrastructure during activation (both on the Hub as well as the registered application).
Therefore its best to activate the registration during non-peak hours.
During/After the sync process keep a watch on the QPs on the Hub and registered application(refer to attachments for QP details) to see if there are any broken items(if yes, re-queueing might be needed).
Pegasystems Inc.
GB
@MattHealy🧠💪📈 @VijayVaddem would you be able to answer this question?
Accepted Solution
Updated: 26 Jan 2024 12:19 EST
Pegasystems Inc.
IN
It is recommended to register applications on QA/UAT/Prod environments directly.
- As realtime data can get published once the sync is in progress.
- It is not advisable to sync Prod data into non-prod environments.
Process Fabric also throws a warning/error when syncing data from non-prod environments if Hub is on Prod environment.
Please keep in mind that based on the no of assignments/cases in the registering application, there could be load on the Queue processor infrastructure during activation (both on the Hub as well as the registered application).
Therefore its best to activate the registration during non-peak hours.
During/After the sync process keep a watch on the QPs on the Hub and registered application(refer to attachments for QP details) to see if there are any broken items(if yes, re-queueing might be needed).