BPEL Tracking for Tivoli Monitoring for Transaction Performance
An add-on to Tivoli Monitoring for Transaction Performance (TMTP) that supports correlation of business workflows with IT end-to-end transaction flows.
Date Posted: August 4, 2005
|
|
 |
|
|
What is BPEL Tracking for Tivoli Monitoring for Transaction Performance?
This addition for Tivoli® Monitoring for Transaction Performance (TMTP) 5.3 FP1 customers provides seamless correlation of the business process execution to the information technology (IT) transaction flow.
A service-oriented architecture (SOA) is an application architecture in which IT functions or services are defined using a description language with interfaces that are invoked to perform business processes (also known as Workflows). The main benefit that SOA brings is the standardization of business process modeling, often referred to as service orchestration. A services-based layer of abstraction can be built over legacy systems and subsequently assembled as business processes. This effort has been standardized by an OASIS standard named Business Process Execution Language (BPEL). BPEL provides a standard, portable language for orchestrating services into end-to-end business processes.
The key benefit of this add-on is that once a transaction policy definition is made at the entry point or "edge" of the business activity on a TMTP monitored system, correlation is done between the business process invocation and the transaction flows that occur as a result of this business activity invocation. TMTP takes the responsibility of automatically generating transaction topology flow diagrams with statistics (context, response times, etc.). The transaction topology generated describes how the flows traverse the system for both business choreographed (BPEL) flows and interactions with other enterprise information systems (EIS) where applicable and monitored.
How does it work?
By using this add-on, TMTP customers will be able to relate the business activity as defined in BPEL (within the WebSphere® Application Server environment) to the IT infrastructure components that support the transaction flow. They need no longer follow the traditional approach of monitoring specific IT transactions or Web URLs and attempting to map them to business functions. With this add-on's capability, it is possible to identify and isolate IT infrastructure components that cause transaction latency or failure for specific business activities
After the user installs the BPEL modifications, no further steps are required. The topology will show the BPEL transaction with yellow nodes and BPEL icons in the topology tree view. The BPEL transactions will be grouped together in the topology tree view for easy viewing.
|
|
|
| | About the technology author(s):
Jean X. Yu is an advisory software engineer with the Tivoli CAM Technology Projects team. Ms. Yu has worked on end-to-end performance monitoring for Web transactions. She is currently leading a team to develop monitoring prototypes for various IBM middleware, such as Tivoli Access Manager, WebSphere Portal Server, and Tivoli LDAP Server.
Wilfred C. Jamison is a senior software engineer working with On Demand Software Development, a team under IBM Strategy and Technology. He is an expert in Java™ technology, Web services, SOA, CEI/CBE, many WebSphere products, and Linux®, among other things. Mr. Jamison's current work includes business innovation and optimization and the Enterprise Service Bus.
Matthew C. Mings is an advisory software engineer who joined IBM in 2000. Currently, he is a member of the CAM Technology Projects team within Tivoli. Mr. Mings has worked in the system management field for the past five years and has experience with both the TMTP and WSAM products.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Tivoli and WebSphere are trademarks of IBM Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
|
|
|
| |
