> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/oracle-e-business-suite-integration-setup.md).

# Oracle E-Business Suite Integration Setup

### Overview: BalkanID Oracle E-Business Suite Agent

The BalkanID Oracle E-Business Suite (EBS) Agent is a **high-performance, cross-platform service** designed to securely extract and manage identity data from on-premise Oracle EBS deployment. Written in Go, the agent runs within the customer's network and acts as a controlled bridge between on-prem AD and the BalkanID identity governance platform.

The agent runs inside the customer network and makes only **outbound** connections, so EBS is never exposed to BalkanID. The agent connects to the EBS database and takes a\
full snapshot of users, responsibilities, and their assignments every 2 hours, and\
uploads it to BalkanID. Because the agent only initiates outbound HTTPS to BalkanID and outbound DB connections to EBS, it requires **no inbound connectivity** and fits environments with strict firewall rules. Each cycle uploads a full snapshot; the backend replaces the previous snapshot for the integration, so there is no incremental-reconciliation state to manage.

### Requirements

* **Oracle E-Business Suite R12.2** (works across R12.x; reads via `APPS` editioning views).
* Network reachability from the agent host to the EBS DB listener (default TCP `1521`, or `2484` for TCPS) and outbound HTTPS (`443`) to `api-integrators.balkanid.app` and `balkanid.app`.
* A read-only Oracle account (see below).
* BalkanID tenant credentials (`tenant_key`, `tenant_secret`) and an installed `oracle-ebs` integration on the tenant.
* A Linux (systemd) or Windows host.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/oracle-e-business-suite-integration-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
