6
Oracle Enterprise Manager

Oracle Enterprise Manager describes the use of Oracle Enterprise Manager with Wireless Edition. Each section of this document presents a different topic. These sections include:

• Section 6.1, "Overview"
• Section 6.2, "Prerequisites"
• Section 6.3, "Configuring the Server, Client, and Middle-tier"
• Section 6.4, "Setting up the ptg_services.tcl File"
• Section 6.5, "Configuration for Another Wireless Edition Instance"
• Section 6.6, "Configuring the Database Logger"
• Section 6.7, "Asynchronous Notification of Error Information"
• Section 6.8, "Launching the Oracle Enterprise Manager Tools"

Important: In this document: WE_HOME is the directory in which Wireless Edition is installed followed by the "panama" sub-directory. For example: c:\ias10210\panama (Windows) /private/ias10210/panama (UNIX) Replace "WE_HOME" with the fully-qualified directory path. ORACLE_HOME is the Oracle 8.1.7 Oracle home.

6.1 Overview

The use of Oracle Enterprise Manager with Wireless Edition provides:

• Performance monitoring
• Fault management
• Configuration management

Performance Monitoring

The Oracle Enterprise Manager Diagnostic Pack includes Performance Manager and Capacity Planner. The Performance Manager is a Windows NT client side tool for viewing performance data collected by the Wireless Edition Cartridge. The Capacity Planner allows you to archive and view performance data collected by the Wireless Edition cartridge. This cartridge is used by the Data Gatherer to collect performance data logged by the Wireless Edition runtime.

Fault Management

The event framework of Oracle Enterprise Manager enables asynchronous notification of error information. When an error occurs, Wireless Edition generates an Oracle Enterprise Manager event at the node where the error occurred. The event provides the details necessary for fault diagnosis. The Oracle Intelligent Agent running on each node picks up these events and forwards them to the Oracle Enterprise Manager Console for display. You can configure the Console to page or email the administrator.

Configuration Management

The configuration management framework provides a way to alter some runtime parameters.

6.2 Prerequisites

To configure Oracle Enterprise Manager for use with Wireless Edition you must first install the following components:

• Oracle Enterprise Manager 2.2 with Diagnostic Pack
• Oracle Intelligent Agent 8.1.7
• Oracle Management Server 2.2

6.3 Configuring the Server, Client, and Middle-tier

The Oracle Enterprise Manager configuration includes server side, client side, and middle tier configuration instructions:

• The Oracle Enterprise Manager server side configuration involves the Oracle Intelligent Agent and Data Gatherer. See Section 6.3.1.
• The Oracle Enterprise Manager client side configuration involves the Console (the navigator and events) and Diagnostic Pack (Performance Manager and Capacity Planner). See Section 6.3.2.
• The Oracle Enterprise Manager middle-tier configuration involves the Oracle Management Server, specifically the configuration to receive threshold events from the Data Gatherer Cartridge on the Console. See Section 6.3.3.

6.3.1 Configuring the Server Side

The server side configuration includes the configuration of the Oracle Intelligent Agent and the Wireless Edition Data Gatherer Cartridge.

6.3.1.1 Configuring the Oracle Intelligent Agent

To configure the Oracle Intelligent Agent on the server:

1. Install the Oracle Intelligent Agent 8.1.7 in ORACLE_HOME. If the Oracle Management Server is to reside on the same host as the Oracle Intelligent Agent, ensure that the Oracle Management Server is also installed in the same ORACLE_HOME.

Note: If running Oracle 8.1.6, perform a custom installation of Oracle 8.1.7 Enterprise Edition. Select the Oracle Intelligent Agent and its subcomponents. Install it in a separate ORACLE_HOME.

2. Copy the file dgmetric.tcl from the WE_HOME/oem/agent directory to the Oracle Intelligent Agent ORACLE_HOME/network/agent/events/oracle/generic/metric directory. This operation replaces the existing dgmetric.tcl file.
3. Copy the file ptg_services.tcl from the WE_HOME/oem/agent directory to the ORACLE_HOME/network/agent/config directory.
4. Append the ptg_services.tcl file name to the nmiconf.1st file found in the ORACLE_HOME/network/agent/config directory.



The agent discovers the Wireless Edition service using these files.
 

5. Edit the ptg_services.tcl file to configure the instance(s) information. See Section 6.4 for instructions on setting up the ptg_services.tcl file. Configuration for a default instance name (PTG1) is provided as an example.

Note: The Oracle Intelligent Agent must be restarted whenever any change is made to the ptg_services.tcl file or to the nmiconf.lst file.

After completing the preceding instructions, install the Wireless Edition Data Gatherer cartridge. The Oracle Intelligent Agent uses this cartridge to collect Wireless Edition performance data. The Performance Manager and Capacity Planner use the collected data to provide runtime metrics for diagnosis.

The cartridge installation steps differ according to the hardware platform.

6.3.1.2 Wireless Edition Data Gatherer Cartridge Installation: Unix

To install the data gatherer cartridge:

Important: The cartridge installation requires an Oracle Enterprise Manager 2.2 Console and Oracle Intelligent Agent 8.1.7 on the server side.

1. Un-tar the ptgsolariscartridge.tar file found in WE_HOME/oem/agent/cartridge/solaris to a directory (referred to as CART_DIR in this document).
2. Copy CART_DIR/lib/libvpxptg.so to the ORACLE_HOME/odg/lib directory.
3. Copy CART_DIR/mesg/vpxptgus.msb to the ORACLE_HOME/odg/mesg directory.
4. Copy CART_DIR/html/vpxptgUS.htm to the ORACLE_HOME/odg/html directory.
5. Append the following entry to the svppcart.dat file in the ORACLE_HOME/odg directory.

PTG ALL libvpxptg vpxptg

This completes the server side configuration. Restart the Oracle Intelligent Agent. Restart the Data Gatherer.

Oracle Intelligent Agent Start and Stop

To stop the agent:

lsnrctl dbsnmp_stop

To start the agent:

lsnrctl dbsnmp_start

Data Gatherer Start and Stop

To stop the gatherer:

vppcntl -stop

To start the gatherer:

vppcntl -start

Note: For more information on commands to restart the Oracle Intelligent Agent, Oracle Management Server, and Data Gatherer, see the Oracle Enterprise Manager Configuration Guide.

6.3.1.3 Wireless Edition Data Gatherer Cartridge Installation: Windows

To install the data gatherer cartridge:

Important: The cartridge installation requires an Oracle Enterprise Manager 2.2 Console and Oracle Intelligent Agent 8.1.7 on the server side.

1. Un-zip the ptgwincartridge.zip file in WE_HOME/oem/agent/cartridge/win32 to a directory (referred to as CART_DIR in this document).
2. Copy the file vpxptg.dll in CART_DIR\odg\bin to the ORACLE_HOME\bin directory.
3. Copy the file vpxptgUS.htm in CART_DIR\odg\html to the ORACLE_HOME\odg\html directory.
4. Copy the file vpxptgus.msb in CART_DIR\odg\mesg to the ORACLE_HOME\odg\mesg directory.
5. Append the following entry to the svppcart.dat file in the ORACLE_HOME\odg directory:

PTG ALL vpxptg vpxptg

This completes the server side configuration for Oracle Enterprise Manager integration. Restart the Oracle Intelligent Agent and the Data Gatherer. This starts the Wireless Edition cartridge along with the Oracle Intelligent Agent startup.

Select the Control Panel and then Services to restart the appropriate service.

6.3.2 Configuring the Client Side

To configure the Oracle Enterprise Manager client side:

Note: Requirement for deployment of the integration classes: JRE 1.1.8_10 for Unix and JRE 1.1.7.30o for Windows.

1. Install the Oracle Enterprise Manager client, including the Console and client tools, Oracle Management Server, and Diagnostic Pack (Performance Manager and Capacity Planner).

Note: The Oracle Enterprise Manager Diagnostic Pack is only available for Windows.

2. Copy the file oemptg.jar from the WE_HOME/oem/client directory to the ORACLE_HOME/classes directory.
3. Extract this file in the copied directory. This extracts the console integration classes, Performance Manager integration classes, events integration classes, and RMI client and stub for the Console interaction with the server. For example:

jar -xvf oemptg.jar

4. The entries in WE_HOME/oem/client/OEMClient.properties.append must be appended to ORACLE_HOME/sysman/config/OEMCLient.properties. The following shows the entries.

#
# System definition of types for Wireless Edition
#
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/isa =test_service1
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/service = true
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/display_class = 
oracle.sysman.ptg.navigator.PtgDisplayDriver

#
# Console definition of types for navigator tree for 
# Wireless Edition
#
/com/oracle/sysman/em/console/navigator/oracle_sysman_ptg/data_source = 
oracle.sysman.ptg.navigator.PtgSubItemContainerSource

/com/oracle/sysman/em/console/navigator/oracle_sysman_ptg/proxy 
=oracle.sysman.ptg.navigator.PtgProxy

#
# Events Integration
#
# Wireless Edition events integration 
#
/com/oracle/sysman/em/console/tests_datasource/ptg/datasource = 
oracle.sysman.ptg.PTGTestsDatasource

# PTG Console credentials classes for Events Integration
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/isa =
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/service = true
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/credentials_display = 
oracle.sysman.vtcConsole.vtcCredentials.PtgCredentialsDisplay
/com/oracle/sysman/em/system/types/oracle_sysman_ptg/credentials = 
oracle.sysman.emSDK.common.credentials.PtgCredentials

5. The entries in WE_HOME/oem/client/vtdclient.properties.append must be appended to ORACLE_HOME/sysman/config/vtdclient.properties. The following shows the entries:

/target/oracle_sysman_diagpack/oracle_sysman_
ptg=oracle.sysman.vtd.VtdPtgCredentials
/options/standalone=TRUE

6. Edit the ORACLE_HOME/classes/oracle/panama/magent/MAgent.properties file to reflect the values of the installed Wireless Edition server name. The port number and the service name are defaulted.

Note: This property file should be in synch with the one on the Wireless Edition server side for each instance to which the file refers.

7. For the Oracle Enterprise Manager client side installation the only pertinent values are magent.server.host and magent.server. The remaining properties may be ignored or defaulted here.

# Server Host Name
magent.server.host=<Wireless Edition server host name>


# The service port: Use the same port as the RMI server as 
#                   in Rmi.properties
magent.server.port=2008

# Service Name
magent.server.name=Magent

8. Verify that the classpath contains the following entries.

For UNIX:

$ORACLE_HOME/classes
$ORACLE_HOME/jdbc/lib/classes111.zip
$ORACLE_HOME/lib/vbjorb.jar
$ORACLE_HOME/lib/vbjapp.jar
$ORACLE_HOME/lib/vbjtools.jar
$ORACLE_HOME/classes/classesFromIDLVisi
$ORACLE_HOME/jlib/ewt-3_3_6.jar
$ORACLE_HOME/jlib/ewtcompat-opt-3_3_6.zip
$ORACLE_HOME/jlib/ewt-swingaccess-1_1_1.jar
$ORACLE_HOME/jlib/share-1_0_8.jar
$ORACLE_HOME/jlib/jssl-1_2.jar
$ORACLE_HOME/jlib/javax-ssl-1_2.jar
$ORACLE_HOME/jlib/netcfg.jar:/

For Windows:

%ORACLE_HOME%\classes
%ORACLE_HOME%\jdbc\lib\classes111.zip
%ORACLE_HOME%\lib\vbjorb.jar
%ORACLE_HOME%\lib\vbjapp.jar
%ORACLE_HOME%\lib\vbjtools.jar
%ORACLE_HOME%\classes\classesFromIDLVisi
%ORACLE_HOME%\jlib\ewt-3_3_6.jar
%ORACLE_HOME%\jlib\ewtcompat-opt-3_3_6.zip
%ORACLE_HOME%\jlib\ewt-swingaccess-1_1_1.jar
%ORACLE_HOME%\jlib\share-1_0_8.jar
%ORACLE_HOME%\jlib\jssl-1_2.jar
%ORACLE_HOME%\jlib\javax-ssl-1_2.jar

The Oracle Enterprise Manager client side configuration is now complete.

6.3.3 Configuring the Middle-tier

The middle-tier hosts the Oracle Management Server. The following configuration is for the Events Integration.

1. Copy the file oemptg.jar in the WE_HOME/oem/oms directory to the ORACLE_HOME/classes directory where the Oracle Management Server is installed.
2. Extract this file in the copied directory, for example:

jar -xvf oemptg.jar

This extracts the Console integration classes, Performance Manager integration classes, events integration classes, and RMI client and stub for the Console interaction with the server.

3. The entries in WE_HOME/oem/oms/OMSRegistry.registry.append must be appended to the OMSRegistry.registry file in ORACLE_HOME/sysman/admin.

# ORACLE_HOME/sysman/admin/OMSRegistry.registry
# Wireless Edition events integration 
#
/com/oracle/sysman/em/tests_datasource/ptg/datasource = 
oracle.sysman.ptg.PTGTestsDatasource

Note: After updating the OMSRegistry.registry file, recreate the Oracle Management Server repository using the Oracle Enterprise Manager configuration assistant. See the Oracle Enterprise Manager Configuration Guide for more information.

This completes the middle-tier configuration. Restart the Oracle Management Server and Oracle Intelligent Agent.

6.4 Setting up the ptg_services.tcl File

To set up the ptg_services.tcl file:

1. Set the correct values of the NEW_PARAMETER_NAME, PTG_INSTANCE_NAME, TRACE_DB_HOSTNAME, TRACE_DB_PORT, TRACE_DB_SID, and TRACE_DB_ORACLE_HOME for each instance.
2. To add another instance:
1. Add a new parameter to store the new ServiceName (the Wireless Edition instance name) to the "global Parameters". See the following example.
2. Copy the lines between "BEGIN EXAMPLE" and "END EXAMPLE", and replace the information with the new instance's parameter name and remaining information.

global Parameters ServiceType HostName tnsaddress argv NEW_PARAMETER_
NAME ServiceName2

set Parameters(oracle_sysman_ptg) {ServiceType HostName tnsaddress };

set Host [lindex $argv 0];

#The Service name is a subnode in the navigator

set NEW_PARAMETER_NAME PTG_INSTANCE_NAME;

lappend ServiceNames $NEW_PARAMETER_NAME;
set ServiceType($NEW_PARAMETER_NAME) oracle_sysman_ptg;
set HostName($NEW_PARAMETER_NAME) $Host;
set tnsaddress($NEW_PARAMETER_NAME) "(DESCRIPTION=(ADDRESS_LIST = 
(ADDRESS = (PROTOCOL = TCP)(HOST = TRACE_DB_HOSTNAME)(PORT = TRACE_DB_
PORT)))(CONNECT_DATA=(SID=TRACE_DB_SID)(ORACLE_HOME=TRACE_DB_ORACLE_
HOME)(SERVER=DEDICATED)))"

In the following example a new parameter (ServiceName2) is added and the values for the PTG_INSTANCE_NAME, TRACE_DB... are set. For this example the listed parameters are replaced with the values in the following. The values are similar to the tnsnames.ora configuration.
Table 6-1 ptg_services.tcl Parameters

Parameter	Value in Example	Description
NEW_PARAMETER_NAME	ServiceName2	Parameter name declaration.
PTG_INSTANCE_NAME	PTG2	The Wireless Edition instance name.
TRACE_DB_HOSTNAME	ptgserver-sun.us.oracle.com	The host name of the database log database.
TRACE_DB_PORT	1521	The port of the database listener.
TRACE_DB_SID	ptgdev	The SID of the log database.
TRACE_DB_ORACLE_HOME	/private/oracle/8.1.7	The Oracle home directory.

# Example:
# The Service name "PTG2" (Wireless Edition Instance name) is a subnode in the 
# Navigator tree

# In the line below, just append the new parameter name 
#  i.e. ServiceName2. Don't duplicate this line.
global Parameters ServiceType HostName tnsaddress argv ServiceName2

set Parameters(oracle_sysman_ptg) {ServiceType HostName tnsaddress };

set Host [lindex $argv 0];

# Lines below need to be duplicated every time a new instance is added
set ServiceName2 PTG2;
lappend ServiceNames $ServiceName2;
set ServiceType($ServiceName2) oracle_sysman_ptg;
set HostName($ServiceName2) $Host;
set tnsaddress($ServiceName2) "(DESCRIPTION=(ADDRESS_LIST = (ADDRESS = (PROTOCOL 
= TCP)(HOST = ptgserver-sun.us.oracle.com)(PORT = 1521)))(CONNECT_
DATA=(SID=ptgdev)(ORACLE_HOME=/private/oracle/8.1.7)(SERVER=DEDICATED)))"

Note: Place this file in ORACLE_HOME/network/agent/config. Add this file name to nmiconf.lst. To reflect any change to either file restart the Oracle Intelligent Agent and rediscover the node.

6.5 Configuration for Another Wireless Edition Instance

The preceding configuration is for one Wireless Edition instance. To configure another Wireless Edition instance:

1. Ptg_services.tcl: Add another entry in the ORACLE_HOME/network/agent/config/ptg_services.tcl file. Give this instance a different service name. See Section 6.4 for instructions and an example.
2. Minstances.properties: Add a corresponding instance's <instance name > = <property file name> entry to the ORACLE_HOME/classes/oracle/panama/magent/config/MInstances.properties file. The RMI client uses this information to communicate with the corresponding server. Each instance is monitored using a Magent.properties file which contains the Wireless Edition server host name, port, and service name. In the case of multiple instances, these are identified by these values. The Minstances.properties file should point the instance name to the corresponding Magent.properties file. For example, for two instances:

PTG1=oracle.panama.magent.config.Magent1
PTG2=oracle.panama.magent.config.Magent2

3. Magent.properties: Configure the Magent.properties file on both the client and server side to point to the new instance's classes and port. Users can have any number of instances but each instance's information is stored in a separate property file.
4. Ensure that an Oracle Enterprise Manager Agent is installed on the node where the Wireless Edition instance is running. The Wireless Edition instance uses the Agent to pipe error messages to the Oracle Enterprise Manager Console.
5. The System.properties.templ file contains parameters for the system logger and the logger schema. Ensure that these are set up appropriately.

6.6 Configuring the Database Logger

The database logger of a Wireless Edition instance must point to a database schema to log the information. This configuration is done in the System.properties file of each Wireless Edition instance. See Chapter 4 for more information on the database logger.

6.7 Asynchronous Notification of Error Information

Asynchronous notification of error information is provided using the event framework provided by Oracle Enterprise Manager. In case of an error, the Wireless Edition server generates an Oracle Enterprise Manager event at the node where the error occurred providing all the necessary details for the fault diagnosis.

Note: An Oracle Enterprise Manager agent must be running on the node where oemevent is invoked. The event must be defined as an unsolicited event and the node must be added as a monitored destination.

The Oracle Enterprise Manager Event properties can be configured by editing the oemevent.properties file in the WE_HOME/server/oracle/panama/core/admin directory.

The oemevent.properties file has the following parameters:
Table 6-2 Properties of the oemevents.properties File

Key	Type	Customizable	Description
oemevent.path	string	Y	Complete path name for the oemevent executable.
oemevent.event. name	string	Y	Unsolicited event name as defined in the console.
oemevent.object. name	string	Y	Object name specified in the event definition.
oemevent.event level	string	Y	Event level specified in the event definition. The level should be defined as "2" and specified as "alert".

6.8 Launching the Oracle Enterprise Manager Tools

Performance Monitoring is accomplished through the Oracle Enterprise Manager Performance Manager and Capacity Planner tools (provided only for Windows NT). Once the installation is complete:

1. Launch the necessary performance monitoring tool. See the Oracle Enterprise Manager documentation for instructions on how to launch it.
2. At the login screen select Stand-alone and no repository connection. Click OK.
3. Double-click PTG PM Targets.
4. Enter the Wireless Edition login information to the schema where the Wireless Edition dumps the runtime log information. This information is the same as the system logger configuration information that is entered in Section 6.6.
5. Enter the Data Gatherer Location. This is the host on which you installed the Data Gatherer and Wireless Edition cartridge.
6. Click OK.

This allows you to begin using the performance monitoring and capacity planning.

The Fault and Configuration Management is accomplished through the Oracle Enterprise Manager Console.

1. Launch the Oracle Enterprise Manager Console. See the Oracle Enterprise Manager documentation for instructions on how to launch it.
2. Log on to the repository which you created during your Oracle Enterprise Manager installation.
3. Discover the node where the Oracle Intelligent Agent is running.
4. Configure the Console to receive unsolicited events from the Nodes (hostnames) on which Wireless Edition is running. See the Oracle Enterprise Manager documentation for instructions on how to configure it.