> Overview of WebLogic Integration > Integration with Back-End Systems

Overview of WebLogic Integration

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Integration with Back-End Systems

BEA SmartConnect provides native connectivity to Enterprise Resource Planning (ERP) systems from AquaLogic Service Bus (ALSB).

WebLogic Integration (WLI) leverages SmartConnect 2.6 through AquaLogic Service Bus (ALSB) 2.6 RP1 by using standard protocols such as web services, JMS, and HTTP. You can use the control mechanism of WLI to connect to ALSB. In addition, you can leverage the tighter integration between WLI 10.2 and ALSB 3.0 to connect to ERP systems.

For more information about SmartConnect 2.6, see BEA SmartConnect 2.6 Documentation. For more information about integration between WLI 10.2 and ALSB 3.0, see Integration with AquaLogic Service Bus.

Note: In the past, WLI supported Application View controls to access J2EE Connection Architecture (JCA)-based adapters built on the Application Integration (AI) framework of WLI. The AI framework was deprecated in WLI 9.2 and is discontinued in WLI 10.2. JCA adapters are still supported, but customers using AI-based adapters are encouraged to start using SmartConnect 2.6 for connectivity with SAP and Siebel applications.

The following table summarizes the application integration features of WLI.

Table 11-1 Application Integration Features
Feature
Description
Application Integration
  • BEA SmartConnect provides the native integration to ERP systems of SAP and Siebel.
  • Standards-based architecture for hosting J2EE CA-based adapters.
Adapters
  • J2EE CA 1.0-based adapter infrastructure with extensions.
  • Service adapters expose application services to WLI.
  • Event adapters publish asynchronous, unsolicited messages from the application to the message broker.
XML Metadata Cache Management
  • The XML metadata cache is a global, domain-wide cache. Data stored in this cache can be accessed by any business process that is deployed in the domain. You can use the cache to share data within a cluster. You can manage the cache through the WLI administration console or by using the MBean API, with which you can create your own NetUI-based consoles.
  • The XML metadata cache stores configuration data in the form of key-value pairs, where the key is of type String and the value contains XML data. Data from the cache is made available permanently through file-based storage.
  • A new XML metadata cache file is created for each XML document that is added to the cache.
  • WLI provides an XML metadata cache control, which you can use in business processes to retrieve data from the cache. The control uses the key (from the key-value pair) to retrieve associated XML metadata from the cache.
For more information, see XML Cache in Using the WebLogic Integration Administration Console.


  Back to Top       Previous  Next