IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM

Plan the IBM IBM ND environment

Before you plan your deployment environment :

These decisions influence trade-offs that you make between the available hardware and physical connections, the complexity of the management and configuration and requirements such as performance, availability, scalability, isolation, security, and stability.


Procedure

  1. Identify the functional requirements of the deployment environment.

    1. Identify the features or runtime capabilities of your deployment environment.

      Consider whether the deployment environment will support other IBM BPM products and non-BPM products in addition to IBM BPM.

    2. Identify the component types that you will deploy.

    3. Identify the import and export implementation types and transports.

      Consider the resources needed for the databases or Java™ Message Service (JMS) resources and the need for business events and their transmission mechanism.

    4. Identify any functional requirements that are not related to applications.

      Consider security servers, routers, and any other hardware or software requirements to handle business events.

  2. Identify the capacity and performance requirements for your environment.
  3. Decide on the number of physical servers that you need for each function.
  4. Identify the redundancy requirements for your environment.

    1. Identify the number of servers that you need for failover.
    2. Identify the number of routers that you need.

      Your choice of router is influenced by exports of deployed modules, the types of queues you define on the service integration bus, Service Component Architecture exports, and the type of load balancing that you want among your clusters. IBM provides an embedded router used for web services exports with SOAP/JMS transports, or JMS exports. However, if you choose not to use this embedded router provided by IBM, you will need to determine how to balance the load among your clusters, based on the technology that you are using.

  5. Design your deployment environment.

    Decide on the pattern. For IBM BPM, you can select one of four established topology patterns:

    If none of these patterns meets your needs, you can use the administrative console to create a custom deployment environment.

    If your configuration supports multiple IBM BPM and non-BPM products in addition to, and compatible with, IBM BPM, the patterns of those products would be available to you when you create your deployment environment.

    See Topologies of an ND environment.

  6. Understand the methods available to you for configuring your deployment environment.

    You can configure the following types of deployment environments for IBM BPM:

    • Standardized ND environment

      Implemented by using the Deployment Environment configuration wizard or wsadmin commands.

      For Distributed systems, use the Deployment Environment Configuration wizard to create clusters with topology patterns...

      For z/OS use the Deployment Environment Configuration wizard to create clusters with topology patterns...

      You can also use the Deployment Environment Configuration wizard in the administrative console to create a custom deployment environment. Alternatively, you can build it yourself through the administrative console.

    • Customized ND environment

      Created from the administrative console, as opposed to template-based configuration from the Deployment Environment wizard.

      Create a customized ND environment only if the topology patterns that are included with the software do not meet your configuration needs.

      As is the case with the standardized environment, you can create a customized ND environment with wsadmin.


See

  1. Overview: Deployment environment topologies and patterns
  2. Topologies of an ND environment
  3. Considerations for selecting a topology
  4. Topology patterns and supported product features
  5. Determining whether to create a standardized or customized ND environment
  6. Load balancing and failover with IBM HTTP Server

Plan for IBM BPM