This section describes how to set up and customize the Control Center for your environment.
If you will run the Control Center as an application, skip this section and go to Running the Control Center as a Java Application.
To set up the Control Center to run as an applet:
To start the Control Center JDBC Applet Server, enter the db2jstrt 6790 command, where 6790 represents any 4-digit port number that is not already in use.
We recommend that you start the Control Center JDBC Applet Server with a user account that has SYSADM authority.
The first time you start the Control Center JDBC Applet Server, it will create several node directory entries, together with various files for administration purposes. In Scenarios 1 and 3 in Machine Configurations, all of these administration files and directory entries will be created in the current DB2 instance.
Most DB2 resources are accessed over database connect or instance attach. In both cases the user must supply valid user ID and password combinations to gain access. However, some resources are accessed directly by the Control Center JDBC Applet Server, including the database and node directories (catalogs), and the Command Line Processor. Access to these resources is performed by the Control Center JDBC Applet Server on behalf of the logged in Control Center user. Both the user and the server are required to have the proper authorization before access will be granted. For example, to update the database directory, a minimum of SYSCTRL authority is required.
It is possible to run an instance of the Control Center JDBC Applet Server with any level of security, but you will be unable to update certain resources such as database and node directories. In particular, you may encounter a SQL1092N message informing you of the lack of authorization for a request. The user specified in the message can be either the user signed into Control Center, or the user account running the Control Center JDBC Applet Server.
On Windows NT, you can start the Control Center JDBC Applet Server by clicking Start and selecting Settings --> Control Panel --> Services. Select the DB2 JDBC Applet Server - Control Center service and click Start.
On Windows 2000, you can start the Control Center JDBC Applet Server by clicking Start and selecting Settings --> Control Panel --> Administrative Tools --> Services. Select the DB2 JDBC Applet Server - Control Center service, click the Action menu and then select Start.
On any system, you can start the Control Center JDBC Applet Server by entering:
net start DB2ControlCenterServer
This step is not required if your Control Center JDBC Applet Server is autostarted.
If you start the Control Center JDBC Applet Server as a Windows NT or Windows 2000 service, you must configure the startup in the services dialog to change the account information.
To work with the Control Center on Windows NT or Windows 2000, the security server must be running. During DB2 installs, the Security Server is usually set up to autostart.
You can check if the Security Server is running on Windows NT by clicking Start and selecting Settings --> Control Panel --> Services.
On Windows 2000, click Start and select Settings --> Control Panel --> Administrative Tools --> Services.
If the DB2 Security Server is not started on Windows NT, select it and click Start. On Windows 2000, select the Action menu and click Start.
After you have started the Control Center JDBC Applet Server and started the Windows NT or Windows 2000 security server (if necessary), go to Running the Control Center as a Java Applet.
You can run the Control Center as a Java application or as a Java applet. If your environment is configured similar to Scenarios 1 or 2 in Table 12, you must run the Control Center as an application. If your environment is configured like Scenarios 3 or 4, you must run it as an applet.
To run the Control Center as a Java application, you must have the correct Java Runtime Environment (JRE) installed. See Table 13 for the correct JRE level for your operating system.
To run the Control Center as a Java applet, you must have a Web server set up on the machine that contains the Control Center applet code and the Control Center JDBC Applet Server. The Web server must allow access to the sqllib directory.
If you choose to use a virtual directory, substitute this directory for the home directory. For example, if you map sqllib to a virtual directory called temp on a server named yourserver, a client would use the URL: http://yourserver/temp
If you do not have the DB2 documentation installed and you would like to configure your web server to work with DB2's online documentation, refer to the Installation and Configuration Supplement.
To run Control Center as an applet on Windows 32-bit or OS/2 operating systems, you must run db2classes.exe on the machine where the DB2 JDBC Applet Server resides to unzip the required Java class files. On UNIX-based systems, you must uncompress and untar db2classes.tar.Z to make the required Java class files available.
To load the Control Center HTML page, perform the following steps:
To automatically start the Control Center the next time you open db2cc.htm, perform the following steps:
param name="autoStartCC" value="false"
to
param name="autoStartCC" value="true"
param name="autoStartCC" value="true" param name="hostNameText" value="yourserver" param name="portNumberText" value="6790"
where yourserver represents the Server name or IP address and 6790 represents the server port value of the machine to which you want to connect.
For general web server configuration information, consult the setup documentation that came with your web server.
For more information on serving DB2 online documentation through a web server, refer to the Installation and Configuration Supplement.