Introduction

Product Package is a part of the CloudBlue Connect Extension for the CloudBlue Commerce that gets deployed to the system for each individual Product as schematically illustrated below:

Lifecycle management of Product Packages is performed automatically using self-service user interface of the Extension Package. Thus users don’t need to install or update Product Packages manually.

Prerequisites

In order to work with Product Packages, users first need to deploy Extension Package. Please refer to that articles for details on how to do that.

1. New Product Installation

Follow these steps to perform installation of the new Product into the CloudBlue Commerce.

1.1 Create Product Connection

CloudBlue Connect stores product-specific configuration associated with the Hub in the special object called “Connection”. Before installing a Product into the Hub, this object needs to be created.

Navigate to the Products management module in the Provider Portal of the CloudBlue Connect and locate Product that you plan to install and navigate to the Connections section as illustrated below:

Click “Create Connection” and select Environment tab and Hub that matches your requirements:

Click Request and you should be able to see new Connection object in the list:

Once Connection is done, you can proceed to the next step of product installation directly in the user interface of the Extension Package directly in the Provider Control Panel of the CloudBlue Commerce.

1.2 Install Product Package

Installation of the Product Package must be performed from the “Connect” menu element of the Provider Control Panel versions 1 and 2. To do that, locate Product of Interest and click “Manage” as illustrated below:

In the Product Details screen you will need to choose 2 possible installation scenarios:

  • Default: Normally, you will only need simple “Install” option
  • Special Backwards Compatibility Cases: Use the “Install including end of sale items” options only when your intention is to get full set of items, even those that were already marked by Vendor as not for sale. This might be handy in various backwards compatibility scenarios, where exact match of the newly created ST is needed.

Once you click “Install” a new asynchronous Task will be created to handle the installation process and corresponding record will be shown in the user interface:

Each task transitions through the following workflow and might take up to 5 minutes to execute:

  1. APS Application Package representing Product version is imported into the CloudBlue Commerce.
  2. APS Application Instance is created based using corresponding version of the APS Application Package.
  3. Resource Types required by the system based on the “Application Service Reference” and “Application Service” Resource Classes are created.
  4. Resource Types that represent Product Items are created using the “Application Counted Reference” Resource Class.
  5. Service Template that contains all of the Resource Types created in steps 3 and 4 is created

1.3 Launch Product Configuration Manager

All Product APS Application Instances are integrated with the Product Configurations Manager (PCM) also known as Initialization wizard (or “Init Wizard) that is required to finalize Product configuration in the system.

Once Product Package installation is complete, launch PCM using the “Configure Product” button in the Application Instance details screen of the Provider Control Panel v1 as illustrated below:

For details on the PCM, please refer to the following section of the CloudBlue Commerce documentation.

2. Product Upgrade

Follow these steps to perform installupgrade of the existing Product in the CloudBlue Commerce.

2.1 Upgrade Product Package

Upgrade of the Product Package must be performed from the “Connect” menu element of the Provider Control Panel versions 1 and 2. To do that, locate Product of Interest and click “Manage” as illustrated below:

In the Product Details screen you will need to choose 2 possible installation scenarios:

  • Default: Normally, you will only need simple “Upgrade” option
  • Special Backwards Compatibility Cases: Use the “Upgrade including end of sale items” options only when your intention is to get full set of items, even those that were already marked by Vendor as not for sale. This might be handy in various backwards compatibility scenarios, where exact match of the newly created ST is needed.

Once you click “Upgrade” a new asynchronous Task will be created to handle the installation process and corresponding record will be shown in the user interface:

Each task transitions through the following workflow and might take up to 5 minutes to execute:

  1. APS Application Package representing Product version is imported into the CloudBlue Commerce.
  2. Existing APS Application Instance is upgraded to the new version of the APS Application Package.
  3. Resource Types that represent new Product Items are created using one of 2 possible options:
    1. Default: using the “Application Counted Reference” Resource Classes
    2. Compatibility Mode: using the “Application Counter” Resource Classes in case Product was initially setup using those Resource Classes

Please note that Resource Types created during upgrade are never automatically added to the Service Template to allow operators choose required business scenario while working with the Product Configurations Manager (PCM) to finalize products setup.

2.2 Launch Product Configuration Manager

Once Product Package upgrade is complete, launch PCM using the “Configure Product” button in the Application Instance details screen of the Provider Control Panel v1 as illustrated below:

For details on the PCM, please refer to the following section of the CloudBlue Commerce documentation.

Is this page helpful?
Translate with Google
Copied to clipboard