Enterprise Service Bus on PhronIQ

Get started with Enterprise Service Bus

Mon, 01 Jan 0001 00:00:00 +0000

Prerequisites

Docker and Docker Compose (v2.23 or later)
A PhronIQ deployment package and licence key (see below)

Start the stack

ESB ships as a licensed artifact, not as source. After your order, PhronIQ delivers a deployment package — the esb container image plus the docker-compose.yml bundle — and a PhronIQ-signed licence key.

Unpack the deployment package and change into its directory.
Install the licence key before the first start: point licence.file in config.yaml at the key file you were issued (or set ESB_LICENCE_FILE / ESB_LICENCE_KEY). The daemon verifies the key at startup and refuses to start without one (licence-missing). The Deployment guide’s Licence key section has the details.
Start the stack:

docker compose up -d

This starts:

Connect a system

Mon, 01 Jan 0001 00:00:00 +0000

Wire an external system into ESB as a route that the mediation engine can invoke. A route binds a service + operation to an outbound endpoint over a supported protocol. This guide covers choosing a protocol, referencing credentials (never pasting plaintext), testing connectivity, and deploying.

Prerequisites

A running ESB (see Getting Started).
A target system reachable from the ESB container.
For protocol UI setup: the Connectors view in the admin console.
A stored secret reference for any credential the endpoint needs (the Secret References page in the admin console, backed by Vault, environment variables or AWS as configured in enterprise.secrets.provider).

Step 1 — Choose a protocol

ESB supports the connector protocols listed below. Pick by what the remote system speaks: