A deployment environment pattern specifies the constraints and requirements of the components and resources involved in a deployment environment. The patterns are designed to meet the needs of most business requirements and are intended to help you create a deployment environment in the most straightforward way.
Each of the three deployment environment patterns addresses a specific set of requirements. Most requirement sets can be met using one of these patterns.
These descriptions are not intended as installation instructions. To create a deployment environment that fits one of the patterns, you make selections during installation, profile creation, or in the administrative console.
The single cluster pattern is suitable for scenarios that are focused on running applications and on synchronous invocations. Any messaging requirements should be kept to a minimum with this pattern. Service Component Architecture (SCA) internal asynchronous invocations, the Java™ Message Service (JMS) and MQ messaging bindings do not support multiple messaging engines in the same cluster. If your modules require any of these, choose one of the other patterns, in which the messaging infrastructure is in a separate cluster from the application deployment target.
The remote messaging pattern provides a separate cluster for the messaging role. This pattern is suitable for scenarios involving asynchronous invocations, because the cluster can be scaled for this load. The components are divided between the two clusters.
You configure the application deployment target to support SCA applications.
With this three-cluster pattern, resources are allocated to the cluster that handles the highest loads. This pattern is the most flexible and versatile, and is preferred by most users. The components are divided between the three clusters.
You configure the application deployment target to support SCA applications.
The following figure shows one way in which resources might be allocated using the remote messaging and remote support pattern. Because the heaviest load for this installation is for application use, there are more resources allocated (server1, server2 and server6) for the application deployment target cluster (Cluster 3) than the other functions.