Skip to content

Run the Integration Control Plane

Follow the steps given below to run the Integration Control Plane.

Configure the Integration Control Plane

All configuration lives in conf/deployment.toml. The defaults work out of the box for local evaluation. ICP will start with the embedded H2 database, listen on https://localhost:9446, and create an admin user.

Essential settings

Setting Default Description
serverPort 9446 HTTPS port for the console and API
runtimeListenerPort 9445 HTTPS port for runtime heartbeat connections
serverHost 0.0.0.0 Bind address
logLevel INFO DEBUG, INFO, WARN, or ERROR
frontendJwtHMACSecret (default key) JWT signing secret — change in production

Database settings

By default ICP uses an embedded H2 database stored in bin/database/. For production, switch to PostgreSQL, MySQL, or MSSQL by uncommenting and editing the [icp_server.storage] section in deployment.toml:

[icp_server.storage]
dbType   = "postgresql"
dbHost   = "db.example.com"
dbPort   = 5432
dbName   = "icp_database"
dbUser   = "icp_user"
dbPassword = "changeme"

A separate credentials database stores user passwords. Configure it with the credentialsDb* settings if you want credential storage on the same external database:

credentialsDbType     = "postgresql"
credentialsDbHost     = "db.example.com"
credentialsDbPort     = 5432
credentialsDbName     = "credentialsdb"
credentialsDbUser     = "icp_user"
credentialsDbPassword = "changeme"

When using H2 (the default), no database configuration is needed.

Observability settings

To enable centralized logs and metrics, refer to Add Centralized Observability in the Integration Control Plane.

Reverse proxy settings

ICP serves the console and API on port 9446 by default. To expose ICP through a reverse proxy:

  1. Point the proxy at https://<icp-host>:9446 (the backend is HTTPS with a self-signed certificate, so configure the proxy to trust it or skip verification for the upstream).

  2. Tell ICP the external URL so the console can reach the API. Add these to deployment.toml:

backendGraphqlEndpoint      = "https://icp.example.com/graphql"
backendAuthBaseUrl           = "https://icp.example.com/auth"
backendObservabilityEndpoint = "https://icp.example.com/icp/observability"
  1. MI runtimes connect to ICP for heartbeats. If they also go through the proxy, set icp_url in the runtime's deployment.toml to the proxy URL:
[icp_config]
icp_url = "https://icp.example.com"

If runtimes connect directly (bypassing the proxy), leave icp_url pointing at the ICP host.

Start the Integration Control Plane

Linux / macOS:

./bin/icp.sh

Windows:

bin\icp.bat

The server logs its startup to the console. Once you see the listener ready message, ICP is available at https://localhost:9446.

Note: ICP ships with a self-signed certificate. Your browser will show a security warning on first visit — accept it to proceed.

Sign In to the Integration Control Plane

Navigate to https://<host>:9446/login. Enter username admin and password admin, then click Sign In.

After login the browser redirects to the organization home at https://<host>:9446/organizations/default.

Warning: Change the default admin password immediately via Access-control

Users > Reset Password.

Stop the Integration Control Plane

To stop the ICP standalone application, go to the terminal and press Ctrl+C.

Default Setting of the Integration Control Plane

ICP ships with these resources out of the box:

Resource Defaults
Organization Default Organization (default)
Environments dev (Non-Critical), prod (Critical)
Roles Admin, Developer, Project Admin, Super Admin, Viewer
Groups Super Admins, Administrators, Developers
User admin / admin (member of Super Admins)

When a project is created, ICP also auto-creates a <Project Name> Admins group with the Project Admin role.

What's next?