As expected with a major version, BEA has added an entire set of exciting new features and functionality in the new WebLogic Server 7.0. You will now take a look at these new features:
Smart Update installer WebLogic Server's new installation program includes a Smart Update feature. This is useful for searching for service packs, patches, and any new updates.
New security model The security model of WebLogic Server has been entirely revamped in version 7.0. The new security model provides support for the standardized Java Authentication and Authorization Service (JAAS) 1.0. The new design provides a set of Security Service Provider Interfaces (SSPI) that can be used by third-party tools, thereby enabling plug-and-play support.
Examples server The examples server that comes as part of the WebLogic Server has been improved in order to enable developers who are new to WebLogic Server to execute and view the sample applications easily.
Java Servlet 2.3 API The Java Servlet 2.3 API is supported by WebLogic Server. Web-enabled applications can now develop Java servlets that can utilize the new Java Servlet 2.3 API features, such as filters and listeners, apart from the standard HTTP protocol support.
JavaServer Pages 1.2 specification Web-enabled applications can now use the JavaServer Pages 1.2 specification in the JavaServer Pages of their application. WebLogic Server 7.0 now supports the new features of the JavaServer Pages 1.2 specification, such as custom tag libraries.
JDBC 2.0 API support New features of the JDBC 2.0 API are now supported by WebLogic Server 7.0. Advanced features such as batch updates and scrollable resultsets, as well as new data types such as STRUCT, ARRAY, and REFs of the JDBC 2.0 API, can now be used in applications deployed on WebLogic Server. Third-party JDBC drivers for MS SQL Server, Oracle, and Sybase are supplied along with WebLogic Server.
Java Naming and Directory Interface 1.2.1 WebLogic Server 7.0 provides its own implementation of naming and directory services, based on the JNDI Service Provider Interface (SPI) specification. This makes the naming and directory services implemented by WebLogic Server compatible with the JNDI specification, and thus any client application can access WebLogic naming and directory services using the JNDI API. The WebLogic Server 7.0 API supports the JNDI API version 1.2.1.
EJB 2.0 support WebLogic Server contains an EJB container that conforms to the EJB 2.0 specification. The EJB 2.0 support includes support for Session, Entity, and Message-driven Enterprise JavaBeans.
Enhancements to WebLogic Query Language (WLQL) The existing WebLogic Query Language extensions have been enhanced for the new EJB Query Language (EJBQL) introduced in the EJB 2.0 specification.
Java Message Service (JMS) 1.0.2 API WebLogic Server supports the Java Message Service API 1.0.2 specification. The Java Message Service API support enables developers to write messaging applications using both the point-to-point and the publish-subscribe models. Additionally, WebLogic Server contains a Java Message Service Bridge that can be used to integrate a JMS application deployed on WebLogic Server with a third-party JMS provider. An adapter for IBM MQSeries is also provided with WebLogic Server.
Java Transaction API (JTA) 1.0.1 The Java Transaction API, used for managing transactions for resources such as database connections and message queue connections, is supported in WebLogic Server. Hence, applications and components deployed on WebLogic Server can use the Java Transaction API for maintaining the integrity of the executed transactions.
Java API for XML Processing 1.1 Java brings together the SAX and DOM APIs in one single package. The Java API for XML Processing (JAXP) enables Java applications to parse XML documents and convert them into XML objects that can be processed by Java applications. JAXP brings together the divergent industry standard SAX and DOM APIs in one package that can be easily used by Java applications. Apart from the SAX and DOM XML parser APIs, JAXP also includes support for XML Stylesheet Language Transformation (XSLT).
J2EE Connector Architecture 1.0 Support for the new enterprise integration technology from J2EE the J2EE Connector Architecture (JCA) has been provided in WebLogic Server 7.0. WebLogic Server is fully compliant with the J2EE Connector Architecture 1.0 specification and enables applications deployed on WebLogic Server to access Enterprise Information Systems (EIS). Sample resource adapters (black box adapters) are also provided.
Web Services WebLogic Server 7.0 enables developers to migrate J2EE components as Web Services. Web Services are inherently complex to implement. WebLogic Server simplifies Web Service development and supports the Java API for XML-based RPC (JAX-RPC).
Web-based administration console The administration of WebLogic Server's various resources can easily be performed using the Web-based administration console in WebLogic Server. Administration of resources such as database connections, message queue connections, enterprise information system connections, and virtual host settings can easily be carried out using the Web-based administration console in WebLogic Server.
XML Inherent support for the Extended Markup Language (XML) is available in WebLogic Server. The two different APIs for parsing SAX API and DOM API are supported by WebLogic Server. In addition to this, WebLogic Server provides the XML Streaming API for parsing and processing XML files.
Clustering WebLogic Server 7.0 now enables setting up different WebLogic Server instances in a cluster on the same machine without requiring the machine to be multihomed, that is, having more than one IP addresses. A BEA WebLogic cluster is a group of WebLogic servers that work together transparently to improve availability and scalability. This is possible by assigning different multicast port numbers to the different WebLogic Servers in the cluster deployed on the same machine.
Improved management of server Apart from the standard administration activities, the Administration Console also provides facilities to monitor the performance of an up-and-running instance of WebLogic Server. This is in addition to the services provided to start and stop WebLogic Server instances.
You will now take a quick tour of some of the tools used in WebLogic Server 7.0.
