Book Image

Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7

Book Image

Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7

Overview of this book

By adopting an SOA approach in Business Process Management (BPM), you can make your application flexible, reusable, and adaptable to new developments. The SOA approach also gives you the potential to lower costs (from reuse), and increase revenue (from adaptability and flexibility). However, integrating basic SOA constructs (such as Process, Business Services, and Components) and core building blocks of BPM (such as Process Modeling and Enterprise Service Bus) in a real-world application can be challenging.This book introduces basic concepts of Business Integration, SOA Fundamentals, and SOA Programming Model and implements them in numerous examples. It guides you to building an Order Management application from scratch using the principles of Business Process Management and Service Oriented Architecture and using WebSphere Process Server (WPS) and WebSphere Enterprise Service Bus (WESB). The various detailed aspects, features, and capabilities of the product are conveyed through examplesWe begin with essential concepts on Business Integration, SOA Fundamentals and SOA Programming Model. Then we set up the development environment to build your first Hello Process and Hello Mediation applications.Gradually, we build an SOA-based Order Management Application. We cover important aspects and functions of WPS and WESB with numerous practical examples. We show how to analyze your application's business requirements and check if an SOA approach is appropriate for your project. Then you do a top-down decomposition of your application and identify its use cases, business processes, and services. Having built the SOA Application, we introduce you to various non-functional topics, including: Administration, Governance, Management, Monitoring, and Security. We also discuss deployment topologies for WPS and WESB, performance tuning, and recommended practices.
Table of Contents (20 chapters)
Application Development for IBM WebSphere Process Server 7 and Enterprise Service Bus 7
About the Authors
About the Reviewers
WID, WPS, and WESB Tips, Tricks, and Pointers

Monitoring WPS/WESB applications

There is also a need to understand, from a runtime perspective, what is happening within the deployed solution. Some of the common visibility items include:

  • Overall System/Server Health—CPU usage, memory usage, IO usage, connection pool, thread pool, event logs, disk space, and so on

  • Module Health—Status of modules, failed events, status of process instances, and so on

  • Services Health and Performance—Response time, throughput, periodic statistics, failure rates, and so on

  • Diagnostic Information—Logs, trace, threads, and so on

  • Business Process/Activity Performance—One of the goals of modelling a business process (like what we did in Chapter 7, Sales Fulfillment Application for JungleSea Inc.) is to measure the efficiency and the performance of the process itself based on KPIs and other instance metrics

From an overall system monitoring perspective, you need to make sense out of the raw data you are looking at. You need meaningful information and capabilities that...