Xcenter Config Path Properties Assembly
This section describes the assembly of the config path properties.
Global Configuration Path Properties
Global config path elements are configurations that are loaded once for the entire application and do not differ from workstation to workstation. They define the standard features and functionality for instances of the application.
The global config path is made up by the elements of the GlobalConfigPathElement enumeration. This enumeration contains both, the individual global config element definitions as well as the ability to build the currently applicable global config path.
The enum instances BASE_FEATURES and GLOBAL_CONFIG_PATH_EXTENSIONS point to properties in the configPath.properties file. The instances substitute their values with the properties xstore.config.path.base.features and xstore.config.path.global.extensions when building the global config path.
For more information about the properties xstore.config.path.base.features and xstore.config.path.global.extensions, see the xstore.config.path.global.extensions section and the xstore.config.path.base.features section below.
For more information about all available base global config path elements, see the Oracle Retail Xstore Point of Service Technical Guide.
xstore.config.path.global.extensions
Config path global extensions indicate non-standard config directories that are applied globally and are included in the config path between static retailer global overrides (version1) and Xstore Office-controlled global overrides (MASTER/DEFAULT). The config path global extensions are controlled by the xstore.config.path.global.extensions property in the configPath.properties file. Since the global extensions property is more of a hidden feature, the property is not maintainable through Xstore Office and must be set manually on any workstation that uses it.
xstore.config.path.base.features
Base features represent config path elements that are used to enable a certain functionality or feature within the application such as loyalty, a payment processor or integration with external applications such as Customer Engagement, Order Broker, and others.
The base features can be enabled and disabled through the Personality Maintenance feature in Xstore Office. For more information on Personality Maintenance, see the Personality Maintenance section.
The table below lists all Xstore Point of Service base features
that can be enabled and disabled as well as their corresponding config
path entries. The enabled base features are represented in the xstore.config.path.base.features property in the configPath.properties file.
Table B-1 Base Features and Config Path Entries
| Feature | Sub-Feature | Config Path Entries |
|---|---|---|
|
Loyalty |
NA |
:cust/loyalty |
|
Loyalty Awards |
:cust/loyalty/award |
|
|
Customer Engagement |
NA |
:relate |
|
Gift Registry |
:cust/registry |
|
|
Use IDCS (Identity Cloud Service) for Authorization |
:idcs/relate |
|
|
Order Broker (Cloud) |
NA |
:order:locate |
|
Use IDCS (Identity Cloud Service) for Authorization |
:idcs/locate |
|
|
Order Management System |
NA |
:crosschannelreturn:serenade |
|
Use IDCS (Identity Cloud Service) for Authorization |
:idcs/serenade |
|
|
: |
||
|
Enterprise Inventory Cloud Service(EICS) |
:sim:sim/$FORM_FACTOR$ |
|
|
Use IDCS (Identity Cloud Service) for Authorization |
:idcs/sim |
|
|
Retail Extension Module (RXM) |
NA |
:rxm:rxm/$FORM_FACTOR$ |
|
Experian Address Verification |
NA |
:avs |
|
Experian AddressVerification (Manual) (For SOAP version) |
:qas/addressmanual |
|
|
Experian Phone Number Verification |
:qas/phone |
|
|
Experian Email Address Verification |
:qas/email |
|
|
Experian Address Verification (Auto) (For REST version) |
:qas/addressauto |
|
|
Xcommerce |
NA |
:xcommerce |
|
Opera Guest Services |
NA |
:opera |
|
Microsoft SQL Server Support |
NA |
:dtv/sql/mssql |
|
EFTLink Authorizations |
NA |
:authprocessor/eftlink |
|
EFT Link Gift Cards |
:authprocessor/eftlink/giftcard |
|
|
24 x 7 (No Store Closing) Functionality |
NA |
:24x7 |
|
Item Selection Grid (cannot be used with Self Checkout) |
NA |
:buttonmatrix |
|
Financial Daily Report |
NA |
:dailyreport |
|
Invoice |
NA |
:invoice |
|
Global Blue Tax Free (cannot be combined with Planet Tax Free) |
:invoice/globalblue |
|
|
Panet Tax Free (cannot be combined with Global Blue Tax Free) |
:invoice/fintrax |
|
|
Luxury receipts |
NA |
:luxuryreceipt |
|
Taxed vouchers |
NA |
:vouchers |
Workstation Overrides Config Path Properties
The elements for workstation-level configuration overrides are controlled by another property, or a set of properties for mobile servers in the configPath.properties file. Since one of these properties indicates all of the override elements for a particular workstation, each override path property name contains the workstation ID to which it applies. The primary purpose of workstation overrides is to support profile group/element pairs that are defined in Xstore Office as part of the profile maintenance. Profile groups and elements are defined and associated with personalities, landscapes, and store personalities in Xstore Office and then each register (or mobile server) in a store downloads its own workstation override config path properties from Xcenter just prior to startup.
xstore.config.path.workstation.overrides.X
The properties containing the workstation overrides config path are xstore.config.path.workstation.overrides.X where X is the workstation ID to which the property applies.
The following configuration files support workstation-level overrides. All other configurations will load files only from global config path elements.
-
SysConfig.xml
-
ActionConfig.xml
-
OpChainConfig.xml
-
MenuConfig.xml
-
PromptConfig.xml
-
DataFieldConfig.xml
-
forms" directory-based configurations
-
FieldLayoutConfig.xml
-
FieldDefinitionConfig.xml
-
FontConfig.xml
-
ListViewConfig.xml
-
ContextConfig.xml
-
"componentPropertySet" directory-based configurations
-
translations.properties
xstore.config.path.overrides.store.Y
The config path property, xstore.config.path.overrides.store.Y, where Y is the store number, is created. This property contains the profile group and element pairs that make up the personality for a particular store. The files that are located in any of the config path entries defined in this property will be loaded at the global (application) level.
Oracle Retail Xstore Point-of-Service Config Path Assembly
The default file Xstore Point of Service uses for its config path properties is called configPath.properties. The file is located in the root directory on an installed register. As mentioned in the section above, the following three properties form the config path for a given register:
-
xstore.config.path.base.feature -
xstore.config.path.global.extensions -
xstore.config.path.overrides.workstation.[workstation ID]