About this article
>>> Read the complete article <<<
The installation of a clustered WebSphere Process Server 6.0.2 (hereafter called WPS) environment included many different steps that had to be done manually: from the creation of multiple databases, the import of complex DDLs to the configuration of a variety of resources in the WebSphere admin console. Especially the configuration of the so called “Full Support Topology” (also referred to as “Golden Topology”; see [RB01] for detailed information on the architecture behind) was very time-consuming and error prone (see [DW01] for a description of the installation procedure). Since this topology can be considered as the reference for enterprise-scale WPS environments, it is most likely that it is the most chosen architecture.
In WPS 6.1 the installation process has dramatically been simplified by the introduction of so-called Deployment Environments. You may consider a Deployment Environment as a template for a specific WPS production topology. Or, if you are familiar with WebSphere Application Server 6.1
you can see it as a variation of the cell profile capability (see also [IC01]). A Deployment Environment describes a specific configuration pattern, which consists of topology information, server definitions, cluster definitions and many other WebSphere resources. Since most of the WPS configuration options are included, or rather assembled during installation, this allows the installation routine to generate almost all resources (for instance database tables, applications, clusters etc.) automatically. This automation in turn leads to a faster and less error-prone installation of complex WPS environments. Currently there are three different patterns available:
Single cluster pattern
This pattern simply consists of one cluster referred to as Application Deployment Target (hereafter called ADT), which incorporates all WPS specific applications, functions and capabilities. This pattern finally results in the so called Basic Topology, which is described in detail in [RB01], chapter 4.2.2.
Remote messaging pattern
With this pattern a WPS environment of two separate clusters will be created, whereas one cluster will contain the messaging infrastructure (referred to as Messaging) and one will become the ADT. This pattern creates a topology which is named Loosely Coupled Topology. A detailed description of the underlying architecture can be found in [RB01], chapter 4.3.2.
Remote messaging and remote support pattern
This pattern enables the creation of a Full Support Topology as described in [RB01] and therefore creates three different clusters: an ADT cluster for applications, one Messaging cluster which holds the messaging infrastructure (based on Service Integration Bus configuration items) and a support cluster (officially referred to as Support) that holds all supporting services as CEI for example. The remote messaging and support pattern therefore enables the installation of the best separation-of-concerns topology.
If you are unsure which topology will meet your business and technical requirements best, please consult the Redbook [RB01] which contains a detailed decision guide on when to choose which topology. However this article is focused on the installation of the Full Support Topology, whereas the installation procedure may easily be adapted to the other topology options.
Setting up the Full Support Topology for WPS 6.1 (The complete article)
Response Files for WPS 6.1 installation