OLAP Setup and User's Guide

Installing the Information Catalog Manager for the Web

You can install the Information Catalog Manager for the Web on any operating system that supports DB2 Universal Database and Net.Data. The operating system must also support Net.Data Live Connection Manager and Perl LE. These operating systems include Windows NT, OS/2, AIX, and the Solaris Operating Environment.

For information about setting MIME types to launch programs, see the Information Catalog Manager Administration Guide.

Security considerations

You must enable authentication on the Web server. After you enable authentication, each user must enter a user ID and password to access the Information Catalog Manager for the Web. Because the Net.Data Live Connection Manager manages the database connections, users do not need to know the database user ID and password.

Depending on the sensitivity of the information in the information catalog, you need to implement the appropriate level of security for your Web server. For additional security beyond the authentication function in the Web server, you can install security packages with encryption and keys. For information about advanced Web server security, see the documentation for IBM SecureWay (part of the Websphere family).

Installing the Information Catalog Manager for the Web on a Windows NT Websphere IBM HTTP Web server

Before you begin to install the Information Catalog Manager for the Web:

  1. Make sure that the IBM HTTP Web server is installed.
  2. Check the Web server port number. If the Web server has a port other than 80 (the usual default), append the port number to the host name in the Web address when you configure the domain name. For example: http://hostname:portnumber/
  3. Create a directory named icm on the Web server to contain the Net.Data executable files (for example, \IBM HTTP Server\icm). Point to this directory as the Net.Data cgi-bin directory. Place the executable file db2www.exe in this directory.

To install the Information Catalog Manager for the Web:

  1. Install the Information Catalog Manager for the Web files onto your Web server:
    1. Insert the DB2 Universal Database CD-ROM into the CD-ROM drive on the Web server workstation. The launchpad opens.
    2. Click Install from the launchpad.
    3. In the Select Products window, select the DB2 Administration Client check box, then click Next.
    4. In the Select Type of Install window, click Custom, then click Next.
    5. In the Select DB2 Components window, clear the check boxes for all components except the Data Warehousing Tools component.
    6. Click Subcomponents.
    7. In the Select Subcomponents window, ensure that the check box for the Information Catalog Manager for the Web is selected and that all other check boxes are cleared.
    8. Click Continue.
    9. In the Select Components window, clear the check boxes for the Communication Protocols component, the Application Development Interfaces component, and the Administration and Configuration Tools component. Make sure that the Data Warehousing Tools component remains selected.
    10. Click Next to continue with the installation. The installation program creates files in the following directories:
      • \sqllib\icmweb\macro
      • \sqllib\icmweb\html
      • \sqllib\icmweb\icons
  2. Copy all the *.mac and *.hti files from the \sqllib\icmweb\macro directory to the Net.Data macro directory (usually \db2www\macro).
  3. Copy all the *.htm and *.gif files from the \sqllib\icmweb\html to the document root directory on the Web server (usually \IBM HTTP Server\htdocs).
  4. Copy all the dg*.gif files from the \sqllib\icmweb\icons directory to the image directory on the Web server (usually \IBM HTTP Server\icons). This directory will be the value for the image_path variable in the dg_config.hti file.
  5. Edit the dg_config.hti file to include the directories where you copied the files and the server name. The macro_path variable uses the alias that is set up on your Web server to control user access. The dg_config.hti file should look like this: 
    %DEFINE {
         server_name="http://winntserver.ibm.com/"
         image_path="$(server_name)icons/"
         macro_path="$(server_name)icm/db2www.exe/"
         help_path="$(server_name)"
%}
  6. Add a link to an existing Web page, or create a Web page with a link to the Information Catalog Manager for the Web home page.

    To create a Web page, edit the file icm.html and add the following lines: 

    <html><head>
<title>Information Catalog Manager for the Web</title>
</head>
<body bgcolor=white>
<p><a href=/icm/db2www.exe/dg_home.mac/Logon>
Information Catalog Manager for the Web</a>
</body>
</html>

    Place the file in the HTML default directory (usually \IBM HTTP Server\htdocs).

  7. Enable basic user authentication on your Web server for each Information Catalog Manager for the Web user.

    When users access the Information Catalog Manager for the Web home page, they are prompted for their user ID and password. When they enter these values, the HTTP environment variable REMOTE_USER is set. This variable is used to prompt users for their user ID and password and to create, update, and delete comments.

    1. Set up an alias.

      Create an alias named icm for the directory where the Net.Data CGI program DB2WWW is located. The macro_path variable that is defined in the dg_config.hti file uses this alias: 

      macro_path="$(server_name)icm/db2www.exe/"

      The alias directory icm should have the user ID and password authentication enabled. To enable authentication, edit the httpd.conf file. This file is usually located in \IBM HTTP Server\conf directory. Add a ScriptAlias directive, like this: 

      ScriptAlias /icm/ "c:/IBM HTTP Server/icm/"

      Also make sure that the httpd.conf file contains a directive that defines the access file name, like this: 

      AccessFileName .htaccess
    2. Create a password file that will contain the authorized user ID and password for each Information Catalog Manager for the Web user. Use the htpasswd command to create and edit the password file.

      For example, to create the password file c:/IBM HTTP Server/icmweb.pwd for the user ID ADMIN, enter the following command: 

      htpasswd -c c:/IBM HTTP Server/icmweb.pwd ADMIN

      Specifying the -c option ensures that you enter a password when you create a password file.

      When you are prompted for the password, enter ADMINPW.

      To add another user ID, ADMIN2, with the password ADMINPW2, enter the following command: 

      htpasswd c:/IBM HTTP Server/icmweb.pwd ADMIN2 ADMINPW2

      The user ID must be 8 characters or less in length, because it is stored in the information catalog tables when a comment is created.

    3. Restrict access to the \IBM HTTP Server\icm\ directory.
      1. To require authentication when users access the \IBM HTTP Server\icm\ directory, edit the httpd.conf file. This file is usually located in the \IBM HTTP Server\conf directory. Add a directory directive for the \IBM HTTP Server\icm directory, like this: 
        <Directory "c:/IBM HTTP Server/icm">
AllowOverride AuthConfig
Options None
</Directory>
      2. Create a file that is named .htaccess in the \IBM HTTP Server\icm directory with the AuthName, AuthType, AuthUserFile, and require directives that are set like this: 
        AuthName ICMWeb
AuthType Basic
AuthUserFile "c:/IBM HTTP Server/icmweb.pwd"
require valid-user

        Because some editors require a file name and a file extension, you might need to create the file with the name htaccess.txt and rename it to .htaccess after you save it.

      You must stop and restart the Web server for these changes to take effect.
      Note:This is one way that you can enable authentication on an IBM HTTP Web server. You can set up more complex directory structures, user groups, and permissions, if necessary, along with additional security packages. More information about setting up basic authentication is available in the IBM HTTP Web server documentation. For information about advanced Web server security, see the documentation for IBM SecureWay (part of the Websphere family).

  8. Set up Net.Data to run Live Connection Manager for the databases that are used by the Information Catalog Manager for the Web.
    1. Edit the Net.Data file \db2www\connect\dtwcm.cnf, and add a CLIETTE DTW_SQL block for each database that the Information Catalog Manager for the Web will use.

      To add the database ICMSAMP with a minimum of one process, a maximum of three processes, starting with private port number 7100, and starting with public port number 7110, add the following block: 

      CLIETTE DTW_SQL:ICMSAMP{
MIN_PROCESS=1
MAX_PROCESS=3
START_PRIVATE_PORT=7100
START_PUBLIC_PORT=7110
EXEC_NAME=./dtwcdb2
DATABASE=ICMSAMP
BINDFILE=NOT_USED
LOGIN=*USE_DEFAULT
PASSWORD=*USE_DEFAULT
}

      Six ports (7100, 7101, 7102, 7110, 7111, 7112) are allocated to the ICMSAMP database. Make sure that these ports are free and not in use by another application. You must use different port number ranges for each CLIETTE DTW_SQL block. See the Net.Data Administration and Programming Guide for more information.

    2. Set the LOGIN value to the user ID for the database, and set the PASSWORD value to the password for the database. If the database is local, you can use *USE_DEFAULT.
    3. Set up the Net.Data initialization file to use Live Connection Manager for the SQL calls. Edit the DB2WWW.INI file in the document root directory on the Web server. Make sure that the ENVIRONMENT DTW_SQL statement ends with CLIETTE "DTW_SQL:$(DATABASE)".

      For example: 

      ENVIRONMENT (DTW_SQL) DTWSQL(IN DATABASE,LOGIN,PASSWORD,
   TRANSACTION_SCOPE,SHOWSQL,ALIGN,START_ROW_NUM)
   CLIETTE "DTW_SQL:$(DATABASE)"
    4. Start Live Connection Manager by using the executable file /DB2WWW/CONNECT/dtwcm.exe. Live Connection Manager must be running so that the Information Catalog Manager for the Web can access the databases. After Live Connection Manager is started, you can minimize the Live Connection Manager window on the Web server. See the Net.Data Administration and Programming Guide for more information.

Follow the steps in Post-installation customization before using the Information Catalog Manager for the Web.

Installing the Information Catalog Manager for the Web on an AIX Websphere IBM HTTP Web server

Before you begin to install the Information Catalog Manager for the Web:

  1. Make sure that IBM HTTP Web server is installed.
  2. Check the Web server port number. If the Web server has a port other than 80 (the usual default), append the port number to the host name in the Web address when you configure the domain name. For example: http://hostname:portnumber/
  3. Create a directory named icm on the Web server to contain the Net.Data executable files (for example, /usr/lpp/HTTPServer/share/icm/). Point to this directory as the Net.Data cgi-bin directory. Place the executable file db2www (usually found in the /usr/lpp/internet/server_root/cgi-bin directory) into this directory.
  4. Copy the db2www.ini file (usually found in the /usr/lpp/internet/server_root/pub/ directory) to the document root directory (usually /usr/lpp/HTTPServer/share/htdocs). Edit the db2www.ini file and update the DB2 instance and path: 
    DB2INSTANCE		db2
MACRO_PATH		/usr/lpp/internet/db2www/macro
INCLUDE_PATH		/usr/lpp/internet/db2www/macro
HTML_PATH			/usr/lpp/HTTPServer/share/htdocs
EXEC_PATH			/usr/lpp/internet/db2www/macro
DTW_LOG_DIR		/usr/lpp/internet/db2www/logs

To install the Information Catalog Manager for the Web:

  1. Log in as a user with root authority.
  2. Insert and mount the DB2 Universal Database CD-ROM. For information about mounting a CD-ROM, see DB2 for UNIX Quick Beginnings.
  3. Change to the directory where the CD-ROM is mounted by entering cd /cdrom, where cdrom is the mount point of your product CD-ROM.
  4. Enter the ./db2setup command. After a few moments, the Install DB2 V7 window opens.
  5. Select the products that you want to install and are licensed to install. Press the Tab key to change the highlighted option. Press the Enter key to select or deselect an option. When you select an option, an asterisk is displayed next to it.

    To select or deselect optional components for a DB2 product that you want to install, select the Customize option. To go back to a previous window at any time, select the Cancel option.

  6. When you have finished selecting the DB2 product and its components, select OK to continue with the installation.

    For more information or assistance during the installation of any DB2 product or component, select the Help option.

    The installation program creates files in the following directories:

  7. Copy all the *.mac and *.hti files from the \sqllib\icmweb\macro directory on the Windows NT workstation to the Net.Data macro directory on the Web server (usually /usr/lpp/internet/db2www/macro. To set the permissions on these files to public read, enter chmod ugo+r *.
  8. Copy all the *.htm and *.gif files from the \sqllib\icmweb\html directory on the Windows NT workstation to the document root directory on the Web server (usually /usr/lpp/HTTPServer/share/htdocs). To set the permissions on these files to public read, enter chmod ugo+r *.
  9. Copy all the dg*.gif files from the \sqllib\icmweb\icons directory on the Windows NT workstation to the image directory on the Web server (usually /usr/lpp/HTTPServer/share/icons). This directory will be the value for the image_path variable in the dg_config.hti file. To set the permissions on these files to public read, enter chmod ugo+r *.
  10. Edit the dg_config.hti file to include the directories where you copied the files and the server name. The macro_path variable uses the alias that is set up on your Web server to control user access. The dg_config.hti file should look like this: 
    %DEFINE {
         server_name="http://aixserver.ibm.com/"
         image_path="$(server_name)icons/"
         macro_path="$(server_name)icm/db2www/"
         help_path="$(server_name)"
%}
  11. Add a link to an existing Web page, or create a Web page with a link to the Information Catalog Manager for the Web home page.

    To create a Web page, edit the file icm.html and add the following lines: 

    <html><head>
<title>Information Catalog Manager for the Web</title>
</head>
<body bgcolor=white>
<p><a href=/icm/db2www/dg_home.mac/Logon>
Information Catalog Manager for the Web</a>
</body>
</html>

    Place the file in the document root directory (usually /usr/lpp/HTTPServer/share/htdocs).

  12. Enable basic user authentication on your Web server for each Information Catalog Manager for the Web user.

    When users access the Information Catalog Manager for the Web home page, they are prompted for their user ID and password. When they enter these values, the HTTP environment variable REMOTE_USER is set. This variable is used to prompt users for their user ID and password and to create, update, and delete comments.

    1. Set up an alias.

      Create an alias named icm for the directory where the Net.Data CGI program DB2WWW is located. The macro_path variable that is defined in the dg_config.hti file uses this alias: 

      macro_path="$(server_name)icm/db2www/"

      The alias directory icm should have the user ID and password authentication enabled. To enable authentication, edit the httpd.conf file. This file is usually located in the /usr/lpp/HTTPServer/etc/ directory. Add a ScriptAlias directive, like this: 

      ScriptAlias /icm/ /usr/lpp/HTTPServer/share/icm

      Also make sure that the httpd.conf file contains a directive that defines the access file name, like this: 

      AccessFileName .htaccess
    2. Create a password file that will contain the authorized user ID and password for each Information Catalog Manager for the Web user. Use the htpasswd command to create and edit the password file.

      For example, to create the password file /usr/lpp/HTTPServer/share/icmweb.pwd for the user ID ADMIN, enter the following command: 

      htpasswd -c /usr/lpp/HTTPServer/share/icmweb.pwd ADMIN

      Specifying the -c option ensures that you enter a password when you create a password file.

      When you are prompted for the password, enter ADMINPW.

      To add another user ID, ADMIN2, with the password ADMINPW2, enter the following command: 

      htpasswd /usr/lpp/HTTPServer/share/icmweb.pwd ADMIN2 ADMINPW2

      The user ID must be 8 characters or less in length, because it is stored in the information catalog tables when a comment is created.

    3. Restrict access to the /usr/lpp/HTTPServer/share/icm directory.
      1. To require authentication when users access the /usr/lpp/HTTPServer/share/icm directory, edit the httpd.conf file. This file is usually located in the /usr/lpp/HTTPServer/etc/ directory. Add a directory directive for the /usr/lpp/HTTPServer/share/icm directory, like this: 
        <Directory /usr/lpp/HTTPServer/share/icm>
AllowOverride AuthConfig
Options None
</Directory>
      2. Create a file that is named .htaccess in the /usr/lpp/HTTPServer/share/icm directory with the AuthName, AuthType, AuthUserFile, and require directives that are set like this: 
        AuthName ICMWeb
AuthType Basic
AuthUserFile /usr/lpp/HTTPServer/share/icmweb.pwd
require valid-user

        Because some editors require a file name and a file extension, you might need to create the file with the name htaccess.txt and rename it to .htaccess after you save it.

      You must stop and restart the Web server for these changes to take effect.
      Note:This is one way that you can enable authentication on an IBM HTTP Web server. You can set up more complex directory structures, user groups, and permissions, if necessary, along with additional security packages. More information about setting up basic authentication is available in the IBM HTTP Web server documentation. For information about advanced Web server security, see the documentation for IBM SecureWay (part of the Websphere family).

  13. Set up Net.Data to run Live Connection Manager for the databases that are used by the Information Catalog Manager for the Web.
    1. Edit the Net.Data file /usr/lpp/internet/db2www/db2/dtwcm.cnf, and add a CLIETTE DTW_SQL block for each database that the Information Catalog Manager for the Web will use.

      To add the database ICMSAMP with a minimum of one process, a maximum of three processes, starting with private port number 7100, and starting with public port number 7110, add the following block: 

      CLIETTE DTW_SQL:ICMSAMP{
MIN_PROCESS=1
MAX_PROCESS=3
START_PRIVATE_PORT=7100
START_PUBLIC_PORT=7110
EXEC_NAME=./dtwcdb2
DATABASE=ICMSAMP
BINDFILE=NOT_USED
LOGIN=*USE_DEFAULT
PASSWORD=*USE_DEFAULT
}

      Six ports (7100, 7101, 7102, 7110, 7111, 7112) are allocated to the ICMSAMP database. Make sure that these ports are free and not in use by another application. You must use different port number ranges for each CLIETTE DTW_SQL block. See the Net.Data Administration and Programming Guide for more information.

    2. Set the LOGIN value to the user ID for the database, and set the PASSWORD value to the password for the database. If the database is local, you can use *USE_DEFAULT.
    3. Set up the Net.Data initialization file to use Live Connection Manager for the SQL calls. Edit the DB2WWW.INI file in the document root directory on the Web server (usually /usr/lpp/HTTPServer/share/htdocs). Make sure that the ENVIRONMENT DTW_SQL statement ends with CLIETTE "DTW_SQL:$(DATABASE)".

      For example: 

      ENVIRONMENT (DTW_SQL) DTWSQL(IN DATABASE,LOGIN,PASSWORD,
   TRANSACTION_SCOPE,SHOWSQL,ALIGN,START_ROW_NUM)
   CLIETTE "DTW_SQL:$(DATABASE)"
    4. Start Live Connection Manager by using the executable file /usr/lpp/internet/db2www/db2/dtwcm. Live Connection Manager must be running so that the Information Catalog Manager for the Web can access data from the databases. After Live Connection Manager is started, you can minimize the Live Connection Manager window on the Web server. See the Net.Data Administration and Programming Guide for more information.
      Note:Live Connection Manager must be started with the DB2 instance that is specified in the db2www.ini file. The DB2 environment must be set up before you run the dtwcm executable file.
  14. Log out.

Follow the steps in Post-installation customization before using the Information Catalog Manager for the Web.

Installing the Information Catalog Manager for the Web on any Web server

Before you begin to install the Information Catalog Manager for the Web:

  1. Make sure that the Web server software is installed on the Web server.
  2. If the Web server has a port number other than 80 (the usual default), append the port number to the host name in the Web address: http://hostname:portnumber/
  3. When you install Net.Data, you are prompted for the Web server's CGI-BIN and HTML directories. Make sure that you specify the Web server's directory where the CGI programs are run, and the document root directory for HTML files. The Net.Data CGI program db2www is placed in this CGI-BIN directory. The Net.Data DB2WWW.INI file is placed in the document root directory.

To install the Information Catalog Manager for the Web:

  1. Install the Information Catalog Manager for the Web files onto your Web server or Windows NT workstation:
    1. Insert the DB2 Universal Database CD-ROM into the CD-ROM drive on the Web server workstation. The launchpad opens.
    2. Click Install from the launchpad.
    3. In the Select Products window, select the DB2 Administration Client check box, then click Next.
    4. In the Select Type of Install window, click Custom, then click Next.
    5. In the Select DB2 Components window, clear the check boxes for all components except the Data Warehousing Tools component.
    6. Click Subcomponents.
    7. In the Select Subcomponents window, ensure that the check box for the Information Catalog Manager for the Web is selected and that all other check boxes are cleared.
    8. Click Continue.
    9. In the Select Components window, clear the check boxes for the Communication Protocols component, the Application Development Interfaces component, and the Administration and Configuration Tools component. Make sure that the Data Warehousing Tools component remains selected.
    10. Click Next to continue with the installation. The installation program creates files in the following directories:
      • \sqllib\icmweb\macro
      • \sqllib\icmweb\html
      • \sqllib\icmweb\icons
  2. Copy or use FTP to transfer as binary all the *.mac and *.hti files from the \sqllib\icuweb\macro directory to the \db2www\macro directory on the Web server. Set the file permissions to allow public read access.
  3. Copy or use FTP to transfer as binary all the *.htm and *.gif files from the \sqllib\icuweb\html directory to the document root directory on the Web server. Set the file permissions to allow public read access.
  4. Copy or use FTP to transfer as binary all the dg_*.gif files from the \sqllib\icuweb\icons directory to the icons directory on the Web server. Set the file permissions to allow public read access.
  5. Edit the dg_config.hti file. Add the names of the directories where you copied the files and the server name. The macro_path variable can be set to an alias that is set up on your Web server to control user access.

    On UNIX operating systems, the dg_config.hti file will look like this: 

    %DEFINE {
          server_name="http://server.ibm.com/"
          image_path="$(server_name)icons/"
          macro_path="$(server_name)icm/db2www/"
          help_path="$(server_name)"
%}

    On Windows NT and OS/2 operating systems, the dg_config.hti file will look like this: 

    %DEFINE {
          server_name="http://server.ibm.com/"
          image_path="$(server_name)icons/"
          macro_path="$(server_name)icm/db2www.exe/"
          help_path="$(server_name)"
%}
  6. Add a link to an existing Web page, or create a Web page with a link to the Information Catalog Manager for the Web home page.

    To create a Web page, edit the file \document_root\icm.html (where document_root is the Web server's document root directory). Set the file permission to allow public read access.

  7. Enable basic user authentication on your Web server for each Information Catalog Manager for the Web user.

    When users access the Information Catalog Manager for the Web home page, they are prompted for their user ID and password. When they enter these values, the HTTP environment variable REMOTE_USER is set. This variable is used to prompt users for their user ID and password and to create, update, and delete comments.

    The user ID must be 8 characters or less, because it is stored in the information catalog tables when a comment is created.

    1. Create an alias named icm for the directory where the Net.Data CGI program db2www is located.
      • On UNIX operating systems, the macro_path variable that is defined in the dg_config.hti file uses this alias: 
        macro_path="$(server_name)icm/db2www/"
      • On Windows NT and OS/2 operating systems, the macro_path variable that is defined in the dg_config.hti file uses this alias: 
        macro_path="$(server_name)icm/db2www.exe/"
    2. Enable user ID and password authentication for the alias directory icm and set the proper permissions.

    See the Web server documentation for more information about enabling authentication.

  8. Set up Net.Data to run Live Connection Manager for the databases that are used by the Information Catalog Manager for the Web.
    1. Edit the Net.Data file dtwcm.cnf, and add a CLIETTE DTW_SQL block for each database that will be used by the Information Catalog Manager for the Web.

      To add the database ICMSAMP with a minimum of one process, a maximum of three processes, starting with private port number 7100 and starting with public port number 7110, add the following block: 

      CLIETTE DTW_SQL:ICMSAMP{
MIN_PROCESS=1
MAX_PROCESS=3
START_PRIVATE_PORT=7100
START_PUBLIC_PORT=7110
EXEC_NAME=./dtwcdb2
DATABASE=ICMSAMP
BINDFILE=NOT_USED
LOGIN=*USE_DEFAULT
PASSWORD=*USE_DEFAULT
}

      This block allocates six ports (7100, 7101, 7102, 7110, 7111, 7112) to the database ICMSAMP. Make sure that these ports are free and not in use by another application. You must use different port number ranges for each CLIETTE DTW_SQL block. See the Net.Data Administration and Programming Guide for more information.

    2. Set the LOGIN value to the user ID and PASSWORD value to the password for the database. If you are using a local database, then you can use the *USE_DEFAULT value.
    3. Set the Net.Data initialization file to use Live Connection Manager for the SQL calls. Edit the db2www.ini file in the Web server's document root directory. Make sure that the environment DTW_SQL statement has CLIETTE "DTW_SQL:$(DATABASE)" at the end.

      For example: 

      ENVIRONMENT (DTW_SQL) DTWSQL(IN DATABASE,LOGIN,PASSWORD,
   TRANSACTION_SCOPE,SHOWSQL,ALIGN,START_ROW_NUM)
   CLIETTE "DTW_SQL:$(DATABASE)"
    4. Start Live Connection Manager by using the executable file dtcmf in the Net.Data directory. Live Connection Manager must be running so that the Information Catalog Manager for the Web can access data in the databases. After Live Connection Manager is started, you can minimize the Live Connection Manager window on the Web server. See the Net.Data Administration and Programming Guide for more information.

Follow the steps in Post-installation customization before using the Information Catalog Manager for the Web.

Post-installation customization

After you install the Information Catalog Manager for the Web, complete the following steps to customize the Information Catalog Manager for the Web for your users:

  1. Edit the file dg_home.hti. Add a link for each information catalog that you want users to access from the Information Catalog Manager for the Web. Use the following format for the links: 
    <LI><A HREF=$(macro_path)dg_frame.mac/frame?DATABASE=xxxx> zzzz </A>

    xxxx
    The information catalog database name (for example, ICMSAMP)

    zzzz
    A descriptive comment that is displayed on the Web page (for example, CelDial sample catalog)

    You can add HTML tags to the dg_home.hti file either before or after the information catalog list. These tags can include links, images, text, or other valid HTML 3.2 tags that you want to add.

  2. Catalog the server node and databases by using the necessary DB2 client function. See the Installation and Configuration Supplement for more information. From the DB2 Command Line Processor, verify that the Web server can connect successfully to the databases.

Before you access information catalogs through the Information Catalog Manager for the Web, make sure that the database manager is started on the database servers, Live Connection Manager is started on the Web server, and the Web server is started.

Notify users of their user IDs and passwords, and inform them of the Web address that they can use to access the Information Catalog Manager for the Web.

[ Top of Page | Previous Page | Next Page ]