1. Using the Oracle Hospitality Adapter with Oracle Integration 3
  2. Troubleshoot the Oracle Hospitality Adapter
  3. Miscellaneous Oracle Hospitality Adapter Errors
  4. Use the REST Adapter as an Alternative Connection

Use the REST Adapter as an Alternative Connection

The main role of the Oracle Hospitality Adapter is to facilitate the integration with the OPERA Cloud/OHIP product. In some extreme situations, you may want to temporarily use the REST Adapter (for example, to troubleshoot connection problems). This section describes the equivalent connection configuration for the SSD and OCIM identity provider authentication topologies of the REST Adapter.

Topics:

OCIM Identity Provider

Configure the REST Adapter connection as follows.


The Properties section shows the Connection Type and Connection URL fields. Below this, the Optional properties subsection is expanded to show the TLS Version, Enable two way SSL for outbound connections (Optional) and Identity keystore alias name (Optional) fields. Below this is the Security section, which shows fields for Security policy and Access Token Request.

Where:
Element Description
Connection Type

Select REST API Base URL.

Connection URL
Enter your OHIP gateway found on the ENV in the OHIP Developer Portal. For example: 
https://mygateway.hospitality-api.us-phoenix-1.ocs.oc-test.com
TLS Version

Select TLSv1.2.

Security policy

Select OAuth Custom Two Legged Flow.

Access Token Request
Enter the following:
-X POST -H "Content-Type: application/x-www-form-urlencoded" -H "x-app-key: <app_key>" 
-H "enterpriseId: <enterprise_id>" -H "Authorization: Basic <base64_clientid:clientesecret>" 
-d "scope=<scope>&grant_type=client_credentials" "<ohip_gateway>/oauth/v1/tokens"
Where:
  • <app_key> is your app key found on the APP in the OHIP Developer Portal (for example, b744843d-5231-2095-8ae9-cea0f1aca20f).
  • <enterprise_id> is your enterprise ID found on the ENV in the OHIP Developer Portal.
  • <base64_clientid:clientesecret> is the base 64 encoding of your client ID and client secret, found on the ENV in the OHIP Developer Portal, separated by a colon symbol (for example, Y2xpZW50aWQ6Y2xpZW50ZXNlY3JldA==).
  • <scope> is your scope found on the ENV in the OHIP Developer Portal. Don't forget to URL-encode it (for example, urn%3Aopc%3Aabcd%3Aws%3A__myscopes__).
  • <ohip_gateway> is again your OHIP gateway found on the ENV in the OHIP Developer Portal. This is the same as the connection URL.

SSD Identity Provider

Configure the REST Adapter connection as follows.


The Properties section shows the Connection Type and Connection URL fields. Below this, the Optional properties subsection is expanded to show the TLS Version, Enable two way SSL for outbound connections (Optional) and Identity keystore alias name (Optional) fields. Below this is the Security section, which shows fields for Security policy and Access Token Request.

Where:
Element Description
Connection Type

Select REST API Base URL.

Connection URL
Enter your OHIP gateway found on the ENV in the OHIP Developer Portal. For example:
https://mygateway.hospitality-api.us-phoenix-1.ocs.oc-test.com
TLS Version

Select TLSv1.2.

Security policy

Select OAuth Custom Two Legged Flow.

Access Token Request
Enter the following:
-X POST -H "Content-Type: application/x-www-form-urlencoded" 
-H "x-app-key: <app_key>" -H "Authorization: Basic <base64_clientid:clientesecret>" 
-d "username=<username>&password=<password>&grant_type=password" "<ohip_gateway>/oauth/v1/tokens"
Where:
  • <app_key> is your app key found on the APP in the OHIP Developer Portal (for example, b744843d-5231-2095-8ae9-cea0f1aca20f).
  • <base64_clientid:clientesecret> is the base 64 encoding of your client ID and client secret, found on the ENV in the OHIP Developer Portal, separated by a colon symbol (for example, Y2xpZW50aWQ6Y2xpZW50ZXNlY3JldA==).
  • <username> is your Oracle Integration user name created in OPERA Cloud.
  • <password> is your Oracle Integration password created in OPERA Cloud.
  • <ohip_gateway> is again your OHIP gateway found on the ENV in the OHIP Developer Portal. This is the same as the connection URL.