1. OXI Installation and Configuration Guide
  2. Manual Configuration

1 Manual Configuration

Introduction

This document is intended to help Oracle Hospitality OPERA Exchange Interface (OXI) installers with manual configuration of the Nor1 OXI interface in cases where script installation is not possible. Additionally, it can serve as a guide to confirm configuration success when using the Nor1 OXI install script.

Prerequisites

The following prerequisites are required for the installation of the Nor1 OXI:

  • The Nor1 OXI license code (OPX_NOR1).

  • OXI schema user login credentials.

  • Nor1 requires the public-facing IP address of the OXI server:

    • Open a web browser and navigate to whatismyip.com.

    • In the upper left-hand corner of the browser window, provide the value for “My Public IPv4: XXX.XXX.XXX.XXX.”

  • Windows Administrator login credentials to the OPERA Application Server or OXI server where the Nor1 interface will be installed.

  • Web access to the property if the OXI machine is firewall controlled and traffic is open and ready for Nor1.

  • Confirmed web access for NOR1 by pointing to the following URLs in Internet Explorer on the OPERA Application Server or where the OXI services will be installed:

    • https://integration.nor1solutions.com/opera/get&propertyName=ABCDEF

    • https://oxi.integration.nor1.com/opera/get&propertyName=ABCDEF

      Note:

      Replace ABCDEF with the actual property code. The property code is not necessarily the default OPERA Resort Code. Nor1 has a specialized naming structure for the property code. Contact Nor1 and provide the default OPERA Resort Code, and Nor1 will provide the unique Nor1 property code.

  • If the script cannot run, reference the project email containing the installation script for the External System Property Code and the User Defined Fields (UDF) conversion information.

Manual Installation Steps

The following are the manual installation steps:

  1. Run the OXI Processor Shell located at D:\MICROS\opera\Tools\OXI\INTERFACE (make sure to select the Run Interface Initialization script).

  2. Verify that the OXI Interface for Nor1 services is installed and set to Automatic startup type (starting the services is one of the last steps).

  3. Log into OXI and insert and activate the OPX_NOR1 license code.

  4. Select No when prompted by the Activate External System Nor1 now? message. If you are executing the configuration from the Nor1 OXI Install script, select Yes as the script will be 100 percent successful due to the active Nor1 external system being required for the script to configure the Business Events and Publisher/Subscriber. For manual configuration of Nor1 OXI, you would select No to avoid unnecessary business event (BE) message generation.

  5. Manually configure all of the following indicated areas:

    1. Activate the external system.

    2. Start the Nor1 OXI service.

    3. Confirm that the outbound message flow is successful; the reservation Ready to Proceed message from External to Nor1 status should appear. No message is sent to OPERA until Nor1 activates the integration once the interface is confirmed installed.

Installation Confirmation

To confirm the installation, send a zip file to nor1-integrations_grp@oracle.com with the following items:

  1. The Message Status screen captures the “Message to External Systems” with message traffic filter search criteria only with OPERA Property = Property and Interface ID = Nor1.

  2. Send the NOR1 OXI log. A copy of the log can be found at C:\Program Files\Micros-Fidelio\OXChange\OXA\Logs. Log Naming Convention: NOR1YYYYMMDD.log.xml.

  3. A screen capture of the configured ATS (Automatic Transmission Schedule).

  4. A screen capture of the external systems and the Nor1 subscription to all external systems.

  5. A screen capture of the Nor1 OXI processors with the processors running.

  6. A screen capture of any conversion codes entered into OXI (conversion codes will be determined on a property by property basis as needed).

  7. A screen capture of the OXI XML version for Reservations.

  8. A screen capture of the OXI registry setting to use UTF8 for NLS_LANG.

Upon receipt of the above items, Nor1 will confirm by email whether all settings are correct.