On Linux, after installing the application server and before enabling the 7application server, you must set up the Linux Java environment. Refer to your Application 7Development Guide: Building and Running Applications book for details on setting 7up the Linux Java environment.

To enable the application server for DB2 UDB, perform the following:

7
1. Log on to the DB2 server as root on Linux or UNIX operating systems, or as a user with Administrator privileges on Windows operating systems.
7
2. For Linux- and UNIX-based operating systems run the following command: 7

      . /db2instance_path/sqllib/db2profile 

   where db2instance_path is where the DB2 UDB instance 7was created.
7
3. Run one the following commands: 7
   7
   • For Linux and UNIX operating systems: 7

        AppServer_install_path/bin/enable.sh 
     7         -db db_alias 
     7         -user db_user 
     7         -password db_password 
     7         -db2path path_to_sqllib 
     7         -instance instance_name
     7         -easpath path_to_eas
     7         -fencedid fenced_userid

   7
   • For Windows operating systems: 7

        AppServer_install_path\bin\enable 
     7         -db db_alias 
     7         -user db_user 
     7         -password db_password 
     7         -db2path path_to_sqllib 
     7         -instance instance_name
     7         -easpath path_to_eas
     

   where: 7
   7
   • db_alias is the alias of the database to 7be enabled.
   7
   • db_user is the user id to use when connecting 7to the database.
   7
   • db_password is the password to use with the 7user id connecting to the database.
   7
   • path_to_sqllib is the path to the DB2 UDB instance 7SQLLIB directory. This path is used to update DB2EAS with the required JAR 7files.
   7
   • instance_name is the name of a DB2 UDB instance.
   7
   • path_to_eas is the path to the embedded application 7server.
   7
   • fenced_userid is the user id for the fenced 7user.

Once the application server for DB2 UDB is enabled, the application server 7is started automatically.

Before you install DB2 Web Tools on WebSphere, ensure that you have:

7
• BEA WebLogic 7.0 application server.
7
• IBM DB2 Administration Client Version 8.
7
• A Web browser that is compliant with HTML 4.0. 7 7
  Note:
  7
  DB2 Web Tools were 7tested using Netscape 4.x, Netscape 6.x, Netscape 7.x, Mozilla 1.x, Internet 7Explorer 5.x, Opera 6.x, Konqueror 3.x (Linux) and EudoraWeb 2.x (Palm OS). Use 7of certain Web browsers that have not been tested might require an explicit 7reference to be added in the servlet configuration.

The following restrictions apply to the DB2 Web Tools deployment:

7
• Multiple language and code page conversions between the middle tier and DB2 servers 7are not supported. Although the language for the server is what is used for 7display, some characters might appear incorrectly.
7
• In order to see the health alerts for databases, table spaces, and table 7space containers in the Web Health Center, you need to ensure that the databases 7are cataloged on the Web application server.
7
• The use of the Web browser buttons (Stop, Back, History) are 7not supported while using DB2 Web Tools.
7
• If you are using Netscape Navigator 4 with DB2 Web Tools, your browser display might 7not refresh properly . If you experience this problem, you can refresh your 7display by minimizing the window and then maximizing it. You can also refresh 7the display by hiding the browser window under another window, and then bringing 7it to the foreground again.
7
• To assign your own alias to any DB2 Universal Database (UDB) system, instance node, or database, you must explicitly catalog 7it on the application server using the DB2 Configuration Assistant or the DB2 Control Center.
7
• During their first startup, the DB2 Web Tools require a significantly longer 7time to initialize than for subsequent startups. Most of this wait is due 7to the automatic catalog process. If you do not want to use the automatic 7catalog functionality, you can shorten the time you must wait by turning the 7automatic cataloging off through the servlet configuration. 7 7
  Note:
  7
  The servlet configuration parameters are available in the deployment descriptor 7file web.xml. The parameter names and default 7values are subject to change with each release. Some application servers might 7allow changes to these parameters, either through their interface or by editing 7the web.xml file directly.
7
• The output (results) buffer has an absolute maximum size of 1MB when using 7a desktop or laptop browser, even if it is configured for larger capacity. 7In the case of PDA Web browsers, the limit is 1KB.
7
• On Linux, UNIX, and Windows operating systems, the DB2 Web Tools automatically 7discover and catalog any systems on the same TCP/IP net as the application 7server. Systems on the same TCP/IP net have the same first three digits in 7their IP address. The tools try to catalog the DB2 UDB system nodes using the original remote 7TCP/IP host name. If there is name duplication, the tools assign a unique 7random name. You must explicitly catalog any other DB2 administration servers on the application 7server if you want them to be accessible. This includes any servers using 7TCP/IP that are not on the same TCP/IP net as the application server, as well 7as any servers that do not use TCP/IP.
7
• On Linux, UNIX, and Windows operating systems, the DB2 Web Tools attempt 7to automatically discover and catalog any DB2 UDB instance nodes and databases that 7reside on cataloged DB2 UDB systems. It is possible to configure a remote instance 7for multiple communication protocols, therefore, the catalog will contain 7a separate node entry for each protocol supported by an automatically cataloged 7instance. If there is name duplication, the tools assign a unique random name.

To install DB2 Web Tools on WebLogic application servers:

7
1. Deploy the DB2 Web Tools through the WebLogic administrative console 7by completing the following: 7
   7
   1. Start the WebLogic administrative console.
   7
   2. Click domain -> deployments -> Web Applications in 7the left pane of the window.
   7
   3. Click the Configure a new Web Application link 7to install DB2 Web Tools Web application.
   7
   4. Browse the listing of the file system to locate Sqllib\tools\web\db2wa.war.
   7
   5. Click on select beside the db2wa.war file name.
   7
   6. Choose a server from the list of available servers to house DB2 Web Tools, select 7the server and click the arrow to move the server to target servers. 7 7
      Note:
      7
      Preserving the original name db2wa is 7mandatory, as DB2 Web Tools has it hardcoded.
   7
   7. Click Configure and Deploy.
   7
   8. Wait until the application server refreshes the deployment status of the 7Web application on the selected server. If successful, it should show Deployed=true
7
2. Invoke the DB2 Web Tools Web application, which is located at: 7

   http://server_name:app_server_port_number/db2wa

   For example, http://server_name:7001/db2wa.

Before you install DB2 Web Tools, ensure that you have:

7
• An application server, such as: 7
  7
  • Tomcat 4.0 Servlet/JSP Container (http://jakarta.apache.org/tomcat/)
  7
  • Macromedia JRun 4.0
7
• IBM DB2 Administration Client Version 8.
7
• A Web browser that is compliant with HTML 4.0.

The following restrictions apply to the DB2 Web Tools deployment:

7
• Multiple language and code page conversions between the middle tier and DB2 servers 7are not supported. Although the language for the server is what is displayed, 7some characters might appear incorrectly.
7
• In order to see the health alerts for databases, table spaces, and table 7space containers in the Web Health Center, you need to ensure that the databases 7are cataloged on the Web application server.
7
• The use of the Web browser buttons (Stop, Back, History) are 7not supported while using DB2 Web Tools.
7
• If you are using Netscape Navigator 4 with DB2 Web Tools, your browser display might 7not refresh properly. If you experience this problem, you can refresh your 7display by minimizing the window and then bringing it back. You can also refresh 7the display by hiding the browser window under another window, and then bringing 7it to the foreground again.
7
• To assign your own alias to any DB2 UDB system, instance node, or database, 7you must explicitly catalog it on the application server using the DB2 Configuration 7Assistant or the DB2 Control Center.
7
• During their first startup, the DB2 Web Tools require a significantly longer 7time to initialize than for subsequent startups. Most of this wait is due 7to the automatic catalog process. If you do not want to use the automatic 7catalog functionality, you can shorten the time you must wait by turning the 7automatic cataloging off through the servlet configuration. 7 7
  Note:
  7
  The servlet configuration parameters are available in the deployment descriptor 7file web.xml. The parameter names and default 7values are subject to change with each release. Some application servers might 7allow changes to these parameters, either through their interface or by editing 7the web.xml file directly.
7
• The output (results) buffer has an absolute maximum size of 1MB when using 7a desktop or laptop browser, even if it is configured for more. In the case 7of PDA Web browsers, the limit is 1KB.
7
• On Linux, UNIX, and Windows operating systems, the DB2 Web Tools automatically 7discover and catalog any systems on the same TCP/IP net as the application 7server. Systems on the same TCP/IP net have the same first three digits in 7their IP address. The tools try to catalog the DB2 UDB system nodes using the original remote 7TCP/IP host name. If there is name duplication, the tools assign a unique 7random name. You must explicitly catalog any other DB2 administration servers on the application 7server if you want them to be accessible. This includes any servers using 7TCP/IP that are not on the same TCP/IP net as the application server, as well 7as any servers that do not use TCP/IP.
7
• On Linux, UNIX, and Windows operating systems, the DB2 Web Tools attempt 7to automatically discover and catalog any DB2 UDB instance nodes and databases that 7reside on cataloged DB2 UDB systems. It is possible to configure a remote instance 7for multiple communication protocols, therefore, the catalog will contain 7a separate node entry for each protocol supported by an automatically cataloged 7instance. If there is name duplication, the tools assign a unique random name.

The following are the procedures for installing DB2 Web Tools using application servers such 7as Tomcat 4.0 or Macromedia JRun 4.0:

7

Tomcat 4.0

7

7

7
1. Prepare the Tomcat 4.0 configuration file (CLASSPATH) by completing the 7following: 7
   7
   1. Create a new environment/system variable CATALINA_HOME to contain the path (root directory) to Tomcat 4.0. For example, D:\jakarta-tomcat-4.0.3.
   7
   2. Confirm that the Tomcat Servlet/JSP Container is functional: 7
      7
      1. Start Tomcat by running startup.bat from 7Tomcat's bin directory.
      7
      2. Access the main Web page http://localhost:8080/ through a Web browser.
7
2. Deploy the DB2 Web Tools into the Tomcat Servlet/JSP Container by 7locating the DB2 Web Tools installation path (i.e. Sqllib\tools\web\db2wa.war) and copying db2wa.war into Tomcat's 7deployment directory (i.e. Tomcat's webapps directory).
7
3. Invoke DB2 Web Tools on Tomcat Servlet/JSP Container by completing the following: 7
   7
   1. Open a DB2 Command Window and change the directory to Tomcat's bin directory.
   7
   2. Start Tomcat using startup.bat and confirm 7that a new directory (db2wa) has been added 7into the webapps directory. 7 7
      Note:
      7
      Running startup.bat from a command prompt window 7would not set DB2PATH. In order to enable DB2PATH being set, the CLASSPATH 7line needs to be changed to explicitly reference the DB2 UDB installation path rather than the 7%DB2PATH% environment variable.
   7
   3. The DB2 Web Tools enterprise application is located at http://localhost:8080/db2wa and can be accessed with an HTML 4.0 compliant 7Web browser.

7

7

JRun

7

7

7
1. Prepare a new application server for DB2 Web Tools by completing the following 7tasks: 7
   7Recommendation 7

   Creating a new application server is recommended, but not mandatory. For 7testing purposes, the default server can be used, and only the configuration 7of the JVM classpath and the deployment is required.

   7
   7
   1. Start the JRun Management Console and login as the administrator of the 7application server.
   7
   2. Create a new application server using Create 7New Server located at the top right of the main page. Do not change the 7host name selection from localhost.
   7
   3. Enter the new server name (DB2WebToolsServer) and click the JRun Server Directory. The value is automatically filled 7in.
   7
   4. Click the Create Server button.
   7
   5. Record the generated values or enter new values for: 7
      7
      • JNDI Provider URL
      7
      • Web Server Port Number. This would be the value to be used in the URL 7for the DB2 Web Tools (i.e. http://localhost:web_server_port_numer/db2wa)
      7
      • Web Connector Proxy Port Number
   7
   6. Click update port numbers if necessary 7and close the window.
7
2. Deploy DB2 Web Tools on the JRun application server by completing the following 7tasks: 7
   7
   1. Start the application server selected to host DB2 Web Tools Web application (DB2WebToolsServer, 7default or any other except admin).
   7
   2. Click Web Applications and then click Add.
   7
   3. Browse the Deployment File section to select 7the Sqllib\tools\web\db2wa.war file in the DB2 UDB 7installation path.
   7
   4. Click Deploy and confirm that the context 7path is /db2wa.
   7
   5. Select the application server and confirm that the DB2 Web Tools application 7appears in the Web Applications section. Do not click Apply on 7this page.
   7
   6. Select the Home link from the upper left 7panel of the main page.
   7
   7. Restart the application server from the Home view that contains the DB2 Web Tools (DB2WebToolsServer).

The DB2 Web Tools enterprise application is located at http://localhost:your_web_server_port_numer/db2wa and can be 7accessed with an HTML 4.0 compliant Web browser. 7

7

If you want to exploit direct disk access, create your DMS device containers 7using Direct I/O to avoid future migration issues.

To stop and start the Information Center daemon:

7
1. Halt the daemon if it is already running. At a command line, enter: 7

   INIT_DIR/db2icd stop

   where INIT_DIR is the installation directory of the db2icd file 7listed previously.
7
2. Change any of the variables for the daemon by editing the db2ic.conf file. Currently, you can modify the TCP port number where the documentation 7is available, and the location of the temporary workspace used by the daemon 7while it is running.
7
3. Start the daemon. At a command line, enter: 7

   INIT_DIR/db2icd start

   where INIT_DIR is 7the installation directory of the db2icd file listed previously.

When the daemon starts, it uses the new environment variables.

There is also an option to shut down and restart the daemon immediately. 7At a command line, enter:

INIT_DIR/db2icd restart

where INIT_DIR is the installation directory 7of the db2icd file listed previously.

You can check the status of the daemon at any time. At a command line, 7enter:

INIT_DIR/db2icd status

where INIT_DIR is the installation directory of the db2icd 7file listed previously. The daemon returns the current status, and displays 7the ID of the daemon process or processes if it is active.