Enterprise Service Bus for z/OS, Version 6.2.0
Operating Systems: z/OS
Installation information
This reference section contains subtasks and supporting conceptual
and reference information related to installing and configuring WebSphere® ESB.
Subtopics
Differences between stand-alone and network deployment configurations
A stand-alone application server cell, also known as a base application
server node, is the simplest configuration you can use to deploy and run WebSphere ESB for z/OS® applications. A stand-alone
configuration provides a framework for a quick start or development environment
and if you are configuring for a small environment you may find that a single
server topology is all you need to meet you requirements. However, you are
probably more likely to use a network deployment configuration because it
can administer application servers that may be dispersed among multiple sysplexes
in a network environment. A network deployment configuration is intended to
support multiple application servers which can be clustered to provide high
availability and reliability.
Installation media contents
The WebSphere ESB for z/OS components that are to be installed on z/OS systems
are supplied on a single tape or as a download package; components
that are to be installed on non-z/OS systems are supplied on CDs.
Port number settings
Prevent port conflicts from occurring when you want an
installation of WebSphere Enterprise Service
Bus to
coexist with another installation of WebSphere ESB, or
with an installation of WebSphere Process
Server, WebSphere Application
Server, or WebSphere Application Server.
Product version information
The properties/version directory in the WebSphere ESB for z/OS installation
file system contains important data about the product and its installed
components, such as the build version and build date.
Response file values
When you have run the installation jobs which install the WebSphere ESB for z/OS product definitions,
sample response files are installed into the installation file system.
Copy and edit these response files according to the configuration
that you want to achieve, and pass in the response file when you run
the augment script.