Plesk in VPS Resource Model

This resource type keeps the result key which is received from the Key Administrator on license issue request for specific customer's Plesk instance. PVPS License keeps the result key combining license data from PVPS Configuration and PVPS KA License resources.

There should be one PVPS License resource per service template.

This resource type keeps the identifier of Plesk license in Key Administrator (the license type can be main, additional, and bundle). This resource is not required, it is needed for Plesk upsell scenarios.

You can include several PVPS KA License resources per service template.

In PCP, this resource is not called PVPS KA License, instead it has a particular name of license, for example, KA ADD-COMPLETE-BACKUP-SOLUTION-M (Additional License), KA ADD-JOOMLA-TOOLKIT-M (Additional License), etc.

This resource type keeps parameters of Plesk configuration, which define what platform, version, edition, modules Plesk will be installed with.

You can include several PVPS Configuration resources per service template.

In PCP, this resource is not called PVPS Configuration, instead it has a particular name of configuration, for example, Plesk Onyx for Linux, etc.