Step 4 Defining Distributed ESB Process

• Control vs. Data Flow
  • Data flow incorporates both synchronous and asynchronous message-flow; more general purpose than pure control flow
• Business Process Orchestration
  • Typically implies a central orchestration engine
  • For distributed ESBs, central orchestration is a bottleneck; Data-flow processes with a graphical representation that maps directly to the physical implementation offer greater flexibility and generality
• Event Warehousing
• Security
• Logging, Tracing & Alerts
• Data format impedance mismatch
• Configuring Business process for failover
• Configuring Business process for performance

• Control Flow
  
  
  
• Data Flow
  
  
  

• Composition using pre-built services
• Data routing
• Control information
• Data transformation
• Identifying Node Names
• Configuring Service Design time properties

• Multiple node names for Services
• State failover for services
• Server level failover
  
  
  
  

• Identifying Parallel data flows
• Dynamic rerouting of data based on load
• Identifying Heavy-weight services (80/20 Rule)
• Running multiple instances of "heavy weight" services on different nodes
• Sub-Flows and Sub-Processes for effective business process execution
• Log/Trace level optimization
• Event tracing optimization
• Service level Load Balancing (static/Dynamic)
  
  
  

Step 5 Deploying ESB Process

• Deployment -what does it mean ?
• Identifying Network Domain/Topology
• Manual Services vs. Auto-Launched Services
• Security issues for Deployment
• Service Development Languages and Platforms

• Deployment Descriptor
  
  
  
  
• Remote Deployment of Service and its dependencies
• Remote installation of service dependencies
• Caching
  
  
  
  
• Managing Dependencies / Order of installation /Order of Launch
  
  
  

• Deployment Domain/Nodes
  
  
  
• Domain/Node Name Alias (Hierarchical Domains)
• Configuration Alias

• Executed externally to the ESB (Servlets, EJBsetc)
• Combination of managed and unmanaged components
• Managed Components like:
  • A Webservice deployed in a Webservice container
  • An EJB deployed in J2EE container
  • A COM Object deployed in COM+ server
  • A CORBA based server Object deployed in an ORB
  • Windows NT/2K Service
• Unmanaged Components like:
  • Java executable archive
  • A C/C++ executable
  • Legacy Application running in a mainframe environment.
  • A Unix shell program (functioning within a pipe-and-filter style architecture).

• Native ESB services: managed and launched by ESB containers
• Auto start/stop and restart of these services
• Connectivity management
• Fine grained monitoring

• Deployment Manager to restrict service deployment