# Plain Agent Use Case Example

# Introduction

Oracle WebLogic Operations Control (WLOC) is a management environment that can increase the efficiency of your operations center by hiding the complexity of the underlying operational environment and presenting the resources and Java applications in a simple supply-and-demand mode.

On the supply side of the equation, you use WLOC to organize the computing resources in your operations center into collections (pools) of resources. A WLOC resource pool can represent a single physical machine or a collection of virtualized resources that are made available through hypervisor software.

On the demand side of the equation, you use WLOC to organize Java applications (processes) into WLOC services. Typically, you organize a group of related processes into a single service and manage the group as a unit, but you can also create one service for each process.

A typical WLOC deployment contains a single WLOC Controller—the centralized component that gathers data about the operating environment—and multiple Agents that manage and monitor resources and communicate that information back to the Controller. A Plain Agent manages the computing resources for the physical machine on which the Agent is installed. The Controller hosts the WLOC Administration Console that enables you to visually configure, manage, and monitor the WLOC environment.

This document provides a basic use-case example for WLOC. In this use case we will describe the steps to:

- Establish a resource environment by installing and creating a Plain Agent and Controller.
- Establish the runtime environment by starting the Agent, Controller, and the WLOC Administration Console.
- Use the Administration Console to define a service to be managed.
- Deploy the service against the available resources.
- Monitor the WLOC service and the resource environment with the WLOC Administration Console.

## Main Steps

The following table summarizes the main steps demonstrated in this example.

Table 1-1 Use Case Example Main Steps
To complete this task . . . | We demonstrate how to perform the following steps . . .
--- | ---
Establish the WLOC resource environment | Step 1: Install WLOC Step 2: Create the Plain Agent Step 3: Create the Controller
Establish the WLOC runtime environment | Step 1: Start the Plain Agent Step 2: Start the Controller Step 3: Start the WLOC Administration Console
Define services under management | Step 1: Create the Service and Process Groups Step 2: Define the Adaptive Runtime Policies
Deploy services against available resources | Deployment Scenario Deploy the Service
Monitor WLOC services and resource environment with the WLOC Administration Console | Create a View Browse the Resources Pane

## Related Documents

The WLOC documentation set includes the following:

- Installation Guide—Describes how to install and uninstall the WLOC components.
- Plain Agent Use Case Example—This document.
- Configuration Guide—Describes how to configure and manage the WLOC Controller and Agents, configure services and policies to manage services, and configure security. It also describes how to use WLOC to monitor, log, and audit the operations of your services and resources.
- Securing a Production Environment—Highlights essential security measures for you to consider before you deploy WLOC into a production environment.
- WLOC Administration Console Help—The online help for WLOC’s graphical user interface. You can access the WLOC Administration Console Help either by clicking the Help link in the upper right corner of the Administration Console, or at http://download.oracle.com/docs/cd/E13156_01/wloc/docs103/ConsoleHelp.
- Controller Configuration Schema Reference—A reference to the XML schema used to persist the configuration of the WLOC Controller component.
- Agent Configuration Schema Reference—A reference to the XML schema used to persist the configuration of the WLOC Agent component.
- Service Metadata Schema Reference—A reference to the XML schema used to persist the configuration of WLOC services.
- Message Catalog—A reference to messages generated by WLOC.