Robotic Solution Deployment into Pega Platform DEV , TEST , PROD environments
Dear Pega Colleagues,
currently we are facing an issue how to deploy our Robotic Solution into PROD Pega Platform.
our infrastructure looks like this:
Robot DEV VM connected to DEV Pega Platform
Robot TEST VM connected to TEST Pega Platform
Robot HOTFIX VM connected to HOTFIX Pega Platform
2x Robot PROD VMs connected to PROD Pega Platform
IN DEV and TEST VMs we have installed Pega Robotic Studio and Package servers.
IN HOTFIX and PROD VMs we have installed Pega Robotic Runtime
VMs are not interconnected so I cannot set in runtimeconfig.xml in PROD environment
<PackageServer baseUrl="http://IPAddressOfDEVVM:5000" /> - connection is not there. to any VM.
The Pega Platform environments are also not connected, so I will not be able to see in PROD the packages from DEV or TEST.
What is please the best practice to make pass our packages through different environment of Peg Platform Robot Manager ?
Thanks
Regards
***Edited by Moderator Marissa to update platform capability tags****
Thank you very much for this answer,
Thank you this is clear for me:
Since you have multiple Package Servers, then you need to move the actual files stored in your lowest level environment package server to your other environment's package servers. This is just a direct copy of your "Packages" directory from one server to another. You shouldn't be publishing any packages to higher environments, so this move should be one way (i.e. your Studio is always connected to your DEV Package server and so that directory always has all of the deployments).
But when we are talking about moving packages from TEST PEGA Platform to HOTFIX PEGA Platform and PROD Pega Platform, is it enough to do the packaging of mentioned clases in TEST Pega Platform , Do Export in TEST and Import in HOTFIX and PROD ? or should I also copy the packages file directories also within VMs to HOTFIX and PROD ?
we do not have package servers in HOTFIX and PROD VMs, what configuration then needs to be done in runtimeconfig.xml in those VMs ?
Thank you
Regards
David
The package server that you are using in whatever environment needs to contain the files you deployed. In your environments without a package server, you'd just use the one from a lower environment. You really only need one. You will need to move the metadata though between Pega platform instances into each environment.
Hi Thomas,
Thanks for answering my colleague's question. I would like to know what the best practice would be?
Having Dev >> Test >> Preprod >> Prod, how would you recommend doing deployment of the robot packages? Through the Pega platform as described above or another way?
Thanks, Craig
As described above. Basically, deploy via Studio to your lowest environment. Move the files from Package Server to Package Server and move the metadata from Pega environment to each subsequent environment. You really could use one Package Server for all environments if you are able to, as that makes things a little simpler.
Since you have multiple Package Servers, then you need to move the actual files stored in your lowest level environment package server to your other environment's package servers. This is just a direct copy of your "Packages" directory from one server to another. You shouldn't be publishing any packages to higher environments, so this move should be one way (i.e. your Studio is always connected to your DEV Package server and so that directory always has all of the deployments).
In addition to moving the files, you'll also need to move the metadata about these files stored in the Pega Platform. To do that, you'll export the following classes;
Data-Robotic-AutomationPackage - corresponds to package names
Data-Robotic-AutomationPackage-Version - versions for each package
Data-Robotic-AutomationPackage-Version-Config - configurations for each package
Data-Robotic-AutomationPackage-DeploymentLevel – deployment levels assignments
On your next environment, you would then import these.