Abstract: Business logic plug-ins can be implemented as Java classes that perform specialized processing of business messages as those messages pass through an integration engine, such as a “B2B” engine for business-to-business messaging. Logic plug-ins can insert rules and business logic along the path traveled by business messages as they make their way through the B2B engine. Logic plug-ins can be defined and stored in an integration repository and executed in the B2B engine, and can be transparent to users. The plug-ins can utilize a plug-in framework, composed of a plug-in manager, as well as interfaces and mechanisms for plug-ins to implement. A plug-in manager can manage all plug-ins in the framework, can be a concrete implementation of the plug-in framework on the server, and can be a central hub through which all plug-in related client requests are routed. This description is not intended to be a complete description of, or limit the scope of, the invention.

Abstract: A plug-in framework can be used in an integration system to extend business process management functionality. A plug-in manager, which can be part of an integration process engine, is used to support configuration, design, and run-time management of the plug-ins. A plug-in API is used to provide support for configuration, design, and run-time interactions between the process engine and a deployed plug-in. The plug-in API can consist of components such as session beans, run-time management classes, and packages. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: A system and method for using session beans to integrate business processes. The system includes a process engine which includes a workflow and a plug-in manager. The system further allows for creating session beans, packaging the session beans for deployment, and deploying the session beans to the process engine as a plug-in, to dynamically modify the workflow. The plug-in manager handles event notifications to and from the deployed session beans at runtime, according to the workflow. In this manner, the environment allows for easy development of software applications that are intended to communicate with business processes and external components.

Abstract: A plug-in framework can be used in an integration system to extend business process management functionality. A plug-in manager, which can be part of an integration process engine, is used to support configuration, design, and run-time management of the plug-ins. A plug-in API is used to provide support for configuration, design, and run-time interactions between the process engine and a deployed plug-in. The plug-in API can consist of components such as session beans, run-time management classes, and packages.

Abstract: Business logic plug-ins can be implemented as Java classes that perform specialized processing of business messages as those messages pass through an integration engine, such as a “B2B” engine for business-to-business messaging. Logic plug-ins can insert rules and business logic along the path traveled by business messages as they make their way through the B2B engine. Logic plug-ins can be defined and stored in an integration repository and executed in the B2B engine, and can be transparent to users. The plug-ins can utilize a plug-in framework, composed of a plug-in manager, as well as interfaces and mechanisms for plug-ins to implement. A plug-in manager can manage all plug-ins in the framework, can be a concrete implementation of the plug-in framework on the server, and can be a central hub through which all plug-in related client requests are routed.

Abstract: A plug-in framework can be used in an integration system to extend business process management functionality. A plug-in manager, which can be part of an integration process engine, is used to support configuration, design, and run-time management of the plug-ins. A plug-in API is used to provide support for configuration, design, and run-time interactions between the process engine and a deployed plug-in. The plug-in API can consist of components such as session beans, run-time management classes, and packages.