Friday Nov 01, 2013

Drink Milk or Got a Pet? Watch what IDEXX Laboratories and Oracle do for you

IDEXX Laboratories is the global market leader in diagnostics and IT for animal health [with 50,000 veterinary practices worldwide], and water and milk quality. Watch this video where Brett Curtis, Senior System Administrator from IDEXX, discusses their business applications and laboratory information management systems. IDEXX uses Oracle WebLogic Server, SOA Suite, Coherence, Enterprise Manager and more. Enterprise Manager is used to manage their entire stack and has enabled IDEXX to achieve an astounding 90% reduction in time to find root cause of problems in their application infrastructure.

Wednesday Jul 24, 2013

New Node Manager Configuration Model

Join the Online Launch Event for WLS 12.1.2 on July 31st.

 In WebLogic Server 12.1.2, we have a great new option for configuring and running the Node Manager: by default, Node Manager is now configured with the domain.

We listened!

In recent months, we’ve heard that customers typically manage Node Manager instances with their domains. That is, they install, upgrade, and run Node Manager instances along with the domains where they host their applications. Also, in most cases, it is the same users who manage Node Manager instances along with related domains. The configuration model for Node Manager in previous releases – sharing Node Manager instances across domains – can be more complicated because different groups in the organization upgrade, patch, and have downtime on different schedules.

We listened, and now the default configuration for Node Manager is a Node Manager instance per domain on each of your Managed Server hosts. 

Per-Domain Node Manager Diagram

With this new configuration option, you can now:

  • Align Node Manager lifecycle management with the domains that it manages and monitors
  • Simplify Node Manager configuration through Configuration Wizard/WLST offline and Pack/Unpack commands
  • Maintain your WebLogic installation directory as a read-only directory (Node Manager configuration is now stored with the domain.)

Configuration Wizard Changes

When you create a domain using either WLST or the Configuration Wizard, Node Manager is configured for use with that domain. When I say “configured for that domain,” I mean that:

  • There is a <domain>/nodemanager folder that includes the Node Manager configuration files (,
  • There is a startNodeManager script in the <domain>/bin directory
  • In the <domain>/security folder, there is a domain-specific and host-specific DemoIdentity.jks keystore used by the Node Manager for OOTB evaluation and demonstrations

In other words – everything you need to run the Node Manager for the domain is set up for you and is encapsulated in the domain! 

Extending Your Domain with Pack/Unpack

We’ve also made it easier to set up Node Manager for the Managed Servers in your domain:

  • When you use the “pack” command with the “-managed=true” option, the configuration framework includes changes to the file in the template file.
  • When you use the “unpack” command on the remote host where you want to run your Managed Servers, the configuration framework sets up the domain, regenerates the file, generates a file (no need to run nmEnroll!), generates a DemoIdentity.jks keystore, and generates a startNodeManager script.

Out of the gate, you are ready to go with a per-domain Node Manager configuration for each host where you will run your Managed Servers.

Give it a try! 

More Information

Don’t forget to register for the WebLogic Server 12.1.2 Online Launch Event on July 31st.

You can also see the following links:

Wednesday Aug 15, 2012


Recently, I had a question about using offline WLST to create a Capacity Constraint in a WebLogic Server configuration. The tricky part is that Constraint MBeans (and resulting configuration) are children of the SelfTuning MBean at the domain level, but the SelfTuning MBean is not listed in the configuration file by default. This behavior is the result of an optimization in WebLogic Server where the configuration file only explicitly lists objects and attributes that are defined. It does not list objects or attributes that completely governed by defaults. Take a look at the documentation at, which says:

"As a performance optimization, WebLogic Server does not store most of its default values in the WebLogic domain's configuration files. In some cases, this optimization prevents management objects from being displayed by WLST offline (because WebLogic Server has never written the corresponding XML elements to the domain's configuration files). For example, if you never modify the default logging severity level for a WebLogic domain while the domain is active, WLST offline will not display the domain's Log management object.

If you want to change the default value of attributes whose management object is not displayed by WLST offline, you must first use the create command to create the management object. Then you can cd to the management object and change the attribute value."

To create a Constraint object, you must first create the SelfTuning object. Here's an example that creates a new domain and then adds a Capacity Constraint to it:

C:\Oracle10.3.6\Middleware\user_projects>java weblogic.WLST

wls:/offline> createDomain('C:/Oracle10.3.6/Middleware/wlserver_10.3/common/templates/

wls:/offline> readDomain('wkmgr_domain3')


Proxy for st: Name=st, Type=SelfTuning



Proxy for myCapacityConstraint: Name=myCapacityConstraint, Type=SelfTuning!




drw-   myCapacityConstraint



-rw-   DeploymentOrder                               1000

-rw-   Name                                          myCapacityConstraint

-rw-   Notes                                         null

-rw-   Target                                        null



That's it!

Happy scripting!


The official blog for Oracle WebLogic Server fans and followers!

Stay Connected


« November 2015