33 Activating OPERA Cloud Hub Integration
OPERA Cloud Hub integration enables
asynchronous OXI (XML) communication between OPERA Cloud Central Services
and (remote) OPERA Cloud Foundation or OPERA Property properties.
![OPERA Cloud Hub integration OPERA Cloud Hub integration](img/opera_cloud_hub_integration.png)
The following data exchange is supported:
Table 33-1 Supported data exchange entities
Entity | Details | Events | Notes |
---|---|---|---|
Profiles |
Identification Membership Negotiated Rates Notes Preferences Relationships |
New Update Merge |
|
Reservations |
Accompanying Alerts Deposit Rules Item Inventory Membership Notes Preferences Routing Sharers Specials Traces |
New Update Cancel Reinstate Check in Check out |
Routing Codes only for Routing (not transaction codes) |
Stay Records |
|
|
|
Blocks |
Room Allotment Notes |
Includes Opportunities when the Opportunities OPERA Control is active. |
|
Catering Events |
New Update |
||
Sales Activities |
New Update |
||
Rate Restrictions |
New Update |
||
Inventory |
|||
Housekeeping |
Out of Order Out of Service |
New Update |
|
Configuration |
Rate Class Rate Category Rate Codes Packages Item Class Item Inventory Function Space
|
|
|
Cloud Hub Activation
Active the Cloud Hub Integration for all Properties function
for a hub location to activate integration for all properties, with OXI-OPERA
as the system default interface, otherwise active
the Cloud Hub Integration function
for a property location to activate integration for a specific property,
with OXI-OPERA
as the system default interface.
Note:
If you plan to activate or inactive Cloud Hub integration for specific properties, always use the property-level Cloud Hub Integration OPERA Control.Cloud Hub Automatic Configuration
The Cloud Hub activation process automates the following configuration:
Interface Setup
An OXI-OPERA
interface is created in the OPERA Cloud Exchange
Module. For more information, see Interface
Setup
External Database Configuration
An external system, Outbound System and external database are configured according to the Cloud Hub Integration OPERA Control context (hub or property).
Business Event Configuration
Business Events are auto-configured
for OXI-OPERA
.
Exchange Interface Controls
Interface Controls for OXI-OPERA
are configured.
Cloud Hub Manual Configuration
The following configuration steps must be completed:
Exchange Interface MappingsInterface Mappings for OXI-OPERA are configured with the system default mappings, you can add more data conversions.
Interface Defaults
Interface default values for Inbound and Outbound messages are optional. To configure defaults for incoming and outgoing messages, see Interface Controls.
Interface Rules
Interface rules determine whether particular UDF data should be updated during data transmission to / from OPERA Cloud. For more information, see Configuring Interface Rules.
Interface Mapping
Interface Mapping defines conversion of OPERA Cloud codes and external system codes at Global (Chain) or Property level for central interfaces. When conversions are defined, the code from an external system is replaced with the OPERA Cloud code for inbound message from the external system; and the OPERA Cloud code is replaced with the code of the external system for outbound message delivered to the external system. For more information, see Configuring Interface Mapping.
OPERA Property OXI Communication Methods
Cloud Hub always acts as Server. The Cloud Hub Event Manager URL must be obtained from Oracle services team during provisioning and configure OXI communication mode as client with the Event Manager URL, along with the chain-level integration user created in Manage Interface User, with Interface Type =DISTRIBUTION and then activated.
For more information, see Communication Method Setup OXI.
-
Select External System to OPERA.
-
Comm Type: Select HTTP/S.
-
Select Client.
-
URL: Enter OPERA Cloud URL (example: https://<cloudhub-evnt-mgr-host>/Operajserv/OXIHUBServlets/ORSInterface).
-
Username: Enter the integration username.
-
Password: Enter the password.
-
Click Save.
-
-
-
Select OPERA to External System.
-
Comm Type: Select HTTP/S.
-
Select Client.
-
URL: Enter OPERA Cloud URL (example: https://<cloudhub-evnt-mgr-host>/Operajserv/OXIHUBServlets/ORSInterface).
-
Username: Enter the integration username
-
Password: Enter the password.
-
Click Save.
-
-
Interface Resync
After activation, data synchronization between OPERA Cloud Central Service and OPERA Property or OPERA Cloud Foundation may be required. Identify the primary / source solution and initiate a resynchronization of data to the target system (example: from OPERA Property to OPERA Cloud Central).
-
For OPERA Property, see Resynchronization of Data OXI.
-
For OPERA Cloud, see Interface Resync.
Message Status Monitoring
OPERA Cloud Central
messages are monitored using Oracle Hospitality Distribution Channels messages for OXIHUB
channel. Grant the Central
Messages Monitoring task to OPERA Cloud roles. In Oracle
Hospitality Distribution Channels, the <property>- CHANNELMANAGEMENT View Interface messages task is required to view individual messages and the <chain/cluster- CLUSTERMGMT View Message Summary in Cluster task is required to view the total number of messages per channel.
OPERA Cloud Foundation is monitored and managed through OXI Message Status.
Related Topics
Parent topic: Exchange