Integrations / Oracle E-Business Suite Integrated SOA Gateway

Oracle E-Business Suite Integrated SOA Gateway

Read-only GET calls to REST operations explicitly deployed by a customer through Oracle E-Business Suite Integrated SOA Gateway. The customer must supply the deployed service alias and operation, confirm that GET is enabled for that operation, and configure HTTPS network reach and least-privilege credentials. This does not imply Fusion API compatibility, undeployed service access, or write support.

Basic auth

Actions

What Telara does

Capability matrix

Indexes No Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

An Oracle E-Business Suite instance with Integrated SOA Gateway configured and a REST service deployed for the target operation.

An EBS integration administrator who can provide the deployed alias and operation, confirm GET is enabled, and grant the least-privilege user access.

Vendor setup

Get the credential

Confirm the deployed operation

Read the deployed service WADL and record the exact alias and operation. Verify the operation is deployed, allows GET, and is reachable at the approved HTTPS endpoint.

Create a least-privilege user

Grant access only to the deployed GET operation the connection will call. The catalog declares Basic Authentication over HTTPS; confirm this matches the EBS instance configuration.

Configure the connection

In Telara’s Oracle E-Business Suite integration settings, enter the verified host base URL and authorized username and password. A Fusion URL or Fusion credential does not establish EBS access.

In Telara

Connect in Telara

Basic auth

Oracle E-Business Suite REST Basic Authentication over HTTPS. The user must hold access to the specifically deployed GET operation.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Base Url
Username
Password

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

The catalog can invoke only customer-deployed ISG operations using HTTP GET.

Undeployed interfaces, other HTTP methods, Fusion API parity, and a free hosted EBS test tenant are not included.