Implementing a Tivoli Solution for Central Management of Large Distributed Environments

364 Implementing a Tivoli Solution for Central Management of Large Distributed Environments

A.3.5 gateway.lst

This file in Example A-12 is used to correlate stores and regions and their related

gateways.

Example: A-12 gateway.lst

## TMR Gateways

hubtmr-gw1393424439.1.594#TMF_Gateway::Gateway#tecsrcrdbspom084fabmmmmmwconmjn

kcbibm

spoketmr-gw1282790711.1.1146#TMF_Gateway::Gateway# tmtreg

## Regional Gateways

#TEXAS01-gw$TMR.x.xx#TMF_Gateway::Gateway#

#OHIO01-gw$TMR.x.xx#TMF_Gateway::Gateway#

region01-gw1282790711.2.23#TMF_Gateway::Gateway#stadev

## Store Gateways

#TEXAS_1234-gw$TMR.x.xx#TMF_Gateway::Gateway#

#OHIO_4321-gw$TMR.x.xx#TMF_Gateway::Gateway#

region_store-gw1282790711.3.23#TMF_Gateway::Gateway# STORE

## Assumptions:

##

## 1 - Endpoint labels must be set at machine installation time to the

following format: <hostname>_<region>_<store>-ep

## 2 - Each store has a unique number (e.g. 1234 does not appear in other

regions)

A.3.6 login_policy

This endpoint policy in Example A-13 is used for all endpoint logins, apart from

the initial login performed for new endpoints. The following implementation only

logs the login, but customized proceeding can be applied.

Example: A-13 login_policy

#!/bin/sh

# -------------------------------------------------------------------------

# Descrizione: Login script

# - sul gateway nella directory $LOG_FILE viene creato un file

# $ep_label. La data/time di ultima modifica e’ usata per capire