The WLS beans are used extensively by WLS components to manage configuration settings and to monitor and manage running servers.

The WLS beans are derived from Java interfaces. At runtime, WLS constructs internal trees of Java beans that can be used to configure and monitor the system. In prior releases, the bean trees were exposed only through JMX, WLST, and configuration files (for example, config.xml).

In this release, WLS dynamically generates the REST resources, incrementally and on-demand at runtime, by using the bean trees and bean infos. These REST resources provide an alternative for managing WLS.

The following sections provide the background information about WLS beans which provide the foundation for the REST interfaces.

There are two main bean types:

• Configuration: Used to configure WLS.

• Runtime: Used to monitor WLS and for some operations, control WLS (for example, starting and stopping servers, shrinking data source connection pools, and so on).

WLS provides the following bean trees:

• Edit access: Available only on the Administration Server, used to modify the configuration (for example, config.xml and system resource files).

• Runtime access: Available on every server, used to view that server's configuration and to access its monitoring data.

• Domain access: Available only on the Administration Server, contains copies of the runtime beans of all of the running servers, provides a single point of access for monitoring, is also used to view the most current configuration that has been persisted.

For more information about WLS MBeans, see Understanding WebLogic Server MBeans in Developing Custom Management Utilities Using JMX for Oracle WebLogic Server.

The Oracle WebLogic Scripting Tool (WLST) presents the bean trees as follows:

• edit: Matches the underlying edit access bean tree.

• domainConfig: The configuration MBean half of the domain access bean tree (such as, the last persisted configuration).

• domainRuntime: The runtime MBean half of the domain access bean tree (such as, for monitoring all servers).

• serverConfig: The configuration MBean half of the runtime access bean tree (such as, the configuration the server is using).

• serverRuntime: The runtime MBean half of the runtime access bean tree (such as, for monitoring a specific server).

The REST resources parallel the MBean trees presentation in WLST: edit, domainConfig, domainRuntime, serverConfig, and serverRuntime.

Within the WLS bean trees, there are several types of parent/child (containment) relationships:

• Writable collections: For example, a domain bean has a collection of server beans.

• Mandatory singletons: For example, a server bean always has an SSL bean which is automatically created and cannot be deleted.

• Optional singletons: For example, an overload protection bean can optionally have a server failure trigger bean.

Beans can include properties (generally scalars, strings, and arrays), references to other beans, and operations (for example, to start a server).

With regard to contained collections:

• Each child has a unique identity within the collection (for example, each network channel has a name that's unique within its server).

• Most collections are homogeneous (for example, a domain's applications) though a few are heterogeneous (for example, a security realm's authentication providers).

The Administration Server and each running Managed Server hosts a REST web application that runs on each server's administrative port. The context root for each is management. The root REST resources mimic the bean trees in WLST.

Table 2-1 describes the root resources on the Administration Server and lists the corresponding bean tree.

Table 2-2 describes the root resources on Managed Servers.

The URLs on Managed Servers are exactly like the ones on the Administration Server, except that the host and port are different.

For example, the URL to view the Administration Server's server runtime:

curl ... -X GET http://adminHost:7001/management/weblogic/latest/serverRuntime

The URL to view a Managed Server's server runtime:

curl ... -X GET http://managed1Host:7002/management/weblogic/latest/serverRuntime

• Strings and Scalars
  
• Arrays
  
• Identities
  
• WLS Bean References
  
• java.util.Properties
  
• Encrypted Properties
  

[ "machines", "Machine-0" ]

{
  machine: [ "domain", "machines", "Machine-0" ],
  links: [
    { rel: "machine", href: "http://localhost:7001/management/latest/weblogic/edit/machines/Machine-0" }
  ]
}

{
  candidateMachines: [
    {
      identity: [ "machines", "Machine-0" ],
      links [ { rel: "canonical", href: "http://localhost:7001/management/weblogic/latest/edit/machines/Machine-0"
    },
    {
      identity: [ "machines", "Machine-1" ],
      links [ { rel: "canonical", href: "http://localhost:7001/management/weblogic/latest/edit/machines/Machine-1"
    }
  ]
}

{
  "property1": "value1",
  "property2": "value2"
}