The WebSphere® ESB for z/OS® installation and configuration is tightly integrated with, and dependent on, the installation and configuration of WebSphere Application Server for z/OS. The task is, therefore, a multiphase process that can span multiple roles.
In order to create a WebSphere Application Server for z/OS server, the default profile that is created when WebSphere Application Server for z/OS is installed must be augmented into a WebSphere ESB profile. This process adds WebSphere ESB functionality to the existing WebSphere Application Server functionality.
Unlike many products that are installed on z/OS, you do not use ISPF dialogs to install and configure WebSphere ESB. Instead, you run two shell scripts that perform tasks such as creating symbolic links between the product installation file system and the product configuration file system.
There are two main phases when installing WebSphere ESB for z/OS:
The configuration file system is a writable file system that holds customized configuration documents and files for the configured product installation. The configuration file system contains the application server root directories (/AppServer and /DeploymentManager) and certain symbolic links that are associated with them. Each different node type under the configuration file system requires its own cataloged procedures under z/OS. By default the configuration file system is mounted at /WebSphere/V6R2.
The configuration file system has symbolic links to the WebSphere ESB installation file system (by default, /usr/lpp/zWPS/V6R2). The symbolic links point to read-only files from the installation file system, such as JAR files and shell scripts.
The relationship between the people involved in the installation, the system programmer and the product administrator, and the installation phases is illustrated in the following diagram:
The product installation is not complete until both phases (loading the product code and running the installation script) have been performed successfully.
After completing the product installation, the WebSphere administrator can begin to configure the product for use.
After completing both stages of the installation process, you can configure WebSphere ESB for z/OS. Prior to configuring WebSphere ESB, you need to create the appropriate database and storage groups for some database types. For information on how to create the databases and storage groups, see Creating the DB2 databases and storage groups using SPUFI, DSNTEP2, or DButility.sh.
The product configuration script (zWESBConfig.sh) is run from a command line.
There are several configuration options, which on z/OS are driven by the WebSphere ESB for z/OS configuration script's use of response files. The content in the response file is used to augment the WebSphere Application Server for z/OS profile with WebSphere ESB for z/OS configuration data.