WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Planning your deployment environment

Setting up your deployment environment involves many decisions that affect everything from the number of physical servers to the type of pattern you choose. Each decision will affect how you set up your deployment environment.

Before you begin

Make sure you completed these tasks.
  • Identified available resources
  • Chose a database type
  • Identified necessary authorities

About this task

Planning the layout of interconnected servers, requires that you make some decisions. These decisions will influence trade-offs you will 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. Determine the purpose for the deployment environment.
  2. Identify the functional requirements of the deployment environment
    1. Identify the component types you will deploy.

      Consider the component types and the interactions between components as part of the requirements.

    2. 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.

    3. Identify any functional requirements not related to applications.

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

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

      Your choice of router will be influenced by exports of deployed modules, the types of queues you define on the service integration bus, Service Component Architecture (SCA) exports, and the type of load balancing you want among your clusters. IBM® provides an embedded router used for Web Services exports with Service Object Access Protocol (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 you are using.

  6. Design your deployment environment.
    Decide on the pattern. There are three established cluster patterns to choose from. If none of these three patterns meets your needs, you can create your own custom deployment environment.
    • Single cluster
    • Remote messaging
    • Remote messaging and remote support

    See "Deployment environment patterns" for more information about the patterns and the differences amongst them.

  7. Identify how you plan to install your deployment environment.

    The single, remote messaging, and remote messaging and remote support clusters can be installed with a wizard through the administration console. You can install the custom deployment environment through a wizard in the administration console or by building it yourself through the administration console. You have the option of using the command line or a silent install for all or some of the installations.

What to do next

Select and follow the planning scenario that best fits your situation.


task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_inst_topologies.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).