Install, configure, and rollout Tivoli Framework (FWK), Software Distribution (SWD), Inventory (INV), and Remote Control (RCL) for one of the largest energy companies in North America, Sempra Energy.
 
Sempra’s computing environment consisted of systems from newly acquired companies throughout all of Southern California. The environment consisted of different operating systems, including Windows 95/98, NT, UNIX, or OS/2. With so many acquisitions, Sempra planned to use Tivoli’s INV software as a way to provide their asset management software with help in controlling computer assets.

Ephibian’s first task was to design a management solution that would support Sempra’s environment. Since Sempra is spread out across Southern California, the Tivoli architecture was divided geographically. Sempra had already designed the underlying network addresses by geography, therefore, it was easier for them to estimate endpoint locations as they were created.
 
Policy Regions were created and given names based on cities or regions where sites were located. Domain login scripts were written that would create endpoints and automatically place them into the correct Policy Region, based on the same network address scheme.
 
Attempting to create all endpoints (approximately 10,000) at roughly the same time would saturate the TMR server. To avoid this, regions were added individually so the server could handle smaller, but manageable “login storms”. Endpoint login scripts were written to allow endpoints into the TMR based on what region the endpoint belonged.
 
Once endpoints were created, the inventory/asset problem was tackled. Sempra’s Asset Management Staff (AMS) provided a listing of available fields that could be captured and ported to an Oracle database. Once it was decided which fields were required, a new table was created. A cron job was developed to automatically import new data files generated by AMS into the Oracle table.
 
Tivoli INV Profiles were used to scan the hardware and software of each endpoint. A Visual Basic program was written to capture personal information about the user and the output stored in a MIF file. Another INV Profile was then distributed to collect the MIF files and store the information into the Oracle database, effectively linking assets to personnel.

• Tivoli architecture scripts
  

• Domain login scripts based on endpoint OS
  

• Endpoint login scripts based on IP addresses
  MIF file generation, collection, and integration of secondary database.
  

• Automated redistribution of failed software rollouts
  

• Architecture design down to subnet level
  Remote Control setup and configuration for Help Desk
  

• Tivoli Administrator training inux Red Hat operating system with the Netscape 4.7 Internet browser