Oracle WebLogic Integration Support Patterns (Doc ID 760943.1)

Last updated on JULY 31, 2023

Applies to:

Purpose

Provide assistance in resolving issues with handling business process exceptions, message loss, and versioning JPD support on running instances in WLI.

Scope

Handling Business Process Exceptions in WLI - A Business Process may raise exceptions just like any Java application. An exception is usually caused by either an application error (e.g. business rule violation) or system error (e.g. back end system unavailable). Either way, it is always desirable in such a case to execute specific logic for error handling and possibly resource cleanup.This pattern should help you during both the design phase abd can also be used as a troubleshooting guideline.

Versioning JPD Support on Running Instances - The Business process may need to change its workflow definition after it gets deployed into Production environments. By using the WebLogic Integration versioning feature in the WebLogic Workshop graphical design environment, you can make changes to your business process without interrupting any instances of the process that are currently running. Some best practices are included.

Message Loss in WebLogic Integration - In every integration scenario using WebLogic Integration, WLI receives and sends messages to various applications around it. The messages also pass through various components inside WLI asynchronously. A message loss is suspected when the expected job is not performed. This pattern helps in tracing those messages and illustrates some configuration best practices to avoid message losses.

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.