Posted: 21 Jan 2019 8:35 EST Last activity: 2 May 2019 10:31 EDT
Reusable Components for Integration
We have around 8 Pega on-premise applications running on separate application & database server. Being responsible for COE related activities, I want to create a repository of all the integrations which are being used across applications so that they can be used as reusable components for any new application later.
I would also like to automate this process so in future if any service or connector is developed by any application team, the same can be stored in our repository.
Any advice on the implementation in Pega would be appreciated?
A single Integration framework application can be built on by including all service integrations in different applications and this application can be added as Built On application for all the existing applications. Even for future applications also this component application can be added as built on so that it can reuse any existing or current service integrations or extend if any customisation needed for it.
Thanks for your reply but developing a component would always be a manual process and I guess someone needs to keep checking for the new integration being made. Is there way we can automate this?
For e.g. we can develop some kind of service in pega which will be triggered by some batch process and it will fetch all integration record from different application and save in our database. I was just curious if there is any easier approach.
I am currently trying to solution the same concept - creating a CoE repository of integrations/components for reusability. Can you share what your team decided to do? Or share any key learnings from your experiences that might benefit the greater Pega community?
We are planning to develop a component which will comprise of all integration related rules. The same can be deployed later for individual applications so that they can reuse it. However if any line of business have any specific requirement/customization, then the rule can be customized in their own ruleset.