Components And Dataflow of the OPERA Xchange Interface
For all interfaces that are considered OXI GENERIC interfaces, the external systems have several options for the communication.
The Interface Configuration
- This can be accessed through the user front-end of OXI. Simply log in to OPERA and select the OXI button. This is permission based access.
- Configuration of interfaces with their External System Name, Data Flow and XML Schema versions.
- Setup Interface Defaults
- Setup Conversion Tables
- Setup Interface Parameters
- Setup Profile Matching
- Setup Communication Methods
- Setup License Codes (for one or more OXI interfaces)
- Setup Automatic Transmission Schedule
- Setup UDF Configuration
The Start and Stop Screen
This screen is used to:
- Start and stop the OXI processors
- View OXI the processors status
- View OXI the processors last update time stamp
The Message Status Screen
- This screen is used to view the dataflow, message details, and to search message contents.
- View XML messages in detail
- View warnings and errors for messages in detail
- Reprocess messages from and to OPERA
- Extract the OPERA or External messages to a local directory for OPERA Support purposes
OXI Components for Dataflow External System to OPERA
The OXI Download Processor
Reads the external system download queue and creates an entry in the temporary XML table
- Performs data validation
- Performs conversion for all activated conversion tables
- Applies download defaults for unsuccessful conversion
- Writes a record into the OPERA API structure and from there the API populates the OPERA tables with the record
OPERA Components for Dataflow External System to OPERA
Business Event Configuration
- All OXI 2-way licenses automatically activate the external system and its business events. It is not necessary to have a separate business events license code.
- In order to run the 2-way interface, the external system has to be activated and configured
- The business events needed for upload have to be configured for the specific external system to create messages
Business Event Processor
- Every time a transaction happens through user input or automatically, a business event is created in OPERA.
- The business event processor transports the data from the business event Enqueue into the Outqueue.
OXI Components for Dataflow OPERA to External System
OXI Processor
- Reads the OPERA Outqueue and creates an entry in the temporary XML table from the business event.
- Performs data validation
- Performs conversion for all activated conversion tables
- Applies upload defaults for unsuccessful conversion
