Service Integrators can deploy SCA modules without considering the server and bus environment that powers the enterprise service bus. However, an Administrator might want to manage the server and bus environment; for example, to start or stop a server, change the quality of service provided to SCA modules, add extra server capacity, or to adopt a more distributed bus environment.
If you choose a Complete (default) installation for WebSphere ESB, a default bus environment is created for you. This bus environment comprises a single server assigned to two service integration buses that are used for deploying SCA modules. You can also use the server to deploy J2EE components and resources, like servlets, enterprise Java beans, and JMS destinations.
The default bus environment might be adequate for your SCA modules. However, you might want to change the topology of the bus environment; for example, to add extra server capacity, or to adopt a more distributed bus environment for different departments or to separate test and production facilities.
Managing the bus environment includes some aspects of setting up WebSphere ESB, sometimes as part of a larger system, typically as a production environment or realistic test environment. This includes some installation and customization activities, bus topology planning, and creating product configurations. The focus is on the administration of service integration buses, servers, their resources, the set up and management of logical administrative domains of cells and nodes, and how to balance workload through clustering and high availability configurations.
The bus environment in WebSphere ESB uses the service integration technologies provided by WebSphere Application Server. This set of topics provides information about tasks involving the service integration technologies needed to manage the bus environment. For more complete information about using service integration technologies, see Service integration buses.