You can view and change aspects of the server and bus environment from the administrative console or from the command line.
The ESB server provides the integration technologies, infrastructure services, configuration, and runtime administration needed to run mediation modules.
The detail settings page for a server provides access to the service integration properties under the Server messaging category label, including messaging engines, messaging engine inbound transports, and WebSphere MQ link inbound transports.
Each service integration bus provides a scope within which you can configure resources for mediation modules and interaction endpoints deployed in WebSphere ESB. The bus enables message routing between endpoints with specific quality of interaction service and can temporarily persist messages if required.
If you create a WebSphere ESB stand-alone profile, the single application server is automatically configured for SCA support, and is made a member of the SCA.SYSTEM bus and the SCA.APPLICATION bus.
In a new network deployment cell, the SCA.SYSTEM bus is created for you when you configure the first cluster or server for asynchronous SCA support with local messaging. The server or cluster being configured becomes a member of the bus. Similarly, when you configure the first cluster or server for JMS SCA support, the SCA.APPLICATION bus is created for you.
When you install a mediation module into WebSphere ESB, the necessary bus destinations are created on the SCA* buses.
The detail settings page for a bus provides access to service integration resources under a number of category labels, including bus destinations.