An introduction to WebLogic Server 6.0 for Linux
Discover the features new to 6.0, plus much more
SummaryShari Jones EA Systems' release of WebLogic Server 6.0 for the Microsoft Windows, Sun Solaris, and HP-UX operating systems in December 2000 added a host of new capabilities to the Java2 Enterprise Edition (J2EE) application server. WebLogic Server is one of the most widely used J2EE application servers in the enterprise application development market. In February the Linux version quickly followed the release of WebLogic Server 6.0 for other platforms.
This article provides a brief overview of the new features in version 6.0 and examines what these changes mean for developers and administrators. It also details some installation and configuration guidelines under Linux.
To cover the complete functionality of WebLogic Server 6.0 is beyond the scope of this article, so refer to the BEA WebLogic Server documentation site for detailed procedures (see Resources for a link).
New and improved features
WebLogic Server 6.0 contains the following new features:
Both WebLogic Server Version 5.1 and the previous version (4.5) ran on a Win32 platform and any non-Win32 platforms, provided that a fully compliant Java Virtual Machine (JVM) was available for that platform. With the new WebLogic Server 6.0, BEA has chosen to bundle the JVM for each supported platform with the server software. Therefore, instead of offering the previous Win32 and non-Win32 versions, BEA now has separate Win32, Solaris, HP-UX, and Linux versions.
Installing WebLogic Server 6.0
Downloading WebLogic Server 6.0 is straightforward and much the same as doing so with previous versions, except that you specify the operating system to which you are downloading. To download WebLogic Server 6.0 from the BEA Website, click the Download link on the main BEA homepage (see Resources for a link) to take you to BEA's Download Center. Click BEA WebLogic Server and then select from the Linux list. A page displays details of the download. You will need to scroll to the bottom of the page and click Proceed to Download. You will then need to login (registration is free), and accept the license agreement.
After downloading WebLogic Server, at the Linux command prompt, change
to the directory to which you downloaded the WebLogic Server software for
Linux. You can perform either a console installation (text only) or a GUI
installation (if running X Window System). To perform a console
When installing WebLogic Server 6.0, the software prompts you to specify a BEA home directory. The BEA home directory is a repository of common files used by multiple BEA products that are installed on the same machine. It is different than the download directory, which can be whatever the user wants it to be. The following components are installed in the BEA home directory as part of the download:
In that path, "beahome" is the BEA home directory in which the WebLogic Server software was installed, and "mydomain" is the domain name specified during installation.
Type the following command at the prompt to start the default server:
The variable parts of the URL include the host and the port. The host is the machine on which the WebLogic Server software runs. Note that you can use localhost if WebLogic Server is running on the same machine as the browser. The port is the address of the Listen Port entered during installation. The default port is 7001.
When starting the console, a username and password to login to the
server are required. Type
Developing under WebLogic Server 6.0
Developers will like the improved deployment features of WebLogic Server 6.0 during their application design, development, and testing. WebLogic Server's implementation of Web applications makes it very easy to deploy and test, then redeploy and retest components during development.
Users of earlier versions of WebLogic Server will be familiar with the extensive server message output at startup. WebLogic Server, by default, now hides those messages so the server will start up faster. Version 6.0 still outputs the messages to the log file as before. Additionally, with the new console and the latest developments in the server, there is less need to restart the server during development.
For an overview of development with J2EE and WebLogic Server, refer to Steven Gould's article in December's JavaWorld (see Resources for a link).
Configuring the server
First, start the default server, then the console. You must start the server before starting the console. The default server is a standalone server that uses settings configured during installation. Administrators can use the console to configure and customize the server with a browser-based GUI.
Creating a server
In the right panel, click the Install a New EJB link to install a new EJB. After installing an EJB, in the right panel, click the link for Configure a New EJB. You then have the options to configure, set targets, and create notes during deployment. Use the Configuration tab to name the EJB, assign the URL and assign the path. Before proceeding, click the Create button to create the new EJB. You will not have access to the other configuration tabs until the EJB is created. Next, deploy the EJB.
To deploy an EJB, select from the list the server on which you want to deploy the EJB. Click the Deployments tab, and select the EJB you want to deploy from the Available column. Use the right arrow to move one or more EJBs to the Chosen column, and apply the changes.
Configure a new servlet under the Deployments section of the administration console, and select Web Applications. The right panel displays a link for Configure a New Web Application. You then have the options to configure, set targets, and create notes during servlet deployment.
After you have created and configured a servlet and want to deploy it, bundle the servlet inside the Web application. Next, select from the list the server on which you want to deploy the Web application. Select the Web application you want to deploy and use the right arrow to move the application to the Chosen column, and apply the changes.
To define JDBC data sources, use the Services option in the left panel of the administration console. Under JDBC, you can select Data Sources to access the Create a New JDBC Data Source link. You can then define a new JDBC data source by completing the Configuration tab and clicking the Create button. You must also define the targets for the data source.
Creating, configuring, and deploying JDBC connection pools are also an important part of deploying JDBC. In the same part of the administration console, you can select Connection Pools to access the Create a New JDBC Connection Pool link. You then can create and configure a new JDBC connection pool.
After creating and configuring the JDBC connection pool, you can assign it to a Web server by selecting the server in the left panel of the console. From the Available column, you can select one or more JDBC connection pools that you want to assign to the server and move the JDBC connection pools you selected to the Chosen column. You must click Apply to save the assignments.
Under JDBC Services in the administration console, you also can assign Multi-Pools (new in Version 6.0) and Tx Data Sources.
Administering the server
Use the administration console in WebLogic Server 6.0 to monitor and change configurations. You access the monitoring views from Servers on the left side of the administration console. After selecting the server you want to monitor, you can select the Monitoring tab and choose a number of ways to monitor servers. WebLogic Server 6.0 provides numerous ways to monitor servers, services, and Web applications, including:
Special thanks to Steven Gould for his expertise and contributions to this article.