This document is intended to provide OXI installer 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 

Please confirm the following prerequisites for the installation of the NOR1 OXI: 

● Confirm you have the NOR1 OXI license code (OPX_NOR1). 

● Confirm you have the OXI schema user login credentials. 

● Confirm you have the Windows Administrator login credentials to the Opera Application Server or OXI server where the NOR1 interface will be installed. 

● Confirm web access with property if OXI machine is firewall controlled and traffic is open and ready for Nor1. 

● Confirm web access for Nor1 by pointing to the below URLs in Internet Explorer on the Opera Application Server or where the OXI services will be installed, and you should see a blank page. 

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

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

o **replace ABCDEF with property code** 

● In the event that the script cannot be run, please reference the project email containing the installation script for the External System Property code and the UDF conversion information.

Manual Installation Steps 

The following are the manual installation steps: 

● Run the OXI Processor Shell located at D:\MICROS\opera\Tools\OXI\INTERFACE (Ensure the 'Run the interface initialization scripts is selected) 

● Verify the OXI Interface for NOR1 services is installed and set to Automatic startup type (starting the services will be one of the last step). 

● Log into OXI, insert and activate the OPX_NOR1 license code. 

● Select NO when prompted to "Activate External System NOR1 now?" (if the configuration is being executed via the Nor1 OXI Install script - you would select YES as the script will only be 100% successful due to active Nor1 external system being required in order for the script to configure the Business Events and Publisher/ Subscriber - For manual configuration of Nor1 OXI - you will indicate NO to avoid unnecessary BE message generation) 

● Manually configure all indicated areas below 

● Activate External System 

● Start the Nor1 OXI service 

● Confirm 'outbound' message flow is successful - ie; Reservation message from External to Nor1 status READY to PROCESSED. No message will be sent to Opera until Nor1 activates the integration once interface is confirmed installed.

Installation Confirmation

Please send a zip file to nor-integrations_grp@oracle.com with the following information:

● Message Status screen capture of "Message to External System" with message traffic Filter search criteria only with Opera Property = Property and interface ID = NOR1.

● Send the NOR1 OXI log; a copy of the log can be found at C:\Program Files\Micros-fidelio\OXChange\OXA\Logs.

Log Naming Conversion: NOR1YYYYMMDD.log.xml

● A screenshot of the configured ATS (Automatic Transmission Schedule)

● A screenshot of the external system and the NOR1 subscription to all external systems.

● A screenshot of the NOR1 OXI processors with the processors with the processors "Running".

● A screenshot of the any conversion codes entered into OXI (conversion codes will be determined on a property by the property basis as needed).

● A screenshot of the OXI XML version for RESERVATIONS.

● A screenshot of the OXI registry setting to use UTF8 for NLS_LANG.

Upon receipt of the above items NOR1 will confirm via email if all setting are correct.

PMS Configuration

Nor1 Department Code

Confirm Department *NOR1 exists in the PMS, if not add the department via Setup > User Configuration > Department. 

Alerts Configuration 

Confirm the application setting for alerts is active. 

Setup > Application Settings > Reservation > Alerts.

Configuring Alerts 

Reservations > Codes > Alert Definition > Alert Message

Configuring Business Events 

Configure the business events via Setup > Business Events > Configuration. 

Set the EXTERNAL SYSTEM to NOR1 

Add the business events for the following Modules: 

AVAILABILITY - Add business event: 

SUMMARY TOTALS - add ALL data elements. 

HOUSEKEEPING - Add business events: 

NEW OUT OF ORDER - add ALL data elements. 

ROOM TYPE OUT OF ORDER - add ALL data elements. 

UPDATE OUT OF ORDER - add ALL data elements. 

NIGHT AUDIT - Add business event: 

ROLL BUSINESS DATE - add ALL data elements. 

PROFILE - Add business event: 

UPDATE PROFILE 

Please add the following data elements: 

ADDRESS PRIMARY YN, ADDRESS TYPE, ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, BUSINESS TITLE, CITY, COMMENTS, COMPANY NUMBER, COMPANY TYPE, COUNTRY, EMAIL, EMAIL LANGUAGE, EMAIL YN, FAX NUMBER, FIRST NAME, GENDER, GUEST PRIVACY YN, IATA NUMBER, IATA TYPE, LANGUAGE, MAILING LIST YN, MARKET RESEARCH YN, MEMBERSHIP EXPIRATION DATE, MEMBERSHIP LEVEL, MEMBERSHIP NUMBER, MEMBERSHIP TYPE, MIDDLE, NAME, NAME TYPE, NATIONALITY, PHONE NUMBER, PHONE PRIMARY YN, PHONE TYPE, POSTAL CODES, PREFERENCE GROUP, PREFERENCE TYPE, STATE, STATUS, THIRD PARTY YN, TITLE, VIP STATUS, WEBPAGE

Please add the following condition for UPDATE PROFILE: 

EXISTS (SELECT 'X' FROM DATA_ELEMENT_TEMP WHERE ((NVL(UPPER(NEW_VALUE),'@#$%')) = ('D')) AND (ELEMENT = 'NAME TYPE'))

RESERVATION - Add business events: 

CANCEL - add ALL data elements. 

CHECKIN - add ALL data elements. 

CHECK OUT - add ALL data elements. 

DELETE RESERVATION - add all data elements from ACCOMPANYING GUEST to TRAVEL AGENT NAME ID and UDF CHAR 38, VIDEO CHECKOUT, YIELD MARKET TYPE, YIELD STATUS. 

DELETE TRACE - add ALL data elements. 

JOIN GUEST - add ALL data elements. 

NEW RESERVATION - - add ALL data elements from ACCOMPANYING GUEST to TRAVEL AGENT NAME ID and UDF CHAR 38, VIDEO CHECKOUT, WAITLIST PRIORITY. WAITLIST REASON CODE, WAITLIST REASON DESCRIPTION, WALK IN, YIELD MARKET TYPE, YIELD STATUS. 

NEW TRACE - add ALL data elements. 

NO SHOW - add ALL data elements. 

REACTIVATE NO SHOW - add ALL data elements. 

REACTIVATE WAITLIST - add ALL data elements. 

REVERSE CHECK IN - add ALL data elements. 

REVERSE CHECK OUT - add ALL data elements. 

ROLLBACK CANCEL - add ALL data elements. 

SEPARATE GUEST FROM SHARE - add ALL data elements. 

TURNAWAYS - add ALL data elements. 

UPDATE RESERVATION - add ALL data elements from ACCOMPANYING GUEST to TRAVEL AGENT NAME ID and UDF CHAR 38, VIDEO CHECKOUT, WAITLIST PRIORITY. WAITLIST REASON CODE, WAITLIST REASON DESCRIPTION, YIELD MARKET TYPE, YIELD STATUS. 

UPDATE TRACE - add ALL data elements. 

STAY RECORDS - Add business events: 

INSERT STAY RECORDS - add data element GUEST_NAME_ID 

UPDATE STAY RECORDS - add date element GUEST_NAME_ID 

(If the module STAY RECORDS does not exist at the customers Opera version skip this set up)

External Systems Cross-Subscriptions

Ensure Nor1 is cross-subscribed to other external systems via Setup > Business Events > External Systems (check then uncheck the Show Inactive checkbox), highlight NOR1, click on Publisher. Ensure that NOR1 is subscribed to ALL external systems. 

OXI Configuration 

OXI Interface Setup 

Configure the interface with the following values: Note: the External System Property value example of 8:MOMA, where 8 = VNor1Chain value indicated within the declaration section of the Nor1 install script, and MOMA = the PMS resort code.

OXI XML Versions (Set the XML setting as follows, if not available set to the highest value):

Conversion Codes 

Conversions are not required as Nor1 returns reservation codes as received by Opera PMS. There may be a unique circumstance where a property requires a conversion code. In this instance the conversion codes required will be listed in the project email. 

OXI Interface Parameters

Additionally there are three (3) parameters that will need to be updated via Opera SQL: 

Note: update XXXXXX to Opera PMS resort code 

OXI Profiles: RELATIONSHIPS INCOMING -> NONE 

update oxi.int_parameters set parameter_value='NONE' where parameter_name='RELATIONSHIPS_INCOMING' and resort='XXXXXX' and interface_id='NOR1' 

OXI Profiles: RELATIONSHIPS OUTGOING -> NONE 

update oxi.int_parameters set parameter_value='NONE' where parameter_name='RELATIONSHIPS_OUTGOING' and resort='XXXXXX' and interface_id='NOR1' 

OXI Reservations: ITINERARY FUNCTIONALITY -> Y 

update oxi.int_parameters set parameter_value='Y' where parameter_name='ITINERARY_FUNCTIONALITY' and resort='XXXXXX' and interface_id='NOR1'

OXI Interface Defaults 

Configuration of default only required on tab 5. Others as reservations are returned using the same codes as received from Opera PMS.

Max Availability Type: DAY 

Max Availability in Advance: 180 

Trace Warning: *NOR1 

*NOR1 may need to be created as a DEPARTMENT, via Set Up, User Configuration, Departments, within the PMS.

COMM Methods 

Nor1 supports two separate domains for the comm methods. The reason for this is to maintain backwards compatibility for servers that cannot support TLS 1.2 and up. The domains: 

● https://integration.nor1solutions.com - Legacy domain that supports less secure TLS protocols 

● https://oxi.integration.nor1.com - Strict domain that only supports TLS 1.2 and 1.3 protocols with secure ciphers 

Nor1 recommends using the strict domain for the comm methods. Each domain has two endpoints, one for each comm method. 

The legacy endpoints: 

● External System to Opera: https://integration.nor1solutions.com/opera/get 

● Opera to External System: https://integration.nor1solutions.com/opera/post 

The strict endpoints: 

● External System to Opera: https://oxi.integration.nor1.com/opera/get 

● Opera to External System: https://oxi.integration.nor1.com/opera/post 

See the screenshots below for details regarding configuring the comm methods: 

External System to Opera:

Opera to External System:

ATS - Automatic Transmission Schedule 

NOR1 requires the configuration of 4 different scheduled transmissions, one (1) for blocks; three (3) for inventory.

OXI Alert Configuration 

(Only necessary if customer has Email delivery is active at the customer) 

Access OXI > Interface Status > Interface Alerts Configure 2 alerts as follows:

Below is the configuration for 'Alert If: Interface machine or OXI service is down'.

Below is the configuration for 'Alert if: One or more Interface threads are down':

Below is the configuration for 'Alert if: One or more Interface threads are down':

UDF Column Conversion

The UDF column tracks the offers rendered and requested by the guest. Configure the UDF column conversion via OXI > Interface Configuration > UDF Conversion.

NOTE: Nor1 uses UDFC38 for tracking the offers, This UDF column might already be in use. Please reach out to nor1-integrations_grp@oracle.com

NLS_LANG 

Set the NLS_LANG registry value to prevent string encoding issues that can break Nor1 parsing of the OXI XML. 

Start > Run > REGEDIT > (HKEY_LOCAL_MACHINE\SOFTWARE\Micros-Fidelio\Opera Interface for NOR1 

Edit > New > String Value > 

Value name: = NLS_LANG 

Value data: = AMERICAN_AMERICA.UTF8

Re-start the OXI Services "Opera Interface for NOR1" 

View the OXI log for NOR1 and confirm MESSAGE = Set NLS_LANG to AMERICAN_AMERICA.UTF8