A stand-alone configuration, also known as a base configuration, is the simplest configuration you can use to deploy and run WebSphere® ESB for z/OS®.
A stand-alone configuration of WebSphere ESB for z/OS consists of a single node running an application server and one daemon server in a single z/OS® system or LPAR.
The application server runs the administrative console, which you can use to deploy and run additional applications. The application server is managed independently from other servers.
The daemon server is a unique server that runs constantly and has one controller region, which distributes server workload.
Application servers in a node do not use workload distribution or common administration. You can define additional application servers in a stand-alone cell, but you cannot control them using the administrative console.
The following figure shows a stand-alone configuration which is made up of a single node running an application server and one daemon server in a single z/OS® system or LPAR:
The following figure shows a stand-alone configuration which is made up of a single node running an application server and one daemon server in a single z/OS® system or LPAR:
Advantages of a stand-alone configuration
Use a stand-alone configuration if you want to isolate the test and production systems in your company. Isolating test and production systems is important because, if the systems are not isolated, applications that are being tested in the test system might cause errors that can affect other applications on which your company depends.
You might choose to use a stand-alone configuration in the following scenarios:
The other type of configuration that you can use for WebSphere ESB for z/OS is a network deployment configuration, which consists of multiple servers. A network deployment configuration is intended for a more sophisticated environment, and improves scalability and security throughout the system.