1. User Guide
  2. Appendix: About Deployments
  3. Examples: Deployment Scenarios

Examples: Deployment Scenarios

This section describes different deployment scenarios.

Deploying an Uploaded File

  1. A file of a supported type is uploaded via the Oracle Retail Xstore Office File Upload feature.

    • Supported files include Dataloader download files, configuration jar files, debit bin files, encryption cipher files, and update jar files.

    • The file is stored on the Oracle Retail Xstore Office server so that it can be deployed.

  2. A file is deployed using the deployment functionality in the File Upload feature.

    • A deployment manifest is created and stored.

    • The file is uploaded to Apache.

  3. The deployment is downloaded and applied at each applicable store. See How a Deployment is Downloaded and Appliedfor more details.

Deploying a Data Manager Change

  1. A data change, or set of data changes, is made within Oracle Retail Xstore Office's Data Manager feature.

  2. The deployment function within the Data Manager feature is used to schedule a deployment of the session.

    • A deployment manifest is created and stored.

    • An update zip file containing a Dataloader download file with the changes made in the Data Manager session is created and uploaded to Apache.

  3. The deployment is downloaded and applied at each applicable store. See How a Deployment is Downloaded and Applied for more details.

Deploying a Configuration Manager Change

  1. A configuration change is made in Oracle Retail Xstore Office's Configuration Manager feature.

    • Changes can be made at a Master Profile (Global) level, at a more granular Profile Group/Profile Element level, or at a Store-Specific level.

  2. A deployment of the configurations is scheduled via the Configuration Manager.

    • The configuration change is versioned. See Version Tracking of Deployments.

      • A deployment manifest is created and stored.

      • An update zip file is created and uploaded to Apache.

        If XML configuration changes are included, they will be transmitted in the form of a jar file containing all XML configuration changes for all profiles.

        If data configuration changes are included, they will be transmitted in the form of a DataLoader download file including data changes for the target profile.

  3. The deployment is downloaded and applied at each applicable store. See How a Deployment is Downloaded and Applied for more details.

  4. The Master Profile (Global) and any assigned Profile Group/Profile Element details are represented on the store system as configuration path entries (for example, Profile Group: COUNTRY/Profile Element: CANADA would be represented as :COUNTRY/CANADA), and determine which of the configurations in the configuration jar apply to the location.

Deploying a File Automatically

  1. A Dataloader download file, including header details that describe the deployment target area and deployment date, is placed in an automatic deployment location on the Oracle Retail Xstore Office server.

  2. Oracle Retail Xstore Office automatically detects the presence of the file and creates a deployment for it, using the provided target details to target the appropriate systems on the appropriate date.

    • A deployment manifest is created and stored.

    • The download file is uploaded to Apache.

  3. The deployment is downloaded and applied at each applicable store. See How a Deployment is Downloaded and Applied for more details.