- Neuron ESB
Zones – General
A zone is a container that represents the Neuron server. Multiple zone definitions are allowed, but a Neuron server only runs under a single zone.
|Name||The name of the zone.|
|Description||A short description of the zone.|
|Location||A short description of the zone.|
|Enabled||Indicates if the Neuron server can run using this zone.|
Zones – Ports
Ports used by Neuron services can be customized for every zone.
|Bootstrap Service||All parties will connect to this service for authentication and configuration.|
|Management Service||All parties will report message statistics to this service, such and the number of messages sent and received.|
|Control Service||All adapters, service endpoints and publishing services will periodically contact this service for status updates.|
|Peer Resolver Service||All topics that are peer channel based will contact this service.|
|Audit Service||Parties use this service when message auditing is enabled|
|TCP Service||The TCP publishing service ports. Every TCP based topic will be assigned a single port number in the specified range. Parties that have TCP topic subscriptions will contact a TCP publishing service.|
Zones – Transports
This page is used to configure the default settings for each topic transport type. When a new topic is created it will use the defaults specified here.
Zones – Server
This page configures server wide settings.
|Client Polling Interval||How often a party will send its message statistics and check for configuration updates. The value is specified in seconds.|
|Service Reporting||How often adapters, service endpoints and publishing services will report its status and check for configuration updates. The value is specified in seconds.|