Defining Versions

Versioning functionality provides support for multiple concurrent catalog versions eliminating any impact on in-flight orders running different versions of catalog configuration. It provides the following functions:

  • Multiple concurrent versions of catalog configuration - Orders are associated to a specific version of the catalog configuration when entering catalog (active configuration) which is used for the entire lifecycle of the order processing. Importation of new versions of the catalog configuration will not alter these orders.

  • Multiple decomposition - Defines which key is used to execute decomposition of the same product.

  • Versioned catalog configuration import - Catalog supports importing new configuration as a new catalog configuration version.

  • Catalog configuration version activation - A new order entering catalog is associated to one and only one active version. inactive version cannot be used by runtime.

  • Default catalog configuration version - A catalog configuration version shall be designated as default, user cannot inactivate default version, but can replace it by an other one. New order entering catalog with no specific version to use, uses default version

  • Catalog configuration version display list - Catalog permits displaying list of different catalog configuration versions. 
    provadmin list catalog

  • Catalog configuration version removal - Catalog permits removal of a configuration catalog version. However, if an order entering catalog is configured to use this version, an error is raised.

  • Catalog configuration GUI editor - Catalog provides pages in Fulfillment Provisioning Catalog user interface, which permit creating/editing/deleting versions of catalog configuration. At creation time, a version can use a former locked version as a basis. Once configuration is complete, operator can activate the new version. All domains within that version are then available

  • Catalog configuration provadmin plugin - Catalog provides a set of commands in catalog catalog to manage catalog versions.

  • Catalog configuration versions recovery - Catalog is able to restart after crash or administrative stop with all imported catalog configuration versions.

Note:

Catalog stores details about versions in new files (<nodename>/kop-version.def). If none is found, but cps.def and cpr.def, Fulfillment Provisioning Catalog creates <nodename>/kop-1.0.0.def with cpr.def and cps.def as resources.