IBM Tivoli Provisioning Manager for OS Deployment, Version 7.1.1.16

Example: Installing a Windows multiserver infrastructure with a DB2 centralized database

About this task

You can set up a multiserver with a single, centralized DB2 database that is shared by all Windows OS deployment servers, with server replication, by performing the following steps:

Procedure

Create an empty DB2 database on a DB2 server machine (UNIX or Windows). Tivoli® Provisioning Manager for OS Deployment has no restrictions for the database name that you choose, but DB2 allows a maximum of 8 characters. The OS deployment server automatically populates the database with the necessary tables. Proceed with steps 2 to 5 for each Windows server on which you want to install the OS deployment server.
Install the IBM DB2 Client and catalog the remote DB2 database. Test the client connection to the database, for example, locally on the database client by running the following commands on the DB2 CLP window:
```
db2 catalog TCPIP NODE <node-name> REMOTE <db2-server-hostname> SERVER <server-name/port>
db2 catalog DATABASE <db-name> AT NODE <node-name>
db2 connect to <db-name> user <dbuser> using <dbpasswd>
```
You can also perform these steps using the DB2 Configuration Assistant.
Create an ODBC system DSN pointing to the database cataloged on the machine in step 2. You must name the DSN AutoDeploy; this is case-sensitive.
Note: If you installTivoli Provisioning Manager for OS Deployment before creating the ODBC DSN, or if you fail to name the DSN AutoDeploy, the installer creates a local Microsoft Access database for this OS deployment server.
Run the Tivoli Provisioning Manager for OS Deployment installation wizard.
At the end of the installation process, you are prompted for an account and a password to use for the database table creation and for the connection. You must have sufficient privileges to create tables, columns, and so on (database owner).

What to do next

When you have installed your OS deployment servers, set up the server hierarchy from the Web UI and the replication. Refer to the Tivoli Provisioning Manager for OS Deployment documentation for details about the various replication methods that can apply to this scenario.

Feedback