Oracle9i Application Server Wireless Edition Configuration Guide Release 1.1 Part Number A86701-01 |
|
This document describes the use of Oracle Enterprise Manager with Wireless Edition. Each section of this document presents a different topic. These sections include:
The use of Oracle Enterprise Manager with Wireless Edition provides:
The Oracle Enterprise Manager Diagnostic Pack includes the 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.
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.
The configuration management framework provides a way to alter some runtime parameters.
To configure Oracle Enterprise Manager for use with Wireless Edition you must first install the following components:
The Oracle Enterprise Manager configuration includes server side, client side, and middle tier configuration instructions:
The server side configuration includes the configuration of the Oracle Intelligent Agent and the Wireless Edition Data Gatherer Cartridge.
To configure the Oracle Intelligent Agent on the server:
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. |
The agent discovers the Wireless Edition service using these files.
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.
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. |
PTG ALL libvpxptg vpxptg
This completes the server side configuration. Restart the Oracle Intelligent Agent. Restart the Data Gatherer.
To stop the agent:
lsnrctl dbsnmp_stop
To start the agent:
lsnrctl dbsnmp_start
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. |
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. |
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.
To configure the Oracle Enterprise Manager client side:
Note: Requirement for deployment of the integration classes: JRE 1.1.8_10 for Solaris and JRE 1.1.7.30o for Windows NT. |
jar -xvf oemptg.jar
# # 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
/target/oracle_sysman_diagpack/oracle_sysman_ ptg=oracle.sysman.vtd.VtdPtgCredentials /options/standalone=TRUE
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. |
# 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
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 NT:
%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.
The middle-tier hosts the Oracle Management Server. The following configuration is for the Events Integration.
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.
# ORACLE_HOME/sysman/admin/OMSRegistry.registry # Wireless Edition events integration # /com/oracle/sysman/em/tests_datasource/ptg/datasource = oracle.sysman.ptg.PTGTestsDatasource
This completes the middle-tier configuration. Restart the Oracle Management Server and Oracle Intelligent Agent.
To set up the ptg_services.tcl file:
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 5-1 ptg_services.tcl Parameters
# 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. |
The preceding configuration is for one Wireless Edition instance. To configure another Wireless Edition instance:
PTG1=oracle.panama.magent.config.Magent1 PTG2=oracle.panama.magent.config.Magent2
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 3 for more information on the database logger.
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.
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 5-2 Properties of the oemevents.properties File
The 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:
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.
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|