Opera Integration Setup Checklist — Is Your Instance Configured Correctly?

Overview

Before troubleshooting any Opera integration errors in Sertifi, confirm that your Opera instance is set up correctly on your end. Many common issues are caused by missing or incorrect configuration settings in Opera itself, not in Sertifi. Use this checklist to verify your setup.

Step 1: Confirm Integration Credentials Are Active

• Your Opera Web Services (OWS) or Oracle Hospitality Integration Platform (OHIP) credentials must be active and valid.
• Log in to your Opera environment and confirm the integration user account has not expired, been locked, or had its password changed without being updated in Sertifi.
• If credentials have changed, contact Sertifi Support to update them.

Step 2: Verify IP Whitelisting

Sertifi communicates with Opera from specific IP addresses. If your property's firewall or Opera server is not configured to allow traffic from these addresses, the integration will fail with a connection error.

• Ask your IT team to confirm that all required Sertifi IP addresses are whitelisted in your property's firewall.
• Simply having HTTPS enabled and being open to the internet is not enough — the specific Sertifi IPs must be explicitly permitted.
• Contact Sertifi Support if you need a current list of IP addresses to whitelist.

Step 3: Confirm Bidirectional Communication

The integration requires that both systems can talk to each other — not just one direction.

• Sertifi must be able to send data to your Opera server.
• Your Opera server must also be able to communicate back to Sertifi.
• Ask your IT team or Oracle representative to verify both directions are working.

Step 4: Check Your SSL Certificate (OWS Properties)

If your property uses an on-premise Opera OWS server, the SSL certificate on that server must be valid and current.

• An expired SSL certificate will cause the error: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."
• If your certificate has expired, contact your IT team or Oracle representative to renew it.

Step 5: Verify Your Endpoint URL Is Correct

An incorrect endpoint URL in your Opera integration settings will prevent Sertifi from connecting.

• If you are using an on-premise OWS connection, the URL format typically ends in .asmx.
• If you are using Opera Cloud (OHIP/OCIM), the URL format is different — confirm with your Oracle representative.
• You can test your endpoint URL by pasting it directly into a browser. If it returns a privacy/SSL error, the certificate may need renewal.

Step 6: Confirm FetchReservation Setting (OWS Properties)

For on-premise OWS properties, the FetchReservation parameter in your Opera configuration must be set to ALL.

• If this is set to WEB, Opera will only be able to retrieve reservations that were created through OWS, which will cause Sertifi to fail to find reservations created through other channels.
• Ask your Oracle representative or IT team to verify and update this setting if needed.

Still Having Issues?

If you have completed all of the above steps and the integration is still not working correctly, contact Sertifi Support with your property name, the error message you are seeing, and the date and time the issue occurred.