5 Integrations
This chapter describes possible integrations with Xstore Office Cloud Service.
Several integrations are possible, especially those sending data from Xstore Office using the broadcaster framework. For more information about broadcasters, see the information on Xstore Office Broadcaster System in the Oracle Retail Xstore Suite Implementation and Security Guide.
For cloud, broadcasters can be configured from the Xadmin UI. For more information on how to configure broadcasters, see the Broadcaster Management section in the Oracle Retail Xstore Office Cloud Service User Guide.
For information on Integrations configurations, see Integration Management section in the Oracle Retail Xstore Office Cloud Service User Guide.
For more information about how to configure web service authentication for Retail Omnichannel products, see the Omnichannel Web Service Authentication Configuration Guide (My Oracle Support Doc ID: 2728265.1)
Oracle Retail Customer Engagement (ORCE)
Xstore Office sends information to Oracle Retail Customer Engagement (ORCE formerly Relate) via Broadcaster integration. It uses either ORCE custom authorization or OAuth2. The XOCS client will have to be granted the correct AppRole(s) defined in ORCE.
Xstore Office also uses SFTP to pull files from ORCE. The status is updated to POLL_FILE_STATUS and files extracted into the auto file-transfer directory.
Oracle Retail XBRi Loss Prevention (XBRi)
Xstore Office sends information to Oracle Retail XBRi Loss Prevention (XBRi) via Broadcaster integration. It uses either XBRi custom authorization or OAuth2. The XBRi broadcaster will be configured via the Broadcaster UI.
Oracle Retail Order Broker (OROB)
Xstore Office sends product (ITM_ITEM) and inventory (INV_STOCK_LEDGER_ACCT) data to Oracle Retail Order Broker (OROB) via OROB's REST file service and uses either OAuth 2 or Basic Auth for authentication depending on where the OROB Service is hosted.
Alternatively, Xstore Office can be configured to use SFTP to send to OROB using an SSH public/private key mechanism.
Oracle Retail Order Management (OROMS)
Since 18.0, direct integration to Oracle Retail Order Management System (OROMS) has been removed from Xstore Office. Instead, direct integration to OROMS happens from Xstore directly.
Oracle Retail Merchandising Suite
For more information about the integrations to Oracle Retail Merchandising Suite, refer to the Oracle Retail Xstore Suite/Merchandising Suite Implementation Guide.
For more information about the Omnichannel Cloud Data Service, see the next section.
Omnichannel Cloud Data Service (OCDS)
The Omnichannel Cloud Data Service is a repository for the merchandising and pricing data used by Xstore Office Cloud Service.
OCDS receives merchandising and pricing data from the Oracle Retail Merchandising Suite. Data flows from Merchandising to OCDS through Oracle Bulk Data Integration (BDI) and Oracle Retail Integration Bus (RIB) infrastructure technologies.
Merchandising and pricing data in OCDS used by Xstore and Xstore Office Cloud Service includes:
-
Merchandise Hierarchy
-
Organizational Hierarchy
-
Stores
-
Item Dimensions
-
Items
-
Related Items
-
Value Added Tax (VAT) rules and item associations
-
Initial Prices
-
Regular and Clearance Price Changes
-
Promotions
Omnichannel applications request data from OCDS by calling RESTful Web Services. Applications can request all data for a data type or only new, deleted, or changed data in OCDS since a point in time. Xstore Office Cloud Service typically call OCDS at regular intervals. For example, a typical request to OCDS from an Xstore Office Cloud Service could be, “What merchandise hierarchy data has changed since yesterday at midnight?”.
Merchandising Foundation Cloud Service (MFCS)
The Merchandising Foundation Cloud Service expose similar REST web services as are exposed by OCDS enabling Xstore Office to communicate directly with MFCS without the need of OCDS.
See Oracle Retail Xstore Suite /Oracle Retail Merchandising Suite Implementation Guide for details.
Oracle Retail Sales Audit (REST Service)
XOCS transactions are broadcasted to Sales Audit (ReSA) directly though the REST API exposed by Sales Audit (ReSA). The transactions are posted to Sales Audit (ReSA) as JSON payloads. No RTLog generator is required as the middleman.
See the Oracle Retail Xstore Suite/Oracle Retail Merchandising Suite Implementation Guide for details.
Oracle Retail Sales Audit (RTLog File)
XOCS transactions are broadcasted to the RTLog generator to convert to flat files in RTLog format for Sales Audit (ReSA) to consume.
RTLog files are either delivered to Sales Audit (ReSA) automatically through FTS or SFTP, or customers can choose to download RTLog files and upload them to Sales Audit (ReSA) themselves.
See the Configuring RTLog Generator section for more details on different delivery options.
See the Oracle Retail Xstore Suite /Oracle Retail Merchandising Suite Implementation Guide for details.