PMS Rate Broker & Inventory Oracle Integration Guide

To synchronize hotel inventory without local database writes, the Trip.Enterprises PMS Rate Broker connects as a read-only client to your PMS.

1. Connection Architecture

The rate broker daemon streams inventory data without storing guest records locally:

• Zero-Storage Sync: The daemon fetches current room occupancy and rates directly from the PMS database view.
• Oracle Publishing: Real-time prices are signed cryptographically and sent to the public booking channel.
• Security: Connection credentials are encrypted and stored in hardware-secured containers (UID One Vault).

2. Database View Configuration

Create a dedicated read-only database view in your PMS schema (e.g., Opera SQL Server, Infor Oracle DB) with the following structure:

CREATE VIEW v_trip_express_inventory AS SELECT room_type_code AS room_type, available_qty AS allocation, base_rate_amount AS rate, currency_code AS currency, last_modified_timestamp AS updated_at FROM pms_inventory_table WHERE is_active = 1;

3. Connector Daemon Setup

Configure the database connector in the node configuration file /etc/trip/connector.json:

{ "connector_type": "opera_jdbc", "connection_string": "jdbc:oracle:thin:@//pms-db.internal:1521/opera", "read_only_credentials": { "username": "trip_express_broker", "password_vault_ref": "vault_id_10294" }, "polling_interval_seconds": 15 }

The daemon polls this view every 15 seconds, detecting changes and streaming delta updates. This lightweight stream ensures zero performance impact on your primary PMS database.