+

Search Tips   |   Advanced Search

Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS

 

Configure the database tier


To access useful information about the database tier, first configure WebSphere® Virtual Enterprise 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.

 

Before you begin

Ensure that a DB2® or Oracle database is installed on the node, and WebSphere Virtual Enterprise is installed with an augmented profile. See Augmenting profiles for more information.

 

About this task

After you have installed either a DB2 or Oracle database on the node and installed WebSphere Virtual Enterprise 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.

 

Procedure

  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. For the Database name field on the Data source Configuration panel, specify the alias name. Under Additional Properties, click Custom Property. 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, under Additional Properties, click Custom Property. 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 Monitor 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, select the Enable Performance Monitoring Infrastructure (PMI) check box. 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.

 

Results

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

 

What to do next

See Monitor the database tier for more information.


 

Related tasks


Monitor the database tier Optimizing the database tier for performance monitoring