This section describes the Controller, Plain Agent, and ESX Agent configurations.
Controller
The WLOC Controller configuration settings control the behavior of the Controller and how it communicates with the WLOC Agents.
The initial Controller configuration is defined by running the WLOC configuration wizard. This process stores the configuration settings in an XML file that is used to establish the Controller’s runtime configuration at startup. The XML file is named loc-controller-config.xml and is located in the following directory:
After the creation of the XML file, the Controller configuration can be changed using the WLOC administration console, by directly editing the XML file, or by re-running the configuration wizard. Modifications made using the administration console take immediate effect, while changes made using the other two methods do not take effect until the Controller is restarted.
Changes to a Controller configuration using the configuration wizard or the administration console are captured in the Controller’s audit log located in the BEA_HOME\user_projects\controller\logs directory, where user_projects is the directory specified while running the configuration wizard.
Agent
A WLOC Agent configuration controls the behavior of the Agent and how it communicates with the WLOC Controller and the managed application. An Agent is required to managed each resource pool in the WLOC environment. The Agent discovers information about the resources available and maintains that information in its configuration.
There are two types of Agents:
Plain Agent—a plain Agent manages a resource pool on a physical machine. Configuration settings include the amount of CPU to allocate for WLOC and path names to software that is available to WLOC services.
ESX Agent—an ESX Agent manages a resource pool on a virtual machine that has been configured by hypervisor software. The Agent communicates with the ESX server to discover the capabilities of the resource pool and allocates all resources in the resource pool as WLOC resources. ESX Agent configuration information includes the path to available ISO images and NFS shares.
An Agent configuration is stored in an XML file named loc-agent-config.xml located in the BEA_HOME\WLOC_HOME\user_projects\agent1\config directory, where agent1 is the directory where the agent was installed.
The creation of an Agent instance and its initial configuration must be performed with the WLOC Configuration Wizard. Thereafter, the configuration can be modified using the Administration Console or by directly editing its configuration file.
Changes to an Agent configuration using the administration console are captured in the Agent’s audit log located in the BEA_HOME\user_projects\agent1\logs directory, where user_projects\agent1 is the directory specified while running the configuration wizard.
Agent Configurations
This sections provides step-by-step instructions for running the configuration wizard in GUI mode. For performing silent-mode configurations, see Appendix A.
Note:
Running the configuration wizard in console mode is currently not supported.
Configuring a Plain Agent
Follow these steps to create a plain Agent instance and its initial configuration:
Invoke the configuration wizard described in Table 3-1.
Table 3-1 Invoking the Agent Configuration Wizard
Platform
Command
Windows
BEA_HOME\WLOC_HOME\common\bin\config.cmd
Note: You may also select WebLogic Operations Control 1.0>WLOC Configuration Wizard from the Windows Start Menu.
UNIX or Linux
BEA_HOME/WLOC_HOME/common/bin/config.sh
On the Choose Agent or Controller window, select Create a new Agent... and click Next.
On the Enter Agent Directory Location window, accept the default location or specify a different directory and click Next.
On the Configure Agent Connection Details window, complete the fields as described in Table 3-2.
Table 3-2 Configure Agent Connection Details
Field
Description
Agent Name
Specify a unique Agent name.
Note:
Managing multiple Agents through the Administration Console requires that each Agent has a unique name.
Agent Host
Fully-qualified host name where the Agent resides; example: agentbox.east.example.com.
Agent Port
Agent’s HTTP port number used when communicating with the Controller in unsecure mode; default: 8001.
Note:
In the unlikely event you are configuring more than one Agent on the same host, be sure that each Agent uses different port numbers.
Agent Secure Port
Agent’s HTTPS port number used when communicating with the Controller in secure mode; default: 8002.
Note:
In the unlikely event you are configuring more than one Agent on the same host, be sure that each Agent uses different port numbers.
Agent Passphrase/ Confirm Agent Passphrase
Passphrase used to apply encryption beyond the Security Mode setting to certain sensitive data passed between the Controller and Agent. The password must be a minimum of 8 characters.
If Security Mode is Unsecure, this setting will still encrypt the most sensitive data.
Note:
This passphrase must be entered when adding the Agent to the Controller or communication between the Controller and Agent will fail.
For development environments, it is sufficient to accept the defaults. You do not need to know these passphrases.
Security Mode
Select a security mode for connections with the Controller.
Unsecure — sufficient for development. Secure — should be used for production environments.
Secure mode ensures confidentiality and integrity of the communication and requires setting up trust as an explicit step between the Controller and the Agent.
NOTE: Both the Controller and Agent must be set to the same security mode.
On the Configure Agent Logging window, complete the fields as described in Table 3-3.
Table 3-3 Configure Agent Logging
Field
Description
Logfile severity
Severity of events to log, default: INFO
In the order of severity from least severe to most severe, the log levels are:
On the Configure Agent Keystore Passwords window, you are prompted for the Agent keystore passwords used for internal WLOC communications. In most cases, this depends on whether you are using WLOC in a production or development environment, as described in Table 3-4. Click Next after completing thew window.
Table 3-4 Configure Agent Keystore Passwords
Environment
Description
Development
Click Next to use the default keystores passwords.
Production
Enter the passwords that will be used to secure the keystores used for production-level communications between WLOC components. Make a note of these passwords. They will be required later when setting trust by importing certificates into the keystores.
For more information about the WLOC Agent keystores,
see
Keystores.
On the Configure Agent Type window, select Plain Agent and click Next.
On the Configure Plain Agent (1 of 2) window, complete the fields as described in Table 3-5 and click Next.
Table 3-5 Plain Agent Configuration (1 of 2)
Field
Description
Resource Pool Name
Enter a unique name for the resource pool managed by the Agent.
Note:
Managing multiple resource pools through the Administration Console requires that each resource pool has a unique name.
Description
An arbitrary description of the resource pool. This description appears in the console.
CPU capacity (MHz)
(Optional) CPU capacity (in normalized megahertz) available to the resource pool.
Stdout directory
Specify a directory under user_projectsfor the JVM stdout output stream.
Default: BEA_HOME\user_projects\agent1\stdout
Stderr directory
Specify a directory under user_projects for Stderr the output stream.
Default: BEA_HOME\user_projects\agent1\stderr
On the Configure Plain Agent (2 of 2) window, specify each available software instance by clicking Add and completing each field as described in Table 3-6. When done, click Next.
Note:
You may skip this step and use the Administration Console to provide the information at a later time.
Table 3-6 Configure Plain Agent (2 of 2)
Field
Description
Name
Name for the software as it will appear in the console.
Description
An arbitrary description of the software as it will appear in the console.
Path
The complete path to the directory containing the software. For a Weblogic domain, specify the path to the domain.
On the Create Agent Configuration window, click Create. Progress messages then appear.
When it becomes active, click the Done button.
Configuring an ESX Agent
Follow these steps to create an ESX Agent instance and its initial configuration:
Note:
Running the configuration wizard in console mode is currently not supported.
Invoke the configuration wizard described in Table 3-7.
Table 3-7 Invoking the Configuration Wizard
Platform
Command
Windows
BEA_HOME\WLOC_HOME\common\bin\config.cmd
Note: You may also select WebLogic Operations Control 1.0>WLOC Configuration Wizard from the Windows Start Menu.
UNIX or Linux
BEA_HOME/WLOC_HOME/common/bin/config.sh
On the Choose Agent or Controller window, select Create a new Agent... and click Next.
On the Enter Agent Directory Location window, accept the default location or specify a different directory under user_projects and click Next.
On the Configure Agent Connection Details window, complete the fields as described in Table 3-8.
Table 3-8 Configure Agent Connection Details
Field
Description
Agent Name
Agent name. The Administration Console displays this as the Agent name.
Agent Host
Fully-qualified host name where the Agent resides; example: agentbox.east.example.com.
Agent Port
HTTP port number used when the Agent and Controller are connecting in unsecure mode; default: 8001.
Note:
In the unlikely event you are configuring more than one Agent on the same host, be sure that each Agent uses different port numbers.
Agent Secure Port
HTTPS port number used when the Agent and Controller are connecting in secure mode; default: 8002.
Note:
In the unlikely event you are configuring more than one Agent on the same host, be sure that each Agent uses different port numbers.
Agent Passphrase/ Confirm Agent Passphrase
Passphrase used to apply encryption beyond the Security Mode setting to certain sensitive data passed between the Controller and Agent. The password must be a minimum of 8 characters.
Even if Security Mode is Unsecure, this setting will encrypt the most sensitive data.
Note:
This passphrase must be entered when adding the Agent to the Controller or communication between the Controller and Agent will fail.
For development environments, it is sufficient to accept the defaults. You do not need to know these passphrases.
Security Mode
Select a security mode for connections with the Controller.
Unsecure — sufficient for development. Secure — should be used for production environments.
Secure mode ensures confidentiality and integrity of the communication and requires setting up trust as an explicit step between the Controller and the Agent. Securing Controller to Agents Communication.
NOTE: Both the Controller and Agent must be set to the same security mode.
On the Configure Agent Logging window, complete the fields as described in Table 3-9.
Table 3-9 Configure Agent Logging
Field
Description
Logfile severity
Severity of events to log, default: INFO
In the order of severity from least severe to most severe, the log levels are:
On the Configure Agent Keystore Passwords window, you are prompted for the Agent keystore passwords used for internal WLOC communications. In most cases, this depends on whether you are using WLOC in a production or development environment, as described in Table 3-10.
Table 3-10 Configure Agent Keystore Passwords
Environment
Description
Development
Click Next to use the default keystore passwords.
Production
Enter the passwords that will be used to secure the keystores used for production-level communications between WLOC components. Make a note of these passwords. They will be required later when setting trust by importing certificates into the keystores.
For more information about the WLOC Agent keystores, see Keystores.
On the Configure Agent Type window, select ESX Agent and click Next.
On the Configure ESX Agent (1 of 6) window, complete the fields as described in Table 3-11 and click Next.
Table 3-11 Configure ESX Agent (1 of 6)
Field
Description
Name
Accept the default name or enter a different one.
Description
Accept or modify the default.
On the Configure ESX Agent (2 of 6) window, complete the fields as described in Table 3-12 and click Next.
Table 3-12 Configure ESX Agent (2 of 6)
Field
Description
Virtual Center Host
The IP address or name of the VirtualCenter Server.
Username
The user name of a VirtualCenter administrator.
Password/Confirm Password
The administrator’s password.
VMWare SSL Certificate
Select the Connect to the Virtual Center to retrieve SSL certificate checkbox.
When selected, the Virtual Center’s public key certificate is obtained and added to the ESX Agent’s trust keystore. This is needed to establish trust between an ESX Agent and Virtual Center.
ESX Agent Configuration Type - Dynamic or Static
Select the Configure the ESX Agentdynamically... checkbox if you want the wizard to connect to the Virtual Center host and obtain information for the remaining configuration windows. Otherwise, you will be required to manually enter this information.
Accept the default selection of the Use secure connection... checkbox if the Virtual Center has been configured to use secure connections. Clear the checkbox if the Virtual Center uses only insecure connections.
If select the Configure the ESX Agent dynamically... checkbox, the wizard will attempt to connect to the Virtual Center. If the connection is successful, click Next and you will be able to complete subsequent fields using dropdown lists. Otherwise, you are prompted to manually complete the fields.
Note:
To connect to Virtual Center and retrieve configuration information using an unsecure connection, the Virtual Center must be set to support access to the SDK using HTTP. Otherwise, a message like the following appears when the connection is attempted:
"Failed to connect to VMware. It appears that the webservices stack is not running on the specified port".
See Virtual Center documentation for more information.
On the Configure ESX Agent (3 of 6) window, complete the fields as described in Table 3-13 and click Next.
Table 3-13 Configure ESX Agent (3 of 6)
Field
Description
Data Center Name
Name of the Datacenter that contains the resource pool managed by this Agent.
Compute Resource
The ESX Server host or cluster name.
Resource Pool Name
The Resource Pool containing the LiquidVM instances to be managed by this Agent.
Resource Pool Description
An arbitrary description of the resource pool.
On the Configure ESX Agent (4 of 6) window, click Add and specify the networking information as described in Table 3-14. If the Agent is managing LiquidVM instances on different network segments, you must specify the network settings for each network segment. Then click Next.
Table 3-14 Configure ESX Agent (4 of 6)
Field
Description
Name
The Virtual Machine Port Group to which the LiquidVM instance is assigned.
If you use the VMWare Infrastructure client, this can be obtained by displaying the host’s Configuration tab and then selecting Networking in the Hardware list.
Note: If you are using a cluster of ESX hosts, all hosts must have a Virtual Machine Port Group with some name and the group must be mapped a physical adapter connected to the same physical network.
JVM IP Address
One or more IP addresses reserved for the LiquidVM instances. Specify multiple addresses on the same line separated using a comma (,).
A LiquidVM instance will use only one of the IP addresses specified.
Description
An arbitrary description.
Gateway IP Address
The Gateway address used by the LiquidVM instance.
The address can be determined from the physical network adapter to which the Virtual Machine Port Group is mapped.
If not specified, the LiquidVM instance will use the default gateway based its IP address.
Netmask
The Netmask used by the LiquidVM instance.
The Netmask can be determined from the physical network adapter to which the Virtual Machine Port Group is mapped.
If not specified, the LiquidVM instance will use the default netmask.
DNS Server Address
The primary and alternate DNS Server used by the ESX Server host. Specify multiple addresses on the same line separated using a comma (,).
Example: 10.344.22.86,10.170.43.81
The LiquidVM instance cannot use remote DNS lookup if this is not specified.
Domain Name
The domain name used by the LiquidVM instance.
On the Configure ESX Agent (5 of 6) window, specify each ISO being used by clicking Add and completing the fields as described in Table 3-15. Then click Next.
Table 3-15 Configure ESX Agent (5 of 6)
Field
Description
Name
The ISO name.
Description
An arbitrary description.
ISO Software Path
The location of the ISO software, including the datastore. If you selected Configure the ESX Agentdynamically... in step 9, you can browse the ESX Server storage for the specific ISO.
To specify it manually, the syntax is [datastore]/path/filename
On the Configure ESX Agent (6 of 6) window, define each NFS share are being used by clicking Add and completing the fields as described in Table 3-16. Then click Next.
Table 3-16 Configure ESX Agent (6 of 6)
Field
Description
Name
The NFS share name.
Description
An arbitrary description.
NFS Software Path
The NFS share path using the following syntax:
<ip_address>:<path>,uid=<uid_num>,gid=<gid_num>
where
<ip_address> — IP Address of the NFS share host <path> — path to the share <uid_num> — userid number <gid_num> — group id number
On the Create Agent configuration window, click Create. Progress messages then appear.
When it becomes active, click the Done button.
Modifying Agent Configurations
There are two ways to modify an existing Agent configuration:
Manually edit the Agent’s configuration file. The structure of the XML document as well as the configuration definitions can be obtained by accessing the Agent schema file. This file is BEA_HOME\WLOC_HOME\schemas\loc-agent.xsd.
Use the WLOC administration console as described in the console’s help system.
Controller Configurations
Configuring a Controller
Follow these steps to create and configure the WLOC Controller:
Note:
Running the configuration wizard in console mode is currently not supported.
Invoke the wizard using one of the commands shown in Table 3-17.
Table 3-17 Invoking the Controller Wizard
Platform
Command
Windows
BEA_HOME\WLOC_HOME\common\bin\config.cmd
Note: You may also select WebLogic Operations Control 1.0>WLOC Configuration Wizard from the Windows Start Menu.
UNIX or Linux
BEA_HOME/WLOC_HOME/common/bin/config.sh
On the Welcome window, click Next.
On the Choose Controller or Agent window, select Create the Controller... and click Next.
On the Enter Controller Directory Location window, specify the location and click Next.
On the Enter Controller Connection Data window, complete the fields as described in Table 3-18.
Table 3-18 Controller Connection Configuration
Field
Description
Controller Host
Fully-qualified host name of the Controller machine; example: adminbox.east.example.com
Console port
HTTP port for the WLOC Administration Console; default: 9001
Console secure port
HTTPS port for the WLOC Administration Console; default: 9002
Console mode
Select one of the following to specify how clients may connect to the administration console:
Secure—HTTPS only Unsecure—HTTP only Both—Either HTTP or HTTPS
Internal port
Port used by agents for unsecure internal communication with the Controller; default: 9003
Internal Secure Port
Port used by agents for secure internal communication with the Controller; default: 9004
Security mode
Select one of the following to specify the security level to be used for internal communications between WLOC components.
Unsecure—use HTTP without SSL and guarantee of message confidentiality and integrity. This is sufficient for development systems.
Secure—use HTTPS providing message confidentiality and integrity. This should be used with production systems.
NOTES:
All Agents must use the same Security mode established on the Controller with which they communicate.
For instructions about configuring production level security, see
Secure Communications.
On the Configure Controller Logging window, complete the fields as described in Table 3-19.
Table 3-19 Configure Controller Logging
Field
Description
Logfile severity
Severity of events to log, default: INFO
In the order of severity from least severe to most severe, the log levels are:
On the first Configure Controller Notifications (1 of 6) window, select the Enable SMTP Notifications checkbox if you want to enable SMTP notifications. Then complete the fields as described in Table 3-20.
If you do not want to enable SMTP notifications, click Next without completing this window.
Table 3-20 Configure Controller Notifications (1 of 6)
Field
Description
To email address
E-mail address to which notifications should be sent.
From email address
E-mail address from which notifications should be sent.
SMTP Server
SMTP mail server through which to send notifications.
On the Configure Controller Notifications (2 of 6) window, select the Enable JMX Notification and/or SNMP checkbox if you want to enable one or both of those notification types. If you select SNMP notification, complete the fields as described in Table 3-21.
If you do not want to enable either notification type, click Next without completing this window.
Table 3-21 Configure Controller Notifications (2 of 6)
Field
Description
Agent Host
Hostname of the SNMP agent.
Agent Port
Port number of the SNMP agent.
Trap Host
DNS name or IP address of the computer on which the SNMP manager is running; default: localhost
Trap Port
Listening port of the SNMP manager; default: 1642
Trap Type
Select SNMPv1 or SNMPv2; default: SNMPv2
On the Configure Controller Notifications (3 of 6) window, select the Enable JMS Notification checkbox if you want to enable JMS notification. Then complete the fields as described in Table 3-22.
If you do not want to enable JMS notification, click Next without completing this window.
Table 3-22 Configure Controller Notifications (3 of 6)
Field
Description
Destination JNDI Name
Fully-qualified package and class of the JMS notifier; default: com.bea.adaptive.loc.notification.JMSNotifier
Fully-qualified package and class of the initial factory; default: org.mom4j.jndi.InitialCtxFactory
Provider URL
JNDI provider URL.
Security Principal
JNDI user name.
Password
JNDI user’s password.
On the Configure Agents for this Controller window, click Add and specify the Agents to be managed by this Controller and click Next.
To perform this step at another time, click Next without specifying any Agents.
Table 3-23 Configure Agents for this Controller
Field
Description
Name
Agent name.
Hostname
The fully-qualified host name or IP address of the machine hosting the Agent.
Port
HTTP port on which to access the Agent. This was specified when configuring the Agent. Default: 8001
Secure port
HTTPS port on which to access the Agent. This was specified when configuring the Agent. Default: 8002
State
One of Enabled, Connected, or Disconnected.
Default: Enabled
Passphrase Confirm Passphrase
The Agent passphrase specified when the Agent was created.
Note:
Communication between the Controller and Agent will fail unless your entry matches the Agent’s current passphrase.
On the Use SSH for WLOC ESX Agents window, select the Enable SSH for LVM instances checkbox to initialize the LVM instance that will be started by the ESX Agent on the ESX Server with the SSH public key. Then specify the location of the SSH Public Key File and click Next.
This allows a SSH client that uses the corresponding private key to be trusted by the LVM instance when the SSH client later connects to the LVM instance using SSH. The Controller will pass the SSH public key to the ESX Agent which in turn will provide the public key to the LVM instance when the LVM instance is initialized by the ESX Agent.
On the Enter User Data window, accept the default username and password for logging in to the WLOC Administrative Console or overwrite these values as desired and click Next.
Notes:
The default password is changeit. This is acceptable for development environments, but not for production.
If you specify a new password, the value is encrypted before being saved in the XML configuration file.
On the Configure Controller Keystore Passwords window, you are prompted for the keystore passwords used for internal WLOC communications. The keystores are used if Secure mode is selected for Controller to Agent communications and if Secure or Both are selected for Console communications.
In most cases, this step depends on whether you are using WLOC in a production or development environment, as described in Table 3-24.
On the Create Controller Configuration window, click Create. Progress messages then appear.
When it becomes active, click the Done button.
Modifying Controller Configurations
Controller configurations can be changed using the WLOC administration console, by directly editing the loc-controller-config.xml, or by re-running the configuration wizard. When rerunning the configuration wizard, the only change that can be made is to add or modify information about the Agents connecting to the Controller.
Modifications made using the administration console take immediate effect, while changes made by editing the XML file or re-running the configuration wizard do not take effect until the Controller is restarted. In addition, no validation or error checking is performed when you directly modify the configuration file.
You can add an Agent to a Controller by running the WLOC Configuration Wizard or using the WLOC Administration Console.
To add an Agent to a Controller by running the WLOC Configuration Wizard:
Start the WLOC Configuration Wizard.
Proceed to the Choose Controller or Agent window and select Create the Controller or extend the existing Controller for this host and click Next.
On the Enter Controller Directory Location window, specify the configuration directory for the existing Controller and click Next.
For each Agent you wish to add to the Controller’s configuration, click Add and enter the information listed in Table 3-23 in each Agent’s row. When done, click Next.
On the Update Existing Controller Configuration window, click Create. This updates the Controller’s loc-controller-config.xml file with the new Agent information.
