Submit the address of the event broker that you deployed to a Customer-Controlled Container. This request configures the Message VPN of the event broker and applies the event broker service configuration.

Submit the address only. The secured management (SEMP) port is taken from the connection endpoint of the event broker service, so it always matches the port the deployment artifacts published.

The response is an operation you poll at GET /eventBrokerServices/{serviceId}/operations/{operationId}. When it succeeds, the event broker service reaches the COMPLETED creation state and the address becomes the event broker service's host name.

You can submit a configuration again after one fails, and again after one succeeds, which is how you bring back an event broker you rebuilt, or move the event broker service to a new address. If you submit it to a running event broker, the request replaces the event broker configuration with the values of the event broker service. This includes the Message VPN, client usernames, Dynamic Message Routing (DMR) cluster, and Java Naming and Directory Interface (JNDI) objects. Changes that you made in Broker Manager are lost. While a configuration is in progress, a second one is refused.

Restricted to tokens with create or update access to the event broker service; read access alone is not enough. Your token must have one of the permissions listed in the Token Permissions and manage rights on this event broker service.