I have automated Pega RAP export and import using PRPC utility (prpcServiceUtils_74) on Pega7 / Pega8. We are using 1 non SSO operator which has multiple access group assigned and its assigned with Developer portal.
We are facing 2 issues at the moment.
1. During export we are expected to set the respective access group of the application for the PRPC to successfully export the RAP file. Otherwise the export fails. Please note import PRPC is successfully able to import the application product even if the respective default access group is not set up. Problem is only with PRPC export.
2. On Prod Pega environment we have disabled developer portal (due to security concern) and enabled admin portal. But PRPC Import fails to swith the default access group automatically, when the operator has admin portal enabled.
We would like to know, if there is a way to set the default access group of the application using PRPC command for both import and export. We found an option updateaccess but looks like its not setting up default access group.
***Edited by Moderator: Pooja Gadige to add platform capability tag***
@NarayananS6702 Have you tired using deployment manager? It does the switch to the correct application context automatically. It also supports integration with external tools like Jenkins along with other needed features to manage application deployments.
No I am using PRPC Service Utils utility to export and import the product and calling the utility using a Jenkins Pipeline. I understand we have deployment manager which can do similar migration and it can switch automatically but we are not using deployment manager for this.
I would like to know how to switch the default access group using command line utility or an API call.
Posted: 4 months ago
Posted: 3 May 2021 5:06 EDT
Anil Kondakindi (konda)
Senior Manager, Cloud Engineering
@NarayananS6702 I dont think prpcServiceUtils supports switching access groups. It takes the user/pwd and uses that operators context to do export/import. As a work around you could use different operators for different applications.
The reason for suggesting deployment manager is, it does all of the required things behind the scenes and gets you a `in the model` experience of managing deployment pipelines. If Jenkins is a mandate from your COE, you could use a combination of deployment manager and Jenkins. Deployment manager has a lot of API's exposed to enable this integration.