Book Image

BPEL Cookbook: Best Practices for SOA-based integration and composite applications development

By : Arun Poduval, Doug Todd, Harish Gaur, Jeremy Bolie, Jerry Thomas, Kevin Geminiuc, Lawrence Pravin, Markus Zirn, Matjaz B. Juric, Michael Cardella, Praveen Ramachandran, Sean Carey, Stany Blanvalet, The Hoa Nguyen, Yves Coene
Book Image

BPEL Cookbook: Best Practices for SOA-based integration and composite applications development

By: Arun Poduval, Doug Todd, Harish Gaur, Jeremy Bolie, Jerry Thomas, Kevin Geminiuc, Lawrence Pravin, Markus Zirn, Matjaz B. Juric, Michael Cardella, Praveen Ramachandran, Sean Carey, Stany Blanvalet, The Hoa Nguyen, Yves Coene

Overview of this book

<p>Service Oriented Architecture is generating a buzz across the whole IT industry. Propelled by standards-based technologies like XML, Web Services, and SOAP, SOA is quickly moving from pilot projects to mainstream applications critical to business operations. One of the key standards accelerating the adoption of SOA is Business Process Execution Language for Web Services (BPEL). <br /><br />BPEL was created to enable effective composition of web services in a service-oriented environment. In the past two years, BPEL has become the most significant standard to elevate the visibility of SOA from IT to business level. BPEL is not only commoditizing the integration market, but it is also offering organizations a whole new level of agility - ability to rapidly change applications in response to the changing business landscape. BPEL enables organizations to automate their business processes by orchestrating services within and across the firewall. It forces organizations to think in terms of services. Existing functionality is exposed as services. New applications are composed using services. Communication with external vendors and partners is through services. Services are reused across different applications. Services are, or should be, everywhere!</p>
Table of Contents (16 chapters)
BPEL Cookbook
Credits
About the Editors
About the Authors
Foreword
Dismantling SOA Hype: A Real-World Perspective

Deleting Stale Instances


Using BPEL Console, you can identify all stale instances and kill them as shown in the following screenshot:

Unfortunately, these stale instances can be searched for only on a specific domain. However, in a production environment, multiple processes will probably be deployed across different domains—resulting in a huge administrative burden. Besides, purging all stale instances at once within a specific domain is not possible.

As an alternative approach, you can find a unique cube instance key (cikey) for every stale instance via the following SQL query:

SELECT CUBE_INSTANCE.cikey, CUBE_INSTANCE.root_id, CUBE_INSTANCE.process_id,
CUBE_INSTANCE.domain_ref
FROM CUBE_INSTANCE
WHERE STATE = 9

Once you have identified a CI key for each stale instance, you can use that key to delete stale instances from CUBE_INSTANCE and other tables that reference the cube instances by invoking delete_ci(CIKEY) for every cube instance found via the SQL query. delete_ci(CIKEY) is a stored...