Setting up your Opera plugin
Before Sertifi can begin setting up your Opera plugin, you must contact your Oracle/Opera representative and gather the following information. Enter this information into the setup form:
You can't set up your plugin without this information. This information can only be provided to you via Oracle/Opera.
- Destination Type ID - the identification number or code for your destination type. This is typically PMS.
- Origin Entity ID - the identification number or code for your origin entity. This is typically KIOSK.
- Department Code - the code that determines the trace in Opera. This code routes notifications. As a best practice, create a code like AUTH or SERTIFI to let the front desk know there's a 3rd party authorization on the reservation.
- Specials Code - the code you use for a Specials request. As a best practice, create a code like AUTH or SERTIFI, similar to your Department Code. Cloud instances tend to use SERTI due to character limits.
- Folio Window Number - the number of the window where you want 3rd party payment information to appear in the Payments screen in Opera. You can make this static or dynamic.
- Static - specify a folio window; for example, 2. If payment information is already present in folio window 2 it gets overwritten.
- Dynamic - specify 0 for the folio window to add the payment information in the first available folio window. If all 8 windows are taken, you receive an error.
- Folio Window Number Options - (optional) indicates which folio windows you can search. Sertifi recommends using windows 2-8, since the first window is typically reserved for the guests' payment method.
- Web Service URL - provide the web service URL for your Opera account. This should be an external, accessible site. In most cases, the URL will be https://opera.sertifi.net:444.
- Card types - the card types you accept and the specific abbreviations you use for each credit card. You should provide all the codes for all the payment types you accept. For example, VS for Visa or AMEX for American Express.
- Reservation and Reservation Advanced - verify with Opera/Oracle that your Reservation and Reservation Advanced codes are "/ows_ws_51/Reservation.asmx" and "/ows_ws_51/Information.asmx" respectively.
Once you gather this information, download and fill out this form and send the form to your Customer Success Manager for them to enable the integration in your portal. When you contact your Customer Success Manager, you should provide them with the above information from Oracle/Opera and the following property-specific information:
- Global Setting Name – your corporate Opera settings.
- Destination Entity ID - the identification number or code for your destination entity. This is usually the hotel code.
- Hotel Code – your hotel code from the Opera system.
- Hotel Chain Code – your hotel chain code in the Opera system. In most cases, this will be the Opera default, which is CHA.
- Username – the username for your Opera system. The Opera default is KIOSK.
- Password – the password for your Opera system.
- Domain – the domain name of your Opera system. This is usually the same as your Destination Entity ID.
- Endpoint URL – the URL where the OWS interface is hosted, in the format of https://{DomainOfOwsAPI}.
- Gateway Token – yes or no as to whether you want to send a gateway token in place of a credit card number if you’re using Merchant Link or Shift 4. If you provide No for this field, you must have TokenEx enabled.
- Cloud Instance – yes or no as to whether your Opera system is running in the cloud or not. This value should usually be set to No.
Next Steps
Once you provide this information to your Customer Success Manager, they can complete the set up of the Sertifi plugin for Opera. To complete the process, create a test reservation in Opera. Provide this test reservation information to your Customer Success Manager including:
- Confirmation number
- Guest Last Name
- Arrival Date
Your Customer Success Manager can then test the communication between Opera and Sertifi and ensure that your plugin is working properly.
Once this is complete, and your CSM confirms successful communication, you can create your Opera documents. For more information, see Formatting Opera documents.