 Deploying IBM DB2 Products
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.
|
