Another technique that you can use to accomplish a mass deployment is to copy the entire hard drive on the model office, using a copy utility such as Ghost**. When the hard drive is copied, you will have to customize the resulting image before using it. For example, the satellite ID on the satellite will have to be set to a unique value, as will many operating system values, such as the TCP/IP host name.
For this technique to be suitable, the following must be true:
To create the image, you can use the model office, or a copy of it.
After you copy the model office, you will have to perform customization to represent the unique environment that each user requires. The following sections outline the customization that you must perform on the DB2 portion of the satellite.
If you perform a mass copy, you need to customize the following for DB2:
When you copy the hard drive of the model office, you not only copy the database and the definitions for tables, indexes, and other database objects, you also copy the data. Most likely, this data will not be the right subset of the corporate data for the satellite. You will have to delete and replace the data. If you are using data replication, you can use it to populate the satellite with its data after deleting the table data that was in the copy. If you are not using data replication, you can populate the tables on the satellite with the load or import utilities.
If you are using data replication to keep data on the satellite synchronized with data in a corporate system, you will need to set up the replication subscription for this satellite and load its initial data. You should:
You will have to customize unique operating system values (such as the computer name) and communications information (such as the TCP/IP host name) for each satellite. The techniques that you use to accomplish the customization, and the list of characteristics that must be customized are beyond the scope of this manual.
You must perform several other steps to fully enable the satellites that you are mass installing. See Completing Your Mass Deployment for more information.
Before your deployed satellites can synchronize, you must define and set them up in the DB2 control server. Assuming that you have been using the model office and test satellites to prepare for the mass deployment, the group, application version, and group batches for the application version already exist. You only need to add the deployed satellites to the group and promote the batches to production
Locate the group for which the mass deployment is being performed, and using the Create Satellite notebook, add the satellites. You must also enable the satellites to execute group batches. If your deployment is very large, using the Satellite Administration Center interface may be very time consuming. A sample SQL script, which you can use to perform a mass insert of the required entries into the satellite control database is available on the Web at the following site:
www.software.ibm.com/data/db2/library/satellite
You should also ensure that the group batches that the deployed production satellites will execute when they synchronize are promoted to production. For information on performing this task, see Promoting a Test Level to a Production Level.
[ Top of Page ]