Vašemu vyhledávání neodpovídají žádné výsledky.
Abyste našli to, co hledáte, doporučujeme vyzkoušet následující postup:
The Oracle Hospitality Partner Integration program offers a comprehensive set of tools to complete and validate integrations with Oracle Hospitality products. Both cloud and on-premise integrations are available for ISVs looking to build repeatable integrations to Oracle Hospitality products. Integrating with Oracle Hospitality suite of property management services can help businesses expand their capabilities and connect to an expansive marketplace of integrators and solutions.
Partners with unvalidated custom arrangement between hotel and vendor which is specific to each hotel and self-supported. Oracle Support is limited to Oracle software, not vendor-specific configuration. Customer specific integrations have no documentation maintained by Oracle and are not listed on internal Oracle sales tool or external list of interfaces.
The partner and Oracle have generated a document that is available in My Oracle Support for customers and Oracle Support, and in an internal repository available to Sales. The document is updated by Oracle as part of the documentation engagement, and outlines any necessary interface-specific setup in OPERA, the general purpose and functionality of the interface and the types of data being exchanged between OPERA and the partner system.
Member level options included from a Documented Integration with the following additional opportunities. Partners will have the option to participate in “Validated Interface” program (License & Hardware track). They will also have the option to download software and maintain private lab environment on own premises and an option to purchase OPERA Cloud lab environment at 75% discount. Validated Integrations also include additional track-specific benefits beyond the hospitality Industry.
To help our partners we have published our APIs on docs.oracle.com. The OPERA APIs are for OPERA 5 premise, OPERA 5 Hosted and OPERA Cloud. We recommend that before going forward with the process you would review the various APIs to get a better idea of what kind of integrations are available
OPERA API Glossary - OWS / KIOSK
OPERA Web Self-Service is designed to support data transfers between clients web booking engine and the OPERA Room Reservation or OPERA Property OWS is a collection of Web Services that provide client applications with access to key functionality in OPERA. The Kiosk Interface provides a link to allow hotel kiosk systems to interact directly with the Property Management System to perform tasks such as unassisted check-in and check-out. The OPERA Kiosk Interface is provided as a web service, utilizing standard SOAP calls.
OPERA API Glossary - OXI
The generic OPERA Exchange Interface and XML standard layout are building the base for all interfaces to OPERA. All customization and specific business logic are programmed into an OPERA Exchange Adapter (OXA) and into OXI module by way off parameters, which also serves as the communication parts. The expectation is that the external system is storing exchanged data in their database. OXI can be used for reservation systems, channel mangers, yield and also revenue management systems. It can also be used for CRMs.
OPERA API Glossary - HTNG
OPERA supports the HTNG 2008b Single Guest Itinerary web service specifications, with added OPERA proprietary message extensions. Supported functionality includes: activity bookings, POS Postings, basic reservation and profile exchange.
Suite 8 API Glossary - Suite 8 Advanced Kiosk
The Kiosk Interface provides a link to allow hotel kiosk systems to interact directly with the Property Management System to perform tasks such as unassisted check-in and check-out. The OPERA Kiosk Interface is provided as a web service, utilizing XML messages.
Suite 8 API Glossary - IFC8 FIAS – OPERA and Suite 8
FIAS is a universal protocol specification which can be used by different kinds of third party systems to exchange data. It allows a system to define its own specific data records using the list of available record types and fields to create desired functionality to be supported within an interface. Currently it supports following IFC Types:
Suite 8 API Glossary Suite 8 OTA
The CRS Standard XML Interface allows uploading trigger based hotel, rate and room type availability for OTA, the OpenTravel Alliance, OTA is a non-profit organization which develops open data transmission specifications for the electronic exchange of business information for the travel industry, including but not limited to the use of XML.
Oracle Hospitality Partner Integration Program Criteria
In order to submit a Oracle Hospitality Partner Integration, our future partners are asked to review the following criteria to ensure they are able to integrate with Orcale’s integration standards.
Hotel Partner Integration Criteria Distribution
Sales & Catering
Self Check-in/ Check-out
Spa, Golf & Leisure
Cruise Integration Criteria
Payment Integration Criteria
Below you can find the breakdown of the fees linked to a validation and more information can be found here
|OPN Membership||Work in Progress||Annual|
|Oracle Validated Integration Program Fees Schedule for Oracle Hospitality||USD $1,500||Annual|
|Oracle Cloud Marketplace||No Program Fee||N/A|
|Oracle Hospitality Consulting Validation + Support SOW||Varies, Average USD $7,000 to $15,000 (cost could be greater based upon the scope of work)||Per Validated Integration|
After having reviewed the criteria, APIs and applicable fees you are now ready to proceed with submitting the request. Submit request via this link below. Request will be reviewed by strategy team – can take up to 4 weeks. Based on the review outcome you will be provided with the information for the next steps. If the request is approved you will be asked to join the Oracle Partner Network and you will also be asked to join the Oracle Cloud Market place for cloud validations and/or the Oracle Validated Integrations path for the on-premise validation