Discover best practices for deploying the IBM® DB2®
9.5 family of products on Linux®, UNIX®, and Windows® platforms across multiple computers quickly, easily, and consistently.
Deploying IBM DB2 products, including IBM DB2 and DB2 Connect™, on Linux, UNIX
and Windows platforms for dozens, hundreds, or thousands of clients and servers might
seem like a daunting task. However, DB2 9.5 has features and tools that enable you to
deploy both servers and clients quickly and seamlessly across your enterprise.
You can deploy DB2 9.5 using deployment technologies such as
Microsoft® Systems
Management Server (SMS), or you can use an easy and effective manual deployment
method. The type of deployment best suited for your organization depends on your
distribution and maintenance requirements, as well as on the hardware, software, and
overall infrastructure of your existing computing environment.
You can run the DB2 installer either as a GUI installer which provides an interactive type
of installation or in a mode where input is passed to the installer through a response file.
The latter method, which is referred to as an unattended or a response file installation,
does not display a GUI and does not require any user input.
An unattended installation, which you can use to deploy software to a large number of
users, provides more functionality and flexibility than a GUI installation. Using the
unattended installation method, you can:
- Create more than one instance
- Catalog and create databases
- Set database manager configuration parameters and profile registry variables
- Import instance profiles generated from the db2cfexp command (the
connectivity configuration export tool)
- Embed DB2 software within applications
- Use the same response file to roll out identical copies of your DB2 products
across multiple computers using the same components, registry variable settings,
and instance configuration settings.
The easiest way to deploy your DB2 product across your organization is to perform
multiple unattended installations using the DB2 installer with a response file. The
unattended installation is designed to eliminate the need for user input at the target
computers.
As an up-front preparation cost, the customization of the response file (specifying
components, registry variable settings, and instance configuration settings) is done once
and the actual deployment can then typically be performed quickly for hundreds or
thousands of computers. Additional computers may be added to the deployment later
with almost no additional preparation required.
- Executive summary
- Introduction
- Planning your deployment
- What should I install?
- DB2 server products
- DB2 clients and drivers
- Redistributing clients and drivers
- Installation methods
- Unattended installation using a response file
- Unattended installation using the db2_install script (Linux and UNIX)
- Manual installation (Linux and UNIX)
- Reducing the size of your installation image
- Deploying using software distribution software (Windows)
- Applying DB2 license files to images that you distribute
- Fix pack installations
- Creating a location for the installation image
- Creating a response file
- Creating response files using the DB2 Setup wizard
- Using the DB2 response file generator (Windows)
- Manually creating a response file using the sample response files
- Modifying a response file
- Instance creation settings
- DAS settings
- Client deployment considerations
- Single-server deployment considerations
- Parallel-server deployment considerations (Linux and UNIX)
- Creating a DB2 configuration profile (optional)
- Creating a deployment package or script
- Packaging IBM Data Server products using SMS 2003
- Creating a deployment script
- Deploying a response file installation
- Post-installation tasks
- Server considerations
- Deploying an installation using db2_install (Linux and UNIX)
- Deploying a fix pack
- Running the deployment script or definition on all computers
- Distributing IBM Data Server products using SMS
- Example of a push installation using a script (UNIX)
- Example of a pull installation using a script (UNIX)
- Reducing the size of a DB2 product installation image
- Pruning a DB2 product installation image using the db2iprune utility
- Best Practices
- Summary
- Further Reading
- Notices
"
Best Practices:
Deploying IBM DB2 Products
"
(May 2008)
Discover best practices for deploying the DB2 9.5 family of products on Linux, UNIX, and Windows platforms across multiple computers quickly, easily, and consistently. (pdf; 756KB; 46 pages)
Comment, edit, or add your own insights to the High Availability
Disaster Recovery best practices
on the IBM Database Wiki.
Check out all the other Best Practices papers and see how you can improve your experience with DB2 for Linux, UNIX, and Windows.
| 
