Step 4: Production Deployment


After completing the testing of your application on DB2, next step is to deploy your DB2 products.

Deployment


Planning the deployment of DB2 based solutions among various operating system platforms and DB2 products might appear be a complex endeavor. This tutorial briefly describes the different methodology for deploying the DB2 family of products on Linux, UNIX, and Windows platforms across multiple computers quickly, easily, and consistently.

The first step in deployment planning is choosing the right product. After selecting the right product, the next step is to deploy it on machines. Installing a product on a single machine will not take much time and effort however deploying the product on mass level might be challenging as each machines will take lot of time and effort.
The steps to install and deploy DB2 product differ by platform, the overall steps are:

  1. Planing your deployment
  2. Creating a response file
  3. Creating a deployment script or definition
  4. Running the deployment script or definition on all computers
  5. Reducing the size of installation image


Example


Figure in the right pane illustrates an environment topology. There are Seven AIX boxes (Box A, B, C, D, E, F, G) targeted for deployment. All the systems have the same operating system and the same version of DB2. The DB2 installation image is on Box A, which acts as a file server. Deployment script executed from Box A will send commands to Box B, C, D, E, F, G across the network. Box A is set-up as a Network File System (NFS) server and Box B, C, D, E, F, G act as NFS clients. Therefore Box B, C, D, E, F, G can access the DB2 installation image on Box A through the network.