Results for “ecx_hubs”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ECX_HUBS is a configuration table owned by the ECX schema and used by the Oracle XML Gateway, a component of Oracle E-Business Suite available in both 12.1.1 and 12.2.2. The table stores the definitions of XML Gateway "hubs." In ETRM terminology, a hub represents a routing endpoint or intermediary through which XML business messages are transmitted—typically a trading partner's transport server, a middleware gateway, or an internal messaging node. Each row describes one hub, binding a logical name to a transport protocol and network address so that the XML Gateway runtime can direct outbound and inbound XML documents to the correct destination.

From a Data Vault modeling perspective, the mined classification for this object is hub-leaning. The table carries a well-defined surrogate primary key and stable business identifiers, which is characteristic of a hub entity in a Data Vault model. This classification is a heuristic suggestion rather than a documented Oracle designation, and implementers modeling XML Gateway data should treat it as guidance rather than an authoritative fact.

Key Information Stored

The table contains nine documented columns. The most significant are:

• HUB_ID — The surrogate primary key, enforced by the ECX_HUBS_PK constraint and confirmed by the unique index ECX_HUBS_U2. It uniquely identifies each hub definition and is the column referenced by all foreign keys pointing at this table.
• NAME — The business name of the hub. Along with PROTOCOL_TYPE it forms the composite unique index ECX_HUBS_U1, making NAME a business-key candidate for hub identification.
• PROTOCOL_TYPE — The transport protocol associated with the hub, such as HTTP, FTP, or similar messaging transport. This column is the second component of the ECX_HUBS_U1 business key.
• PROTOCOL_ADDRESS — The network address or endpoint (URL, host path, or equivalent) used to reach the hub during message transmission.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the user and timestamp of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification, supporting change tracking and troubleshooting of hub configuration drift.

The combination of NAME and PROTOCOL_TYPE provides the natural business key, while HUB_ID serves as the technical surrogate used throughout the referential model.

Common Use Cases and Queries

Administrators and support analysts query ECX_HUBS to audit XML Gateway connectivity configuration, verify which transport endpoints are defined, and troubleshoot failed transmissions. A typical listing query resembles:

• SELECT hub_id, name, protocol_type, protocol_address FROM ecx.ecx_hubs ORDER BY name;
• Joining to ECX_HUB_USERS to determine which users are associated with a given hub: SELECT h.name, u.user_id FROM ecx.ecx_hubs h, ecx.ecx_hub_users u WHERE h.hub_id = u.hub_id;
• Joining to ECX_TP_DETAILS to correlate trading partner definitions with their assigned hubs, supporting partner onboarding and message routing reviews.
• Reporting on duplicated or conflicting business keys: SELECT name, protocol_type, COUNT(*) FROM ecx.ecx_hubs GROUP BY name, protocol_type HAVING COUNT(*) > 1;

These queries are commonly embedded in custom concurrent programs or BI Publisher reports for integration health monitoring.

Related Objects

The referential model around ECX_HUBS is intentionally narrow. Documented foreign keys identify the following dependent tables:

• ECX_HUB_USERS — References ECX_HUBS via HUB_ID, mapping users or user accounts to hubs and controlling which principals may use a given hub.
• ECX_TP_DETAILS — References ECX_HUBS via HUB_ID, linking trading partner detail records to their associated hub definitions and driving transaction routing.

These two children are the principal dependents. Any custom extension, validation, or cleanup of hub data must account for rows in ECX_HUB_USERS and ECX_TP_DETAILS, since orphaned references there would break XML Gateway routing. Together, ECX_HUBS, ECX_HUB_USERS, and ECX_TP_DETAILS form the core configuration surface of the ECX XML Gateway integration layer.