332 Implementing a Tivoli Solution for Central Management of Large Distributed Environments
6.1 Automating deployment
The process that facilitates automatic deployment of software packages and
monitoring profiles is based on the endpoint policy support in the Tivoli
Management Framework. This allows for executing specialized scripts when the
endpoints log in, and provides support for handling the first login (initial login) as
a special case. Outlet Systems Management Solution will use those capabilities,
as shown in Figure 6-1.
Figure 6-1 The automated deployment process
The outline of the process is:
1. An endpoint is installed on the outlet server, and attempts login to the hubtmr
system (specified during installation).
2. The allow_login policy script is executed at the hubtmr, and uses the
<store>.lst files and the gateway.lst file to verify the eligibility of the endpoint
to log in.
3. The select_gateway policy script takes control, still at the hubtmr, in order to
identify the primary gateway for the endpoint. The gateway.lst file controls
this, and at the end, both the endpoint and the gateway are notified. The
endpoint logs off from the hubtmr.

Get Implementing a Tivoli Solution for Central Management of Large Distributed Environments now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.