Config Path Retrieval Process

An empty configPath.properties file is part of the POS overlay and can be found in xstore/configPath.properties after the installation. When Xenvironment is started for the first time after Xstore Point of Service is installed, the configPath.properties file is copied to environment/res/data/configPath.properties.

When Xenvironment is used to start Xstore POS or Xstore Mobile (including during Xenvironment startup), Xenvironment will contact Xcenter to check for any updates to the config path settings. If any changes are found, the file in environment/res/data will be updated. Xenvironment will update copies of the file in xstore/configPath.properties and xstore-mobile/configPath.properties. Before retrieving updates, Xenvironment will read the values of xstore.location.mobile.workstationId.range.start and xstore.location.mobile.workstationId.range.end from xstore-mobile/system_mobile.properties. This range will be forwarded to Xcenter to retrieve settings for mobile registers in addition to the current register.

Retrieving updates to configPath.properties from Xcenter is enabled by default. To disable the feature, the following setting can be added to the Xenvironment overlay in version1/actions.properties:

chain.RETRIEVE_CONFIG_PATH.disabled=true

If set to true, Oracle Retail Xstore Point of Service will use its current values, for more information, see the If Not Using Xcenter to Get the Config Path section.

Retrieving config path properties from Xcenter will overwrite any of the same-named properties that already were present in the configPath.properties file.

  • For the desktop application, the global config path properties and the workstation overrides property for the specific workstation the system represents are retrieved from Xcenter and written to the configPath.properties file.

  • For the Xstore Mobile server, the global config path properties and the workstation overrides properties for the entire range of mobile device workstations is retrieved from Xcenter and written to the configPath.properties file. The range of mobile device workstation IDs is defined in the system.properties file using the properties xstore.location.mobile.workstationId.range.start and xstore.location.mobile.workstationId.range.end.

At Oracle Retail Xstore Point-of-Service Startup

When Oracle Retail Xstore Point of Service starts, it sends a request to the URL that contains parameters indicating the organization ID, store number, and workstation ID of the machine that is sending the request. (See Config Path Retrieval Process.)

In Xcenter, the config path lookup end-point looks up the store personality based on those parameters and assembles the config path properties from the assigned personality and landscape. The response from Xcenter contains a serialized Java Properties object that contains the appropriate values.

Note:

If no personality and landscape are assigned to the store, then the specific properties will not be present. Note that in this case, blank values will be used for the xstore.config.path.base.features and xstore.config.path.overrides.workstation.# properties.

Once the property values from Xcenter are obtained, they are compared to the existing values from the configPath.properties files. If either of the property values from Xcenter are different than the property values from the file, the values from Xcenter will be written to the configPath.properties file, the last.updated.date property will be set to the current date and time, and Oracle Retail Xstore Point of Service will shut itself down and be restarted by the wrapper.

Till/Register Data

Also during the startup process, till/register data from Xcenter is synchronized with Oracle Retail Xstore Point-of-Service's lead register. Any till/register data that was updated on the store primary is also updated on other workstation databases when the nightly backup and restore process occurs (in an off-line scenario). With this process, it is no longer necessary to manually run till/register setup scripts before starting up the lead register.

Processing Overview

  1. Oracle Retail Xstore Point of Service starts up on the lead register or store primary.

  2. During the startup process Oracle Retail Xstore Point of Service compares the till/ register data from Xcenter and synchronizes the data on the store primary.

    The following data objects are synchronized:

    • Store record

    • Tax location mapping record

    • Corresponding org hierarchy records

    • Workstation records

    • Tender repository records (till and register records)

    • Inventory buckets

    • Inventory location buckets