Overview Of WebSphere Process Server and WebSphere Enterprise Service Bus

• IBM WebSphere Process Server: The heart of SOA

1. WebSphere Process Server enables simple and flexible execution of standards-based business process management solutions in SOA.
2. Implements WS-BPEL compliant process engine that executes complex business process automation securely, consistently, and with transactional integrity using advanced human workflow, business rules, system-to-system and B2B capabilities
3. Enables building of composite integration applications 
4. Provides high performance and qualities of service with fault tolerance and error-detection capability
5. Includes a prebuilt Web 2.0 business user client (Business Space)
6. WebSphere Process Server provides business value.
7. Provides a comprehensive SOA offering — standards-based
8. Completes the life cycle of business process management as the runtime engine for deployed applications
9. Helps maximize reuse of existing IT assets in SOA

• WebSphere Process Server foundation: WebSphere Application Server ND and WebSphere ESB

1. WebSphere Application Server and Network Deployment provides high availability, workload management, and qualities of service.
2. WebSphere ESB integration provides a communication infrastructure for integrating services, applications and data.
3. WebSphere Process Server adds business process management functionality to the platform

• IBM WebSphere Process Server components

1. WebSphere Process Server adds process management components to the WebSphere platform and includes WebSphere Enterprise Service Bus mediation capabilities.

• WebSphere Enterprise Service Bus

1. WebSphere Enterprise Service Bus is the IBM, open-standards based ESB runtime environment
2. Mediations intercept messages between service requesters and providers
3. Centralizes logic to handle events, route, transform, convert data
4. Provides Web service connectivity, JMS messaging, and service-oriented integration (SOI)
5. Changing business needs met through dynamic selection, substitution, matching
6. Decouples the point-to-point connections from interfaces
7. Enables reuse, flexible coupling and decoupling of applications

SOA development and process management

• Business processes and business process management (BPM)

1. A business process is a collection of service interactions and activities executed to fulfill a business need.
2. A business process defines the potential execution order of services:
3. Defines how to coordinate interactions between a process instance and its partners
4. Specifies how to handle errors (faults)
5. Specifies other required technology patterns like compensation
6. Business process management is a systematic approach to improving an organization’s business processes.
7. BPM makes business processes more effective and efficient through a cycle of continuous improvement

• IBM Products for the SOA development life cycle

• Business Integration Roles In SOA Development

• Interactive Process Design

1. Interactive process design supports direct deployment of simple process models to test environments.
2. Provides faster time to value for human workflow applications
3. Business space provided as a client for workflow applications
4. Interactive process design gives business users more control.
5. Business user defines, tests processes using WebSphere Business Modeler
6. IT assists with problem determination and deploys the application
7. Interactive design avoids complex iterative development scenarios.
8. Direct deployment provides shorter path between requirements and executable processes.

• IBM BPM Suite and Foundation Offerings

1. IBM BPM products are bundled into two foundation offerings for specific process types.
2. Content-aware processes (FileNet)
3. Dynamic processes (WebSphere Business Services Fabric, Process Server)

Process Integration in the SOA reference architecture

IBM BPM SOA(Service Oriented Architecture)

• Evolution of enterprise integration toward SOA

1.  Goal: Architectures should enable flexibility and reuse.
2.  Integrate applications using Loosely-coupled and Welldefined interactions
3. Hide the implementation details from the service-invoking application
4. Provide common service definition independent of specific technology

• Introduction About SOA

1.  A service in SOA is:
2. A self-contained entity performing distinct business function
3. Based on open standards
4. A building block for composite applications that share information within and beyond the enterprise to include customers, suppliers, partners, and so forth
5. Service-oriented architecture (SOA) is an architectural approach to building distributed systems using service interactions.
6. SOA transforms the IT infrastructure into flexible, reusable, standardsbased services.
7. SOA separates interface technology from implementation so knowledge of the underlying implementation details is not required to develop composite applications.
8. The key to business agility is to reuse and combine standardized components (services) to address changing business priorities.

• SOA programming model: Open standards with IBM extensions

1. Data manipulation, service invocation, and process choreography are implemented in SOA using simplified, open standards.
2. Web Services-Business Process Execution Language (WS-BPEL) is used to choreograph service interactions.
3. Service Component Architecture is a programming framework that standardizes service invocation by isolating service implementation.
4. Service Data Objects provide a standard mechanism for working with data.