
	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	e-docs.beasys.com \| Site Map \| Search \| PDF Files \| Contact \| Glossary

WLE Doc Home \| Getting Started \| Previous \| Next \| Contents \| Index

Overview of the WLE Product

The BEA WebLogic Enterprise (WLE) product allows you to build, deploy, and manage component-based solutions for your enterprise. WLE brings together the Object Request Broker (ORB) and online transaction processing (OLTP) functions with industry programming models such as ATMI, CORBA, and EJB. The result is a platform that enables you to deliver scalable, secure, and transactional e-commerce applications in a well-managed environment.

The WLE product now lets you add Enterprise JavaBeans (EJBs) to your existing WLE applications.WLE CORBA objects and EJBs share the same WLE transaction, security, configuration, and monitoring infrastructure. Therefore, you can write transactions that span TUXEDO services, CORBA objects, and EJBs. In addition, the WLE product supports client applications built using Remote Method Invocation (RMI). RMI provides a pure Java application programming interface (API) for accessing remote objects. Using RMI, client applications can directly access EJBs.

WLE CORBA objects use the Object Management Group (OMG) Internet Inter-ORB Protocol (IIOP) in a WebLogic Enterprise environment. IIOP is the standard protocol for communications running on the Internet or on an enterprise's intranet. The WLE product has a native implementation of IIOP, ensuring high-performance, interoperable, distributed-object applications for the Internet, intranets, and enterprise computing environments.

Figure 1-1 illustrates the WLE product.

Figure 1-1 WLE Product

The WLE product provides:

A set of integrated components that can be used to build robust, distributed e-commerce applications. These components can be accessed from C++, Java, COM, or RMI client applications.
A choice of server-side components. One or more EJB, RMI, CORBA Java, CORBA C++, or TUXEDO ATMI server-side components can be deployed in a single WLE application.
Interoperability with third-party vendor CORBA ORB products. IIOP-compliant ORBs may send client requests to a WLE application.
Access to databases via a Java API is provided with JDBC drivers for Oracle and Microsoft SQL server databases. A JDBC-XA driver is provided for Oracle 8.1.5 databases. These drivers can also be deployed in a more optimal manner using the WLE connection pooling feature.
A Management Information Base (MIB) that defines the key management attributes of WLE applications.
Support for the Java Naming and Directory Interface (JNDI) used for finding and registering EJB Home objects and RMI objects.
Support for the CORBA and Java transaction services to ensure the integrity of your data even when transactions span multiple programming models, databases, and applications.
A security service that handles authentication for principals that need to access resources in a CORBA or EJB server environment. Access control lists (ACLs) are also provided for EJBs in your WLE application.
An interface repository that stores meta information about WLE CORBA objects. Meta information includes information about modules, interfaces, operations, attributes, and exceptions.
Dynamic Invocation Interface (DII) support. DII allows WLE CORBA client applications to dynamically create requests for objects that were not defined at compile time.

The topics in Getting Started describe the CORBA and EJB programming environments of the WLE product and the development process for building a transactional application using either programming environment.