Installation and Configuration Supplement
7
7
7Application server for DB2 UDB
7The application server for DB2 Universal Database (UDB) no longer supports
7remote administration or stored procedures.
7The updated topics are as follows:
7
7Enabling the application server for DB2 UDB
7Enabling the database does the following:
7
7- Connects to a specified database
7- Creates and populates metadata tables
7- Updates the DBM CFG parameters, JDK_PATH, and JAVA_HEAP_SZ
7- Installs the DB2 Web Services Application.
7
7Prerequisite
7On 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.
7
7Procedure
7To enable the application server for DB2 UDB, perform the following:
7
7- 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- 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- 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.
7Once the application server for DB2 UDB is enabled, the application server
7is started automatically.
7
7Starting the application server for DB2 UDB locally
7The application server should be started using the fenced user ID for systems
7creating web services in a .NET environment or running XML Metadata Registry
7(XMR) only.
7
7Starting the application server for DB2 UDB remotely
7This section is removed. The application server for DB2 UDB no longer
7supports remote administration.
7
7Stopping the application server for DB2 UDB locally
7The application server should be stopped using the fenced user ID for systems
7creating web services in a .NET environment or running XML Metadata Registry
7(XMR) only.
7
7Stopping the application server for DB2 UDB remotely
7This section is removed. The application server for DB2 UDB no longer
7supports remote administration.
7
7Uninstalling the application server for DB2 UDB
7This section is removed. The application server for DB2 UDB no longer
7supports remote administration.
7
7
7DB2 Embedded Application Server enablement
7The enabled database of a DB2 Embedded Application Server must be located
7in a 32-bit instance Any databases accessed from the DB2 Embedded Application
7Server can be located in 32-bit or 64-bit instances.
7
7
7Deploying DB2 Web Tools
7Application servers using JDK 1.4 no longer require customization of the
7CLASSPATH variable during DB2 Web Tools deployment. All dependencies, including those
7for XML parser and transformer, are now deployed with the web module and are
7expected to be loaded from the WEB-INF\lib directory
7according to the J2EE specification. This change affects two information topics:
7
7- Deploying DB2 Web Tools on WebLogic application servers
7- Deploying DB2 Web Tools on other application servers
The updated topics are as follows:
7
7Deploying DB2 Web Tools on WebLogic application servers
7This task describes how to deploy and configure DB2 Web Tools (including the Web Command Center
7and the Web Health Center) on BEA WebLogic 7.0. These tools run as Web applications
7on a Web server to provide access to DB2 servers through Web browsers.
7
7Prerequisites
7Before you install DB2 Web Tools on WebSphere, ensure that you have:
7
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:
7DB2 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.
7
7Restrictions
7The following restrictions apply to the DB2 Web Tools deployment:
7
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:
7The 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.
7
7Procedure
7To install DB2 Web Tools on WebLogic application servers:
7
7- Deploy the DB2 Web Tools through the WebLogic administrative console
7by completing the following:
7
7- Start the WebLogic administrative console.
7- Click domain -> deployments -> Web Applications in
7the left pane of the window.
7- Click the Configure a new Web Application link
7to install DB2 Web Tools Web application.
7- Browse the listing of the file system to locate Sqllib\tools\web\db2wa.war.
7- Click on select beside the db2wa.war file name.
7- 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:
7Preserving the original name db2wa is
7mandatory, as DB2 Web Tools has it hardcoded.
7- Click Configure and Deploy.
7- 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- 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.
7
7Deploying DB2 Web Tools on other application servers
7This task describes how to deploy and configure DB2 Web Tools (including the Web Command Center
7and the Web Health Center) on other application servers such as Tomcat 4.0
7and Macromedia JRun 4.0. These tools run as Web applications on a Web server
7to provide access to DB2 servers through Web browsers.
7
7Prerequisites
7Before you install DB2 Web Tools, ensure that you have:
7
7- An application server, such as:
7
7- IBM DB2 Administration Client Version 8.
7- A Web browser that is compliant with HTML 4.0.
7
7Restrictions
7The following restrictions apply to the DB2 Web Tools deployment:
7
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:
7The 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.
7
7Procedure
7The following are the procedures for installing DB2 Web Tools using application servers such
7as Tomcat 4.0 or Macromedia JRun 4.0:
7
7- Tomcat 4.0
7-
7
7- Prepare the Tomcat 4.0 configuration file (CLASSPATH) by completing the
7following:
7
7- 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- Confirm that the Tomcat Servlet/JSP Container is functional:
7
7- Start Tomcat by running startup.bat from
7Tomcat's bin directory.
7- Access the main Web page http://localhost:8080/ through a Web browser.
7- Deploy the DB2 Web Tools into the Tomcat Servlet/JSP Container by
7locating the DB2 Web Tools install path (i.e. Sqllib\tools\web\db2wa.war) and copying db2wa.war into Tomcat's
7deployment directory (i.e. Tomcat's webapps directory).
7- Invoke DB2 Web Tools on Tomcat Servlet/JSP Container by completing the following:
7
7- Open a DB2 Command Window and change the directory to Tomcat's bin directory.
7- Start Tomcat using startup.bat and confirm
7that a new directory (db2wa) has been added
7into the webapps directory.
7
7
Note:
7Running 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- 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- Prepare a new application server for DB2 Web Tools by completing the following
7tasks:
7
7Recommendation
7Creating 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- Start the JRun Management Console and login as the administrator of the
7application server.
7- 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- Enter the new server name (DB2WebToolsServer) and click the JRun Server Directory. The value is automatically filled
7in.
7- Click the Create Server button.
7- 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- Click update port numbers if necessary
7and close the window.
7- Deploy DB2 Web Tools on the JRun application server by completing the following
7tasks:
7
7- Start the application server selected to host DB2 Web Tools Web application (DB2WebToolsServer,
7default or any other except admin).
7- Click Web Applications and then click Add.
7- Browse the Deployment File section to select
7the Sqllib\tools\web\db2wa.war file in the DB2 UDB
7installation path.
7- Click Deploy and confirm that the context
7path is /db2wa.
7- 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- Select the Home link from the upper left
7panel of the main page.
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
7
7
7Direct I/O on block devices (Linux)
7Direct I/O is now supported on both file systems and block devices for
7distributions of Linux with a 2.6 kernel. Direct I/O on block devices
7is an alternative way to specify device containers for direct disk access
7or for raw I/O. The performance of Direct I/O is equivalent to the raw character
7device method. DB2 Universal Database (UDB) enables Direct
7I/O while opening the table space when the CREATE TABLESPACE statement specifies
7a block device name for the container path. Previously, the same performance
7was achieved using the raw I/O method, which required binding the block device
7to a character device using the raw utility.
7
7
7
7Table 27. Comparison of direct I/O and raw I/O
7
7
7Direct I/O (new method) |
7Raw I/O (old method) |
7
7
7
7
7
7CREATE TABLESPACE dms1
7MANAGED BY DATABASE
7USING (DEVICE '/dev/sda5' 11170736) |
7
7CREATE TABLESPACE dms1
7MANAGED BY DATABASE
7USING (DEVICE '/dev/raw/raw1' 11170736) |
7
7
7
7Although the raw I/O method is still supported by DB2 UDB, it has been deprecated and support
7for it might be removed from future kernels.
7
7Recommendation
7If you want to exploit direct disk access, create your DMS device containers
7using Direct I/O to avoid future migration issues.
7
7
7Note:
7Direct I/O is not supported by DB2 UDB on Linux/390.
7
7
7DB2 Information Center daemon (Linux and UNIX)
7The DB2 Information Center daemon is responsible for the control of the DB2 documentation
7server. The daemon, which is part of the DB2 Information Center installation, is composed
7of two files:
7
7- db2icd - the initialization script
7- db2ic.conf - the configuration file
These files are installed in the following locations:
7
7- AIX
7- /etc/db2icd
7
/var/db2/v81/db2ic.conf
7
7- HP
7- /sbin/init.d/db2icd
7
/var/opt/db2/v81/db2ic.conf
7
7- Solaris Operating Environment
7- /etc/init.d/db2icd
7
/var/db2/v81/db2ic.conf
7
7- Linux
7- /etc/init.d/db2icd
7
/var/db2/v81/db2ic.conf
7
7
7
7Starting or stopping the Information Center daemon (AIX, Solaris Operating
7Environment, HP, Linux)
7The only time you should need to start or stop the daemon manually is when
7you want to change the configuration variables for the daemon. Normally, the
7daemon is started at system startup, according to the run levels created during
7the installation of the DB2 Information Center.
7
7Procedure
7To stop and start the Information Center daemon:
7
7- 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- 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- 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.
7There is also an option to shut down and restart the daemon immediately.
7At a command line, enter:
7INIT_DIR/db2icd restart
where INIT_DIR is the installation directory
7of the db2icd file listed previously.
7You can check the status of the daemon at any time. At a command line,
7enter:
7INIT_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.
8
8
8Response file keywords and sample files
8To install the DB2 Information Center Version 8.2 using a response file,
8use the following information:
8
8- Response file keyword (PROD)
8- INFORMATION_CENTER
8
8- Response file name
8- db2doce.rsp
8
8
7
7
7Response file installation error codes
7The following error code is for Windows only and is not applicable to Linux and UNIX operating systems.
7
7- 3010
7- The installation is successful, however a system restart is required
7to complete the installation.
7
7
7
7
7Required user accounts for installation of DB2 servers (Windows)
7
7- Increase quotas
7- The Increase quotas user right has been
7changed to Adjust memory quotas for a process on
7the Windows XP and Windows Server 2003 operating systems.
7
7- User rights granted by the DB2 installer - Debug Programs
7- The DB2 installation program does not grant the Debug Programs user right.
7The DB2 installer grants the following user rights:
7
7- Act as part of the operating system
7- Create token object
7- Lock pages in memory
7- Log on as a service
7- Increase quotas
7- Replace a process level token
7
7
7
7
7Asynchronous I/O support (Linux)
7Asynchronous I/O (AIO) support is now available on Linux (2.6 and
7some 2.4 kernels) for raw devices and O_DIRECT file systems. AIO improves
7page cleaner performance. You can enable or disable AIO on Linux by issuing
7the db2set command.
7To use AIO, users must install libaio-0.3.98 or later and have a kernel
7that supports AIO. Users must also run the db2set DB2LINUXAIO=true command and restart DB2 Universal Database.
8
8
8db2ln command modified to create DB2 UDB 64-bit library links (Linux and UNIX)
8In previous levels of DB2 Universal Database (UDB) Version 8, the db2ln command created certain DB2 links under
8/usr/lib and /usr/include. On platforms where both 32-bit and 64-bit DB2 UDB
8instances are supported, these links point to library files or include files
8under DB2DIR/lib64 or DB2DIR/include64 by default, where DB2DIR is the directory
8where DB2 UDB Version 8 is installed. If the default is not desired, you can
8specify the bit width by running the db2ln command
8with the -w flag:
8db2ln -w 32|64
This prevents DB2 UDB 32-bit instances
8from coexisting with 64-bit instances on some platforms.
8Starting with DB2 UDB Version 8.2, the db2ln command
8creates DB2 64-bit library links on those platforms in appropriate directories.
8 In this case, the -w flag is only used for populating /usr/include. When
8the db2ln command creates the links for DB2 UDB library
8files, both 32-bit and 64-bit links are created on supported platforms. This
8allows both 32-bit instances and 64-bit instances to exist and run at the
8same time.
8On some Linux distributions, the libc RPM command comes with the /usr/lib/libdb2.so
8or /usr/lib64/libdb2.so library. This library is used for Sleepycat Software's
8Berkeley DB implementation and is not associated with IBM's DB2 UDB. However,
8this file prevents the db2ln command and the db2rmln command from functioning. The db2ln command does not overwrite the file and the db2rmln command does not remove the file. In this case, to compile applications
8using DB2 UDB, compiling and linking processes need to provide a full path
8to DB2 UDB's headers and libraries, respectively. This is the recommended
8method because it allows compiling and linking against multiple releases of DB2 UDB
8on the same computer.
8See the DB2 UDB Version 8.2 Installation and Configuration manual for details about restrictions using the db2ln command.
[ Top of Page |Previous Page | Next Page | Contents ]