PEGA 7 Release Management best practises and tools
I am looking for document or set of document where we have the list of best practises in PEGA 7 for release management and any tools that can be used for migrations from one environment to another, can anyone help me with this. Thank You
Pegasystems Inc.
US
To move an application, see this PDN article: Migrating Applications with the Application Packaging Wizard
Moving an entire schema uses the migration tool and is similar to an out-of-place upgrade. For more information, look in the Deployment Guides for the Upgrade Guide for your version of PRPC or Pega 7. Then look for instructions on using the migration tool. The details depend on your database and on whether you have a spit schema.
De Lage Landen
NL
Thanks Carbs for the info, my requirement is more to get the best practises for release management with the development into production together with smaller fixes being done by Production Support, we are not doing any upgrades or big migrations. Hope this is clearer now.
Pegasystems Inc.
IN
a strange side note: on Application packaging wizard: so double checking post RAP creation would be helpful.
- few Data- class instances such as Parties, Integration, System, security & correspondence have to be manually added in the RAP rule
Pegasystems Inc.
IN
>>> best practises for release management with the development into production together with smaller fixes being done by Production Support...
- not sure what practices we're expecting here... but my two cents...
- create a RAP rule for new functionalities and import on prod server
- if there is a schema change or any new function libraries that need to be learnt by system ... we might need to restart the sys
Pegasystems Inc.
IN
What I understand from the requirement/question –
- User deployed the application into production
- Now – a new feature development has to be moved to production …
- In this scenario – what are the best practices or checklist we should be following – is there a formal document, if any, can you please share…
Response to the post – from my learnings…
- User has to create a R-A-P rule for the new delta work and import on production system
- It could be a normal app import process using export option or
- via Migrate process
- if there are firewall settings applied … Migrate process doesn’t work
- another question – while importing delta RAP – should I need to bounce the server?
- It depends on the RULE TYPE we’re migrating…
- If the delta RAP contains just the RULES… it is not required to bounce the server…
- If the delta RAP contains any custom classes, libraries or cache changes or a server setting change,
- we need to bounce the server for application to reflect these changes.
- It depends on the RULE TYPE we’re migrating…
Please share your thoughts/comments, Thank you!
De Lage Landen
NL
Thank You Phani for the details they are helpful. The current way is manual and for someone to do this he/she needs to know PEGA application, Is there a automated way? Do you know or can provide details about this?
Pegasystems Inc.
IN
Is there a automated way?
- automated way to build a RAP rule for the new functional delta work AND to deploy on production server...?
- there is no OOTB wizard to auto create RAP rule for the delta work.
- however, we could spike around doing it.
generating Jar from RAP rule...
- again we could spike around looking at the onClick activity thats been called...
auto deploy?
- ant scripts or some scripts (few samples are available... need to search on PDN)
- or migration tool... but this will just place in the service export directory...