BEA WebLogic is a J2EE application server and also an HTTP web server by
BEA Systems of San Jose, California, for Unix, Linux, Microsoft Windows, and
other platforms. WebLogic supports Oracle, DB2, Microsoft SQL Server, and other
A D V E R T I S E M E N T
WebLogic Server supports WS-Security and is compliant
with J2EE 1.3.
BEA WebLogic Server is part of the BEA WebLogic Platform™. The
other parts of WebLogic Platform are:
- Portal, which includes Commerce Server and Personalization Server (which
is built on a BEA-produced Rete rules engine),
- WebLogic Integration,
- WebLogic Workshop, an IDE for Java, and
- JRockit, a JVM for Intel CPUs.
WebLogic Server includes .NET interoperability and supports the
following native integration capabilities:
- Native enterprise-grade JMS messaging
- J2EE Connector Architecture
- WebLogic/Tuxedo Connector
- COM+ Connectivity
- CORBA connectivity
- IBM WebSphere MQ connectivity
BEA WebLogic Server Process Edition also includes Business Process Management
and Data Mapping functionality.
WebLogic supports security policies managed by Security Administrators. The
BEA WebLogic Server Security Model includes:
- Separate application business logic from security code
- Complete scope of security coverage for all J2EE and non-J2EE components
WebLogic, Inc., was founded by Paul Ambrose, Bob Pasker, Laurie Pitman, and Carl
Resnikoff, in September, 1995.
Up until then, Paul and Carl had been developing (pre-JDBC) Oracle, Sybase, and
Microsoft SQL Server database drivers for Java under the name dbKona, as well as
a "three tier" server to permit applets to connect to these databases. An old
dbKona/An T3 Usenet posting. This was the WebLogic 1.48 server, and was called
T3Server (a bastardization of 3-Tier Server).
Concurrently, Laurie and Bob had been working on network management tools in
Java. Bob had written a SNMP stack in Java and a W32 native method for ICMP
ping, while Laurie worked on applets to display the management data.
One of the hidden features of the 1.48 server version was the ability to extend
it by modifying a dispatcher and adding a handler for different types of
messages. Bob talked Paul into sending him the source code for the server, and
Bob extended it so that Applets could make SNMP and PING requests on the
network, and display the results.
At this point, the founders worked together to pursue what was eventually to be
called the Application Server.