# Oracle Opera Streaming Import Integration

This feature is in Beta. Contact your Customer Success Representative for more information.

Many hospitality businesses use the Oracle OPERA Property Management System (PMS) to streamline various functions such as reservations, front desk operations, housekeeping, and billing. For those businesses that have deployed instances of the OPERA PMS application server, this integration enables data ingestion in real time and allows the Treasure Data CDP to be used as a centralized dashboard to provide exceptional customer experiences.

## Prerequisites

- Basic Knowledge of Treasure Data
- Ability to configure the Oracle OPERA Exchange Interface (OXI) to send events and objects to an external system
- Ability to configure the firewall policy, or any equivalent mechanism, to allow the OXI component to reach specified the Treasure Data static IP addresses.


## Limitations and Constraints

- This integration supports XML data sent in as a POST request. Other data formats are not currently supported.
- All imported data, which could be different business objects, will be transformed into JSON and stored in the same table. Additional data processing with TD Workflow can be used to tailor the data for specific use cases.
- The maximum XML payload size is 998KB.


## Static IP Address of Treasure Data Integration

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following link:
[https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/](https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/)

## Import Oracle Opera via TD Console

### Create a New Authentication

Your first step is to create a new authentication with a set of credentials.

1. Select **Integrations Hub**.
2. Select **Catalog**.
![](/assets/integrationshub-catalog2.e33c0a4c7d81c40cc83dd056c2143b97b1406220e213cab14ef349d69412ffef.7705d4c2.png)
3. Search for Opera in the Catalog; hover your mouse over the icon and select **Create Authentication**.
![](/assets/oracleopera.4fb14462070ec45f8300aff1e777ed4d7fa3215f96571ee6270626b67d4b6a40.211c5e0c.png)
4. Ensure that the **Credentials** tab is selected and then enter credential information for the integration.


**New Authentication Fields**

| Parameter | Description |
|  --- | --- |
| TD API Key | A TD write-only API Key is required for access to the database. See [Getting Your API Keys](https://docs.treasuredata.com/smart/project-product-documentation/getting-your-api-keys). |
| Public Key Pin | Use this optional configuration if you can configure a TLS/SSL certification on the OXI server to strengthen the security of the integration. Contact your Treasure Data Customer Success representative for details |


1. Enter a name for your authentication and select **Done**.


### Create a Source

1. Open TD Console.
2. Navigate to **Integrations Hub > Authentications**.
3. Locate your new authentication and select **New Source**.


In the Connection tab, enter the following information and then select **Next**.

| Parameter | Description |
|  --- | --- |
| Data Transfer Name | Specify a name for the source. |
| Authentication | Specify the name of the authentication to use. |


![](/assets/oracle-opera-streaming-import-integration-2024-11-13-1.cb94d7483805c3f8a7b8d00ccdf488228fd2acfdadd8c03020e5e70a6156e9f0.211c5e0c.png)

#### Configure the Data Settings

In the Data Settings tab, enter the following information and then select **Create**.

| Parameter | Description |
|  --- | --- |
| Datastore | Plazma is the only available option. |
| Tags (optional) | Comma-delimited list of tags. These tags can be used to find the data source more easily later. |
| Database | Specify the database within Treasure Data where the import data will be located. |
| Table | Specify the table (which has been created in advance) within the database. |


![](/assets/operacreatesourcedatasetting.5b3dedaa159e0b0cedde857f11f551c68d7a8b24d523474b96fe77b7429a9546.211c5e0c.png)

### Construct the Endpoint for Data Import

The unique ID of the Source created in the previous steps is a part of the endpoint allowing the data import into your TD account. To prevent misuse, the Source ID and the endpoint URL should not be disclosed to any unauthorized persons

If you do not configure the the Public Key Pin authentication, anyone knowing the Source ID (UUID v4) or the Endpoint URL could send arbitrary data into your data source. Consequently, Treasure Data recommends that you treat the Source ID as a secret credential.

1. Navigate to **Integrations Hub > Sources**.
2. Search for the created Source
3. In the row of the source you want to use, select the more icon(![](/assets/more3dots.bc4a1401016eaf0793b9566848561f9c8890f33f8ea5cf23c19795702a04882d.211c5e0c.png)) at the far right., and select**Copy Unique ID**.


The ID is a 32-character UUID.
![](/assets/oracle-opera-streaming-import-integration-2024-11-13-3.7e841d1e3da71d8de775edb74074b3418067995870d6f7bf7977fc9abfed2095.211c5e0c.png)
4. Construct the endpoint by replacing the copied source ID at the end of this URL:

`https://opera-in-streaming.treasuredata.com/v1/task/<source\_id>`

An example of a full endpoint would be:

`https://opera-in-streaming.treasuredata.com/v1/task/abcdef12-3456-7890-abcd-ef1234567890`

## Incorporating TD Workflow

To incorporate TD Workflow with this integration see [Using TD Workflow with TD Integrations](/int/using-td-workflow-with-td-integrations).