WebSphere Extended Deployment V6.0.x     操作系统: AIX, HP-UX, Linux, Solaris, Windows, z/OS

Configuring the database tier

In order to access useful information about the database tier, you must first configure WebSphere Extended Deployment for performance monitoring. With database tier performance monitoring, you can view central processing unit utilization, average response time, and throughput. The information provided in performance monitoring is valuable for detecting and preventing bottlenecks.

在您开始之前

Ensure that a DB2 or Oracle database is installed on the node, and Extended Deployment is installed with an augmented profile. See Augmenting the WebSphere Application Server profile for more information.

关于本任务

After you have installed either a DB2 or Oracle database on the node and installed WebSphere Extended Deployment with an augmented profile, you can then configure the database tier for performance monitoring. Monitoring the database tier provides the information needed to prevent the system from experiencing slower response time due to bottlenecks.

过程

  1. Create a database server in the WebSphere Application Server configuration.
    1. Create a new generic server and give it a name, for example DB2Instance1. Select the database node from the list.
    2. Click Generic Servers > DB2Instance1.
    3. Under Additional Properties, click Process Definition > Java Virtual Machine > Custom Properties.
    4. Add the following entries:
      GENERIC_SERVER_TYPE = DBSERVER
      GENERIC_SERVER_SUB_TYPE = DB2 (for DB2) or ORACLE (for Oracle)
      INSTANCE_NAME = name of database instance (DB2) or SID (Oracle)
  2. Configure data sources for Java Database Connectivity (JDBC) monitoring:
    1. Click Resources > JMS Providers > JDBC Providers > Database_server_name > Data sources > Data_source_name > Customer properties. Add the property: dbServerName = generic server name, for example, DB2Instance1.
    2. Follow these steps, depending on the database type and Java database connectivity (JDBC) driver type you use:
      • For type 2 DB2 data sources. If the database name on the server is different from the database alias name used on the local DB2 client, take these actions:
        1. For the Database name field on the Datasource Configuration panel, specify the alias name.
        2. Under Additional Properties, click Custom Property.
        3. Add a remote Database Name custom property, using database name as the value on the database server.
      • For Oracle data sources: If the database name does not display in the connection URL:
        1. Under Additional Properties, click Custom Property.
        2. Set the value of the database name property to the name of the Oracle database.
  3. Enable performance monitoring infrastructure (PMI) for JDBC statistics collection:
    1. Click Monitoring and Tuning > Performance Monitoring Infrastructure (PMI). This action displays a list of servers in the cell.
    2. For every server in the list that has a data source:
      1. Click the server name.
      2. In the Configuration panel:
        1. Select the Enable Performance Monitoring Infrastructure (PMI) check box.
        2. Set the Currently monitored statistic set to Extended or All. However, if the currently monitored statistic set is set to Custom, and for improved performance, enable the JDBC counters in the Custom Level.

结果

Your system is now ready for extended monitoring of WebSphere Extended Deployment components, including JDBC. You can view your database from the runtime topology.

下一步做什么

See tdbtiermonitor.html for more information.



相關工作
tdbtiermonitor.html
tdbtieroptimize.html
任务主题    

使用条款 | 反馈

最近更新日期: Aug 14, 2006 2:01:54 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/tdbtierconfigure.html

© Copyright IBM Corp. 2004, 2006. All Rights Reserved.
本信息中心基于 Eclipse 技术。(http://www.eclipse.org)