Other features in BEA WebLogic are also best suited to larger enterprises. With Java Database Connectivity (JDBC) connection pools, a WebLogic Server can dynamically create, alter and destroy JDBC connection pools, allowing the system to adjust and allocate resources as needed.

BEA WebLogic ships with native JDBC drivers for Oracle, Sybase, Informix and Microsoft SQL Server, as well as with a generic driver for any JDBC-compliant database. The presence of native drivers—as opposed to a generic driver—distinguishes BEA WebLogic from other application servers that rely on generic JDBC drivers. In addition, BEA WebLogic works with all major Web servers, including the Apache HTTP Server. (We tested BEA WebLogic on a Slackware Linux system running Apache.)

The main difference between BEA WebLogic Server and most of the other application servers on the market is that BEA WebLogic Server is not closely tied to a proprietary application development environment from a single manufacturer. Instead, it is tied closely to Symantec's Visual Café Enterprise Suite (which also emphasizes EJB via the development side), and allows easy integration with IBM VisualAge, Microsoft Visual J++, and Borland JBuilder.

BEA WebLogic Server remains a leading player in the application server field. With the new clustering technology and advanced EJB support, enterprises looking for an e-commerce solution should look carefully at BEA WebLogic Server, particularly if they have already made a commitment to Java.

« Back: Implementing an Enterprise-Quality App Server Under Linux