Overview

The following sections provide an overview of programming logic plug-ins:

• Types of Applications

• Logic Plug-Ins

Note: Custom Logic Plug-Ins are deprecated as of this release of WebLogic Integration. For information about the features that are replacing them, see the BEA WebLogic Integration Release Notes.

 

---

Types of Applications

WebLogic Integration provides the following types of applications that can be used for B2B integration:

• Logic plug-ins—For customized routing, filtering, and information processing. This document introduces logic plug-ins.

• Management applications—Used to monitor B2B integration activities. Based on BEA-implemented MBeans.

• Messaging applications—XOCP applications that use the WebLogic Integration Messaging API. An XOCP application implements a trading partner role and interacts directly with the B2B engine to manage the conversation and handle business messages.

For more information about management and messaging applications, see Programming Management Applications for B2B Integration and Programming Messaging Applications for B2B Integration.

For an introduction to B2B integration, see Introducing B2B Integration.

 

---

Logic Plug-Ins

Logic plug-ins are Java classes that perform specialized processing of business messages as those messages pass through the B2B engine. Specifically, logic plug-ins insert rules and business logic along the path traveled by business messages as they make their way through the B2B engine. WebLogic Integration provides router and filter logic plug-ins for each business protocol. A service provider or trading partner can develop and install custom logic plug-ins to provide additional value in hub-and-spoke configuration (see "Message Mediation Models" In Getting Started with B2B Integration in Introducing B2B Integration).

Logic plug-ins are defined and stored in the WebLogic Integration repository and executed in the B2B engine. They are transparent to users.