DB2 graphic  QMF Version 8

Deploying under WAS Advanced Single Server Edition version 4 (non-z/OS)

The following steps are used to deploy QMF for WebSphere under WebSphere Application Server Advanced Single Server Edition, version 4 (on non-z/OS platforms).

Start the WebSphere Administrative Console

Start the WebSphere Administrative Console by opening a web browser on a client machine, and entering the appropriate URL. By default, the URL is http://host:port/admin, where host is the host name of the WAS server and port is the port on which the Administrative Console is configured to listen (9090, by default).

Install the application

In the navigation tree on the left side of the Administrative Console window:

  1. Expand Nodes.
  2. Expand the node on which you wish to install the QMF for WebSphere application.
  3. Click on Enterprise Applications. The Enterprise Applications page displays on the right side of the Administrative Console window, listing the installed applications.
  4. Click Install to display the Application Installation Wizard.
  5. On the first Preparing for the application installation page, you must specify the location of the module to install. If you installed the QMF for WebSphere files on the local machine, enter the local directory name followed by QMFWebSphere.ear in the Path field. If you installed the files on the WAS server machine, enter the remote directory name followed by QMFWebSphere.ear in the Remote Path on server field. Click the corresponding Next button.
  6. On the Mapping Users to Roles page, click Next. (Mapping the qmfadmin role to users or groups will be performed after installing the application.)
  7. Simply click Next on all of the following pages until the final confirmation page. On this page, click Finish.

Save the configuration.

Map the qmfadmin role to users and groups

A single security role named qmfadmin is defined for the QMF for WebSphere application. This role is used authenticate a user before performing various administrative tasks in QMF for WebSphere, such as binding packages. You use the WebSphere Advanced Administrative Console to map the qmfadmin role to users and groups.

In the navigation tree on the left side of the Administrative Console window:

  1. Expand Nodes.
  2. Expand the node on which you installed the QMF for WebSphere application.
  3. Expand Enterprise Applications.
  4. Click on QMF for WebSphere. The application properties page displays on the right side of the Administrative Console window.
  5. Click on Modify Role to User Mappings. The Mapping Roles to Users window displays. Use this window to specify whether the role should be mapped to everyone (effectively eliminating authentication for the role), to all authenticated users (allowing any authenticated user to perform QMF administration functions), or only to users or groups that you specify.
  6. When you have finished creating the mappings, click Next, then click Finish.

Save the configuration.

Configure access to JDBC drivers

The last element of configuration that you must perform using the WebSphere Administrative Console is to provide access to any JDBC drivers that will be used by QMF for WebSphere.

In the navigation tree on the left side of the Administrative Console window:

  1. Expand Nodes.
  2. Expand the node on which you installed the QMF for WebSphere application.
  3. Expand Application Servers.
  4. Expand Default Server.
  5. Expand Process Definition.
  6. Click on JVM Settings. The JVM Settings page appears on the right side of the Administrative Console window.
  7. In the Classpath field, add all of the *.zip or *.jar files that are required by the JDBC drivers that will be used by QMF for WebSphere. For example, for the DB2 Universal Database V8 Type 4 driver on Microsoft Windows, you might enter:
    C:\Program Files\IBM\SQLLib\Java\db2jcc.jar
    C:\Program Files\IBM\SQLLib\Java\db2java.zip
    C:\Program Files\IBM\SQLLib\Java\sqlj.zip
    C:\Program Files\IBM\SQLLib\runtime.zip
  8. When you have finished adding the required files, click OK.

Save the configuration. After the configuration is saved, you must restart the server for the changes to take effect.


Go to the previous page Go to the next page

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright IBM Corporation 1982,2004 Copyright IBM Corporation 1982, 2004
timestamp Last updated: March, 2004