Exporting Package for Resilient Protectors

The export package process includes an API for exporting the package from the ESA. The exported package is used by the resilient protectors.

The following table provides information about each component that must be used or configured to export the package from the ESA.

Policy ComponentsDescriptionReference
RPS APIAfter the package is configured on the ESA, the RPS API helps in exporting the package that can be imported to the resilient protectors.
For more information about how resilient packages are imported to protectors, refer to the respective Resilient Protector documentation.
For more information about the RPS API, refer to section APIs for Resilient Protectors in the Protegrity APIs, UDFs, Commands Reference Guide.
RPS ServiceThe RPS service is installed on the ESA. This service must be up and running before any resource is requested using the RPS API.- Verifying the RPS service - section Verifying the RPS Service for Policy Deployment on Resilient Protectors in the Installation Guide.
- RPS service - section Start and Stop Services in the Appliance Overview Guide.
Export Resilient Package permissionThe Export Resilient Package permission must be assigned to the role that will be granted to the user exporting the package.For more information about the permission, refer to Managing Roles in the Appliance Overview Guide.