April 2, 2020
Hot Topics:

BEA WebLogic 9.x New Features and Configuration Gems

  • By Vlad Kofman
  • Send Email »
  • More Articles »

Memory Considerations

Gem: Note the big difference in the memory requirements between 8.x and 9.x servers. If you want to decrease the memory for the admin server running the web configuration console, you need to change the mem_args parameter to the VM, in the shell script.

mem_args for WL9 in the startWeblogic script (or remote params for admin server in the web console)

set MEM_ARGS=-Xms64M

By default, the settings go up to 512mb—a bit large just to run one web app console.

Cluster configuration tips

WebLogic 9.x offers some of the best features for application clustering and failover among other application servers in the industry. The distributed WebLogic Server instances are controlled with the Node Manager utility. The Node Manager is an independent process, not associated with a specific WebLogic domain instance, but with a machine.

The node manager in WebLogic Server 9.x now can start, monitor, and restart Administration Servers. And, you can now use WLST commands to access Node Manager and to start, stop, and suspend server instances remotely or locally; obtain server status; and retrieve the contents of the server output log, without requiring the presence of a running Administration Server. In addition, you can configure the machine on which WLST is running to be monitored by the Node Manager.

If you are running a cluster or want to run one, the configuration is much easier with 9.x than with 8.x. Here is the example of how a cluster domain should look.

Click here for a larger image.

On the application level, you need to add a <distributable/> tag in the generic web.xml, and of course make sure all of your objects associated with user sessions are serializable.

Here is an example of Web.xml:

<?xml version="1.0" encoding="ISO-8859-1"?>

   "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"



      <display-name>Search Servlet</display-name>



Also, at the application level, you can indicate a replication parameter for cluster environment in the WebLogic's specific configuration file. The PersistentStoreType sets the persistent store method to one of the following options:

  • memory: Disables persistent session storage.
  • file: Uses file-based persistence (see PersistentStoreDir, above).
  • jdbc: Uses a database to store persistent sessions (see PersistentStorePool, above).
  • replicated: Same as memory, but session data is replicated across the clustered servers.
  • cookie: All session data is stored in a cookie in the user's browser.
  • replicated_if_clustered: If the Web application is deployed on a clustered server, the in-effect PersistentStoreType will be replicated. Otherwise, memory is the default.

Here is a sample of Weblogic.xml with this parameter:

<?xml version="1.0"?>

<!DOCTYPE weblogic-web-app
   PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"






This article talked about some of the configuration gems for the latest BEA WebLogic Sever 9.x that I personally found very useful. It discussed some of the most important new features and presented configuration gems on application, IDE, and the cluster level. The WebLogic 9.x includes a lot of evolutionally enhancements, in its architecture, web console, and overall structure that make it a very capable application server. It will be very interesting to see what BEA will introduce in the future releases.



About the Author

Vlad Kofman works on enterprise-scale projects for major Wall Street firms. He also has worked on the defense contracts for the U.S. government. His main interests are object-oriented programming methodologies, UI, and the design patterns.

Page 2 of 2

This article was originally published on October 18, 2006

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date