IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan the ND environment > Topologies of an ND environment
Remote Messaging, Remote Support, and Web topology pattern
The Remote Messaging, Remote Support, and Web topology pattern is an IBM-supplied topology pattern. In this pattern, the deployment environment functions are divided among four separate clusters.
The Remote Messaging, Remote Support, and Web topology pattern is the preferred topology for IBM BPM Standard and IBM BPM Advanced. It is also the default for the configureNode command, except for z/OS.
This four-cluster topology pattern is similar to the Remote Messaging and Remote Support topology pattern, except that supporting web applications reside on their own cluster.
The application deployment target cluster hosts the following:
- Business Process Choreographer (BPC) container
- Process Server
The messaging infrastructure cluster hosts the following:
- Business Process Choreographer bus members
- Common Event Interface bus members
- Performance Data Warehouse bus members
- Process Server bus members
- Service Component Architecture application bus members
- SCA system bus members
The support infrastructure cluster hosts the following:
- Common Event Infrastructure server application
- Performance Data Warehouse
The web application cluster hosts the following:
- Business Process Choreographer Explorer
- Business Rules manager
- Business Space
- Process Portal
- REST API Services
In a Remote Messaging, Remote Support, and Web topology pattern, the deployment environment functions are divided among four separate clusters. One cluster is used for messaging functionality, one cluster for support functionality, one cluster for applications, and one cluster for web-based functions. In addition to the ability to precisely control the individual components in your environment, the advantages of this topology pattern are similar to the advantages of the Remote Messaging and Remote Support topology pattern.
In this topology you must also configure a routing server such as IBM HTTP Server, WebSphere Application Server proxy server, or a reverse proxy server to ensure that requests that are intended for Process Portal are directed to the correct cluster.