This document specifies the best practices, lessons learnt, and key considerations which help WebLogic Integration users such as application architects, developers, and operation staff to develop and run high quality WebLogic Integration (WLI) applications.
Note:
It is recommended that you read the following documents before you use this document:
While reading this document, you may have to refer to relevant documents and information about WLI 9.2, available on the WebLogic Integration documentation page.
WebLogic Integration is specially designed for enterprise integration. Figure 1-1 shows the architecture of WebLogic platform.
Figure 1-1 Architecture of WebLogic Platform
Features of WLI
WebLogic Integration provides you with the capability to design, develop, deploy and run integration-centric applications. The main features or capabilities of WebLogic Integration are:
Creates system (Java Process Definition) and human-centric (Task Plan) business process applications using an Eclipse-based unified IDE.
Defines system-centric transactional processes that have fine-grained control over the process using JPD graphical editor.
Defines human-centric, multi-step, task-oriented, and long running business processes using Task Plan graphical editor.
Uses standard-based Beehive controls to enable easier access to enterprise resources such as EJBs, JMS and web services. In most WLI applications, JPDs, controls, and Task Plans work with each other in realizing overall business objectives. They can be easily integrated with each other and remain loosely coupled.
Uses JPD controls and task plans that are property and annotation driven. Properties and annotations can be either static or dynamic. Dynamic properties can be changed during runtime which makes business processes that run with WLI applications agile and flexible.
Provides extensive support of Business to Business (B2B) capabilities for inter-enterprise business processes using Trading Partner Management, Rosettanet, ebXML, and EDI.
Creates loosely coupled, publish and subscribe architecture, style based process integration using event generators, message brokers, and event handlers.
Provides extensive Enterprise Application Integration features such as adapters, and XQuery (2004) based data transformation. The large number of integration controls such as service and process controls make the task of integrating enterprise resources easier.
Supports enterprise computing services support such as transaction management, clustering, security, and J2EE container services.
