Chapter 2. DB2 server deployment 57
During the execution of InstallTester, you can see how original progress
information and general messages are processed. For example, a message like
this:
Message: PROGRESS TASK START :: INSTALLATION :: 3 :: 253 :: SQL procedures
Will be transformed to this format:
Purpose: Received when a new task starts
Task type: INSTALLATION
Estimated task time: 3 second(s)
Task ID: 253
Task description: SQL procedures
With the INTERACTIVE keyword set as MACHINE, DB2 installer outputs the
messages with “::” embedded as a delimiter. The InstallTester parses each
message according to the delimiter “::” and then presents it back to the user in a
more meaningful format.
As in response file installation, a default log file is generated in /tmp/
db2setup.log. We can find more details in this log file, for example, what
components have been installed, what commands were used in the deployment,
and what post deployment tasks have been finished.
2.2.4 Payload file deployment (for Linux and UNIX)A payload file is a compressed tar archive that contains all of the files and
metadata for an installable component. This method extracts component files
from the payload file, directly save them into the target path, then use db2chgpath
to update the embedded runtime path. This deployment method is for the
advanced user only and is not a recommended installation method.
For more details about the payload file deployment, visit the DB2 Information
Center:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/
com.ibm.db2.luw.qb.server.doc/doc/t0023683.html
Note: This method requires further manual configuration steps. Ensure that
the payload installation is required for your enterprise before using it in your
deployment.