Question
Flextronics International USA Inc
US
Last activity: 22 Mar 2018 19:34 EDT
How to restrict Package Server Access
We were using one package server for all environments and ran into an issue when deploying a package with same version number which is overwriting and caused issues. so we decided to separate package servers for each environment. But how do we force/restrict users to access package server? Is there anyway we can restrict robomanager to connect to a particular package server only? Right now there is no way we can enforce developers to use correct package server. How do we do it?
***Edited by Moderator Marissa to update categories***
Pegasystems Inc.
US
Hi, the Robot Manager does not connect to the package server at all. Instead, Robotics Studio can be configured for the location of the package server. Check the Studio config files. Automation developers publish packages to the server referenced in their instance of Robotics Studio.
By the way it's better to have one single package server. You can still have multiple Pega environments. Just migrate the package metadata across your Pega instances to in a RAP to keep things in sync.
Your RAP should contain instances of the following classes:
Data-Robotic-AutomationPackage
Data-Robotic-AutomationPackage-DeploymentLevel
Data-Robotic-AutomationPackage-Version
Data-Robotic-AutomationPackage-Version-Config
(and all associated history files)
Flextronics International USA Inc
US
Thank you! But recently we had an issue. There was a package deployed in production. Somehow the developer rebuilt the same package with same version as production in development which overwritten the production copy. How do we control this? We know it is not best practice to rebuild the package with version same or lower than the production version. But visual studio allows this. Is there any documentation on package server apart from installation document?