Custom deployment environment layout configuration

Custom deployment environment layout configuration

This overview describes two major configuration considerations for custom deployment environments: selecting clusters and single servers to use with the environment and specifying the deployment environment configuration. An understanding of these considerations enables you to plan and implement a deployment environment effectively.
Selecting Clusters and Single Servers to use with a deployment environment defines the clusters and servers that make up your deployment environment. Unlike the patterned deployment environments, where clusters are created for each function, in a custom deployment environment you add the clusters and servers that you need to perform functions.
Defining the Deployment Environment Configuration describes the functions you configure for the clusters and servers. These functions are messaging, Common Event Infrastructure, or application support.
Before you complete the deployment environment configuration in the system by generating it, you can return to your configuration and make changes. After you generate the deployment environment configuration in the system, you can look at the current configuration. You can also add more servers and clusters, configure more functions, or you can remove servers and clusters from management by this deployment environment. You cannot undo a function configuration that you have already generated, and you cannot remove a server or cluster from the deployment environment definition that is still required by another server or cluster in your deployment environment.

Requirements for all custom deployment environments

A custom deployment environment layout includes these restrictions:

After you complete a configuration by generating the deployment environment, the associated controls become checked and disabled.
You cannot undo the configuration.
After you generate the deployment environment, if a control is not checked and disabled for a component, configure the associated functions in the following order: configure the associated messaging engine, then configure the Common Event Infrastructure (CEI), then the application support (described later in this topic).
The configurations that exist on a system override the topology layout configuration. Thus, exporting a custom topology reflects the actual configuration of the servers involved in the topology.

The Topology Layout page in the administrative console has four sections that configure for a custom topology:

Select Cluster and Single Servers
Messaging
Common Event Infrastructure
Components

The following sections include other requirements for completing a custom topology layout configuration.

Selecting Clusters and Single Servers to use with a deployment environment

Use the Select Cluster and Single Servers section of the Topology Layout page to manage the clusters and servers within the deployment environment and define which functions they provide.
The Select Cluster and Single Servers section of the Topology Layout page includes a list of available clusters and servers, which you configure as part of the deployment environment. You assign clusters and servers to collaborative units in the function configuration. Each collaborative unit represents a group of clusters and servers that provides, as a whole, a function in the deployment environment.
You can remove clusters or servers from the deployment environment. However, you can remove only clusters or servers that are no longer needed by other clusters or servers in the configuration.

Defining the Deployment Environment Configuration

Use the Specify the Deployment Environment Configuration section of the Topology Layout page to define which clusters or servers participate in specific functions for the deployment environment.

Messaging

Partitioned messaging engines are not supported.
You use the fields in the Messaging tab to configure the messaging destination for selected targets. Each table represents one collaborative unit, and the Messaging section can include multiple tables. Select only one target (Cluster/Server) for the option of local configuration for each unit, and all other targets in this unit assume the remote destination. When applications send messages to targets with a remote destination configuration, the system routes the messages to the local target for their unit.
The messaging configuration applies to the Service Component Architecture, the CEI, and the Business Process Choreographer system buses.
To prevent conflicts with the local destinations in your topology configuration, the following rules apply:

The SCA system bus messaging engine configuration determines the local and remote destination locations. The SCA application, the CEI and the Business Process Choreographer bus configurations follow the SCA system bus configuration.
If you locate the messaging engines for other buses on different targets in a unit, then the other targets in that unit assume the remote destination role. If the CEI or Business Process Choreographer buses have different configurations, an information message indicates that the messaging engine for a given bus is not located on the same target as the SCA messaging engine.
If you try to add a target that already has a remote or local destination configured that conflicts with the current bus settings of a given unit, the system generates an error message.

Common Event Infrastructure

You configure CEI on the CEI tab. The CEI can have multiple tables, each representing a unit. In each table you select one CEI cluster or server (Cluster/Server column) that acts as the server by selecting Server. All targets that are not configured as a server assume the destination role. On the corresponding targets the event Infrastructure emitter factory Java™ Naming and Directory Interface (JNDI) name is configured so that Common Base Events that are emitted on this target are sent to the server in their appropriate collaborative unit.

Application support

The Application Support tab lists all of the components that you can configure for a given deployment target. You configure component functions in a related collaborative unit.
For example, you configure a Business Process Choreographer event collector in a unit to collect the Common Base Events that are emitted by the Business Process Choreographer container that is configured in the same unit. Each component configuration has requirements and dependencies on other component configurations. Dependencies are represented by cleared and disabled controls. To enable them, configure dependent controls first.
Dependent controls are configured on either on the Messaging or the CEI tab. Table 1 describes the relationships between the components.

Deployment environment component relationships
Component Purpose Related Component Considerations
Service Component Architecture Configures the deployment target for SCA application support.
The SCA system and application bus members are configured locally if the corresponding messaging configuration is local; otherwise, they are configured remotely with the remote destination as specified in the corresponding messaging unit.
Messaging SCA configuration is not available if you have not configured the deployment target for messaging.
Business Process Choreographer container Configures the deployment target for both business flow and human task support.
The configuration follows the SCA configuration for setting up the Business Process Choreographer system bus.

Messaging
Service Component Architecture
Business Process Choreographer Explorer

Business Process Choreographer configuration is not available if the deployment target has not been configured for messaging or if it has not been configured for Service Component Architecture support.
One collaborative unit supports one Business Process Choreographer configuration. Add as many units as you need on the Application Support tab.
To manage a container, consider configuring Business Process Choreographer Explorer .
Business Process Choreographer Explorer Configures Business Process Choreographer Explorer on the selected deployment target.
Business Process Choreographer Explorer is a web application that manages the Business Process Choreographer container that is configured in the same collaborative unit.
It includes an optional reporting function (Business Process Choreographer Explorer reporting ) which was previously known as the Business Process Choreographer Observer. The reporting function can be configured after the deployment environment ifs created
Business Process Choreographer container The Business Process Choreographer Explorer configuration is available after you have selected a Business Process Choreographer container configuration in the same collaborative unit.
You must configure the deployment target for web application support
You can configure as many instances of Business Process Choreographer Explorer on a deployment target as you want. Add the deployment target to the collaborative units with a configured container and check the Business Process Choreographer Explorer configuration control.
Business Process Rules Manager Configures the Business Process Rules Manager on the selected deployment target.
The Business Process Rules Manager allows you to configure business rules that determine business process behavior.
Service Component Architecture The Business Process Rules Manager configuration control is available after you configure SCA support on the same deployment target.
You can configure only one Business Process Rules Manager for a deployment environment.
You might need to configure only one Business Process Rules Manager in your system because one instance can manage the business rules configuration of the entire cell.

Component	Purpose	Related Component	Considerations
Service Component Architecture	Configures the deployment target for SCA application support. The SCA system and application bus members are configured locally if the corresponding messaging configuration is local; otherwise, they are configured remotely with the remote destination as specified in the corresponding messaging unit.	Messaging	SCA configuration is not available if you have not configured the deployment target for messaging.
Business Process Choreographer container	Configures the deployment target for both business flow and human task support. The configuration follows the SCA configuration for setting up the Business Process Choreographer system bus.	Messaging Service Component Architecture Business Process Choreographer Explorer	Business Process Choreographer configuration is not available if the deployment target has not been configured for messaging or if it has not been configured for Service Component Architecture support. One collaborative unit supports one Business Process Choreographer configuration. Add as many units as you need on the Application Support tab. To manage a container, consider configuring Business Process Choreographer Explorer .
Business Process Choreographer Explorer	Configures Business Process Choreographer Explorer on the selected deployment target. Business Process Choreographer Explorer is a web application that manages the Business Process Choreographer container that is configured in the same collaborative unit. It includes an optional reporting function (Business Process Choreographer Explorer reporting ) which was previously known as the Business Process Choreographer Observer. The reporting function can be configured after the deployment environment ifs created	Business Process Choreographer container	The Business Process Choreographer Explorer configuration is available after you have selected a Business Process Choreographer container configuration in the same collaborative unit. You must configure the deployment target for web application support You can configure as many instances of Business Process Choreographer Explorer on a deployment target as you want. Add the deployment target to the collaborative units with a configured container and check the Business Process Choreographer Explorer configuration control.
Business Process Rules Manager	Configures the Business Process Rules Manager on the selected deployment target. The Business Process Rules Manager allows you to configure business rules that determine business process behavior.	Service Component Architecture	The Business Process Rules Manager configuration control is available after you configure SCA support on the same deployment target. You can configure only one Business Process Rules Manager for a deployment environment. You might need to configure only one Business Process Rules Manager in your system because one instance can manage the business rules configuration of the entire cell.