1. User Guide
  2. Appendix: About Deployments
  3. How a Deployment is Downloaded and Applied

How a Deployment is Downloaded and Applied

  1. Oracle Retail Xenvironment queries Xcenter for any open deployments at a fixed interval.

  2. When Oracle Retail Xenvironment receives deployment details, it processes them in an appropriate manner.

    • An update message is sent to Xcenter to indicate that each manifest has been successfully received.

    • Connectivity details are stored so they can be used to download deployed files.

  3. Oracle Retail Xenvironment stores each deployment either for immediate download or download during the closing process.

    • If a deployment is scheduled for immediate download, Oracle Retail Xenvironment will begin to download the file immediately.

    • If a deployment is scheduled for download during the close, Oracle Retail Xenvironment will wait until the nightly closing process is initiated to begin downloading the file.

  4. Oracle Retail Xenvironment applies each downloaded deployment at the appropriate time.

    • If a deployment is scheduled to be applied immediately (applies to MNT files, DAT files, and application updates only), Oracle Retail Xenvironment executes the jar. (DataLoader is not used to apply immediate application updates).

      Note:

      Oracle Retail Xenvironment will stop Oracle Retail Xstore Point of Service before applying an immediate application update, but it the responsibility of the code within the jar file to restart Oracle Retail Xstore Point of Service, not Oracle Retail Xenvironment.

    • If a deployment is scheduled to be applied during the closing process, it will be handled properly during that process.

      • Dataloader download files are applied via the Dataloader on the lead Oracle Retail Xenvironment register.

        If the download data was provided by any feature other than the Configuration Manager, it is loaded into the DB.

        If the download data was provided by the Configuration Manager, it is loaded into the DB only if the system's configuration path includes the associated profile.

      • Update jar files are applied by distributing them to each system and executing them.

      • Encryption cipher files are applied by distributing them to each system.

      • Debit bin files are applied by distributing them to each system.

      • Configuration Manager jar files are applied by distributing them to each system.