IBM Books

DB2 Universal Database Control Center


Table of Contents

Control Center Installation and Configuration

  • Components to Install
  • Machine Configuration
  • Supported Java Virtual Machines for the Control Center
  • Setting Up and Working with the Control Center
  • Control Center Services Setup
  • Working with the Control Center
  • Functional Considerations
  • Installation Tips for Control Center Help on UNIX Operating Systems
  • Configuring TCP/IP on OS/2
  • Enabling Local Loopback
  • Enabling Localhost
  • Verifying TCP/IP Configuration on OS/2
  • Troubleshooting

  • Control Center Installation and Configuration

    The Control Center is the main DB2 graphical tool for administering your database. The Control Center provides a clear overview of all the systems and database objects being managed. You can also access other administration tools from the Control Center by selecting icons on the Control Center toolbar or from the Tools pop-up menu.


    Components to Install

    The DB2 Control Center is a selectable component during DB2 installations on Windows 32-bit, OS/2, and UNIX operating systems.

    You can run the Control Center either as a Java application or as a Java applet through a web server. In both cases you need a supported Java Virtual Machine (JVM) installed on your machine to run the Control Center. A JVM can be a Java Runtime Environment (JRE) for running applications, or a Java-enabled browser for running applets.


    Machine Configuration

    You can set up your Control Center 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 "Control Center Services Setup" section that follows the table.

    Table 1. Control Center Machine Configuration Scenarios
    Scenario Machine A Machine B Machine C
    1 - Stand-alone, Application
    JRE
    Control Center application
    JDBC Applet Server
    DB2 server

       

    2 - Two Tier, Application


    JRE
    Control Center application
    JDBC Applet Server
    DB2 client

      DB2 server

    3 - Two Tier, Browser


    Supported Browser
    (Intel only)
    Control Center applet


    Web server
    JDBC Applet Server
    DB2 server

     
    4 - Three Tier, Browser
    Supported Browser
    (Intel only)
    Control Center applet


    JDBC Applet Server
    DB2 client

    DB2 server

    Figure 1 summarizes the four basic Control Center machine configurations:

    Figure 1. DB2 Control Center machine configurations


    Figure db2cntrl not displayed.


    Supported Java Virtual Machines for the Control Center

    The following table lists supported Java Virtual Machines (JREs and browsers) required to run the Control Center as an application or applet:

    Table 2. Supported Java Virtual Machines (JVMs) for the Control Center
    Operating System Correct Java Runtime Environments Supported Browsers
    Windows 32-bit JRE 1.1.7b IBM Enhanced (installed) Netscape 4.5 (shipped) or IE 4.0 Service Pack 1
    AIX JRE 1.1.6 GA 1 None
    OS/2 JRE 1.1.7 GA 2 Netscape 4.04 3
    Linux Redhat JRE 1.1.7 v1a 4 None
    Linux Caldera JRE 1.1.7 v1a None
    Linux Pacific JRE 1.1.7 v1a None
    Linux Suse JRE 1.1.7 v1a None
    Solaris JRE 1.1.7 Production 5 None
    HP 10.20 and 11 JRE 1.1.6 6 None

    Notes:

    1. AIX JRE available from http://www.software.ibm.com/java/jdk/index.html

    2. OS/2 JRE available from http://www.software.ibm.com/java/jdk/index.html

    3. OS/2 supported browser available from ftp://ftp.netscape.com/pub/communicator

    4. Linux Redhat JRE available from http://www.blackdown.org/java-linux/info.html

    5. Solaris JRE available from http://www.sun.com/solaris/java/index.html

    6. HP-UX 10.20 and 11 JRE available from http://www.internetsolutions.enterprise.hp.com/2_60_index.html

    Setting Up and Working with the Control Center

    This section describes how to set up and customize the Control Center for your environment.

    Control Center Services Setup

    To set up the Control Center, perform the following steps:

    Step  1.

    Start the Control Center JDBC Applet Server. The Control Center JDBC Applet Server is required by the Control Center client when running both as an application and applet.

    Step  2.

    On Windows NT, start the security server.

    Step 1. Start the Control Center JDBC Applet Server

    We recommend that you start the Control Center JDBC Applet Server with a user account that has SYSADM authority.

    If you start the Control Center JDBC Applet Server as a Windows NT service, you must configure the startup in the Windows NT services dialog to change the account information. If you installed a DB2 server on the same machine as the Control Center JDBC Applet Server, then the Control Center JDBC Applet Server service entry will have been updated with the same account information as the DB2 Administration Server service entry.

    Most DB2 resources are accessed over database connect or instance attach. In both cases the user must supply valid userid 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 signed-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 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.

    To start the Control Center JDBC Applet Server:

    Step 2. Start the Windows NT Security Server

    To work with the Control Center on Windows NT, 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 by clicking on Start->Settings->Control Panel->Services. If the DB2 Security Server is not started, select it and click on the Start push button.

    Working with the Control Center

    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, 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.

    Running the Control Center as a Java Application

    To run the Control Center as a Java application, you must have the correct Java Runtime Environment (JRE) installed. See Table 2 for the correct JRE level for your operating system.

    To start the Control Center, perform the following steps:

    Step  1.

    On Windows 32-bit operating systems:

    Click on Start and select Programs->DB2 for Windows->Control Center.

    On OS/2:

    Open the DB2 for OS/2 folder and double-click on the Control Center icon.

    On all supported platforms:

    Start the Control Center from a command prompt by entering the db2cc command. If you want to use a port number other than the default (6790), enter the new port number after the db2cc command.

    Step  2.

    The Control Center Sign On window opens. Enter your user ID and password. This user ID must have an account on the machine that is running the Control Center JDBC Applet Server. Your initial logon will be used for all database connections. It can be changed from the Control Center pull-down menu. A unique user profile will be assigned to each user ID. Click on OK.

    Step  3.

    The DB2 Control Center window opens.

    Step  4.

    You can start working with the Control Center without an existing database by creating a sample database. Enter the db2sampl command on the DB2 Universal Database server. On UNIX operating systems, ensure that you are logged in to the DB2 instance before you enter the db2sampl command.

    Running the Control Center as a Java Applet

    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 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 FAT file systems, these class files may take up more disk space because of the large number of files and the way FAT file systems allocate disk space.

    To load the Control Center HTML page, perform the following steps:

    Step  1.

    Start the Control Center Launch page through your web server. In your browser, select File->Open Page. The Open Page dialog box appears. Enter the URL of your Web server and the main Control Center page and click on the Open push button. For example, if your server is named yourserver, you would open http://yourserver/cc/prime/db2cc.htm.

    Step  2.

    In the Server port field, enter a value for the Control Center JDBC Applet Server port. The default server port value is 6790.

    Step  3.

    Click on the Start Control Center push button.

    Step  4.

    The Control Center Sign On window opens. Enter your user ID and password. This user ID must have an account on the machine that is running the Control Center JDBC Applet Server. Your initial logon will be used for all database connections. It can be changed from the Control Center pull-down menu. A unique user profile will be assigned to each user ID. Click on OK.

    Step  5.

    The DB2 Control Center window opens.

    Step  6.

    You can start working with the Control Center without an existing database by creating a sample database. Enter the db2sampl command on the DB2 Universal Database server. On UNIX operating systems, ensure that you are logged in to the DB2 instance before you enter the db2sampl command.

    Customizing Your Control Center HTML File

    To automatically start the Control Center the next time you open db2cc.htm, perform the following steps:

    Configuring Your Web Server to Work with the Control Center

    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.


    Functional Considerations

    If you are using the Control Center over the Internet, be aware that there is no encryption of the data flow between the Control Center JDBC Applet 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 Control Center on an OS/2 FAT drive, 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 Control Center under Scenarios 3 or 4, the local system is Machine B. The local system is the system name as it appears in the DB2 Control Center window.


    Installation Tips for Control Center Help on UNIX Operating Systems

    When installing the Control Center online help on UNIX operating systems you should keep the following in mind:


    Configuring TCP/IP on OS/2

    To run the Control Center on OS/2 Warp 3 or Warp 4 while disconnected from a LAN, you will need to configure TCP/IP to enable local loopback and localhost.

    Enabling Local Loopback

    To enable local loopback on your system:

    Step  1.

    Open the OS/2 TCP/IP folder.

    Step  2.

    Open the TCP/IP Configuration notebook.

    Step  3.

    View the Network page.

    Step  4.

    In the Interface to Configure list box, highlight loopback interface.

    Step  5.

    If the Enable interface check box is not selected, select it now.

    Step  6.

    Verify that the IP address is 127.0.0.1 and Subnet Mask is empty.

    Enabling Localhost

    To enable localhost on your system:

    Step  1.

    To check if localhost is enabled, enter the ping localhost command.

    • If data are returned, localhost is enabled, and you can skip steps 2 and 3 below and go directly to step 4.

    • If localhost unknown is returned, or if the command hangs, localhost is not enabled. Go to step 2.

    Step  2.

    If you are on a network, make sure that loopback is enabled. To enable local loopback see Enabling Local Loopback.

    Step  3.

    If you are not on a network, enable localhost by performing these steps:

    1. Add the following line after other ifconfig lines in the MPTN\BIN\SETUP.CMD command file:
         ifconfig lo 127.0.0.1
      
      Note:If you have OS/2 Warp with Internet Access Kit, add the line to the \STARTUP.CMD instead of the MPTN\BIN\SETUP.CMD file. If the file doesn't exist, you will have to create it.

    2. In the TCP/IP configuration folder, perform the following steps:

      1. Go to the Configure Name Resolution Services page.

      2. In the Hostname configuration without a Nameserver table, add an entry with IP Address set to 127.0.0.1 and Hostname set to localhost.
      Note:If you have a hostname for your machine on the Configure LAN Name Resolution Services page, you must add this name as an alias when you set the IP Address 127.0.0.1 to localhost.

    3. Select the Look through HOSTS list before going to the nameserver list box. This step tells your OS/2 system that when it is looking for a host, such as localhost, it should use the host address found on your machine rather than checking the nameserver. If the host is not defined on your machine, OS/2 continues looking for the host by using the nameserver you configured.

    4. Close TCP/IP Configuration and reboot the system.

    5. You should be able to ping localhost without being connected to any network.

    Step  4.

    Verify that your hostname is correct. On an OS/2 command line, enter the hostname command. The hostname returned should match the one listed in the TCPIP Configuration notebook on the Hostnames page and it must be less than 32 characters. If the hostname deviates from these conditions, correct it on the Hostnames page.

    Step  5.

    Verify that your hostname is set properly in CONFIG.SYS. You should see a line similar to the following:

    SET HOSTNAME=<correct_name>
    

    where <correct_name> is the value returned by the hostname command. If this is not the case, make the necessary changes and reboot your system when you are finished.

    Verifying TCP/IP Configuration on OS/2

    If you are having trouble running the Control Center on OS/2 while disconnected from a LAN, try running the sniffle /P command and to diagnose the problem.


    Troubleshooting

    For the latest service information on the Control Center, point your browser to http://www.software.ibm.com/data/db2/udb/db2cc

    If you are having problems running the Control Center, check the following:

    If you are having problems running the Control Center as an application, also check the following:

    If you are having problems running the Control Center as an applet, also check the following: