This topic provides conceptual information about WebLogic and its Sun Java CAPS Adapter.
BEA defines WebLogic Server as a fully featured, standards-based, application server providing the foundation on which an enterprise builds its applications. More specifically, WebLogic Application Server is used to build Web applications that share data and resources with other systems, and then generate dynamic information for Web pages and other user interfaces.
WebLogic Application Server streamlines the process of building distributed, scalable, highly available systems by offering services that users previously had to write themselves, including connectivity, business logic, re-usability, security, concurrency (access is serialized), and transactionally (using XA to assure a successful transfer/update or rollback).
Other features offered by WebLogic include:
Object Pooling– conserves system resources by placing objects in a pool, so that the next request for the object does not require a re-allocation of memory.
Thread and Connection Pooling– works much the same way as Object Pooling to save memory and connection resources.
Clustering– allows easy movement or distribution of applications to other machines.
The WebLogic Adapter is an application specific Adapter that facilitates integration between applications built on the WebLogic platform and Sun Java CAPS ESB using the Enterprise Java Bean (EJB) component model (synchronous communication). The Adapter also provides an example of how to exchange JMS messages between WebLogic server and Sun Java CAPS ESB asynchronously.