Robot manager migration
Hi,
We are migrating from Pega Robot manager on Pega.7.3 with a separate Package Server to a Pega 8.5 environment with also a packager server.
Migrating the packages on the package server to a new file share is easy.
But, how to migrate the Robots data that is in Pega robot Manager application?
I have searched for answers but wasn't able to find it.
Kind regards,
Arjan Maus
Achmea
NL
@ArjanM04
Hi all,
I still need help on this issue, sin't there anyone who has experience with this kind of work or should we not even try to migrate this way?
Kind regards,
Arjan Maus
Pegasystems Inc.
GB
Hi,
Are there any specific needs for you to keep the old versions of the packages?. I'd recommend to re-deploy the packages to the new repository instead of copying them.
Which robot data you want to migrate? you can migrate any RM data via RAP but I'd need to understand which data you are referring to.
Achmea
NL
@Angel Hermira
I hope this makes any sense:
What Arjan means with the robot data, is the package meta data that is stored on the Robot Manager. So which versions are available, which solutions are deployed in which environment, assignments, etc. (Essentially all information that is stored behind the "Packages" page in the Robot Manager per seperate robot listed. The package server does not have his information stored.
About your recommendation for the redeploying, I think this a rather time consuming action. Within Achmea we have had several seperate dev groups and I do like to think we have all sources. But we have to gather them, select the correct version and open them and then redeploy them. We currently have around 60-70 operating solutions.
Regards,
Niels Lewerissa
Pegasystems Inc.
GB
@NielsL ,
The packages metadata is stored as data instances of Data-Robotic-AutomationPackage and its descendent classes. If you migrate all those instances you'll migrate all the package's metadata. Are you planning to migrate the assignments as well? if so, you'll need to migrate Link-Robotic-PackageAssignment data instances.
The new package repository uses the package ID to name the package files stored in the repository. You'll need to rename the package files as part of the migration process.
Doing the above will get you to a like for like packages and assignments system.