Thank you for the URL, However this URL has details on how to create a Jenkins JOB.
my question is that when jenkins is making a REST-Service call to pega we have to have a RESTService package and a Service Rule where we should handle the ACtivity for RAP creation i assume its ExportRAP, Parameters, GET/POST/PUT/DELETE. Would you be able to provide an example rule which is working for creating RAP's when initaited VIA JENKINS?
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query.
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s at the top of this screen and also on our Pega Support Community homepage. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.
Basically, if you want to avoid using CLI (prpcServiceUtils), as I did, you need to create a REST service which will be called by Jenkins to initiate migration.
Pega already has ootb activity to trigger migration process (look into Migration Wizard for more details) - RequestMigration in a class PegaAccel-Management-Migration-Request. Save-as into your ruleset, and make small changes:
1. Comment out a line 6 ("Set a flag to indicate that the request is initiated from CLI")
2. Add new line to the end Property-Set with step page .ResponseBody where you set some values as a response from your service (I set Code, ResponseStatus and WorkID).
Your service must use this activity and provide several crutial parameters:
1. RAP name, version to migrate
2. Name of the system to migrate (you must create it beforehand)
Hope it will get you idea about starting point. Basically, everything is already implemented in Pega, you just need to adjust it for your needs.
Any questions - ping me
Posted: 2 years ago
Posted: 7 Aug 2019 9:34 EDT
Linoy Alexander (alexl)
Director, Developer Productivity
I should point out that there is no need to avoid using the prpcServiceUtils package. It is a convenience command line utility that can be invoked from any tool or choice, the above link referencing Jenkins is just an example. The prpcServiceUtils package also include some starter ANT scripts that can be integrated into any build tool of choice and supports all of these actions out of the box
Export RAP archives and applications
Retrieve asynchronous job status
There are rule level APIs in the platform and you can create your own service packages and it will be a lot more work to recreate everything.