Configuring and Administering Integration Nodes and Servers
Configuring and administering integration nodes and servers
This domain tests runtime topology and administration: integration nodes, integration servers, independent integration servers, server.conf.yaml, policies, listeners, security, and BAR deployment. You must know where a property is set and how it reaches the running flow.
Core rules
- An integration node can host multiple integration servers. Independent integration servers run without a node and are configured primarily through
server.conf.yaml. - Use configurable properties and policy overrides for values that change by environment. Do not edit a BAR to change an endpoint or credential.
- Configure MQ and HTTP listeners at the correct scope; a missing or misconfigured listener explains many connection failures.
- Security configuration includes SSL/TLS keystores and truststores, LDAP or file-based authentication, and policy credentials. Keep secrets out of source control.
- Use administration commands and the web administration UI to start, stop, report properties, and reload configuration. Verify effective values after a change.
Worked example
A BAR is deployed to an integration server, but it points at a test database. Set the database URL in server.conf.yaml or through the appropriate configurable property, reload the server, and verify with a property report command. Do not rebuild the BAR for each environment; promote the same BAR and change the override. Confirm the flow reconnects and check the event log for connection errors.
Traps
Editing BAR contents manually creates an untraceable artifact. Setting a property on the node when the flow reads it at server scope has no effect. Forgetting to restart or reload leaves old values active. Deploying to the wrong integration server is common when names are similar.