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
Credits
About the Authors
About the Reviewers
Preface
WID, WPS, and WESB Tips, Tricks, and Pointers
Index

What is WID history logging?


History logging is primarily meant to aid debugging during development and also help IBM support people when working on issues. It's a capability that is configurable in WID (turned on by default) whose intent is to gather, at a coarse level, just enough information so that we can have a good idea of the steps that a user took that led to an error. Rotating logs are written in the user's workspace .metadata directory and are named widHistory_n.log. These logs are viewable in the Server Logs view within WID by navigating to the workspace and loading the logfiles from the workspace .metadata directory. To view the configurable properties, open WID | Preferences | Business Integration | Logging and Tracing, as shown in the following screenshot:

There are various aspects that get logged in the history logs and are viewable through the WID Server Logs view. As shown in the following screenshot, when a history log is loaded, the aspects name appears in the content area, and these names can be filtered using the content filter of the Server Logs view. These include:

  • GeneralUI—shows WID start/end, view, or if editor is opened/activated/closed.

  • BUILD—shows build-related activities (incremental and clean).

  • REFACTOR—shows refactoring start/stop and what is being refactored.

  • SERVER—shows server initialization, state change for server and module on a server start, details about port, connection information, modules deployed to server, and so on.

  • PUBLISH—shows publish start/stop, publish type, and type of publish (added, changed, removed), and publish time.

  • INTEGRATED TEST CLIENT—shows server starts, modules added and published to the server, waits for modules to start, and how a server start or publish originated.

  • MIGRATE—shows files migrated to WID.

  • FROM_ECLIPSE_ERROR_LOG—shows errors that appear in the Eclipse error log, that is, the Error Log view. These errors indicate the workspace state when the error occurred.

WID Tracing

Tracing in WID is switched off by default. Rotating logs are written in the user's workspace .metadata directory and are named widTrace_n.log. These files are viewable through the WID Server Logs view. You can turn it on and must specify components that should be traced. You must specify the Trace string and example including:

com.ibm.*=finest would trace all.
com.ibm.wbit.*=finest: com.ibm.wbit.ui=info

Tracing levels can be one of fine, finer, finest, info, warning, or error. Any changes made are immediate—no need to restart WID.