> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/integrations-overview/setup-opera-oxi.md).

# How to Set Up Opera On-Premise (OXI)

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator** or **Supervisor**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Opera OXI part number** added to your Oracle account. Contact Oracle Support and request part number **OPX\_PEOPLEVINE**. Oracle will schedule installation of the OXI software on your system.
* **Gateway URL** from Opera OXI (provided by Oracle after installation).
* **Opera User** and **Password** for the OXI connection.
* **Property Code** (Hotel Code) from your Opera system.
* **Firewall whitelisting** -- if your property has a firewall, whitelist Peoplevine's IP addresses:
  * Virtual IP: `40.70.147.2`
  * Outbound IPs: `13.68.114.115`, `13.68.114.136`, `40.70.63.81`, `40.70.147.2`

> OXI is a legacy interface being phased out. For new integrations, use [Opera OHIP](/products/integrations-overview/setup-opera-ohip.md) instead. OXI is only necessary for on-premise Opera installations that cannot be upgraded to Opera Cloud.

> For Oracle-side OXI setup, see [Connect Oracle OXI and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) in Peoplevine Connect.

### Instructions

1. Navigate to [**AUTOMATE > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx).

> **Note (Pro Dash):** Same path -- **AUTOMATE > Integrated Platforms**.

2. Under **Property Management Systems (PMS)**, select **Oracle Opera Hospitality**.
3. In the **Connection Type** section, choose **On-Premise via OXI**.
4. Enter the following credentials:

| Field           | What to Enter                           |
| --------------- | --------------------------------------- |
| **Opera User**  | OXI connection username                 |
| **Password**    | OXI connection password                 |
| **Gateway URL** | URL from Opera OXI (provided by Oracle) |
| **Hotel Code**  | Your Property Code                      |

5. In **Select Membership Program to Automatically Enroll into**, choose a temporary membership for non-member hotel guests (optional).
6. Enable **Sync both member and non-member reservations** if you want all Opera data. Leave unchecked to sync member data only.
7. Click **CONNECT**.
8. A URL will be generated. Add this URL in the OXI system under **Interface Configuration > Comm Methods > Opera to External System**.

### What Gets Synced

| Data                                                       | Direction           | Notes                                                       |
| ---------------------------------------------------------- | ------------------- | ----------------------------------------------------------- |
| Member profiles (name, email, phone, address, preferences) | Peoplevine -> Opera | On creation + updates                                       |
| Membership status and tier                                 | Peoplevine -> Opera | Uses SKU-to-type mapping                                    |
| Member profile attributes                                  | Peoplevine -> Opera | Synced for personalized service                             |
| Reservations                                               | Opera -> Peoplevine | Synced when OXI pushes reservation data                     |
| PMS payments                                               | Opera -> Peoplevine | Displayed in Peoplevine as "PMS Processed"                  |
| Temporary membership                                       | Peoplevine -> Opera | Non-member guests auto-enrolled on check-in (if configured) |

**Limitations compared to OHIP:**

| Feature                                             | OHIP                       | OXI                                         |
| --------------------------------------------------- | -------------------------- | ------------------------------------------- |
| Member notes sync                                   | Yes                        | No                                          |
| Inbound reservation sync from PMS                   | Full (via Business Events) | Limited                                     |
| Payments through Peoplevine payment methods via PMS | Yes (Auto tender)          | No -- not supported                         |
| Contact/reservation change sync from PMS            | Yes                        | No                                          |
| Setup complexity                                    | Medium                     | High (requires Oracle on-site installation) |

### Best Practice

* **Plan your migration to OHIP** -- Oracle is retiring OXI. Coordinate with your Oracle account team to move to Opera Cloud and OHIP when feasible.
* **Set membership SKUs to match Opera Membership Types** -- same rules as OHIP. Create a `PPV` type in Opera for memberships without a matching SKU.
* **Test member sync before going live** -- sync a single member and verify the profile appears in Opera with the correct membership type.

### Common Issues

**Data not syncing in either direction:** Verify that the OXI software is installed and the generated Peoplevine URL is correctly entered in the OXI Comm Methods configuration (Opera to External System). Check that the Opera User credentials are valid.

**Reservations from Opera not appearing in Peoplevine:** OXI has limited inbound reservation sync compared to OHIP. Verify that OXI is configured to push reservation data. If reservations still do not appear, this may be a limitation of your OXI version.

**Members cannot pay through PMS using Peoplevine payment methods:** This is not supported on OXI. Payments closed in Opera are displayed in Peoplevine as "PMS Processed," but members cannot use Peoplevine card-on-file or house account tender types through the PMS. Consider upgrading to OHIP for this capability.

**Duplicate profiles in Opera:** Profiles are matched using an `extended_id` (first letter of first name + last name + email or phone). Ensure last names are entered correctly during profile creation.

### What Happens Next

* Members synced to Opera are recognized during hotel check-in
* Reservations pushed from OXI appear on the member's Peoplevine CRM profile
* Payments closed in Opera appear in Peoplevine as "PMS Processed"
* Non-member hotel guests can be auto-enrolled in a temporary membership for club access during their stay
* Pre-arrival and post-stay communications can be automated based on reservation data

*Last updated: 2026-05-24*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.peoplevine.com/products/integrations-overview/setup-opera-oxi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
