The Web Control Center is the Java version of the DB2 Universal Database Control Center. From a tools perspective, it is modeled on the DB2 Release 5 Control Center, but it provides you with a more flexible network-centric database administration environment. The Web Control Center is implemented as a Java applet that uses DB2's JDBC support.
Information on supported Web browsers and operating systems can be found on the Web at http://www.software.ibm.com/data/db2/library/browsers.html
To get started with the Web Control Center, you need to install DB2 Universal Database Server Version 5.2, where the server is any of:
To run the Web Control Center, you need:
You can set up your Web Control Center (Web CC) in a number of different
ways. The following table identifies four scenarios, each showing a
different way of installing the required components. These scenarios
are referenced throughout the "Web Control Center Setup" section that follows the table.
| Scenario | Machine A | Machine B | Machine C | ||
|---|---|---|---|---|---|
| 1 - Standalone |
Browser Web CC applet JDBC server DB2 server | ||||
2 - Two Tier1 |
Browser Web CC applet JDBC server CAE3 | DB2 server | |||
3 - Two Tier2 | Browser |
Web CC applet Web server JDBC server DB2 server | |||
| 4 - Three Tier | Browser |
Web CC applet Web server JDBC server CAE | DB2 server | ||
| |||||
In Scenarios 1 and 2, there is no requirement for a Web server because the Web Control Center (Web CC) applet and the browser are on the same machine.
In Scenarios 3 and 4, the Web Control Center applet code is remote, which enables code sharing across several browsers. This means that you can access the Web Control Center from browsers on different machines. Since the applet has not been implemented as a trusted applet, the Web server and the JDBC server must reside on the same machine.
This section describes how to install the Web Control Center and how you can customize it for your environment.
| Note: | This step is not required if your security server is autostarted. |
On the UNIX operating system, logon to the account where you want to run the JDBC server and issue the db2start command.
start db2jd 6790
On the UNIX operating system containing the JDBC server, enter:
db2jd 6790 &
The port number 6790 is an example; any 4-digit number that is not already in use can be used. The default port number is 6789.
| Note: | The first time you start the JDBC server, it will create several node directory entries, together with various files for administration purposes. In Scenario 1 and 3, all of these administration files and directory entries will be created in the current DB2 instance. |
Click on the Open push button.
If you want the Web Control Center started automatically the next time you open the db2webcc.htm file:
PARAM name="prompted" value="true"
to
PARAM name="prompted" value="false"
PARAM name="prompted" value="false" PARAM name="host" value="yourserver" PARAM name="port" value="6790"
where yourserver is the host name and 6790 is the port value of the machine you want to connect to.
Consult the setup documentation that came with your Web server for general Web server configuration information.
To configure your Web server for use with the Web Control Center, use sqllib as your home directory. If you choose to use a virtual directory, substitute this directory for the home directory. For example, if you name your virtual directory temp then you should use sqllib/temp.
If you do not have the DB2 documentation installed and you would like information on configuring your Web server to work with DB2's online documentation, see the Web at . http://www.software.ibm.com/data/pubs/papers/db2html.html
If you are using the Web Control Center over the Internet, be aware that there is no encryption of the data flow between the JDBC server and the browser.
To use the color options of Visual Explain on Netscape, you must set your operating system to support more than 256 colors.
DB2 does not support the installation of the Web Control Center on a FAT drive for OS/2, because an OS/2 FAT drive does not support long filenames required by Java.
Every activity will be associated with an explicit DB2 connection or attachment. For security purposes, every DB2 activity will be validated.
When you are using the Web Control Center under Scenarios 3 or 4, the local system is Machine B.
When installing the Web Control Center online help on UNIX operating systems you should keep the following in mind:
Each user has a profile of their own preferences stored on the machine were the JDBC server exists.
You cannot start a new Control Center from the existing Control Center.
The Event Analyzer and Snapshot Monitor are not included as part of the DB2 Web Control Center for Version 5.2.
If you are having problems running the Web Control Center applet:
If you are having problems connecting to the JDBC or Web server: