Deploying under WAS version 5 (non-z/OS)
The following steps are used to deploy QMF for WebSphere
under WAS version 5 (on non-z/OS platforms).
Note:
The WAS support for web services changed between
version 5.0 and 5.0.2. If you are using a version of WAS earlier
than 5.0.2 and you plan on using the QMF for WebSphere web service,
you should apply the appropriate WAS maintenance to upgrade to version
5.0.2 or later. You should apply this maintenance prior to continuing
with the QMF for WebSphere installation.
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:
- Expand Applications.
- Click on Install New Application. The Preparing for the application installation page
displays on the right side of the Administrative Console window.
- 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 Local path field.
If you installed the files on the WAS server machine, enter the
remote directory name followed by QMFWebSphere.ear in the Server path field.
Click Next.
- On the second Preparing for the application installation page,
click Generate Default Bindings and then click Next.
- On the Step 1page, if you are installing
on WAS 5.0.2 or later, select the Deploy Web Services check
box. Otherwise, this check box will not display. Click Next.
- On the Step 2 page, accept the default
values and click Next.
- On the Step 3 page, note the name of the
application server listed for the QMF for WebSphere module and then
click Next.
- On the Step 4 page, accept the default
values and click Next. (Mapping the qmfadmin
role to users or groups will be performed after installing the application.)
- Click Next on any remaining pages, and
finally click Finish.
After WAS has finished installing the application, 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
to authenticate a user before performing various administrative
tasks in QMF for WebSphere, such as binding packages. You use the
WebSphere Administrative Console to map the qmfadmin role
to users and groups.
In the navigation tree on the left side of the Administrative
Console window:
- Expand Applications.
- Click Enterprise Applications. The Enterprise
Applications page displays on the right side of the Administrative
Console window.
- In the display list of installed applications, click QMF for
WebSphere.
- In the Additional Properties list, click Map security roles to users/groups. The
Mapping Users to Roles page displays. Use this page to specify whether the
role should be mapped to all users (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.
- When you have finished creating the mappings, click OK.
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:
- Expand Servers.
- Click on Application Servers. The Application
Servers page displays on the right side of the Administrative Console
window.
- In the displayed list of application servers, click on the application
server where you installed the QMF for Windows application. The
properties of the application server display.
- In the Additional Properties list, click Process Definition.
The Process Definition page displays.
- In the Additional Properties list, click Java(TM) Virtual Machine.
The Java Virtual Machine page displays.
- In the Classpath list, 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(TM) 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
- 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.
Start the application
The installation and configuration of the application
is complete, so you can now make it available.
In the navigation tree on the left side of the Administrative
Console window:
- Expand Applications.
- Click Enterprise Applications. The Enterprise Applications page
displays on the right side of the Administrative Console window.
- In the displayed list of installed applications, select the
check box next to QMF for WebSphere, then
click Start.
The application is now available.
