> Use Case Example > Establish the WLOC Runtime Environment

Use Case Example

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Establish the WLOC Runtime Environment

Now that we have installed and configured the Plain Agent and the Controller to establish the resource environment for this example, we need to start each of them and the Administration Console. This will establish the runtime environment needed to define the service to be managed.

The tasks in this topic include:

 

Step 1: Start the Plain Agent

To start the Plain Agent:

  1. Open a Command Prompt window.
  2. Navigate to \bin of the directory in which we created the Plain Agent:
    3. C:\BEAHOME\user_projects\PlainAgent\bin
  3. Enter startAgent at the prompt.

As the Plain Agent starts, status messages are displayed in the Command Prompt window. After the start sequence is complete, the following information message is displayed in the window: 

<Mar 16, 2008 10:05:18 PM> <Info> <ServiceInspector> <All internal systems are now RUNNING.>

 

Step 2: Start the Controller

To start the Controller:

  1. Open a Command Prompt window.
  2. Navigate to \bin of the directory in which we created the Controller:
    3. C:\BEAHOME\user_projects\controller\bin
  3. Enter startController at the prompt.

As the Controller starts, status messages are displayed in the Command Prompt window. After the start sequence is complete and the Controller establishes the connection with the Plain Agent, the following information messages are displayed in the window: 

<Mar 16, 2008 10:08:25 PM> <Info> <ServiceInspector> <All internal systems are now RUNNING.>
STREAM: found system propertyweblogic.xml.stax.XMLStreamOutputFactory
<Mar 16, 2008 10:08:27 PM EDT> <Info> <OSGiLogReaderAdapter> <BEA-000000> <Bundle[141] com.bea.arc.u
i, Message (ServiceEvent.REGISTERED {objectClass=[com.bea.arc.ui.UserInterfaceService] , service.id=
123} ), Exception (null), Time (1205719707093)>
<Mar 16, 2008 10:08:27 PM EDT> <Info> <com.bea.core.tomcat.Activator> <BEA-000000> <SimpleBundle: Se
rvice of type com.bea.arc.ui.UserInterfaceService registered.>
<Mar 16, 2008 10:08:28 PM EDT> <Info> <Configuration> <BEA-2013535> <Successfully wrote file C:/BEAH
OME/user_projects/controller/agent-configuration-cache/PlainAgent-log-agent-config.xml.>
<Mar 16, 2008 10:08:28 PM EDT> <Info> <Configuration> <BEA-2013535> <Successfully wrote file C:/BEAH
OME/user_projects/controller/agent-configuration-cache/PlainAgent-log-agent-config.xml.>
<Mar 16, 2008 10:08:28 PM EDT> <Info> <ResourceBrokerCommon> <BEA-2012151> <Established connection w
ith WLOC Agent running at http://myhost.bea.com:8001.>
[AGENTS-HANDLING] : Getting the observer service for : http://myhost.bea.com:8001/AgentLumpe
rObserver
[AGENTS-HANDLING] : ObserverService URL = http://myhost.bea.com:8001/AgentLumperObserver
<Mar 16, 2008 10:08:28 PM EDT> <Info> <ResourceBrokerPool> <BEA-2012203> <ResourceBroker agent with
id plain-resource-pool - Registered>

 

Step 3: Start the WLOC Administration Console

To start the WLOC Administration Console:

  1. Open a Web Browser.
  2. Enter the following URL:
    3. http://localhost:9001/wloc-console
    Note: Because we are running the Controller on the local machine, we can use localhost. If the Controller was installed on a remote machine, you need to specify the host name for the machine hosting the Controller.
  3. In the Console Welcome window, enter the user name and password required to access the Controller. Because we accepted the defaults when we created the Controller, we enter the following values in this example:

    4. In this field   
    Enter the following     
    Username
    WLOCBootUser
    Password
    changeit



    After logging in successfully, the Home page of the WLOC Administration Console is displayed.



    Note that the Event Viewer at the bottom of the Console indicates that the resource pool, named plain-resource-pool, that we defined when we created the Plain Agent was discovered.

 

What’s Next?

After establishing the runtime environment, we need to define the service to be managed. For the steps in this process, go to Define the Service Under Management.


  Back to Top       Previous  Next