This guide is designed to help you get started with connecting your hotel to OHIP. Here, you’ll find details of the onboarding process, including the steps you'll need to take and guidance on key values required for mapping.
For information on the integration functionality between ResDiary and OPERA, please refer to the Integration Overview
Important: Hotels must have an active OPERA Cloud Foundations license in order to integrate with OHIP. Without this license, connectivity cannot be established.
Hoteliers should be prepared to provide the following to ResDiary. This information is required for the connectivity to take place.
| Tenant/Chain Code | The hotel tenant code |
| Hotel ID | The OPERA ID of the hotel |
| SSD URL | This is the URL for your Opera Login Page (Only needed if not using OCIM) |
| Enterprise ID | Only needed if using OCIM |
| Region | The region in which the hotel’s Opera Cloud Environment is running |
| Activity Location | Refers to the specific location within your property where ResDiary restaurant reservations will be assigned in OPERA. (Oracle guide: Configuring Scheduling Activities Location) |
| Example Opera Profile ID | ID of a profile in Opera that can be used for testing |
Here’s an overview of the process your team will go through to set up the integration between OPERA and ResDiary.
1. Request integration
Contact ResDiary Support to request that the OPERA OHIP integration be added to your account.
2. Confirm Licensing
To begin, your property must have the Oracle Cloud Foundations license in place. This license enables access to OHIP and is required for the integration to proceed.
3. Share Required Details with ResDiary (See above for details)
Tenant/Chain Code
Hotel ID
SSD URL or Enterprise ID
Region
Activity Location
Example Opera Profile ID
4. Add ResDiary as an External System
In OPERA, your team will need to add ResDiary as an external system:
Use the code:
RESDIARYOHIPOracle guide:Configuring External Systems
5. Approve the Connection Request
Once the connection is initiated, your administrator will receive a request to approve it. The process differs slightly based on the authentication method your OPERA environment uses:
a. Resource Owner Group (SSD) Authentication
Your chain administrator will get an email from SSD with the connection request.
The approval must be completed in the SSD Portal.
Please ensure the WSACCESS role is assigned to the user
b. Client Credentials (OCIM) Authentication
All chain administrators will receive a notification email.
The approval will take place within the OHIP (Customer) Developer Portal.
6. ResDiary Activates and Tests the Integration
Once the setup is complete on your side, ResDiary will enable the integration and run a few basic tests to ensure everything is working properly:
Get Profile: We’ll test retrieving guest profile data from OPERA.
Create Booking: We’ll create a booking in OPERA using a retrieved profile.
Cancel Booking: We’ll confirm a booking can be successfully cancelled.
After these steps, the integration will be live and ready to use.