TME 10 Software Distribution User s Guide. Version 3.6

Transcription

1 TME 10 Software Distribution User s Guide Version 3.6 September 1998

2

3 TME 10 Software Distribution User s Guide (September 1998) Copyright Notice Copyright 1998 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management Environment, TME 10, TME 10 ADE, TME 10 AEF, TME 10 Distributed Monitoring, TME 10 EIF, TME 10 Enterprise Console, TME 10 Framework, TME 10 Inventory, TME 10 Software Distribution, TME 10 User Administration. Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notice References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System s or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York

4

5 TME 10 Software Distribution User s Guide Preface... ix I Getting Started Chapter 1 What is TME 10 Software Distribution? TME 10 Software Distribution Features TME 10 Software Distribution and the Framework Endpoints Nested File Packages File Package Definitions AutoPacks Configuration Programs WAN-smart Capabilities Multiplexed Distributions Network Bandwidth Tuning Security Chapter 2 Installation Installing TME 10 Software Distribution Products Installing with TME 10 Software Installation Service Installing with the TME 10 Desktop Desktop Command Line Upgrading from Software Distribution Desktop Command Line Removing TME 10 Software Distribution TME 10 Software Distribution User s Guide i

6 Installing the AutoPack Control Center Installing on Windows NT or Windows Installing on Windows Installing the AutoPack Agent II Using TME 10 Software Distribution Chapter 3 The Distribution Environment Introducing NoonTide Network Architecture Creating a Repeater Hierarchy Configuring Repeater Sites Setting Repeater Parameters Creating NetWare Managed Sites The dollar-win NetWare Managed Site The rainbow-win NetWare Managed Site The rainbow-95 NetWare Managed Site Installing Additional TME 10 Applications Chapter 4 Software Deployment Using File Packages Creating a Staging Area for Source Files Creating FrameMaker File Packages Setting File Package Properties Setting Properties from the Desktop Setting Properties Using Export and Import Creating Configuration Programs and Input Files The bfr_hp.sh Before Program The aft_hp.sh After Program The lic.sh Script The aft.txt and lic.txt Files Setting File Package Subscribers ii Version 3.6

7 Creating TME 10 Inventory Queries Distributing the FrameMaker File Packages Chapter 5 Software Deployment Using AutoPacks Introducing the AutoPack Control Center Creating the AutoPack File Creating the Baseline Snapshot Installing the Software Building the AutoPack File Setting AutoPack File Properties Editing an Existing AutoPack File Creating an AutoPack Profile Distributing Office III Performing Software Distribution Operations Chapter 6 Profile Setup Creating a Software Distribution Profile Desktop Command Line Cloning a Profile Desktop Command Line Setting the Profile Subscribers Drag and Drop Desktop Command Line Deleting a Profile Desktop Command Line TME 10 Software Distribution User s Guide iii

8 Chapter 7 File Package Properties Defining and Editing File Package Properties Desktop Command Line Exporting and Importing File Package Definitions Desktop Command Line Creating File Packages from an Application Management Package Invoking the winstruct_file Command Distributing the Application Chapter 8 File Package Options Configuration Programs Before Program After Program Removal Program After Removal Program Commit Program On Error Program Input Files Multiple Configuration Programs and Input Files Return Status of Configuration Programs Running Configuration Programs in the Background Processing Arguments to Configuration Programs Encoding and Decoding Distribution Data Setting UNIX File Package Options Desktop Command Line Setting NetWare File Package Options Desktop Command Line iv Version 3.6

9 Setting PC File Package Options Desktop Command Line Chapter 9 File Package Operations Distributing a File Package Drag and Drop Desktop Command Line Calculating the Size of a File Package Desktop Command Line Pulling a File Package Removing a File Package Desktop Command Line Setting Timeout Values for a Distribution Configuration Script Timeout Repeater Manager Timeout High-level TCP Timeout Gateway Session Timeout Distribution Processes Distributing File Packages Distributing Nested File Packages First Chapter 10 AutoPack Properties and Operations Setting AutoPack Profile Properties Calculating the Size of an AutoPack Distributing an AutoPack Profile Drag and Drop Desktop Command Line TME 10 Software Distribution User s Guide v

10 Removing an AutoPack IV Additional Features Chapter 11 UserLink for TME 10 Software Distribution Activating UserLink for Software Distribution Creating a TME 10 Administrator for UserLink Desktop Command Line Using UserLink for TME 10 Software Distribution Notifying Users about UserLink Configuring the Status Dialog Chapter 12 Historical Database Feature The Configuration Repository The Query Facility Updating the Repository Enabling the Historical Database Feature Disabling the Historical Database Feature Creating SWDIST_QUERIES Query Library Running SWDISTDATA_QUERY Desktop Command Line Modifying SWDISTDATA_QUERY Chapter 13 TEC Integration Installation The tecad_sd.conf File Software Distribution Classes vi Version 3.6

11 Chapter 14 File Package Blocks Fpblock Commands Using Fpblocks Chapter 15 NetWare Managed Sites Configuring NetWare Managed Sites Creating a NetWare Managed Site Desktop Command Line Editing NetWare Managed Site Properties Desktop Command Line Removing an Unavailable Client Desktop Command Line Additional Commands for NetWare Managed Sites V Reference Appendix A Frequently Asked Questions Software Distribution and Framework Concepts... A-1 File Packages... A-6 AutoPack Files... A-9 AutoPack Profiles... A-11 Distributions... A-14 Configuration Programs... A-19 Troubleshooting and Logging Information... A-22 PCs... A-24 TME 10 Software Distribution User s Guide vii

12 Appendix B Authorization Roles Setting Up TME 10 Software Distribution Profiles...B-1 Defining and Deleting Profiles...B-2 Performing Operations...B-3 viii Version 3.6

13 Preface Preface Tivoli Management Environment 10 (TME 10) Software Distribution provides a means of managing and distributing software across a multi-platform network. For distributions that encompass wide area networks (WANs), TME 10 Software Distribution has a built-in, WAN-smart capability that reduces inter-network traffic and ensures an efficient distribution. This guide explains the concepts and procedures necessary for you to effectively use TME 10 Software Distribution to distribute software over local area networks (LANs) and WANs. Who Should Read This Guide The target audience for this guide is system administrators performing daily TME 10 Software Distribution operations. Users of the guide should have some knowledge of the following: UNIX and NT operating systems Shell programming Concepts such as directories, files, and symbolic links Operating systems running on target machines to which software is distributed Prerequisite and Related Documents You must understand the information in the following manuals before attempting to use this guide: TME 10 Framework User s Guide, TME 10 Framework Planning and Installation Guide, and TME 10 Framework Reference Manual Provide detailed information and procedures to manage the TME 10 environment from the TME 10 desktop or the command line interface (CLI), including information about configuring, maintaining, and troubleshooting your TME 10 installation. TME 10 Inventory User s Manual Provides detailed information on how to manage hardware and software using TME 10 Inventory. TME 10 Software Distribution User s Guide ix

14 Preface TME 10 Enterprise Console User s Guide and TME 10 Enterprise Console Adapters Guide Provide detailed information about integrating network, systems, database, and application management with TME 10 Enterprise Console. What This Guide Contains The TME 10 Software Distribution User s Guide contains the following sections: Part I Getting Started Chapter 1, What is TME 10 Software Distribution? Provides an introduction to the application by describing file packages, distribution programs, platform-specific options, profile management, performance, and security. Chapter 2, Installation Describes the instructions for installing or upgrading the TME 10 Software Distribution products on UNIX and NT managed nodes, and for installing the AutoPack Control Center and AutoPack agent on PC managed nodes in your environment. Part II Using TME 10 Software Distribution Chapter 3, The Distribution Environment Introduces a Tivoli Management Region (TMR) scenario to illustrate how to configure a network topology. This chapter provides steps for setting up a distribution environment that uses endpoint gateways, repeaters, and NetWare managed sites. Chapter 4, Software Deployment Using File Packages Describes the steps required to deploy software, including creating file packages, creating configuration programs, using TME 10 Inventory queries, setting file package subscribers, and distributing file packages. x Version 3.6

15 Preface Chapter 5, Software Deployment Using AutoPacks Describes the steps needed to create and distribute an AutoPack profile. These steps include using the AutoPack Control Center to create an AutoPack file and distributing the file in an AutoPack profile. The AutoPack profile provides a very easy and automated way to bundle software for deployment to PC targets. Part III Performing Software Distribution Operations Chapter 6, Profile Setup Provides instructions for creating, cloning, and deleting profiles. This chapter also describes how to set profile subscribers. Chapter 7, File Package Properties Describes how to set non-platform-specific file package properties. Chapter 8, File Package Options Describes how to use configuration programs to perform various operations during a file package distribution. This chapter also provides procedures to define and set platform-specific file package options. Chapter 9, File Package Operations Details conceptual information and instructions for distributing, calculating size of, retrieving, and removing file packages. Chapter 10, AutoPack Properties and Operations Describes the AutoPack utility, which enables you to create installable images on multiple target machines without running scripts to perform all system changes required by a software package. This chapter details how to create, calculate the size of, distribute, and remove an AutoPack. TME 10 Software Distribution User s Guide xi

16 Preface Part IV Additional Features Chapter 11, UserLink for TME 10 Software Distribution Describes the new UserLink for TME 10 Software Distribution utility, which enables an end-user to retrieve Software Distribution profiles using the TME 10 UserLink interface. This chapter provides instructions for creating and distributing UserLink for Software Distribution files to client machines. Chapter 12, Historical Database Feature Provides a conceptual overview of the TME 10 Framework query facility and the TME 10 Inventory configuration repository. This chapter also describes how to enable the Software Distribution historical database feature and how to access information from the configuration repository. Chapter 13, TEC Integration Explains how to install and enable the TME 10 Enterprise Console integration product. This chapter also provides a description of the Software Distribution event configuration file and event classes. Chapter 14, File Package Blocks Discusses creating file package blocks (also called data warehousing, archiving, or depoting) and the fpblock commands. Chapter 15, NetWare Managed Sites Provides instructions for creating and editing a NetWare managed site. Part V Reference Appendix A, Frequently Asked Questions Lists common questions concerning TME 10 Software Distribution functionality and provides answers to each. Appendix B, Authorization Roles Describes the roles required to perform TME 10 Software Distribution tasks. xii Version 3.6

17 Preface Typeface Conventions The guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Italics Commands, keywords, file names, or other information, for which you will provide literal expressions, appear in bold. Names of windows, dialogs, and other controls also appear in bold. Variables and values that you must provide appear in italics. Bold Italics New terms appear in bold italics when they are defined in the text. Monospace Code examples appear in a monospace font. Many procedures in this guide include icons in the left margin. These icons provide the context for performing a step within a procedure. For example, if you start a procedure by double-clicking on a policy region icon, that icon appears in the left margin next to the first step. If the fourth step of the procedure instructs you to open another icon, that icon appears in the left margin next to the fourth step. Platform-specific Information The following table identifies text used to indicate platform-specific information or procedures. Platform AIX 4.x AS/400 Digital UNIX DG/UX Supported Versions Managed Node, Endpoint: IBM RS/6000 series running AIX, Versions 4.1, 4.2, and 4.3 Endpoint: V3R2, V3R7, V4R1, and V4R2 Managed Node, Endpoint: Versions 4.0a and 4.0d. Endpoint: Versions 4.11 and 4.20 on the ix86 platform TME 10 Software Distribution User s Guide xiii

18 Preface Platform HP-UX NCR NetWare OS/2 Pyramid Sequent SCO SGI Solaris Solaris Intel SunOS Supported Versions Managed Node, Endpoint: HP9000/700 and 800 series running HP-UX, Versions 10.01, 10.10, and Managed Node, Endpoint: NCR 3000 series running NCR UNIX SVR4 MP-RAS and PC Agent, Endpoint: IBM-compatible PCs 486 or higher running Novell NetWare, Versions 3.11, 3.12, 4.01, 4.1, and 4.11 TME 10 Desktop for Windows, PC Agent, Endpoint: IBM-compatible PCs 486 or higher running IBM OS/2, Versions 2.0, 2.1,Warp 3.0, and Warp 4.0 with Win-OS/2 Endpoint: Pyramid MIServer-ES, Version 5.4MN Managed Node, Endpoint: Sequent DYNIX/ptx, Releases and Managed Node, Endpoint: SCO UnixWare 7, SCO UnixWare Versions and Managed Node, Endpoint: SGI IRIX, Versions 6.2 and 6.4 Managed Node, Endpoint: Sun SPARC series running Solaris, Versions 2.4, 2.5, 2.5.1, and 2.6 Managed Node, Endpoint: Solaris2-ix86, Versions and 2.6 Managed Node, Endpoint: Sun SPARC series running SunOS, Versions and xiv Version 3.6

19 Preface Platform Windows Windows NT Supported Versions TME 10 Desktop for Windows, PC Agent, Endpoint: IBM-compatible PCs 486 or higher running Microsoft Windows, Versions 3.1, 3.11, and Windows 95 TME 10 Desktop for Windows, PC Agent, Managed Node, Endpoint: IBM-compatible PCs 486 or higher running Microsoft Windows NT, Versions 3.51 SP5, 4.0, and 4.0 SP3. TME 10 Software Distribution Icons The following icons represent TME 10 Software Distribution profile resources: File package and AutoPack profile resources are created in the context of a profile manager and are distributed to subscribing systems or profile managers managed by TME 10. Contacting Customer Support If you encounter difficulties with any Tivoli products, you can enter to view the Tivoli Support home page. After you link to and submit the customer registration form, you will be able to access many customer support services on the Web. Use the following phone numbers to contact customer support in the United States: the Tivoli number is (1-800-TIVOLI8) and the IBM number is (press or say 8 after you reach this number). Both of these numbers direct your call to the Tivoli Customer Support Call Center. We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send to pubs@tivoli.com. TME 10 Software Distribution User s Guide xv

20 Preface xvi Version 3.6

21 I Getting Started This section contains chapters that introduce you to basic software distribution concepts and TME 10 Software Distribution s powerful features. These features include file packages, AutoPacks, configuration programs, and the central control for software deployment and management. Chapter 1 What is TME 10 Software Distribution? TME 10 Software Distribution Features TME 10 Software Distribution and the Framework Endpoints Nested File Packages File Package Definitions AutoPacks Configuration Programs WAN-smart Capabilities Multiplexed Distributions Network Bandwidth Tuning Security Chapter 2 Installation Installing TME 10 Software Distribution Products Installing with TME 10 Software Installation Service Installing with the TME 10 Desktop Desktop Command Line Upgrading from Software Distribution Desktop Command Line Removing TME 10 Software Distribution TME 10 Software Distribution User s Guide

22 Getting Started Installing the AutoPack Control Center Installing on Windows NT or Windows Installing on Windows Installing the AutoPack Agent Version 3.6

23 1 1What is TME 10 Software Distribution? What is TME 10 Software Distribution? A primary issue facing system administrators and information technology (IT) organizations is deployment management. This issue is complicated by today s prevalence of large, distributed networks. Succeeding at deployment management on distributed networks challenges administrators and IT organizations to Configure machines running different operating systems, which are geographically spread out. Install software in a timely and efficient manner. Maintain software by performing frequent updates using resources that can constrain efforts. Monitor software and data to ensure that it is synchronized with administrative policy. Automate, if possible, the software life cycle, from development through production. These challenges can equate to difficult problems, given today s large, distributed networks comprised of thousands of UNIX machines, Netware and NT servers, and PCs. Attempts to solve deployment management problems often can result in the inefficient use of resources and personnel as too many system administrators use too many management tools to oversee a system. This inefficiency, in turn, can lead to mistakes that disrupt end-users. Existing solutions often TME 10 Software Distribution User s Guide 1 1

24 TME 10 Software Distribution Features fail to reduce the complexity of heterogenous and distributed environments. Tivoli, however, provides an efficient, scalable solution to these deployment management issues through the Tivoli Management Environment 10 (TME 10). Using several TME 10 applications, administrators can develop and distribute desktop and client/server applications, manage the software life cycle, automate system inventories, and monitor system and configuration changes. TME 10 Software Distribution is a key component in solving the deployment management problem. It is used to distribute and deploy software across multi-platform networks, which can include UNIX machines, NetWare and NT servers, and PCs running Windows, Windows 95, Windows NT, and OS/2. TME 10 Software Distribution Features TME 10 Software Distribution provides an efficient method for distributing, installing, and controlling software across a network. Typically, an organization maintains a large stock of software applications and tools for its employees to use. Software Distribution establishes a centralized software management system through which the administrator can install and configure new applications, update existing software with newer versions, and synchronize software on distributed systems. Specifically, TME 10 Software Distribution offers the following features: Enterprise scalability From a central point, an administrator can bundle all files and distribution options and deploy an application to an unlimited number of machines. File packages and AutoPacks provide two containers for, or ways to distribute, these software components. Synchronized deployment By using configuration programs, Software Distribution enables you to distribute an application in a synchronized manner (through commit operations). You can also remove applications and restore target machines to their original state using removal operations. Automatic change discovery The AutoPack enables an administrator to create an installable image that can be 1 2 Version 3.6

25 TME 10 Software Distribution Features distributed to target PCs across the TME 10 environment. The AutoPack utility provides a scriptless installation of software by employing scanning or differencing technology, and thus eliminating the need for configuration programs used by file packages. See the TME 10 Software Distribution AutoPack User s Guide for more information about AutoPacks. WAN-smart capabilities Software Distribution supports parallel distribution, fanout, network bandwidth tuning, pipelining, and data warehousing, all of which propagate rapid and optimal software distributions. Integration with other TME 10 applications The following list summarizes Software Distribution s integration with other TME 10 applications and services: TME 10 Software Distribution Historical Database enables you to use the TME 10 Framework query facility to query a configuration database. Using TME 10 Inventory views and tables, you can determine the appropriate targets of a distribution, as well as track information about software distributions and removals. UserLink for TME 10 Software Distribution enables your end-users on UNIX, Windows, OS/2, and AS/400 endpoints to retrieve Software Distribution profiles using a web-enabled browser to launch the TME 10 UserLink interface. TME 10 Software Distribution TEC Integration enables you to monitor Software Distribution operations as events sent to TME 10 Enterprise Console s event server. TME 10 Software Distribution Extension API enables you to use TME 10 AEF and TME 10 ADE to customize the dialogs and behavior of Software Distribution. See the TME 10 Software Distribution Reference Manual for Software Distribution customization information and procedures. This chapter introduces the main features of TME 10 Software Distribution. Procedures for using Software Distribution features and functionality are covered in detail in later chapters. What is TME 10 Software Distribution? TME 10 Software Distribution User s Guide 1 3

26 TME 10 Software Distribution and the Framework TME 10 Software Distribution and the Framework Endpoints With TME 10 Software Distribution, you can install, configure and update software on networked systems from a single source machine, thereby eliminating the task of manually updating software on those systems. This is accomplished by distributing file packages or AutoPacks. File packages and AutoPacks are Software Distribution profiles that contain references to the files and directories to be distributed, and instructions on how to distribute them. As with other TME 10 profile-based applications, Software Distribution functions in the context of a profile manager. File packages and AutoPacks are created in a profile manager, which contains profiles and subscribers. A subscriber is any managed node, endpoint, PC managed node, NetWare managed site, or profile manager that is the target of the distribution. Finally, the host on which the referenced files and directories reside is the source host. Any UNIX or Windows NT machine in your TME 10 installation can be a source host after the Framework and Software Distribution are installed. For TME 10 Software Distribution profiles, the underlying semantics and effects of a distribution are different than those of other TME 10 profiles. When you distribute a file package or AutoPack, the contained information is actually copied from the source host to the targets. Also, the file package and AutoPack icons only appear in the profile manager in which it was created. For more information on profiles and profile managers, see the TME 10 Framework User s Guide. TME 10 Software Distribution supports file package and AutoPack distributions to endpoints as well as to managed nodes, PC managed nodes, and NetWare managed sites. In the TME 10 environment, an endpoint is a TME 10 client that receives TME 10 operations. Each endpoint is assigned to an endpoint gateway, which provides all communication services between a group of endpoints and the rest of the TME 10 environment. The gateway includes the multiplexed distribution (MDist) function, enabling it to act as the fanout point for 1 4 Version 3.6

27 TME 10 Software Distribution and the Framework distributions to many endpoints. See the TME 10 Framework Planning and Installation Guide for detailed information about how endpoints and gateways can be configured and used in the TME 10 environment. Nested File Packages By adding a file package as an entry to another file package, you can create a nested file package. When Software Distribution distributes a file package that contains nested file packages, it also distributes the nested file packages. Use nested file packages to complete the following: Distribute files from more than one source host. Run different configuration programs for different portions of a single distribution. Distribute sets of files with different properties. There is no limit to the number of nested file packages you can create. In addition, you can nest file packages that belong to different Tivoli Management Regions (TMRs). When file packages are nested, the operations performed on the nesting (parent) file package are also performed on the nested file packages. The nested file package inherits most of the properties from the parent file package. For example, if file package B is nested in file package A (A contains B), then file package B inherits the distribution type, distribution mode, and targets of parent file package A. Properties not inherited by file package B include log information options, operation targets, distribution type, and distribution options. File package nesting is run-time binding: the file package is not included in the nested file package until the parent file package is distributed. This feature allows you to make any necessary changes to a nested file package, even distribute it by itself, and still have TME 10 Software Distribution automatically include any changes when you distribute the parent file package. For instructions on nesting file packages, see Chapter 7, File Package Properties. See Distribution Processes on page 9-27 for instructions and examples of distributing nested file packages. What is TME 10 Software Distribution? TME 10 Software Distribution User s Guide 1 5

28 AutoPacks File Package Definitions AutoPacks In addition to defining file packages from the TME 10 desktop, Software Distribution offers the added flexibility of modifying file packages as text files using the Software Distribution export and import capabilities. Exporting and importing file package definitions provides an easy method to define and customize file packages. This capability is particularly useful when you have a long list of files or nested file packages to distribute, or when you want to create custom file packages with advanced options not supported through the dialogs. If you have a long list of files to distribute, editing a file package definition is more efficient than entering each file name from the dialogs or the command line. For example, suppose you want to distribute an existing file package definition with the exception of one or two files. You can export the file package definition to a text file, exclude the files you do not want to distribute, import the file package definition back into the file package, and distribute the package. For detailed desktop and command line instructions on exporting and importing file package definitions, see Exporting and Importing File Package Definitions on page For more information on file package definition parameters, keywords, and formats, see the TME 10 Software Distribution Reference Manual. An AutoPack is a TME 10 Software Distribution resource type that is similar to a file package but provides a simpler, more convenient way to create installable images for Windows, Windows 95, and Windows NT PCs managed by TME 10. AutoPacks enable you to distribute software to client endpoints without doing anything outside of its creation process. Using the AutoPack feature, you need not create and run configuration programs all scripts necessary to install and run the software are built-in. The AutoPack utility automatically determines the files that need to be distributed and handles Windows installation issues such as 1 6 Version 3.6

29 Configuration Programs registry changes, desktop icons, and programs listed on the Start menu. For more information about creating and distributing AutoPacks, see Chapter 10, AutoPack Properties and Operations. Additionally, the TME 10 Software Distribution AutoPack User s Guide is available with this product. This manual explains concepts and procedures necessary to use TME 10 Software Distributions AutoPack technology. It also describes and demonstrates how to create, distribute, set properties for, and customize AutoPacks. What is TME 10 Software Distribution? Configuration Programs Run.CMD files on OS/2 machines only The synchronization capabilities of TME 10 Software Distribution save time and eliminate the hazard and inconvenience of networked managed nodes running different versions of the same software. Synchronization and transaction-based deployment are achieved by using configuration programs, which you can run at the following times: Before or after distributing software During a commit operation Before and after removing file packages If an error occurs on a target that stops a distribution or removal Before, after, removal, after removal, commit, and on error programs can run on the source hosts and the target. On UNIX, you can run any executable program (for example, a shell script, C program, or Perl script). On NetWare servers, you can run NetWare loadable modules (NLMs) and.ncf batch files. On PCs, you can run executable programs written as.bat,.exe,.com, or.cmd files. In addition, you can specify multiple configuration programs of the same type and input files to run during a distribution or removal operation. When specifying a configuration program for a file package, you can designate where this program will reside. The configuration program and any input files can reside on the source host or on the target machines on which they will run. If the configuration program is a large executable file, it is more efficient to run it from the target TME 10 Software Distribution User s Guide 1 7

30 WAN-smart Capabilities machines rather than from the source host running a conf iguration program from a target saves time and network bandwidth. If you specify that the configuration program and its input files will reside on the source host, Software Distribution automatically distributes these programs and input files from the source host to temporary files on the target machines. You may want to keep the configuration program or input file on the source host for security reasons. For example, if you can control who has root access to the source host but not the target machines, keeping the configuration programs and input files on the source host allows you to more easily prevent someone from making unauthorized changes to them. See Part III, Performing Software Distribution Operations for instructions on specifying configuration programs on UNIX servers, NetWare servers, and PCs. See Chapter 9, File Package Operations for information on how configuration programs are run in nested file packages. See the TME 10 Software Distribution Reference Manual for detailed information on configuration program keywords, related commands, example programs, and limitations of NLMs. WAN-smart Capabilities For distributions that span wide area networks (WANs), Software Distribution utilizes WAN-smart capabilities that reduce network traffic and ensure a fast, efficient distribution. These capabilities include parallel distributions, fanouts, and network bandwidth tuning. Multiplexed Distributions TME 10 Software Distribution performs distributions in parallel when distributing software to multiple target machines. It relies on the MDist service, which enables synchronous distributions of large amounts of data to multiple targets in an enterprise. By default, the TMR server serves as the repeater distribution server for all targets in the TMR.You can configure managed nodes to serve as additional MDist repeaters. Endpoint gateways automatically use MDist to distribute information to endpoints they do not need to be configured after installation. Each MDist repeater, whether it is a 1 8 Version 3.6

31 Use a repeater site as a fanout point to all supported machine types; use a NetWare managed site to distribute a file package from a NetWare server to its PC clients. Security managed node or a gateway, is capable of distributing data in parallel to a large number of clients. If targets reside in a remote TMR network, Software Distribution automatically makes the initial remote distribution to the target s TMR server. From that TMR server, Software Distribution makes a second local distribution of the software to other target machines in that same TMR. This results in a distribution that is faster than sending copies of the software one at a time to each machine. You can fine tune this feature to control the number of simultaneous parallel distributions that should be initiated from each fanout server. This approach is a more effective use of the network than sending a copy of the software across the network gateway for each remote target. You must set up repeaters or NetWare managed sites to route a single copy of the software across the network to a remote machine, and use that machine as a local distribution or fanout point to multiple targets. For information on repeaters, gateways, and NetWare managed sites, see the TME 10 Framework Planning and Installation Guide and the wrpt and wcrtnwms commands in the TME 10 Framework Reference Manual. What is TME 10 Software Distribution? Network Bandwidth Tuning In addition to using repeaters to conserve bandwidth, you can fine tune various network parameters to control the percentage of network bandwidth used during a distribution. You can set values for repeater parameters such as disk space, TCP timeout, disk block, and network load using the wrpt command. See the TME 10 Framework Reference Manual for more information about this command. Security TME 10 Software Distribution functions within the bounds of TME 10 authorization roles to ensure secure and authorized use of the application. To perform an operation within Software Distribution, you must have the required authorization role for the task. Each TME 10 Software Distribution User s Guide 1 9

32 Security procedure in this guide is prefaced with a table showing the role needed for that procedure. In general, the roles in the context of Software Distribution are as follows: Role super senior admin user install-product Operations Install and remove an application; perform operations listed for senior, admin, and user Create, delete, and clone file packages and AutoPacks; edit AutoPacks and file package properties and platform-specific options; import file package definitions; perform operations listed for admin and user Subscribe resources to a profile manager, schedule and perform AutoPack and file package distributions, remove AutoPacks and file packages from subscribers, perform operations listed for user View AutoPacks and file packages, export file package definitions Install an application Software Distribution also supports policy validation for all aspects of file packages and AutoPacks. For more information on policy, see the TME 10 Software Distribution Reference Manual Version 3.6

33 2 2Installation The TME 10 Software Distribution application adds software distribution capabilities to the TME 10 environment. This chapter provides information on how to install and upgrade this application. See the TME 10 Software Distribution Release Notes for system requirements for all TME 10 Software Distribution products. Installation Installing TME 10 Software Distribution Products Before and after installing Software Distribution, Tivoli recommends that you backup your TME 10 database for all machines in the Tivoli Management Region (TMR). Creating backups will enable you to go back to the state of the object database before installation if, for some reason, you encounter a problem while installing the product. To create a backup of the TME 10 server and clients, select Backup from the Desktop menu or use the wbkupdb command. See the TME 10 Framework Reference Manual for information about the wbkupdb command. After installing Software Distribution, you should update the managed resource types of policy regions in which you wish to create file packages. Also, you should update the notice group subscriptions of any administrators who will receive Software Distribution notices. See the TME 10 Framework User s Guide for instructions on changing managed resource types and on assigning administrator s properties. TME 10 Software Distribution User s Guide 2 1

34 Installing TME 10 Software Distribution Products Installing with TME 10 Software Installation Service The TME 10 Software Installation Service (SIS) is a new product that can install multiple TME 10 products on multiple systems in parallel. This Java-based product can, therefore, install more products on more systems in much less time than the TME 10 Framework s install facility. SIS performs product prerequisite checks and, if defined, user-specified prerequisite checks, ensuring as few install failures as possible. In most cases, failures now occur only when machines are turned off or removed from the network. SIS also creates an install repository (IR) into which you can import the installation image of one or more TME 10 products. You can import the libraries and binaries of only those operating systems needed in your environment, which saves you disk space and import time. The IR is then the source of all of your TME 10 installations. You can even share a single IR across multiple TMRs. Tivoli recommends that you upgrade the Framework install facility in your current TME 10 installation by installing SIS. If you are installing TME 10 for the first time, install SIS on the first managed node running an SIS-supported operating system. Once installed, you should use SIS to install other TME 10 products. See the TME 10 Software Installation Service User s Guide for instructions on installing SIS in your TME 10 installation and installing products using SIS. Installing with the TME 10 Desktop You can also install the TME 10 Software Distribution products from either the desktop or command line. The following table provides the context and authorization role required for this task: Activity Context Required Role Install TME 10 Software Distribution products TME 10 super or install-product 2 2 Version 3.6

35 Desktop Installing TME 10 Software Distribution Products Use the following steps to install the application from the TME 10 desktop. 1. Select Install -> Install Product... from the Desktop menu to display the Install Product dialog. Installation If the Select Product to Install scrolling list is empty or does not list the TME 10 Software Distribution products, proceed to step 2. If products are listed in this scrolling list, skip to step 3. TME 10 Software Distribution User s Guide 2 3

36 Installing TME 10 Software Distribution Products 1. Press the Select Media... button to display the File Browser dialog. The File Browser dialog enables you to specify the path to the installation media. If you know the path to the TME 10 Software Distribution CD-ROM image, complete the following steps: a. From the Hosts scrolling list, choose the host on which the CD-ROM is mounted. Choosing a host updates the Directories scrolling list to show the directories (under root) of the host you chose. a. Enter the full path in the Path Name field. OR From the Directories scrolling list, double-click on the directory containing the install media. Update the Files list by choosing a directory from the Directories list. If the application files are contained in a subdirectory, continue to double-click on a directory until the application files are listed. 2 4 Version 3.6

37 Installing TME 10 Software Distribution Products a. Press the Return keyortheset Path button to change to the specified directory. a. Press the Set Media & Close button to save the new media path and return to the Install Product dialog. The dialog now contains a list of products that are available for installation. Installation 1. Select a TME 10 Software Distribution product from the Select Product to Install scrolling list. The Software Distribution products include the following: TME 10 Software Distribution, Version 3.6 Installs TME 10 Software Distribution 3.6 and the manual pages for CLI commands. Install this product component on your TMR server and on any managed nodes where you will create Software Distribution profiles or where you will run Software Distribution commands from the command line. TME 10 Software Distribution Gateway, Version 3.6 Installs the files that enable an endpoint gateway to recognize Software Distribution methods, download the methods to TME 10 Software Distribution User s Guide 2 5

38 Installing TME 10 Software Distribution Products endpoints, and execute the methods on these clients to perform the requested Software Distribution operation. Install this product on all managed nodes that are configured as endpoint gateways or which you plan to configure as endpoint gateways. TME 10 Software Distribution TEC Integration, Version 3.6 Installs the files that enable Software Distribution to send events to the TME 10 Enterprise Console s event server when a Software Distribution operation is performed. You must have Version 3.6 of the TME 10 Enterprise Console (TEC) and the TME 10 Enterprise Console Server installed prior to installing this component, and you must install this integration product on each event server in your TMR. Also, you must create an event console prior to installing TME 10 Software Distribution TEC Integration. When you install the TEC integration product, the following Install Product dialog is displayed. This dialog enables you to set a default or currently active rule base to manage events. See Chapter 13, TEC Integration for in-depth information about configuring and using this product. TME 10 Software Distribution Extension API, Version 3.6 Installs header files, libraries, and IDL files that enable developers to customize Software Distribution using TME 10 Application Development Environment. If you do not plan to 2 6 Version 3.6

39 Installing TME 10 Software Distribution Products alter the application, or do not have TME 10 Application Development Environment (ADE) installed, you do not need to install the TME 10 Software Distribution Extension API product. If you select this product, the following Install Product dialog is displayed to set installation options. This dialog enables you to specify a destination directory where the extension API is installed. Installation Enter the full path of the directory in which you want the extension API files to be installed in the TME 10 Software Distribution Include Files field. If the directory structure specified in this field does not exist on the target, select the When installing, create Specified Directories if missing check box. Select the Set button to apply the information and return to the Install Product dialog. TME 10 Software Distribution Historical Database, Version 3.6 Installs and enables the Historical Database feature that automatically updates the TME 10 Inventory configuration repository with information about Software Distribution operations that have been performed in your TME 10 environment. You must have the TME 10 Inventory product installed prior to installing this component. See Chapter 12, Historical Database Feature for in-depth information about using this feature to access information from the configuration repository. TME 10 Software Distribution User s Guide 2 7

40 Installing TME 10 Software Distribution Products 1. To specify the clients on which this product will be installed, use the arrow keys to move clients to the Clients to Install On scrolling list. Move all other clients to the Available Clients scrolling list. 1. Press the Install & Close button to install the product and close the Install Product dialog. OR Press the Install button to install the application and keep the Install Product dialog open. To install other TME 10 Software Distribution products or to install the same product on another set of clients, repeat steps 3 5. The installation process prompts you with a Product Install dialog similar to the following: 2 8 Version 3.6

41 Installing TME 10 Software Distribution Products This dialog provides the list of operations that take place when installing the software and warns you of any problems that you may want to correct before installing. 1. Press the Continue Install button to begin the installation process. The Product Install dialog displays status information as the installation process proceeds. OR Press the Cancel button to abort the installation process. When the installation is complete, the Product Install dialog displays a message similar to the following: Installation 1. Press the Close button to close the dialog. TME 10 Software Distribution User s Guide 2 9

42 Upgrading from Software Distribution 3.1 Command Line Use the winstall command to install the TME 10 Software Distribution product on managed node proton from a CD-ROM image. To place the files in the default location, enter the following command: winstall c /dev0/cdrom -i COURIER pescado where: -c /dev0/cdrom Specifies the path to the CD-ROM image. -i COURIER Specifies the COURIER product index file from which the TME 10 Software Distribution product is installed. pescado Specifies the managed node pescado on which to install TME 10 Software Distribution. If you do not specify a managed node, the product is installed on all clients. See the winstall command in the TME 10 Framework Reference Manual for more information. Upgrading from Software Distribution 3.1 You can upgrade from TME 10 Software Distribution, Version 3.1, to TME 10 Software Distribution, Version 3.6, from either the desktop or the command line interface. Tivoli recommends that you backup the databases for all machines in the TMR before upgrading. See the TME 10 Framework Planning and Installation Guide for complete backup instructions. The following table provides the context and authorization role required for this task: Activity Context Required Role Upgrade TME 10 Software Distribution TME 10 super or install-product 2 10 Version 3.6

43 Upgrading from Software Distribution 3.1 Desktop Use the following steps to upgrade the application from the TME 10 desktop. 1. Select Install -> Install Patch... from the Desktop menu to display the Install Patch dialog. Installation TME 10 Software Distribution User s Guide 2 11

44 Upgrading from Software Distribution Press the Select Media... button to display the File Browser dialog. The TME 10 Software Distribution patches reside in the UPGRADE directory on the TME 10 Software Distribution CD-ROM image. If you know the path to the image, complete the following steps: a. From the Hosts scrolling list, choose the host on which the CD-ROM is mounted. a. Enter the full path in the Path Name field. a. Press Return or the Set Path button to change to the specified directory Version 3.6

45 Upgrading from Software Distribution 3.1 a. Press the Set Media & Close button to save the new media path and return to the Install Patch dialog. The dialog now contains a list of patches that are available for installation. Installation If you do not know the path to the TME 10 Software Distribution CD-ROM image, complete the following steps to select a path: a. From the Hosts scrolling list, choose the host on which the CD-ROM is mounted. Choosing a host updates the Directories scrolling list to show the directories (under root) of the host you chose. a. From the Directories scrolling list, double-click on the directory containing the install media. Choosing a directory updates the Files list. If the application files are contained in a subdirectory, continue to double-click on a directory until the application files are listed. a. Press the Set Media & Close button to save the new media path and return to the Install Patch dialog. The dialog now contains a list of patches that are available for installation. TME 10 Software Distribution User s Guide 2 13

46 Upgrading from Software Distribution From the Install Patch dialog, select the TME 10 Software Distribution Upgrade, Version 3.1 to 3.6 patch from the Select Patch to Install scrolling list to upgrade your current installation to TME 10 Software Distribution, Version 3.6. Press the Install button to install the patch. The installation process prompts you with a Patch Install dialog similar to the following: This dialog provides the list of operations that take place when installing the software and warns you of any problems that you may want to correct before installing Version 3.6

47 Upgrading from Software Distribution Press the Continue Install button to begin the installation process. The Patch Install dialog displays status information as the installation process proceeds. OR Press the Cancel button to abort the installation process. 1. Press the Close button to close the Patch Install dialog and return to the Install Patch dialog when the patch installation is complete. 1. You also must update older versions of the following Software Distribution product components. If you have Version 3.1 of the following components installed, complete steps 4 and 5 to install patches to update to Version 3.6. TME 10 Software Distribution Extension API Upgrade, Version 3.1 to 3.6 TME 10 Software Distribution Historical Database Upgrade, Version 3.1 to 3.6 Note: If you do not have Version 3.1 of these Software Distribution product components installed, you can install a current version from the Install Product dialog. 1. Press the Close button to close the Install Patch dialog when the installation is complete. Installation Command Line To upgrade TME 10 Software Distribution, Version 3.1 from the command line, use the wpatch command to install the TME 10 Software Distribution Upgrade, Version 3.1 to 3.6 patch. Enter the following commands: wpatch c /dev0/cdrom/upgrade -i COURIERU pescado where: -c /dev0/cdrom/upgrade Specifies the path to the CD-ROM image. TME 10 Software Distribution User s Guide 2 15

48 Removing TME 10 Software Distribution -i COURIERU Specifies the COURIERU product index file from which the patch is installed. pescado Specifies the managed node pescado on which to install the patch. If you do not specify a managed node, the product is installed on all clients. See the wpatch command in the TME 10 Framework Reference Manual for more information. Removing TME 10 Software Distribution TME 10 Framework provides a command line utility to remove TME 10 applications from a specified node or from the entire TMR. The wuninst command is a wrapper script that invokes product-specific uninstall scripts. Using the wuninst command with an application-specific tag, you can remove Software Distribution products from any machine in your environment or from the TMR. Tivoli provides the following registered product tags for Software Distribution products: Courier TME 10 Software Distribution, Version 3.6 CourierGw TME 10 Software Distribution Gateway, Version 3.6 COUR_TEC SwDist_DB TME 10 Software Distribution TEC Integration, Version 3.6 TME 10 Software Distribution Historical Database, Version 3.6 SwDist_ADE TME 10 Software Distribution Extension API, Version 3.6 The following examples demonstrate a number of removal operations you can use to uninstall Software Distribution or its components from your TMR environment. See the TME 10 Framework Reference Manual for more information about command line syntax and usage for the wuninst command Version 3.6

49 Removing TME 10 Software Distribution To view the usage statement for Software Distribution, enter the following at the command line: wuninst Courier where: Courier Specifies the registered product tag for TME 10 Software Distribution. To remove Software Distribution from the entire TMR in which pescado is the TMR server, enter the following command. Note that if the node is the TMR server, Software Distribution will be removed from the TMR server and from all managed nodes on which Software Distribution is installed. wuninst Courier pescado -rmfiles where: Courier Specifies the registered product tag for TME 10 Software Distribution. pescado Specifies the TMR server name. Because pescado is the TMR server, Software Distribution is removed from every node in the TMR. rmfiles Specifies that all local database objects and all the associated files are removed regardless if they are shared files. The default behavior without the rmfiles option is to only remove the database entries for the specified node. If the node is the TMR server, this option removes all database objects. Installation To remove Software Distribution products that are installed on multiple nodes, but not on the TMR server, include the all option at the command line. For example, if you need to remove the TME 10 Software Distribution Gateway product from odin managed node, and this product is not installed on the TMR, enter the following command: wuninst CourierGW odin -rmfiles -all TME 10 Software Distribution User s Guide 2 17

50 Installing the AutoPack Control Center where: CourierGW Specifies the registered product tag for TME 10 Software Distribution Gateway. odin Specifies a node in the TMR from where the product is being removed. rmfiles Specifies that all local database objects and all the associated files are removed regardless if they are shared files. all Specifies that the product is removed from all nodes in the TMR where is it installed. In this case, the TME 10 Software Distribution Gateway is removed from all nodes in the TMR where odin is configured. Note:Although only one TMR node is specified, the product is removed from all nodes in the TMR (except the TMR server) where the product is installed. To remove database entries from a single node odin, enter the following at the command line: wuninst Courier odin where: Courier Specifies the registered product tag for TME 10 Software Distribution. odin Specifies the node from where the product is removed. Installing the AutoPack Control Center The AutoPack Control Center enables you to create an AutoPack file, which contains all the files necessary to install a shrinkwrapped application, such as Microsoft Word or Netscape Navigator. These files include scripts that are needed to perform system configuration changes to the client machine. You can install the AutoPack Control Center on a pristine, Windows platform-specific machine that will serve as the AutoPack Control 2 18 Version 3.6

51 Installing the AutoPack Control Center Center preparation (prep) machine. Although not recommended, you can install the prep machine on an NT managed node, a Windows-based endpoint, or PC managed node in your Tivoli Management Region (TMR); note, however, that installing the AutoPack Control Center on a TME 10 client machine may lead to file contention. Tivoli also recommends that the prep machine have minimal software installed. Note: The prep machine does not require a PC agent or lcfd. The TME 10 Software Distribution AutoPack User s Guide provides instructions, important information, and recommendations about using Software Distribution s AutoPack technology. Also, the online help provided with the AutoPack Control Center provides easily referenced information from the graphical user interface. Installing on Windows NT or Windows 95 The following procedure details steps to install an AutoPack Control Center on either Windows NT or Windows 95 systems: Installation 1. From the File Manager or Program Manager window, select Run... from the File menu to display the Run dialog. 1. Enter the path to the SETUP.EXE file, which resides in the X:\PC\ACC directory on the CD-ROM, in the Open text field, as follows: where X: is the CD-ROM drive where the TME 10 Software Distribution CD-ROM image is inserted. TME 10 Software Distribution User s Guide 2 19

52 Installing the AutoPack Control Center If you do not have a CD-ROM drive on your PC, see the PC agent chapter in the TME 10 Framework Planning and Installation Guide for instructions on copying the installation media to diskettes. 1. Press the OK button to run the setup program and display the Welcome dialog for the AutoPack Control Center. The setup program leads you through the AutoPack Control Center installation. Use the Back, Next, or Cancel buttons to navigate through these option dialogs. 1. To start the AutoPack Control Center, double-click on the AutoPack icon or select the AutoPack Control Center option in the AutoPack group on the Start -> Programs menu Version 3.6

53 Installing on Windows 3.1 Installing the AutoPack Control Center The following procedure details steps to install an AutoPack Control Center on Windows 3.1 machines. To install and run the AutoPack Control Center on a Windows 3.1 machine, you must first install win32s, Version or later. Step 2 applies for Windows 3.1 with EIDE only 1. Ensure that SHARE.EXE is included in the AUTOEXEC.BAT file and is running. 1. Ensure that the Use 32-Bit File Access option is disabled. To do so, complete the following steps: a. Open the Control Panel. a. Open the 386 Enhanced group and press the Virtual Memory... button. The Virtual Memory dialog is displayed. Installation TME 10 Software Distribution User s Guide 2 21

54 Installing the AutoPack Control Center a. Press the Change>> button to expand the Virtual Memory dialog. a. Ensure that the Use 32-Bit File Access check box is not selected. a. Press the OK button to close the Virtual Memory dialog. a. Reboot your Windows machine. 1. From the File Manager or Program Manager window, select Run... from the File menu to display the Run dialog. 1. Enter the path to the SETUP.EXE file, which resides in the X:\PC\ACC directory on the CD-ROM, in the Command Line text field as follows: where X: is the CD-ROM drive where the TME 10 Software Distribution CD-ROM image is inserted Version 3.6

55 Installing the AutoPack Agent If you do not have a CD-ROM drive on your PC, see the PC agent chapter in the TME 10 Framework Planning and Installation Guide for instructions on copying the installation media to diskettes. 1. Press the OK button to run the setup program and display the Welcome dialog for the AutoPack Control Center. Installation This program leads you through the AutoPack Control Center installation. Use the Back, Next, or Cancel buttons to navigate through these option dialogs. 1. To start AutoPack Control Center on Windows 3.1 machines, double-click on the AutoPack icon. Installing the AutoPack Agent For managed nodes and PC managed nodes only. In order to distribute an AutoPack profile, you must first install the AutoPack agent on all managed nodes and PC managed nodes that will receive AutoPack distributions endpoints are automatically configured with the AutoPack agent during installation. In conjunction with the lcfd on endpoints or the PC agent on PC managed nodes, the AutoPack agent is responsible for receiving and unpacking an AutoPack profile. TME 10 Software Distribution User s Guide 2 23

56 Installing the AutoPack Agent Before installing the AutoPack agent on a PC, you must install the PC agent and create a PC managed node for it. See the TME 10 Framework Planning and Installation Guide for instructions on how to perform both of these procedures. Once you have installed the AutoPack agent on a subscriber, you will only need to reinstall it if a new release of the AutoPack Control Center is installed on the preparation machine. Note: Ensure that you are installing a current version of the AutoPack agent. The following table shows the context and authorization role required to perform this task:. Operation Context Required Role Create, edit, and distribute an AutoPack Profile manager senior or super Use the following steps to install the AutoPack agent on Windows, Windows 95, and Windows NT machines in your environment. Note that the steps include procedures to create, edit, and distribute an AutoPack profile that contains the AutoPack agent. Refer to Part III, Performing Software Distribution Operations for more information about creating and distributing an AutoPack profile. Additionally, the TME 10 Software Distribution AutoPack User s Guide provides in-depth information about installing Windows-based applications using Software Distribution s AutoPack technology. 1. From the TME 10 desktop, double-click on a policy region icon to display the Policy Region window. 1. Add the AutoPack and ProfileManager resources to the policy region s list of managed resources. For instructions on adding resource types to a policy region, see the TME 10 Framework User s Guide. 1. Create a profile manager in which the AutoPack will reside. See the TME 10 Framework User s Guide for instructions on creating profile managers. 1. Double-click on a profile manager icon to display the Profile Manager window Version 3.6

57 Installing the AutoPack Agent 1. Select Profile... from the Create menu in the Profile Manager window to display the Create Profile dialog. Installation 1. Enter a unique name for the profile in the Name/Icon Label field that describes the AutoPack and select AutoPack from the Type scrolling list. 1. Press the Create & Close button to create the new profile and return to the Profile Manager window. An icon representing the newly-created AutoPack is displayed in the Profile Manager window. TME 10 Software Distribution User s Guide 2 25

58 Installing the AutoPack Agent 1. Double-click on the AutoPack icon to display the Set AutoPack Properties window. 1. In the Managed Node field, type the name of the managed node where the TME 10 Software Distribution CD-ROM is mounted. 1. Type the following full path in the Path field. /cdrom/ap_agent.pak where cdrom is the path to the mounted CD-ROM drive. The ap_agent.pak file is an AutoPack file that contains the AutoPack agent files and scripts needed to install it on the target. 1. Press the Save & Close button to save the AutoPack and return to the Profile Manager window Version 3.6

59 Installing the AutoPack Agent 1. Select Distribute... from the AutoPack icon pop-up menu to display the Distribute AutoPack dialog. Installation 1. Ensure that the Distribute AutoPack To scrolling list accurately displays the subscribers on which you want the AutoPack agent installed. Perform the following actions using the scrolling lists: To move a subscriber to the Distribute AutoPack To scrolling list, choose one or more subscribers from the Available Subscribers scrolling list and press the left arrow button. By default, all subscribers in the profile manager are displayed in the Available Subscribers scrolling list. To remove a subscriber, choose one or more subscribers from the Distribute AutoPack To scrolling list and press the Remove button. TME 10 Software Distribution User s Guide 2 27

60 Installing the AutoPack Agent 1. Press the Distribute & Close button to begin distributing the AutoPack to the selected subscribers and dismiss the dialog. Note: The dialog is not dismissed until the distribution is complete and the operation stops. If the distribution fails for any of the subscribers, a pop-up dialog is displayed to inform you which subscribers failed the distribution. This status is also displayed on the TME 10 desktop Version 3.6

61 II Using TME 10 Software Distribution This section contains chapters that provide an overview of TME 10 Software Distribution and work through deployment scenarios similar to those faced by Software Distribution customers. Chapter 3, The Distribution Environment introduces a fictitious company called NoonTide Enterprises that has a network of heterogeneous machines in several subnets. NoonTide s network topology includes a variety of managed nodes, endpoints that are connected through endpoint gateways, and PC managed nodes, as well as repeaters and NetWare managed sites to optimize the network for the software distributions. Chapter 4, Software Deployment Using File Packages describes and provides examples of how to create the necessary policy regions, profile managers, and file packages to house and distribute Adobe FrameMaker files. It also explains how to use configuration programs to deploy the software, set the file package subscribers, and distribute the file packages. Chapter 5, Software Deployment Using AutoPacks addresses how to seamlessly install software on a Windows-based PCs using Software Distribution s AutoPack technology. Using a scenario in which Microsoft Office 97 is installed on Windows clients, this chapter details procedures for creating the AutoPack file on a prep machine using the AutoPack Control Center, as well as for creating an AutoPack profile on a managed node to distribute the AutoPack file to the target machines. Procedures in each of the NoonTide chapters assume that you are NoonTide s senior system administrator. Chapter 3 The Distribution Environment Introducing NoonTide Network Architecture Creating a Repeater Hierarchy Configuring Repeater Sites TME 10 Software Distribution User s Guide

62 Using TME 10 Software Distribution Setting Repeater Parameters Creating NetWare Managed Sites The dollar-win NetWare Managed Site The rainbow-win NetWare Managed Site The rainbow-95 NetWare Managed Site Installing Additional TME 10 Applications Chapter 4 Software Deployment Using File Packages Creating a Staging Area for Source Files Creating FrameMaker File Packages Setting File Package Properties Setting Properties from the Desktop Setting Properties Using Export and Import Creating Configuration Programs and Input Files The bfr_hp.sh Before Program The aft_hp.sh After Program The lic.sh Script The aft.txt and lic.txt Files Setting File Package Subscribers Creating TME 10 Inventory Queries Distributing the FrameMaker File Packages Chapter 5 Software Deployment Using AutoPacks Introducing the AutoPack Control Center Creating the AutoPack File Creating the Baseline Snapshot Installing the Software Building the AutoPack File Setting AutoPack File Properties Editing an Existing AutoPack File Creating an AutoPack Profile Distributing Office Version 3.6

63 3 3The Distribution Environment Installing TME 10 Software Distribution is the first step to solving the deployment management challenge. Although you can immediately start creating file packages and AutoPacks, and distributing software, some planning and forethought at this point will lead to a more efficient and manageable distribution environment. In particular, you will want to consider the following questions: What types of software will be distributed and how much disk space will each require? Will certain types of network connections hinder a distribution (such as slow WAN connections)? How can the network and TME 10 repeaters be configured to efficiently distribute multiple file packages? Can established relationships between machines be used to help distribute software (such as endpoints connected to a server via an endpoint gateway, or PCs connected to a NetWare server)? Are other TME 10 applications available to ease distribution efforts? The Distribution Environment TME 10 Software Distribution User s Guide 3 1

64 Introducing NoonTide This chapter addresses these questions by presenting an example scenario involving NoonTide Enterprises. NoonTide Enterprises is a fictitious company with many of the network complexities that face today s businesses. This chapter steps through the process of configuring a distribution environment, which includes the following: Assessing the network topology and available departmental resources Determining if multiplexing a distribution by configuring an endpoint gateway with the MDist feature is useful and, if so, determining which machines are suitable to be multiplexed in this manner Creating the necessary repeaters, their range of clients, and parameters Creating NetWare managed sites to represent the NetWare servers on the network Using the distribution environment that is established in this chapter, the following chapters demonstrate how to distribute software packages using Software Distribution s file packages and AutoPack technology. Procedures in this and subsequent NoonTide chapters assume that you are NoonTide s senior system administrator. The procedures in this chapter require the senior authorization role and are geared toward senior administrators. Introducing NoonTide NoonTide Enterprises develops, markets, and sells electronic products to an international market. Their principal departments include Engineering, Support, Marketing, Administration, and Sales. Noontide has installed and uses TME 10 Framework and several TME 10 applications to manage a distributed network that is divided into seven subnets four in the corporate office and three in regional offices. Each department is represented by a policy region, which is created to model the management and organizational structure of a network computing environment, as well as to enforce common policies between related departments. In NoonTide s TMR environment, each policy region houses each department s resources 3 2 Version 3.6

65 Introducing NoonTide such as subregions, managed nodes, endpoints, PC managed nodes, and profile managers. The following policy regions exist on the lead administrator s desktop: The Distribution Environment TME 10 Software Distribution User s Guide 3 3

66 Network Architecture For example, the Engineering policy region represents the Engineering department. Opening the Engineering policy region displays the following window: The Engineering policy region contains a UNIX managed node, big, that serves managed nodes (such as swiss and cheddar), endpoints (such as philly), and PC managed nodes (such as cottage). The Engineering policy region also contains the Product, Research, and Test subpolicy regions that group and control access to resources for these three components of the Engineering department. NoonTide also organizes its environment according to administration tasks. The System Monitors and Software Distribution policy regions contain TME 10 Distributed Monitoring and TME 10 Software Distribution subregions, jobs, and tasks. The pescado-region policy region is the default policy region that is created when the TMR server is installed. The name of the default policy region is derived from the name of the machine that is hosting the TMR server (pescado). Network Architecture Understanding and planning NoonTide s network topology is essential to configuring its distribution environment. NoonTide has seven subnets four in the corporate office and three in regional offices. Subnets are connected either by Ethernet connections, which have 3 4 Version 3.6

67 Network Architecture bandwidths of 10 MB/second, or by T1 lines, which have bandwidths of 1 MB/second. Each subnet contains a UNIX, a NetWare, or an NT managed node server that connects to the TMR server. Endpoint gateways are installed on managed nodes in subnets that have endpoint clients. Note that the endpoint manager controls and configures gateways and endpoints, assigns endpoints to gateways, and maintains the endpoint list. The endpoint manager is available from the TME 10 desktop. For detailed information about the endpoint manager, endpoint gateways, and managed resources, refer to the TME 10 Framework Planning and Installation Guide. The following diagram illustrates NoonTide s network topology. Subnet 3 Subnet 4 Subnet 5 Subnet 6... Subnet oak rainbow big TMR server pescado pearl diamond lapis electron The Distribution Environment... odin... dollar Subnet 1 Subnet 2 TME 10 Software Distribution User s Guide 3 5

68 Network Architecture Subnet 1 Subnet 1 includes machines that are connected by Ethernet to the TMR server, pescado, in the corporate office. These include the NoonTide Operations, NoonTide Administration, and Marketing departments. NoonTide Operations odin (Solaris server) thor (Solaris) frey (SunOS) loki (Solaris) balder (Solaris) NoonTide Administration rainbow (NetWare server) red (Windows; NetWare client) orange (Windows; NetWare client) green (Windows; NetWare client) blue (Windows 95; NetWare client) yellow (Windows; NetWare client) violet (Windows 95; NetWare client) NoonTide Marketing dollar (NetWare server) shilling (Windows 95; NetWare client) pound (Windows 95; NetWare client) rupee (Windows 95; NetWare client) yen (Windows 95; NetWare client) peso (Windows 95; NetWare client) franc (Windows 95; NetWare client) drachma (Windows 95; NetWare client) dinar (Windows 95; NetWare client) lira (Windows 95; NetWare client) 3 6 Version 3.6

69 Subnet 2 Network Architecture Subnet 2 is located in the corporate office and is connected to pescado by a T1 connection. It includes machines in the HQ Sales department. NoonTide Sales (Corporate) electron (Windows NT 4.0 server) gold (Windows) silver (Windows) platinum (OS/2) Subnet 3 Subnet 3 is located in the corporate office and is connected to pescado by an Ethernet connection. It includes machines in the NoonTide Support department. NoonTide Support oak (SunOS server) cedar (Solaris) mahogany (HP-UX) maple (AIX) walnut (HP-UX) elm (HP-UX) Subnet 4 Subnet 4 includes machines in the Engineering department. This subnet is located in the corporate office and is connected to pescado through an Ethernet connection. big (HP-UX server) NoonTide Engineering brie (Solaris) The Distribution Environment philly (Windows) cottage (Windows) american (Solaris) jack (HP-UX) provolone (AIX) camembert (HP-UX) ricotta (AIX) parmesan (SunOS) bleu (HP-UX) edam (HP-UX) TME 10 Software Distribution User s Guide 3 7

70 Network Architecture NoonTide Engineering gouda (SunOS) swiss (HP-UX) gruyere (SunOS) stilton (HP-UX) Subnet 5 cheddar (HP-UX) Subnet 5 includes machines in the West Coast Sales department and is located in a regional office. It is connected to electron with a T1 line. NoonTide Sales (West Coast) pearl (NT 4.0 server) agate (Windows) Subnet 6 Subnet 7 coral (Windows) Subnet 6 includes machines in the Central Sales department and is located in a regional office. It is connected to electron with a T1 line. NoonTide Sales (Central) diamond (NT 4.0 server) emerald (Windows 95) ruby (Windows 95) Subnet 7 includes machines in the East Coast Sales department and is located in a regional office. It is connected to electron with a T1 line. NoonTide Sales (East Coast) lapis (NT 4.0 server) opal (Windows 95) sapphire (Windows 95) 3 8 Version 3.6

71 Creating a Repeater Hierarchy Creating a Repeater Hierarchy NoonTide Enterprises has configured its network environment using TME 10 s Multiplexed Distribution (MDist) service. MDist enables synchronous distributions of large amounts of data to multiple targets in an enterprise. The MDist service maximizes NoonTide s data throughput by enabling the following: Supporting parallel distribution to hosts on the same subnet. Using this feature, pescado can simultaneously distribute software to all machines connected to the rainbow and dollar servers if both the Marketing and Administration departments need this application. This results in a faster distribution than one in which copies of the software are sent to each machine in serial. Spreading the distribution load across networks. Dispersing the distribution load across a network tree limits resource contention that can arise when one server is responsible for distributing to many client machines. Sending a single copy of the data across slower links, to a specially designated host, called a repeater site, which redistributes it in parallel to other hosts on the far side of the slow connection. This is a more effective use of the network than sending a copy of the software across the network gateway for each remote target. For example, pescado can efficiently distribute to pearl, diamond, and lapis using electron as a repeater site. By default, the TMR server (pescado) serves as the repeater distribution server for all targets in the TMR. Endpoint gateways are automatically configured to act as MDist repeaters for distributing information to their endpoints. The NoonTide network includes endpoint gateways at odin, big, pearl, diamond, and lapis. NoonTide has configured electron and oak managed nodes to serve as additional MDist repeaters. It also includes configures rainbow and dollar with the MDist functionality. However, because rainbow and dollar are Novell NetWare servers, they are each configured as a Tivoli NetWare repeater (TNWR). In the TME 10 environment, creating a NetWare managed site enables profiles to be distributed through the TNWR to client PCs using either TCP/IP or IPX. See Chapter 15, NetWare The Distribution Environment TME 10 Software Distribution User s Guide 3 9

72 Creating a Repeater Hierarchy Managed Sites for information about using NetWare managed sites to distribute Software Distribution profiles. The following diagram illustrates NoonTide s repeater hierarchy: pescado File package distribution from pescado (source host) dollar (TNWR)... T1 line oak (repeater) electron (repeater) odin... (gateway) rainbow (TNWR)... big (gateway) pearl (gateway) diamond (gateway) lapis (gateway) As in the case of NoonTide s network topology, one repeater site is often not enough to handle heavy network traffic and large software distributions. To determine the number of repeaters needed in any given environment, use the following guidelines: If the network has slow network links, designate one managed node on each side of the network link to be a repeater with a local copy of the TME 10 binaries Version 3.6

73 Creating a Repeater Hierarchy If a client is often a source host for software distribution, make it a repeater site to enhance performance. If the range (clients that receive data from the repeater site) of a repeater site contains too many clients in multiple subnets, add a repeater site for each subnet. Taking these guidelines into consideration, the remainder of this chapter examines how to determine if additional repeaters are needed and how to configure the parameters for each repeater. Refer to the TME 10 Framework Planning and Installation Guide to determine the repeater environment and settings that will best serve your environment. Additionally, the TME 10 Framework Planning and Installation Guide provides information about configuring endpoint gateways on managed nodes that serve endpoints. Configuring Repeater Sites As NoonTide s senior system administrator, you must complete each of the following steps to determine if more repeater sites are necessary and, if so, how to set them up: 1. Determine which machines are defined as repeaters by entering the wrpt command from the command line of any managed node in the TMR. For example, when you first install TME 10 Framework on the pescado server, wrpt results in the following output: pescado [1] -d- [default] After fully configuring NoonTide s environment, running wrpt will list the default repeater on pescado, all endpoint gateways, and each managed node that is configured with a repeater. 1. List the machines in the range of the pescado repeater. Enter the following odadmin command from the command line of any managed node in the TMR to list the clients of the pescado repeater: The Distribution Environment odadmin odlist TME 10 Software Distribution User s Guide 3 11

74 Creating a Repeater Hierarchy The output of this command is as follows: Region Disp Flags Port IPaddr Hostname(s) ct pescado,pescado.noontide.com 2 ct odin,odin.noontide.com 4 ct frey,frey.noontide.com 5 ct loki,loki.noontide.com 6 ct electron, electron.noontide.com 7 ct gold, gold.noontide.com 8 ct silver, silver.noontide.com 9 ct platinum, platinum.noontide.com 10 ct oak,oak.noontide.com 11 ct cedar,cedar.noontide.com 12 ct mahogany,mahogany.noontide.com 13 ct maple,maple.noontide.com 14 ct walnut,walnut.noontide.com 15 ct elm,elm.noontide.com 16 ct big,big.noontide.com 17 ct american,american.noontide.com 18 ct jack,jack.noontide.com 19 ct provolone,provolone.noontide.com 20 ct gouda,gouda.noontide.com 21 ct swiss,swiss.noontide.com 22 ct cheddar,cheddar.noontide.com 23 ct brie,brie.noontide.com 24 ct camembert,camembert.noontide.com 25 ct ricotta,ricotta.noontide.com 26 ct parmesan,parmesan.noontide.com 27 ct bleu,bleu.noontide.com 28 ct edam,edam.noontide.com 29 ct gruyere,gruyere.noontide.com 30 ct stilton,stilton.noontide.com 31 ct pearl, pearl.noontide.com 32 ct coral,coral.noontide.com 33 ct diamond,diamond.noontide.com 34 ct ruby,ruby.noontide.com 35 ct lapis,lapis.noontide.com 36 ct sapphire,sapphire.noontide.com Note that this list contains the names and IP addresses of managed nodes in each subnet in Network Architecture on page 3-4. Endpoints and PC managed nodes are not listed because they do not have the full Framework (oservs). Both endpoints and PC managed nodes rely on managed nodes for communication with the TMR server. 1. If a client system is often a source host for software distribution, defining a repeater in this manner enhances performance. Create a repeater site on all managed nodes that will serve as distribution points. Endpoint gateways are automatically configured as repeater points for their client endpoints. However, if an endpoint 3 12 Version 3.6

75 Creating a Repeater Hierarchy gateway will act as a distribution point for a managed node or a PC managed node, you must add this machine to the repeater range of the gateway. For example, oak and electron are good candidates for repeater sites: configuring these servers as repeaters will enable pescado to spread the distribution load across oak and electron rather than sending a copy of the software across the network to each remote target. Using the lists generated by the odadmin odlist commands, create a repeater on oak and electron by entering the following wrpt commands (separately) from a command line: wrpt -n electron range=7-9,31,33,35 wrpt -n oak range=11-15 The first wrpt command shown above configures electron as a repeater site for gold, silver, platinum, pearl and its client, diamond and its client, and lapis and its clients. The second configures oak as a repeater site for cedar, mahogany, maple, walnut and elm. 1. Use the wrpt command to verify that repeater sites are configured correctly. The output for NoonTide s configuration follows: pescado [1] -d- [default] odin [2] --- [default] electron [6] --- [7-9,31,33,35] oak [10] --- [11-15] big [16] --- [default] pearl [31] --- [default] diamond [33] --- [default] lapis [35] --- [default] Note that the TMR server (pescado) and all endpoint gateways list default as their range. The electron and oak repeaters list the host numbers of the machines they serve. In NoonTide s environment, pescado distributes file package A to clients rainbow, odin, and dollar, as well as to the oak and electron repeaters. oak then distributes file package A to its clients, cedar, mahogany, maple, walnut, and elm; electron pushes file package A to its clients, gold, silver, platinum, and the pearl, diamond, and lapis repeaters. Finally, pearl, diamond, and lapis distribute the file The Distribution Environment TME 10 Software Distribution User s Guide 3 13

76 Creating a Repeater Hierarchy package to their clients. Each repeater and endpoint gateway distributes file package A in parallel to its clients. See the TME 10 Framework Reference Manual for more information about the wrpt and odadmin commands. Setting Repeater Parameters Now that you have created repeater and endpoint gateway sites for NoonTide s network, you must configure each repeater site to efficiently handle software distributions: configuring wrpt parameters correctly at this time can avoid time-consuming and costly hung distributions in the future. Refer to the wrpt command manual page in the TME 10 Framework Reference Manual for more information about command syntax and arguments. As this scenario continues, you will distribute Adobe FrameMaker to various NoonTide departments. Therefore, the following procedure determines how much disk space is required for the application and how much memory is available on each repeater site in order to define the repeater parameters. You will configure each repeater and endpoint gateway in the NoonTide network to account for the amount of available memory, disk space, and network bandwidth, and the number and bandwidth capacity of the repeater s targets. For brevity, the following steps configure two of the repeaters, electron (a Windows NT machine) and pescado (a Solaris machine): 1. List the current settings of the repeaters parameters by entering the following wrpt commands (separately): wrpt -t electron wrpt -t pescado The default output of these commands are the same: mem_max = disk_max = disk_hiwat = disk_time = 1 disk_dir = "/tmp" net_load = 500 max_conn = 100 stat_intv = Version 3.6

77 Creating a Repeater Hierarchy where: mem_max disk_max disk_hiwat disk_time disk_dir net_load Specifies the maximum memory used as buffer space for the file package before the repeater pages data to disk (measured in KB). mem_max + disk_max should at least equal the size of the largest file package that will be distributed if max_conn is less than the number of clients connected to the repeater. Specifies the maximum disk space used by the repeater for paging to disk (measured in KB). mem_max + disk_max should at least equal the size of the largest file package distributed if max_conn is less than the number of clients connected to the repeater. Specifies the repeater s disk space usage (in KB) at which a delay occurs between disk block allocations. The delay period is specified by the disk_time tuning parameter keyword. A disk block allocation is 16 KB. Tivoli recommends that this value equal about 50% of the maximum disk space available by the repeater. Specifies the delay (in seconds) between disk block allocations. The delay starts only after disk usage rises above the number indicated by the disk_hiwat tuning parameter keyword. Specifies the directory used for temporary paging, or swap, space. This directory is dependent on where the disk space is available. Also, the temporary directory must have write permissions set to user, group, and other. Note that the repeater must be configured with adequate swap space to avoid hung distributions: This swap space must be at least as large as disk_max. Specifies the maximum amount of data (in KB per second) that the repeater will send to the The Distribution Environment TME 10 Software Distribution User s Guide 3 15

78 Creating a Repeater Hierarchy max_conn network for each distribution. Tivoli recommends that this value equal about 25% of the network bandwidth (between repeater and clients). Note that you can not set the net_load parameter to a value greater than 32 MB/sec. Specifies the maximum number of simultaneous parallel client connections initiated by the repeater during a distribution. stat_intv Specifies a high-level TCP timeout (in seconds) after which an error terminates the blocked connection. This value is dependent on the network client machines processors, particularly the PC processors and RAM. 1. Determine the disk requirements for the applications to be distributed by referring to the applications installation guides. This scenario distributes both the install media and some of the application files in the file package. The install media requires 180 MB and the application requires about 25 MB. Thus, assume the largest FrameMaker file package will be 210 MB, considering configuration programs and file package overhead. 1. Check that the electron and pescado sites have the needed disk space and memory. Note: You must be logged in as Administrator to perform the steps to determine disk space and memory allocations. a. Check for available disk space on electron (a Windows NT machine) by double-clicking on the Disk Administrator icon in the Administrative Tools window group Version 3.6

79 Creating a Repeater Hierarchy The C:\ drive has 1778 MB of free disk space. a. Check for available memory on electron (a Windows NT machine) by double-clicking on the Windows NT Diagnostics icon in the Administrative Tools window group. Select the Memory property sheet to display the following window: Nearly 27 MB (26,952 KB) of memory are available and 62 MB (62,304 KB) of paging space are available. Also, the C:\ directory is used for the system s paging file. a. Check for available memory and paging space on pescado,a Solaris machine, and locate a file system with free space that can be used to buffer distributions. (Commands used for finding available memory and paging space vary by operating system). The Distribution Environment TME 10 Software Distribution User s Guide 3 17

80 Creating a Repeater Hierarchy To check for free swap space, use the swap l command. The output is as follows: Swapfiledevswaploblocksfree /dev/vx/dsk/swapvol115, To check the amount of RAM installed on the machine, enter the prtconf grep Memory size command. Note that this command returns the total amount of memory installed, not just the free memory. The output is as follows: Memory size: 512 Megabytes Finally, to check the disk partitions for available space, use the df k command. The output is as follows: FilesystemkbytesusedavailcapacityMounted on /dev/vx/dsk/rootvol %/ /dev/vx/dsk/usr %/usr /proc %/proc fd %/dev/fd /dev/vx/dsk/rootdg/vol %/var swap %/tmp The /tmp file system uses a portion of swap space and, therefore, is a poor candidate for repeater use. The /var file system is the best choice for this system because it has the largest free space and it does not use swap space. 1. Set electron s repeater parameters. Note that the max_conn parameter is not reconfigured in this example electron only distributes to six clients (gold, silver, and platinum client machines, as well as pearl, diamond, and lapis repeater sites); the default value for this parameter is 100. Also, the stat_intv parameter is not reconfigured the slowest processor on the network is a 486 with 8 MB of RAM; the default TCP timeout is 180 seconds, which is sufficient for this system s configuration. a. Set the mem_max and disk_max parameters. According to step 3a on page 3-17, electron s available memory is 27 MB and available paging space is 62 MB. Also, increase the paging space (virtual memory) for electron to enable it to handle its repeater tasks Version 3.6

81 Creating a Repeater Hierarchy To set these parameters, open the Virtual Memory dialog. Double-click on the Control Panel icon in the Main window group. Double-click on the System icon in the Control Panel window to display the System Properties window. Press the Change... button on the Performance property sheet to display the Virtual Memory window. The Paging File Size for Selected Drive fields show that the maximum paging file size is currently set to 125 MB, adding 50 MB to the initial paging space. This allows for 139 MB of free virtual memory: 27 MB of memory plus 62 MB of paging space plus 50 MB extra of virtual memory. Set mem_max to about half of the available virtual memory, or 69.5 MB. This leaves virtual memory for other applications that may run on the repeater. However, because the file package size is about 210 MB, additional staging space will be needed. Thus, set the disk_max parameter to 150 MB, which is the approximate difference between the file package size and the allocated virtual memory, as follows: The Distribution Environment wrpt -t electron mem_max=69500 disk_max= TME 10 Software Distribution User s Guide 3 19

82 Creating a Repeater Hierarchy a. Set the disk_dir parameter. The directory specified for this parameter must reside on the NTFS drive and must be accessible (read, write, and execute permissions) by everyone. In this case, use the recommended \temp directory on the C: drive, as follows: wrpt -t electron disk_dir=c:\temp For network connections with different bandwidths, the repeater parameter values must be scaled proportionally. Note that you can use a backslash (\) in the directory path if you enter this command from electron. If you enter this command from a UNIX managed node, you must use a forward slash (/). a. Set the disk_hiwat, disk_time, and net_load parameters, taking into account that the connection to the clients is a T1 connection (bandwidth = 1 MB/second). Set the disk_hiwat parameter to about 50% of the repeater s disk space. If a client receives data slower than it is sent by the repeater, the data received by the repeater is spooled to the repeater s memory and disk. The disk_hiwat parameter sets the repeater s disk space usage at which a delay occurs between disk block allocations. This is referred to the disk s high watermark. If spooled data reaches this high watermark, the repeater must stop receiving data until some of the spooled data is received by the clients. The delay between data transmissions to the repeater is defined by the disk_time parameter. Because the repeater s disk space is 150 MB, set the disk_hiwat to 75 MB (75000 KB), as follows: wrpt -t electron disk_hiwat=75000 To set the disk_time parameter, first determine if the high watermark is less than the size of the largest file package to be distributed. In this case, the largest file package is about 210 MB and the high watermark is set to 75 MB. Thus, set a delay so that not all 210 MB of data is sent to the repeater before it is forwarded to the clients. Second, take network connections to and from the repeater into account. An Ethernet connection s optimal bandwidth is 10 MB/second 3 20 Version 3.6

83 Creating a Repeater Hierarchy and a T1 s optimal bandwidth is 1 Mb/second. Ethernet transmits data ten times faster than a T1. Set the delay to 10 seconds, as follows: wrpt -t electron disk_time=10 Finally, set the net_load parameter to about 25% of the connection s bandwidth, leaving bandwidth for other network traffic. This parameter controls the rate at which data is sent to the clients. Because the repeater-to-client connection has a bandwidth of 1MB/second (128 KB/second), set the net_load parameter to 32 (25% of 128), as follows: wrpt -t electron net_load=32 1. Set pescado s repeater parameters. Note that the max_conn parameter will not change pescado only distributes to six clients and the default value for this parameter is 100. Also, the stat_intv parameter will not change the slowest processor on the network is a SPARC ELC with 8 MB of RAM; the default TCP timeout is 180 seconds, which is sufficient. a. Set the mem_max parameter. According to the information in step 3c, pescado s physical memory is 512 MB and available swap space is 486 MB. Because pescado is used for tasks in addition to acting as a repeater, set this parameter to use a smaller portion of the resources. Set the memory parameter as follows: wrpt -t pescado mem_max=64000 a. Set the disk_dir and disk_max parameters. The directory specified for the disk_dir parameter must be writable by everyone. The /var file system has available disk space and files should be buffered in the /var/tmp directory. Of the 297 MB available on /var, the repeater will be limited to use 200 MB to ensure that it does not consume all of the file system s space. The Distribution Environment TME 10 Software Distribution User s Guide 3 21

84 Creating a Repeater Hierarchy Set the parameters as follows: wrpt -t pescado disk_dir=/var/tmp disk_max= For network connections with different bandwidths, the repeater parameter values must be scaled proportionally. a. Set the disk_hiwat parameter. Because the disk_max parameter is set to 200 MB, set the disk_hiwat to about 50% of this, or 100 MB, as follows: wrpt -t pescado disk_hiwat= a. Set the disk_time parameter based on the network connections to and from pescado. The connection to the repeater s clients is Ethernet, but there is no connection to pescado. It is not necessary to reset the value of the disk_time parameter. a. Set the net_load parameter taking into account that the connection to the clients is an Ethernet connection (bandwidth = 10 MB/second = 1280 KB/second). Set the net_load parameter to about 25% of the connection s bandwidth (25% of 1280), as follows: wrpt -t electron net_load= Verify that the repeater parameters are set correctly by entering the wrpt -t command for each repeater. The output for the electron repeater follows: mem_max = disk_max = disk_hiwat = disk_time = 10 disk_dir = "C:\temp" net_load = 32 max_conn = 100 stat_intv = The output for the pescado repeater follows: mem_max = disk_max = disk_hiwat = disk_time = 1 disk_dir = "/var/tmp" net_load = 320 max_conn = 100 stat_intv = Version 3.6

85 Creating NetWare Managed Sites Creating NetWare Managed Sites The NoonTide network has two NetWare servers, dollar and rainbow, to which PCs running Windows 3.x and Windows 95 are connected. By creating a NetWare managed site to represent each of these servers, NoonTide uses these established network relationships to distribute file packages. A NetWare managed site acts as a repeater file package distributions fan out from the designated NetWare server to the clients connected to it. Without this capability, each PC managed node or endpoint would have to subscribe to the profile manager in which a file package resides. Now, only the NetWare managed site subscribes to the profile manager to distribute a file package to the PCs. Note: NetWare managed sites cannot discern which platformspecific information is defined for a file package. The NetWare managed site sends the file package to all of its clients, regardless of the client s operating system. As NoonTide s system administrator, you will complete the following steps to create NetWare managed sites to represent the dollar and rainbow NetWare servers, which reside in the Marketing and Administration policy region. A NetWare managed site is created for each of the following: dollar s clients, rainbow s Windows clients, and rainbow s Windows 95 clients. The wcrtnwms command also creates NetWare managed sites, as documented in Chapter 15, NetWare Managed Sites. The Distribution Environment TME 10 Software Distribution User s Guide 3 23

86 Creating NetWare Managed Sites The dollar-win NetWare Managed Site Complete the following steps to create a NetWare managed site for the dollar NetWare server. All of dollar s clients are Windows machines so you only need to create one NetWare managed site for this server. 1. Display the Marketing policy region, where the dollar NetWare server s managed node resides, by double-clicking on the Marketing policy region icon. 1. Specify the NetWareManagedSite resource as a managed resource for this policy region. To do so, select Managed Resources... from the Properties menu and move the NetWareManagedSite resource to the Current Resources scrolling list and press the Set & Close button Version 3.6

87 Creating NetWare Managed Sites 1. Create the dollar-win NetWare managed site by selecting NetWareManagedSite... from the Create menu to display the Create NetWare Managed Site dialog. Enter the following options in the text fields: a. Enter dollar-win in the NetWare Managed Site Label field. a. Enter pescado in the NetWare Managed Site Location field because the NetWare managed site should reside on the local TMR server (pescado). a. Enter /tmp/dollar.log in the Log File Path field. Diagnostic information about the dollar-win NetWare managed site will be written to this file, which will also reside on pescado. a. In the NetWare Server Name field, enter dollar (it is not necessary to enter the IP address in the NetWare Server IP Address field). This field specifies the NetWare server for The Distribution Environment TME 10 Software Distribution User s Guide 3 25

88 Creating NetWare Managed Sites which to create the NetWare managed site. The staging area, the SYS:/TIVOLI/STAGE directory, resides on the dollar server and is where a file package will reside before it is distributed to the clients. This is the default staging area. a. Ensure that the Subscribe All Clients radio button is enabled. When you enable this button, the NetWare Clients section of the dialog is disabled. This button will subscribe all of the NetWare server s clients, which are all Windows machines, to the NetWare managed site. Because these machines are NetWare managed site clients, each PC managed node (previously created for these machines) will not need to subscribe to the profile manager containing the file package. When you distribute a file package to the dollar-win NetWare managed site, the file package is automatically distributed to the clients. a. Press the Create & Close button to create the dollar-win NetWare managed site. The dollar-win NetWare managed site now resides in the Marketing policy region, and is represented by a new NetWare managed site icon Version 3.6

89 Creating NetWare Managed Sites If the dollar NetWare server will also receive the file package distributions, ensure that a NetWare machine exists that represents the dollar machine. Although the clients of the dollar-win NetWare managed site will receive any file packages distributed to their NetWare managed site, the actual NetWare server from which the NetWare managed site was created does not. The file package passes from the staging area to the clients the data in the file package is not installed on the server. To distribute a file package to a NetWare managed site, create a PC managed node to represent that NetWare server. The rainbow-win NetWare Managed Site Complete the following steps to create a NetWare managed site for the rainbow NetWare server and its Windows clients. 1. Display the Admin policy region, where the rainbow NetWare server s managed node resides, by double-clicking on the Admin policy region icon. 1. Specify the NetWareManagedSite resource as a managed resource for this policy region. To do so, select Managed Resources... from the Properties menu and move the NetWareManagedSite resource to the Current Resources scrolling list and press the Set & Close button. The Distribution Environment TME 10 Software Distribution User s Guide 3 27

90 Creating NetWare Managed Sites 1. Create the rainbow-win NetWare managed site by selecting NetWareManagedSite... from the Create menu to display the Create NetWare Managed Site dialog. Enter the following options in the text fields: a. Enter rainbow-win in the NetWare Managed Site Label field. a. Enter pescado in the NetWare Managed Site Location field because the NetWare managed site should reside on the local TMR server (pescado). a. Enter /tmp/rain-win.log in the Log File Path field. Diagnostic information about the rainbow-win NetWare managed site will be written to this file, which will also reside on pescado Version 3.6

91 Creating NetWare Managed Sites a. In the NetWare Server Name field, enter rainbow (it is not necessary to enter the IP address in the NetWare Server IP Address field). This field specifies the NetWare server for which to create the NetWare managed site. The staging area, the SYS:/TIVOLI/STAGE directory, resides on the rainbow server and is where a file package will reside before it is distributed to the clients. This is the default staging area. a. Deselect the Subscribe All Clients radio button, which sensitizes the NetWare Clients area of the dialog. The available clients are listed in the Available Clients scrolling list. This NetWare managed site will represent the Windows clients of rainbow so move red, orange, yellow, and green to the Selected Clients scrolling list. Because these machines are NetWare managed site clients, each PC managed node (previously created for these machines) will not need to subscribe to the profile manager containing the file package. When you distribute a file package to the rainbow-win NetWare managed site, the file package is automatically distributed to the selected clients. a. Press Create & Close to create the rainbow-win NetWare managed site. If the rainbow NetWare server will also receive the file package distributions, ensure that a NetWare machine exists that represents the rainbow machine. Though the clients of the rainbow-win NetWare managed site will receive any file packages distributed to their NetWare managed site, the actual NetWare server from which the NetWare managed site was created does not. The file package passes from the staging area to the clients the data in the file package is not installed on the server. To distribute a file package to a NetWare managed site, create a PC managed node to represent that NetWare server. The Distribution Environment TME 10 Software Distribution User s Guide 3 29

92 Creating NetWare Managed Sites The rainbow-95 NetWare Managed Site Complete the following steps to create a NetWare managed site for the rainbow NetWare server and its Windows 95 clients. 1. Create the rainbow-95 NetWare managed site from the Admin policy region by selecting NetWareManagedSite... from the Create menu to display the Create NetWare Managed Site dialog. Enter the following options in the text fields: a. Enter rainbow-95 in the NetWare Managed Site Label field. a. Enter pescado in the NetWare Managed Site Location field because the NetWare managed site should reside on the local TMR server (pescado) Version 3.6

93 Installing Additional TME 10 Applications a. Enter /tmp/rain-95.log in the Log File Path field. Diagnostic information about the rainbow-95 NetWare managed site will be written to this file, which will also reside on pescado. a. In the NetWare Server Name field, enter rainbow (it is not necessary to enter the IP address in the NetWare Server IP Address field). This field specifies the NetWare server for which to create the NetWare managed site. The staging area, the SYS:/TIVOLI/STAGE directory, resides on the rainbow server and is where a file package will reside before it is distributed to the clients. This is the default staging area. a. Deselect the Subscribe All Clients radio button, which sensitizes the NetWare Clients area of the dialog. The available clients are listed in the Available Clients scrolling list. This NetWare managed site will represent the Windows 95 clients of rainbow so move blue and violet to the Selected Clients scrolling list. Because these machines are NetWare managed site clients, each PC managed node (previously created for these machines) will not need to subscribe to the profile manager containing the file package. When you distribute a file package to the rainbow-95 NetWare managed site, the file package is automatically distributed to the selected clients. a. Press Create & Close to create the rainbow-95 NetWare managed site. Installing Additional TME 10 Applications Now that the NoonTide network is configured to handle network traffic efficiently, it will use existing and newly-created relationships to deploy software. Before taking advantage of network configurations to distribute file packages in your network, you may want to install other TME 10 applications that can ease our distribution efforts. To finish configuring the distribution environment, you should consider installing other TME 10 applications that provide additional capabilities to TME 10 Software Distribution TME 10 Inventory and TME 10 UserLink. Using Inventory, you can query a configuration The Distribution Environment TME 10 Software Distribution User s Guide 3 31

94 Installing Additional TME 10 Applications database to determine targets of a distribution. For example, you may query the database for machines that have 20 MB of available disk space before distributing an application. Using UserLink, a Windows, Windows 95, or Windows NT user can retrieve a file package from a managed node. This is useful if a PC was not available when the file package was originally distributed or if the user wants to update an application using an existing file package. If these products are available to an administrator, installing them before distributing file packages may help the deployment. Refer to the corresponding user s guide for installation instructions for these products Version 3.6

95 Installing Additional TME 10 Applications The Distribution Environment TME 10 Software Distribution User s Guide 3 33

96 Installing Additional TME 10 Applications 3 34 Version 3.6

97 4 4Software Deployment Using File Packages Software Deployment Using File Packages Using TME 10 Software Distribution, you can deploy desktop and distributed applications with ease. From a central point, you can create profiles and distribute them in parallel to machines in the same or different TMRs. Software Distribution s profiles include file packages and AutoPacks. The previous chapter introduced NoonTide Enterprises to illustrate how network topologies can be configured to efficiently utilize network resources. This chapter builds on the NoonTide scenario by describing how to distribute file packages that define and contain media for a software application. Although software packages can be deployed as a desktop or distributed application, this scenario explains how to distribute software as a desktop application. The steps in this chapter can be modified to distribute any desktop or distributed application such as Microsoft Excel or Lotus Notes. As NoonTide s senior system administrator, you will create file packages to distribute FrameMaker to machines in the Engineering, Administration, Support, and Sales departments whose operating systems are supported by both TME 10 and FrameMaker. FrameMaker is available for several major operating systems, including UNIX and Windows platforms. (OS/2 and NetWare are not supported by FrameMaker). For the purposes of this scenario, the following procedures define and distribute only HP-UX and Windows file packages. TME 10 Software Distribution User s Guide 4 1

98 Creating a Staging Area for Source Files All of the following Software Distribution procedures are explained in detail in Part III, Performing Software Distribution Operations of this book, beginning with Chapter 6, Profile Setup. TME 10-specific procedures, such as defining managed resources, can be found in the TME 10 Framework User s Guide and TME 10 Framework Planning and Installation Guide. This chapter includes the following procedures: Copying the FrameMaker install media to staging areas on the file package source host Creating policy regions, profile managers, and file packages that will be used to distribute the application Defining file package properties, such as which files will be distributed and what configuration programs will run on the target machines Creating the configuration programs that will be included in the file packages Subscribing machines that will receive FrameMaker Creating queries to search for viable targets for the file package distribution. Distributing the application to the target machines Creating a Staging Area for Source Files To avoid having to mount a CD-ROM drive every time FrameMaker file packages are distributed, you should copy the FrameMaker installation CD-ROMs to staging areas. In this example, FrameMaker files are copied to pescado, the TMR server, by completing the following steps: 1. On pescado, create the directories to which CD-ROM contents will be copied as follows: mkdir -p /apps/framemkr/unix mkdir -p /apps/framemkr/win 4 2 Version 3.6

99 Creating a Staging Area for Source Files Note: When setting up the staging areas in your environment, ensure that the owner-id and group-id of the new directories are set to your user-id and group-id. Tivoli recommends that you not create these directories as root. Ensure the permissions for these directories are set to at least drwxr-xr-x using the chmod command: chmod 755 /apps/framemkr/unix Software Deployment Using File Packages chmod 755 /apps/framemkr/win 1. Place the UNIX FrameMaker installation CD-ROM in the CD-ROM drive. If necessary, mount the CD-ROM drive using the following steps: a. Log in as the root user on pescado. You must have root permissions to mount a drive. a. Create a directory that will be the mount-point for the CD-ROM drive and change the permissions on the directory: mkdir /mnt chmod 755 /mnt a. Mount the CD-ROM drive by entering the following command: mount /dev/cdrom0 /mnt where /dev/cdrom0 is the device node for the CD-ROM drive and /mnt is the mount point. a. Return to the original user s permissions. 1. Copy the contents of the CD-ROM (/mnt directory) to the /apps/framemkr/unix directory: cp -r /mnt /apps/framemkr/unix The r argument recursively copies all files and subdirectories from the CD-ROM to the /apps/framemkr/unix directory. 1. Remove the UNIX FrameMaker installation CD-ROM and replace it with the Windows FrameMaker installation CD-ROM. TME 10 Software Distribution User s Guide 4 3

100 Creating FrameMaker File Packages 1. Copy the contents of the CD-ROM (/mnt directory) to the /apps/framemkr/win directory: cp -r /mnt /apps/framemkr/win Creating FrameMaker File Packages File packages and profile managers can be arranged many different ways in a TMR. In this scenario, you will create several subregions in the Software Distribution policy region that will contain platform-specific profile managers and file packages. Some of the profile managers will house only subscribers, and one will contain file packages for each target platform. You will also create a FrameMaker file package for every platform on which FrameMaker will be installed. Creating unique file packages for the different operating systems enables you to specify different staging areas and configuration programs for the installations. For example, creating a unique file package for HP-UX machines enables you to specifically set the /tmp directory as the staging area in the FrameMkr - HP file package. 1. Ensure that the managed resources are set correctly in the Software Distribution policy region by selecting Managed Resources... from the Properties menu. TME 10 displays the Set Managed Resources dialog. 4 4 Version 3.6

101 Creating FrameMaker File Packages By default, no managed resources are set for policy regions. You must have the FilePackage, ProfileManager, and QueryLibrary resources available when creating and distributing file packages. Select these resources then press the left arrow button to move them to the Current Resources scrolling list. Press the Set & Close button. 1. In the Software Distribution policy region, create a subregion called Desktop Apps. You will create profile managers and file packages in this policy region for FrameMaker and any other desktop applications you may want to install in the future. To create a subregion, select Subregion... from the Create menu. TME 10 displays the Create Policy Region dialog: Software Deployment Using File Packages TME 10 Software Distribution User s Guide 4 5

102 Creating FrameMaker File Packages After you create the Desktop Apps subregion, the subregion icon is displayed in the Policy Region window: 1. In the Desktop Apps subregion, create several profile managers one to house application file packages and one for each operating system to which you will distribute FrameMaker. Double-click on the Desktop Apps policy region icon to display the Policy Region dialog. To create profile managers in this policy region, select ProfileManager... from the Create menu. The Create Profile Manager dialog is displayed. 4 6 Version 3.6

103 Creating FrameMaker File Packages Note that a Dataless Endpoint Mode radio button is available when creating the profile manager. A profile manager can operate in one of two modes: dataless mode or database mode. The dataless mode enables a profile manager to distribute to any TME 10 client managed nodes, endpoints, PC managed nodes, and NetWare managed sites but not to other profile managers. The database mode, in turn, enables distributions to any profile manager (dataless or database), all managed nodes, all PC managed nodes, and NetWare managed sites but not to endpoints. For more information about operating a profile manager in either of these modes, refer to the TME 10 Framework User s Guide. NoonTide Enterprises uses all TME 10 client types in its network, and needs both dataless mode and database mode profile managers to successfully manage distributions to all of its machines. The following diagram illustrates NoonTide s distribution strategy. Software Deployment Using File Packages FrameMkr database mode profile manager file package distributed to dataless mode profile managers 95Machs AIXMachs HPMachs NTMachs SolMachs SunMachs WinMachs TME 10 Software Distribution User s Guide 4 7

104 Creating FrameMaker File Packages NoonTide creates the following profile managers to maximize distribution performance: Several dataless mode profile managers to house platform-specific machines: 95Machs, AIXMachs, HPMachs, NTMachs, SolMachs, SunMachs, and WinMachs. For example, all Windows 95 managed nodes, endpoints, and PC managed nodes will subscribe to 95Machs. A database mode profile manger to distribute to the platform-specific profile managers. The FrameMkr profile manager distributes FrameMaker to the platform-specific profile managers. For example, the 95Machs profile manager subscribes to the FrameMkr profile manager. Alternatively, NoonTide could create two separate sets of profile managers: a database mode set of platform-specific profile managers to distribute to all clients except endpoints, and a dataless mode set of platform-specific profile managers to distribute only to endpoints. This would, however, be an inefficient method of distributing software applications. After creating all of the profile managers, the following icons are displayed in the Policy Region window: 4 8 Version 3.6

105 Creating FrameMaker File Packages The distribution schema involves a two-step process: Within the FrameMkr profile manager, you will create each platform-specific application file package. For example, you will create the FrameMkr - AIX file package to distribute FrameMaker to the AIXMachs profile manager. Within each of the platform-specific profile managers, you will define managed nodes, endpoints, and PC managed nodes of the indicated operating system type as subscribers. For example, you will create AIXMachs to contain all of NoonTide s AIX machines as subscribers. 1. The FrameMaker binaries and application files are platform-specific and reside in platform-specific staging areas on pescado. For each platform to which you want to distribute this application, create separate file packages in the FrameMkr profile manager. For example, for HP-UX machines, create the FrameMkr - HP file package, and for Windows machines, create the FrameMkr - Win file package. To create a file package, select Profile... from the Create menu. The Create Profile dialog is displayed. Software Deployment Using File Packages TME 10 Software Distribution User s Guide 4 9

106 Creating FrameMaker File Packages The FilePackage resource is available for creating Software Distribution file packages. The AutoPack resource is available for creating Software Distribution AutoPack profiles. Chapter 5, Software Deployment Using AutoPacks introduces how to create and distribute an AutoPack profile to Windows-based machines. The InventoryProfile resource is available because TME 10 Inventory is installed. This resource enables us to create Inventory profiles in which you can create query libraries and queries. Queries can then be used to scan machines for the hardware and software that is installed on them. In the Name/Icon Label field, enter the name of the profile and select FilePackage from the Type scrolling list. After creating all necessary file packages, TME 10 displays these icons in the Profile Manager window Version 3.6

107 Setting File Package Properties Setting File Package Properties To set file package properties, you must define where the FrameMaker source files can be found and in which directory on the target machines the distributed files will be placed. You must also define distribution options such as how errors are handled, where to post logging messages from Software Distribution about distributions, and which machines will receive the distribution. The following procedures detail two different methods for defining file package properties for two file packages, FrameMkr - HP and FrameMkr - Win. The procedures, Setting Properties from the Desktop on page 4-12 and Setting Properties Using Export and Import on page 4-17, give steps for defining file package properties either from the desktop or by using file export and import capabilities. Both of these procedures are fully detailed in Chapter 7, File Package Properties. Software Deployment Using File Packages TME 10 Software Distribution User s Guide 4 11

108 Setting File Package Properties Setting Properties from the Desktop Perform the following steps to set the properties of the FrameMkr - HP file package from the desktop: 1. Double-click on the FrameMkr - HP file package icon to display its File Package Properties window. Complete the following steps: a. In the Source Host field, specify the machine on which the source files reside. The source host is the machine on which you copied the contents of the installation CD-ROMs Version 3.6

109 Setting File Package Properties a. Enter the directory path to the staging area on pescado, /apps/framemkr/unix/, in the Source Directories & Files field and press the Return key. The entry is automatically added to the scrolling list. Note that the directory path is put in quotation marks ( ) when it is added to the list. You do not need to use quotes when entering the directory path. OR Press the Directories and Files... button to display the Select Directories & Files dialog. Software Deployment Using File Packages Double-click on the directory containing the install media. Update the Files list by choosing a directory from the Directories list. If the application files are contained in a subdirectory, continue to double-click on a directory until the application files are listed. a. Set the file package distribution options from the General Options check boxes on the File Package Properties dialog: TME 10 Software Distribution User s Guide 4 13

110 Setting File Package Properties - Leave the Stop distribution on error check box selected. If an error occurs during a distribution to one of the target machines, the distribution to that target should stop. An error is logged so that you can determine why the distribution has failed. - Select the Descend into directories check box. This option distributes the contents of any subdirectories that may be included in the source directories. a. Select the Preserve mode of source files radio button to set the permissions of the distributed files to those of the source files. a. Set logging options as follows: - Leave the Send to Software Distribution notice group check box selected to have Software Distribution send information to the notice group whenever a file package operation is performed. - Select the Send to log file on check box to have Software Distribution send information to the specified log file. In the Host field, enter pescado, and in the Path field, enter /logs/framemkr/hp.log. 1. Define platform-specific properties that govern where the distributed files will reside and what configuration programs should be run on the target. To set UNIX options, select Platform-Specific Options -> Unix Options... from the Edit 4 14 Version 3.6

111 Setting File Package Properties menu. Software Distribution displays the File Package Unix Options dialog. Software Deployment Using File Packages Complete the following steps: a. In the Destination Directory Path field, specify where the files distributed by Software Distribution will reside on the target. Enter /tmp/framemkr/stage here. This will be the staging area on the target machines from which the installation script will run. a. Leave the Resolution of Links, User Ownership of Files on Subscribers, and Group Ownership of Files on Subscribers options as they are to preserve installation settings. a. Because you are distributing the installation CD-ROM contents to a staging area on the target machine, specify a before program that checks to ensure that enough disk space TME 10 Software Distribution User s Guide 4 15

112 Setting File Package Properties is available for this and the FrameMaker application files. To do so, press the Before Distribution button under Program Options. Ensure that the Source Host radio button is selected. This configuration program will be distributed from the source host by Software Distribution because nothing has been distributed or created on the subscribers yet. The after program will be distributed to the staging area and will run on the subscriber. In the Enter Program Name field, enter the name of the before program, /apps/framemkr/bfr_hp.sh. Create this and other configuration programs as described in Creating Configuration Programs and Input Files on page Finally, select the Skip distribution to a host on a non-zero exit code of program check box to ensure that the distribution will stop if the target does not have enough disk space. a. To run the FrameMaker installation script after FrameMaker is copied to the staging area on the target machine, and to create a license file for the new FrameMaker installation, specify an after program. To do so, press the After Distribution button under Program Options. Ensure that the Subscribers radio button is selected to run the after program from the staging area on each target. In the Enter Program Name field, enter the name of the after program, /tmp/framemkr/stage/aft_hp.sh. 1. Press the Set & Close button to save the options and return to the File Package Properties window. 1. Press the Save & Close button to save the file package and return to the Profile Manager window. 1. Lastly, set the UID of the configuration scripts that will run before and after the file package distribution. FrameMaker recommends that you do not install the application as root. Because root is the default UID under which configuration programs run, you must change it to the UID of a TME Version 3.6

113 Setting File Package Properties administrator. Assuming the administrator Marc Cervantes, whose UID is 110, will distribute the file packages, enter the following command to set the UID for the configuration programs: wsetfpprgs -T unix -u - UNIX" where T unix - UNIX" specify to set the UNIX properties for the FrameMkr - UNIX file package and u 110 specifies Marc s UID. Software Deployment Using File Packages Setting Properties Using Export and Import The following steps set properties for the FrameMkr - Win file package using export and import functions. TME 10 Software Distribution provides the export and import capabilities that enable you to save file package properties in a text file. The properties are represented as keyword value pairs and lists. Once you export a file package, you can set the values of keywords and specify source directories and files, nested file packages, and files to exclude from the file package. After modifying the text file, you can update the file package properties by importing the contents for the file. Chapter 7, File Package Properties provides detailed information about setting file package properties using the TME 10 desktop, the command line, or by exporting and importing files. Also, the file package definition and all of the keywords are explained in detail in the TME 10 Software Distribution Reference Manual. TME 10 Software Distribution User s Guide 4 17

114 Setting File Package Properties To set file package properties for the FrameMkr - Win file package by exporting and importing the file package definition file, complete the following steps: 1. Double-click on the FrameMkr - Win file package icon to open the File Package Properties dialog for FrameMkr - Win. Select Export... from the File Package menu item to display the Export File Package Definition dialog: This dialog enables you to save the file package definition to a text file, which you can edit to set file package properties. In this dialog, set the managed node (pescado) and path to the file (/tmp/frm_win.txt). When you press the Export & Close button, the file package definition is saved to this file and the dialog closes Version 3.6

115 Setting File Package Properties 1. From a command line, change to the /tmp directory and open the frm_win.txt file in a text editor, such as vi or emacs, for editing: Software Deployment Using File Packages As illustrated by the contents of this dialog, the file package definition is simply a text file that lists one keyword value pair per line. The file package definition can also include sections delimited by percent signs (%), which follow the keywords. Anything listed after the first % is a file or directory to be distributed. Entries listed after the second % are nested file packages. Files or directories listed after the third % are to be excluded from the file package. To set file package properties, find the keywords and set their values, and list source file and directories, nested file packages, and files to be excluded after the appropriate %. 1. Set the appropriate keywords. The TME 10 Software Distribution Reference Manual provides a full listing of available keywords TME 10 Software Distribution User s Guide 4 19

116 Setting File Package Properties that can be set. In this example, you must set the following keywords to the indicated values: log_host=pescado Sets the machine on which the log file will reside. log_file=/logs/framemkr/win.log Specifies the name of the log file. Diagnostic or error messages are written to this log file when file package operations are performed on this file package. append_log=y Appends to, instead of overwriting, the log file and enables you to view old and new log file entries. This file package property is not available from the desktop. descend_dirs=y Distributes the contents of any subdirectories that may be included in the source directories. win_platform_prefix=c:/apps/framemkr/stage Specifies the destination directory of the distributed files and directories. Remember to use a forward slash (/) when specifying paths, even though the file or directory resides on the PC. win_before_prog_path=c:/stage/framemkr/win/bf R_WIN.BAT Specifies to run the BFR_WIN.BAT program before distributing the source files and directories. This program will ensure that there is enough disk space on the target machine for the staged files and the resulting FrameMaker files. Create this program in Creating Configuration Programs and Input Files on page win_before_prog_from_src=y Specifies that this configuration program will run on the client machine from the source host. The after programs will be distributed to the staging area and, thus, will run on the target machines. win_before_skip_non_zero=y Because the before program will exit with a non-zero value if the target machine does not have enough disk space, set this keyword to skip the distribution to that machine. win_after_prog_path=c:/apps/framemkr/stage/af T_WIN.BAT Runs the AFT_WIN.BAT program after the 4 20 Version 3.6

117 Setting File Package Properties staged files are distributed. This program runs the FrameMaker installation script and license program then removes the staged files. Other keywords that should be set already have default values defined. Some of these include the following: - stop_on_error=y Stops the distribution to all targets if an error occurs during a distribution. - post_notice=y Posts diagnostic information to the Software Distribution notice group. - win_optional_dist=n Does not permit the user on the Windows machine choose to receive the distribution. The distribution is mandatory. - win_after_option= If left null, does not reboot or restart the Windows target after a distribution. 1. Set the source directory. Scroll past the keywords in the frm_win.txt file. After the first %, enter /apps/framemkr/win/, which is the path to the staging area on electron. This directory path should be on a line by itself. 1. Save and exit the frm_win.txt file. 1. The only file package property not available in the file package definition is the source host, which you must specify because a source directory is defined. If you try to import a file package definition without setting the source host, Software Distribution displays a file browser dialog so that you can select a source host. You can also use the command line to set file package contents, as follows: Software Deployment Using File Packages wsetfpcontents -h - Win" where h pescado sets the source host to pescado for the FrameMkr - Win file package. Use double quotes around the file package name because it contains spaces. 1. Now that you have edited the file package definition, import it into the file package. From the File Package Properties window, select Import... from the File Package menu. Software TME 10 Software Distribution User s Guide 4 21

118 Setting File Package Properties Distribution displays the Import File Package Definition dialog. Select pescado, the source host, and /tmp/frm_win.txt, the text file, from which to import the file package definition and press Import & Close. The file package properties are immediately updated to those specified in the /tmp/frm_win.txt file. 1. To verify the file package properties that you set using the export and import capabilities or with the command line, close the File 4 22 Version 3.6

119 Creating Configuration Programs and Input Files Package Properties window and open the file package again to redisplay it. Software Deployment Using File Packages Creating Configuration Programs and Input Files While defining the file package properties, you specified several before and after programs that you must create before initiating the distributions. The following sections list and describe the UNIX configuration programs. Line numbers are provided for reference. TME 10 Software Distribution User s Guide 4 23

120 Creating Configuration Programs and Input Files The bfr_hp.sh Before Program The bfr_hp.sh before program verifies that the target HP-UX machine has enough disk space to stage the FrameMaker install files. If not, the program exits with a non-zero value. Because you selected the Skip distribution to a host on a non-zero exit code of a program check box (the unix_before_skip_non_zero keyword) from the desktop, Software Distribution will not distribute the file package to the failed target. The following code is an example of a before script: 1 #!/bin/sh 2 3 # Define variables - K_NEEDED is # of KB need for staging 4 # area, STAGE_DIR is staging area on target HP machines 5 K_NEEDED= STAGE_DIR=/tmp/FrameMkr/stage 7 DF_PROG=/bin/bdf 8 TAIL_PROG=/bin/tail 9 10 mkdir -p $STAGE_DIR 11 cd $STAGE_DIR # Determine if the target machine has space available ; 14 # if not, exit non-zero 15 AVAIL='$DF_PROG. $TAIL_PROG -1 awk '{print $4}'' if [ "$AVAIL" -le $K_NEEDED ] 18 then 19 exit 1 20 fi exit 0 Lines 5 through 8 define variables. The K_NEEDED variable ensures that the target machine has 210 MB of available disk space. The STAGE_DIR variable specifies the staging area, the /tmp/framemkr/stage directory, in which the FrameMaker installation script and files will be copied from pescado. Line 10 creates the staging area and line 11 changes to that directory. Finally, the script checks for the disk space on line 15 and exits the program appropriately in lines 17 to 22. The aft_hp.sh After Program The aft_hp.sh after program runs the FrameMaker installation script, which is distributed with the entire contents of the staging area on pescado to the /tmp/framemkr/stage directory. This script also runs 4 24 Version 3.6

121 Creating Configuration Programs and Input Files the FrameMaker licensing program, which sets up licensing for each FrameMaker installation. It then removes the staging area and exits with 0. The following code is an example of an after script: 1 #!/bin/sh 2 3 CURDIR='pwd' 4 5 # change to the staging directory 6 cd /tmp/framemkr/stage 7 8 # Run the FrameMaker installation program 9 /tmp/framemkr/stage/"read.cd;1" </tmp/framemkr/stage/aft.txt # Run the script containing the licensing program 12 /tmp/framemkr/stage/lic.sh </tmp/framemkr/stage/lic.txt cd $CURDIR # Once done, remove the staging directory 17 rm -r /tmp/framemkr/stage exit 0 For the FrameMkr - Win, FrameMkr - 95, and FrameMkr - NT file packages on PC managed nodes, you could add the following lines before line 9 to the PC equivalent of this program: Software Deployment Using File Packages PATH=%PATH%;D:\xxx waddicon -g "FrameMaker" -c D:/APPS/FrameMkr/maker -t "FrameMaker" where xxx designates the path to the TME 10 agent CLI directory. These lines add the path of the agent CLI directory to your PATH environment variable and run the waddicon command. This command creates the FrameMaker windows group and icon. Also, remember that if you create a configuration program on a UNIX machine that will run on a PC, you must include a carriage return (ctrl-m or ^) at the end of each line in the file. PC systems expect a carriage return at the end of each line in addition to the newline character. After creating this program, set the permissions to enable execution: chmod 755 aft_sun_instl.sh TME 10 Software Distribution User s Guide 4 25

122 Creating Configuration Programs and Input Files The lic.sh Script After the aft_hp.sh program executes the FrameMaker installation script, it runs a licensing script, lic.sh. This script runs the FrameMaker licensing program and has an input file that lists all hosts on which FrameMaker is installed, and the corresponding users and license passwords. The lic.sh script is as follows: 1 #!/bin/sh 2 3 INTERP=hpux9 4 UNAME_PATH='uname -n' 5 6 THIS_HOST='$UNAME_PATH -n' 7 8 while true 9 do 10 read hostname password username 11 if [ -z "$hostname" ] 12 then 13 break 14 fi if [ "$THIS_HOST" = "$hostname" ] 17 then 18 break 19 fi 20 done if [ -z "username" ] 23 then 24 echo "No match found for this host!" 25 exit 1 26 else 27 /usr/framemkr/bin/fmaddlicense << EOF 28 add $password $username 29 EOF 30 fi exit 0 Line 4 retrieves the name of the operating system on which this script is running. Line 10 reads the lic.txt file specified with this script in the aft_hp.sh script. It continues to read the input file until the name of the machine and the hostname in the lic.txt file match. (If a match is not found, line 25 exits the program with an error.) Lines exit the while loop, which processes standard input when the line matching the machine is encountered. In lines 27 and 28, the script runs the 4 26 Version 3.6

123 Creating Configuration Programs and Input Files fmaddlicense program, adding licensing information for the FrameMaker installation on the machine. The aft.txt and lic.txt Files The aft.txt input file, which is passed to the aft_hp.sh script, lists the responses to the installation script, one per line, as follows. Note that line 22 is blank as a result of the return from line y 2 /usr/framemkr 3 y 4 n 5 n 6 n 7 y 8 y 9 n 10 y 11 y 12 n 13 n 14 n 15 n 16 n 17 y 18 n 19 n 20 y 21 y 22 These values are obtained by performing an actual FrameMaker installation and recording the responses to the FrameMaker installation script. The lic.txt file, which is passed to the lic.sh script, lists the hosts and their corresponding users and license passwords: Software Deployment Using File Packages american sjones brie mherman The license passwords are provided by FrameMaker. TME 10 Software Distribution User s Guide 4 27

124 Setting File Package Subscribers Setting File Package Subscribers In Creating FrameMaker File Packages on page 4-4, you created several profile managers, including one database profile manager that contains the FrameMaker file packages and several dataless profile managers that represent each type of machine in the TMR. In this section, you will populate each platform-specific profile manager so that it contains its corresponding machines. These dataless mode profile managers were created explicitly for this purpose to subscribe managed nodes, endpoints, and PC managed nodes for each operating system. Each platform-specific profile manager, in turn, subscribes to the FrameMkr profile manager. Later, you can distribute a platform-specific file package simply by dragging-and-dropping it on its corresponding profile manager. To subscribe managed nodes, endpoints, and PC managed nodes to the appropriate profile managers, complete the following steps: 1. Double-click on the Desktop Apps policy region icon to display the Policy Region window. 1. Double-click on the HPMachs profile manager icon to display its Profile Manager window. Because you have not created file packages in this profile manager, none are displayed in the Profiles region of the window. Likewise, because you have not 4 28 Version 3.6

125 Setting File Package Subscribers yet set subscribers for this profile manager, none are displayed in the Subscribers region of the window. 1. To subscribe HP-UX targets, select Subscribers... from the Profile Manager menu. TME 10 displays the following dialog: Software Deployment Using File Packages All managed nodes, endpoints, and PC managed nodes available in the TMRs are listed in here. 1. Select all of the HP-UX targets from the Available to become Subscribers scrolling list. Refer to Chapter 3, The Distribution Environment to verify which targets are HP-UX machines. Press the left arrow button to move all HP-UX client systems to the Current Subscribers scrolling list. Press the Set Subscriptions & Close button to set these subscribers and return to the Profile Manager window. TME 10 Software Distribution User s Guide 4 29

126 Setting File Package Subscribers 1. The Profile Manager window now displays all of NoonTide s HP-UX subscribers in the Subscribers scrolling list. 1. Double-click on the WinMachs profile manager icon to display its Profile Manager window. Subscribe all Windows systems by selecting Subscribers... from the Profile Manager menu. 1. Press and hold down the <Ctrl> key to select multiple Windows PC managed nodes and endpoints from the Available to become Subscribers scrolling list. After selecting all of the Windows machines, press the left arrow button to move the selected items to the Current Subscribers scrolling list. Press the Set Subscriptions & Close button to set these subscribers and return to the Profile Manager window Version 3.6

127 Setting File Package Subscribers The WinMachs profile manager displays all of NoonTide s Windows managed nodes, endpoints, and PC managed nodes. All Windows machines in the rainbow-win NetWare managed site will also receive FrameMaker: therefore, subscribe rainbow-win to this profile manager. Software Deployment Using File Packages 1. Repeat steps 6 and 7 for the rest of the platform-specific profile managers. Refer to Chapter 3, The Distribution Environment to select the correct managed nodes or PC managed nodes for each profile manager. 1. Once each profile manager s subscribers are set, subscribe the profile managers to the FrameMkr profile manager. To do so, open the FrameMkr profile manager. Either drag each profile manager and drop it on the FrameMkr profile manager s icon, or perform steps 2 4, subscribing the platform-specific profile managers as you subscribed the individual machines. After TME 10 Software Distribution User s Guide 4 31

128 Creating TME 10 Inventory Queries subscribing the profiles managers to the FrameMkr profile manager, the Profile Manager window displays the following: Creating TME 10 Inventory Queries If you have installed TME 10 Inventory, you can use queries to further select targets of the software distribution. For example, in the NoonTide environment, you can use queries to list machines of a certain operating system and version, to list machines with a particular application installed on them, or to obtain a list of machines with specific hardware configurations. The following procedure describes how to create the Software Queries query library as well as how to create its Win & No FrameMkr query. The Software Queries query library will reside in 4 32 Version 3.6

129 Creating TME 10 Inventory Queries the Software Distribution policy region, and will contain a query for determining the operating system and software installed on a machine. 1. Double-click on the Software Distribution policy region icon to display the Policy Region window: Software Deployment Using File Packages 1. Ensure that the InventoryProfile and QueryLibrary resources are available in this policy region by selecting Managed Resources... from the Properties menu. If they are not listed as current resources, move them to the Current Resources scrolling list and press Set & Close. 1. Select QueryLibrary... from the Create menu. The Create Query Library dialog is displayed: TME 10 Software Distribution User s Guide 4 33

130 Creating TME 10 Inventory Queries Enter Software Queries in the Name/Icon Label field then press Create & Close to create the query library. 1. Double-click on the Software Queries query library icon to display its query library window. 1. Select Query... from the Create menu to display the Create Query dialog. 1. Create the Win & No FrameMkr query to determine which Windows machines do not have FrameMaker installed Version 3.6

131 Creating TME 10 Inventory Queries Complete the following steps to create the Win & No FrameMkr query: a. In the Query Name field, enter Win & No FrameMkr. a. In the Table/View Name field, enter INVENTORY_SYSTEM_VIEW, and press the Set button. OR Press the ellipses (...) button to select INVENTORY_SYSTEM_VIEW from a list of views in the repository. Selecting INVENTORY_SYSTEM_VIEW populates the Available Columns scrolling list. a. From the Available Columns list, select the following columns and move them to the Chosen Columns scrolling list with the arrow button: BOOTED_OS_NAME, and SOFTWARE_ID. a. Create the following SQL query clauses in the Where Clause and Additional Clauses section of the dialog to query all machines for Windows systems that do not have FrameMaker installed: - Enter BOOTED_OS_NAME in the Column Name field and Windows (in single quotes) in the Column Value field. Press the Add button to add this property and value to the Where Clause scrolling list. - Enter the following SQL statement in the Additional Clauses section: and HARDWARE_SYSTEM_ID not in (select HARDWARE_SYSTEM_ID from INVENTORY_SYSTEM_VIEW where SOFTWARE_ID = Framemaker) a. Press the Run Query... button to execute the query. TME 10 Inventory runs the query on all machines and posts the results to the Run Query dialog in tabular form. The TME 10 Inventory User s Guide provides detailed information about queries, query properties, and the TME 10 configuration repository. Software Deployment Using File Packages TME 10 Software Distribution User s Guide 4 35

132 Distributing the FrameMaker File Packages Distributing the FrameMaker File Packages After creating and setting properties for all of the file packages, you can easily and quickly deploy FrameMaker to machines in NoonTide s Engineering, Administration, Support, and Sales departments. Either use the drag-and-drop method by dragging a file package and dropping it onto the corresponding profile manager, or use the GUI to select distribution options and perform queries before distributing a file package. Assuming that all file packages except FrameMkr - Win have already been distributed using drag-and-drop, the following procedure distributes the FrameMkr - Win file package using the Distribute File Package dialog. This dialog enables you to perform a query to find out which Windows machines do not already have FrameMaker installed. Note that the querying function is available because TME 10 Inventory is installed. Note: Distribute the file packages as an administrator, not as root. Adobe recommends that you not install FrameMaker as root. Also, Tivoli has found that the licensing program will not work if the application is run as root Version 3.6

133 Distributing the FrameMaker File Packages Complete the following steps to distribute the FrameMkr - Win file package: 1. Select Distribute... from the FrameMkr - Win file package icon menu to display the Distribute File Package dialog. Software Deployment Using File Packages All of the profile managers that are subscribed to the FrameMkr profile manager are available in the Available Subscribers scrolling list. TME 10 Software Distribution User s Guide 4 37

134 Distributing the FrameMaker File Packages The plus sign (+) indicates that the listed subscriber is a profile manager. By double-clicking on the profile manager name, you can expand the list to view all subscribers to this profile manager. Note that the managed resource type for each subscribing machine is listed next to the machine name in this example (MN) parmesan shows that parmesan is a managed node and (EP) thor indicates that thor is an endpoint. 1. Because you have not specified a commit program, leave the Distribution Only radio button selected. Likewise, because you have not distributed this file package, leave the Distribute all entries radio button selected. 1. Press the Query button to display the Execute a Query dialog. This dialog lists the Software Queries query library that you created previously. By clicking on Software Queries, you can see that this library contains the following queries: 1. To execute a query, select the Win & No FrameMkr query listed in the Queries scrolling list and press the Execute button. TME 10 Inventory queries the TME 10 configuration repository 4 38 Version 3.6

135 Distributing the FrameMaker File Packages for Windows machines that do not have FrameMaker installed and populates the Distribute File Package To scrolling list: Software Deployment Using File Packages The Win & No FrameMkr query returns all Windows machines that do not already have FrameMaker installed. Note that the rainbow-win NetWare managed site is not included in this list. Use drag and drop to distribute to machines in rainbow-win. 1. To distribute the FrameMkr - Win file package to the Windows targets that are returned by the query, press the Distribute & Close button. TME 10 Software Distribution User s Guide 4 39

136 Distributing the FrameMaker File Packages Having distributed each file package to the machines in the Engineering, Administration, Support, and Sales departments, FrameMaker is ready for use. Each file package distributes the desktop application, installs it, and sets up licensing for each installation Version 3.6

137 5 5Software Deployment Using AutoPacks The previous chapter described how to create and distribute a desktop application using file packages. This chapter introduces how to build and distribute an AutoPack a TME 10 Software Distribution resource type that is similar to a file package but provides a simpler, more convenient way to create installable images for Windows-based PCs managed by TME 10. An AutoPack enables you to distribute software to client machines without doing anything beyond its creation process. Using the AutoPack feature, you need not create and run configuration programs all scripts necessary to install and run the software are built-in. The AutoPack utility automatically determines the files that need to be distributed to the target machine and handles Windows installation issues such as registry changes, desktop icons, and programs listed on the Start menu. An AutoPack is built and distributed to target machines by Creating an AutoPack file with the AutoPack Control Center. The AutoPack Control Center is installed on a Windows-based PC and enables you to create an AutoPack file, which contains all the files necessary to install a shrink-wrapped application, such as Microsoft Office 97 or Netscape Navigator. The files include scripts that are needed to perform system configuration changes to the client machine. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 1

138 Introducing the AutoPack Control Center Installing an AutoPack agent on each managed node and PC managed node that will receive AutoPacks. The AutoPack agent is automatically installed on an endpoint when the endpoint is created. In conjunction with other services on the target machine, the AutoPack agent is responsible for receiving and unpacking an AutoPack profile. Creating an AutoPack profile within a policy region in the Tivoli Management Region (TMR) policy region to distribute the AutoPack file. The AutoPack profile, which is distributed to clients in the TMR, provides a container for the AutoPack file s application and system configuration information. As NoonTide s senior system administrator, you will distribute Microsoft Office 97 to Windows 95 and Windows NT machines in all departments of NoonTide Enterprises. Although you can distribute AutoPack profiles to Windows 3.x machines, Microsoft Office 97 is not supported on this platform. The steps in this chapter can be modified to distribute any PC application, such as Adobe Acrobat, Netscape Navigator, or Lotus Notes to Windows-based machines. Refer to the following sources for more conceptual and procedural information about Software Distribution s AutoPack technology: Chapter 10, AutoPack Properties and Operations of this book, the TME 10 Software Distribution AutoPack User s Guide, and the AutoPack Control Center online help. Introducing the AutoPack Control Center The AutoPack Control Center is a TME 10 Software Distribution tool installed on a Windows-based PC that enables you to create an AutoPack file. An AutoPack file is an installable image of a software application that can be distributed to client machines using an AutoPack profile. Based on file package block (fpblock) technology, the AutoPack file contains the files and system configuration changes that are installed on target PCs with an AutoPack profile. You will install the AutoPack Control Center on a preparation (prep) machine, which can be any Windows, Windows 95, or Windows NT machine. Tivoli strongly recommends that this prep machine be pristine, having few or no other applications installed. Because the 5 2 Version 3.6

139 Introducing the AutoPack Control Center AutoPack Control Center relies on differencing technology that detects files and system configurations, using a pristine system will avoid file contention. If other applications are installed on the prep machine before creating the AutoPack file, the AutoPack Control Center may include unwanted data and system files in, or exclude vital system files from, the AutoPack file. Also, Tivoli strongly recommends that you create an AutoPack file on the same operating system as the target machine. This avoids file contention that may result between different versions of Windows. For example, if you are installing Netscape Navigator on Windows 95 and Windows NT systems, you should create an AutoPack file on each platform. The AutoPack file is created using the AutoPack Control Center by Creating the pre-installation (baseline) snapshot of the prep machine s drive and system configurations. Installing the target application on the prep machine. Creating the post-installation snapshot of the prep machine, and building the AutoPack file. The AutoPack file encapsulates the differences between the two snapshots and includes distribution instructions that will eventually be executed on client machines. Before creating the AutoPack file, you must install the AutoPack Control Center on a preparation (prep) machine, as described in Installing the AutoPack Control Center on page In the following procedures, you will use a PC managed node named ladybug, a Windows NT 4.0 PC, as the prep machine to create an AutoPack file for NT 4.0 targets. The same procedures may be used to create AutoPack files for Windows 3.x, Windows 95, and Windows NT 3.5 PCs, although you must complete these steps on each specific platform. Only Windows NT 4.0 procedures are described in this chapter. Verify that ladybug has few to no applications installed. To list the applications installed on a Windows NT 4.0 PC, select the Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 3

140 Introducing the AutoPack Control Center Add/Remove Programs icon from the Windows NT Control Panel to display the Add/Remove Program Properties dialog. You may also want to refer to the Windows NT Start -> Programs menu because not all application installations add an entry to the Windows NT Add/Remove Programs group. 5 4 Version 3.6

141 Creating the AutoPack File As seen from this dialog, only Tivoli applications are installed on this machine. Creating the AutoPack File An AutoPack file cannot perform OS upgrades or installations. An AutoPack file contains all the files necessary to install a software application, including any necessary system-configuration changes. You will build an AutoPack file with the AutoPack Control Center on the prep machine by completing the following steps: Scanning a drive on the prep machine where software will be installed in order to create a pre-installation snapshot of drive and system configurations. It is important that the prep machine is pristine and of the same operating system type as the target PC. Installing software on the prep machine the file and system changes that result from this software installation are bundled and eventually distributed to target machines. Taking a post-installation scan of the prep machine drive and identifying the installed files. Setting the AutoPack file s distribution properties, including information about target machines. Building an AutoPack file based on the difference between the pre- and post-installation scans and on user-defined properties. After creating the AutoPack file, you can distribute it using an AutoPack profile in a Tivoli Management Region (TMR) policy region. Instructions to create, set properties for, and distribute an AutoPack profile are explained in Chapter 10, AutoPack Properties and Operations as well as in the TME 10 Software Distribution AutoPack User s Guide. Tivoli recommends that you log in to the NT prep machine as Administrator to build the AutoPack file. Often applications require that you have these permissions to perform the installation and modify the system configuration. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 5

142 Creating the AutoPack File Note: If you distribute the Office AutoPack profile to targets where the PC agent is running as a service or where the user is logged off, the application may not run properly. Microsoft addresses this and similar issues in articles contained in their Knowledge Exchange. In particular, see article ID Q at for more information about problems you may encounter when installing programs on Windows NT 4.0 machines. To display the AutoPack Control Center, select AutoPack from the Start -> Programs menu. The AutoPack Control Center provides an easy-to-use interface that guides you through the steps to create an AutoPack file. Note that the fourth button on the dialog is used to edit existing AutoPack files. Although you will not use this feature in this procedure, you could easily repeat this process to modify an AutoPack file to specify a different destination directory for the target machines or to change the logging options, for example. Creating the Baseline Snapshot The baseline snapshot is a preliminary snapshot of the prep machine s drive and system configuration. Before running the scan to create the 5 6 Version 3.6

143 Creating the AutoPack File The AutoPack Control Center cannot scan a network drive. snapshot, you will specify the drive to scan, the working directory, the files to monitor, and the files to exclude. 1. Create a pre-install snapshot by pressing the Create Baseline Snapshot button on the AutoPack window. The Create Baseline Snapshot dialog is displayed. In the Drive field on the General Options property sheet, specify the drive where you will install the software on the prep machine. When the AutoPack Control Center compares the pre- and post-install snapshots, it compares the files found on this drive to create the contents of the AutoPack file. Note: Ensure that you specify file and directory paths using \ (backslashes). The AutoPack Control Center will not convert / (forward slashes) to \ (backslashes). 1. In the Directory field, specify the working directory where the AutoPack Control Center will store the files used to create the AutoPack file. These files will require a little more disk space than recommended by the installed application. This space consideration depends on the actual software you are installing. 1. On the Files to Monitor property sheet, enter additional.ini files to monitor. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 7

144 Creating the AutoPack File The AutoPack Control Center monitors listed.ini files, even if they reside on different drives, by detecting differences in preand post-installation.ini files. This differencing allows files to be updated, rather than replaced, with new differencing information. By default, the AutoPack Control Center monitors the files listed in the dialog shown below. Tivoli strongly recommends that you do not change or edit files listed here. You can, however, add additional files to be monitored. For example, you can include My.INI to this list, which prompts the AutoPack Control Center to gather information about sections or items that have been modified inside My.INI. These modifications are then automatically replicated in the target My.INI file. 1. On the Files to Exclude property sheet, include any files you want to exclude from the snapshots. 5 8 Version 3.6

145 Creating the AutoPack File Add files and directories to this property sheet if you are not interested in replicating any changes to these files or directories on the target system. Because Tivoli code is installed on the preparation machine, a PC managed node, you should exclude the Tivoli directory, which contains the TMEAGENT.CFG file, by completing the following steps: a. Press the Browse Directories button to display the Directories dialog. a. Select the C:\Tivoli directory and press the OK button to return to the Create Baseline Snapshot dialog. This adds the C:\Tivoli directory to the list of files to be excluded from the scans. All other directories listed are excluded by default. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 9

146 Creating the AutoPack File 1. Press the Run button to create the baseline snapshot and save the baseline snapshot to the directory specified in the Directory field on the General Options property sheet. While the AutoPack Control Center creates the baseline snapshot, a dialog similar to the following window is displayed. Installing the Software To install Microsoft Office 97 on ladybug, press the Install Software button on the AutoPack Control Center. The Install Software dialog is displayed Version 3.6

147 Creating the AutoPack File 1. In the Install Executable field, enter the drive and path, E:\SETUP.EXE /m, to the installation setup program. This is the path to the CD-ROM drive and the Office 97 setup executable. Note: Include /m to skip the licensing prompts. If installing Office 95 on Windows 95 or Windows NT machines, search Microsoft s Knowledge Exchange at for more information about installing products on these Windows platforms. 1. If you wish to close the AutoPack Control Center before beginning the installation, as some installations recommend, select the Exit AutoPack Control Center before installing software check box. 1. Press the Run button. The setup program displays the following Microsoft installation dialog. Software Deployment Using AutoPacks 1. Complete the installation as directed.you can also install the software as you would normally, from the File menu of the Program Manager or from the File Manager. Regardless of how you run the executable, be sure to close all applications, including the AutoPack Control Center, if the installation requires that you do so. TME 10 Software Distribution User s Guide 5 11

148 Creating the AutoPack File Building the AutoPack File After installing Office 97 on ladybug, select AutoPack from the Windows NT Start -> Programs menu to launch the AutoPack Control Center. This dialog provides the Build AutoPack button that prompts the AutoPack Control Center to create a second snapshot and build the AutoPack file. This process performs a post-scan of the prep machine s drive and compares the first scan s files with those of the second scan. Complete the following steps to build the AutoPack file: 1. Press the Build AutoPack button on the Autopack Control Center dialog to display the Build AutoPack dialog. Enter the full path to the AutoPack file in the Name field. The.PAK extension is appended to the name automatically when the AutoPack file is built, regardless of any extension that you may add the AutoPack Control Center identifies files with the.pak extension as AutoPack files. Note: Ensure that the AutoPack file name conforms to file naming conventions required by Windows 3.1 systems if you will be distributing the AutoPack file to a Windows 3.1 machine. 1. Press the Run button. The AutoPack Control Center takes the second snapshot, compares it to the baseline, and creates the.def,.chg,.err, and.rep files. While the AutoPack Control Center scans the prep machine for the second time, the following 5 12 Version 3.6

149 Creating the AutoPack File dialog is displayed. The OK button is enabled when all files are scanned successfully. Although you will not change configurations of the.def and.chg files in this scenario, you can edit both of these files to further define the distribution behavior of the AutoPack file. Refer to the TME 10 Software Distribution AutoPack User s Guide for detailed information about editing the.def and.chg files. 1. Press the OK button to close the Scan Status dialog and display the AutoPack Properties window. Software Deployment Using AutoPacks Setting AutoPack File Properties The AutoPack Control Center displays the AutoPack Properties window after the AutoPack file is built. From this window, you can set the AutoPack s distribution properties, including information about the destination machine. This dialog has four property sheets: General, File Mode, Log Info, and Distribution. TME 10 Software Distribution User s Guide 5 13

150 Creating the AutoPack File Complete the following steps to set AutoPack Properties: 1. On the General property sheet, specify the following information: a. In the Destination Drive field, specify the drive on the target machine where the files contained in the AutoPack file will be installed. The program files will be installed on the specified drive. However, all system files in the AutoPack file will be installed on the system directory. An AutoPack profile can only be distributed to one destination drive at a time. If you wish to distribute an AutoPack profile to multiple drives, create a separate AutoPack file and profile for each target drive. a. In the Staging Directory field, specify the working directory on the target machine that TME 10 Software Distribution will use when distributing the AutoPack profile. In general, the staging directory on the target machine should have enough space to hold the required system files, but not the entire software package. Note: Ensure that you specify file and directory paths using backslashes (\). The AutoPack Control Center will not convert forward slashes (/) to backslashes Version 3.6

151 Creating the AutoPack File 1. Set the options on the File Mode property sheet. This dialog enables you to set the defaults for the AutoPack Properties window, which lets you set options for distributing the AutoPack file on the target. Select the Preserve mode of source files radio button to set the permissions of the files distributed by the AutoPack profile to those of the source files contained in the AutoPack file. Select the Change mode of destination files to radio button to change the permissions of the files distributed by the AutoPack profile to those specified in the Read and Write check boxes. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 15

152 Creating the AutoPack File 1. Set the logging options for the AutoPack file on the Log Info property sheet. Check the Send to Distribution notice group check box to have TME 10 Software Distribution send a notice to its notice group when the AutoPack profile is distributed. Check the Send to check box to have TME 10 Software Distribution send to the specified address when the AutoPack profile is distributed. You can specify multiple addresses by separating each domain name with a comma. Check the Send to log file on check box to have TME 10 Software Distribution post a notice to the AutoPack log file, specified in the Host and Path fields. This log file is the best source of information about an AutoPack profile distribution and Tivoli recommends that you select this check box and fill in the Host and Path fields. If you choose to post a notice to the AutoPack log file in this manner, check the Append log file check box to append the log file to an existing log file rather than overwriting it Version 3.6

153 Creating the AutoPack File 1. Set distribution options on the Distribution property sheet. Not supported on Windows NT Check the Stop distribution on error check box to immediately stop the AutoPack profile distribution if an error occurs on a target. Check the Perform compression on distribution check box to compress the data in the AutoPack profile before distributing it. Select the Mandatory radio button to have TME 10 Software Distribution distribute the AutoPack profile without giving the targets users the option to cancel the distribution. Select the Optional radio button to have TME 10 Software Distribution distribute the AutoPack profile, giving the targets users the option to cancel the distribution. An optional distribution displays a pop-up dialog on the target at distribution time. The user can then choose to accept the distribution or not. If the user does not choose in the amount of time specified in the seconds field, the AutoPack profile is distributed. Specify a time (in seconds) that is between 1 and 6000 seconds, inclusive. The default value is 120 seconds. Check the Timeout check box to specify a timeout value (in seconds) to terminate a distribution if it does not complete in the allotted time. The default is no timeout. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 17

154 Editing an Existing AutoPack File 1. After setting all of the options, press the Build button.the AutoPack Control Center creates the officent4.pak file by bundling all files, options, and system configuration changes necessary to install the application on the target machines. When the AutoPack Control Center is finished, you can select the Contents button to view the list of files that will be distributed in the AutoPack file. This list includes system files. Note that the paths of the files begin with C:/tmesdist/staging, which is the directory you specified as the staging directory on the target machines. Editing an Existing AutoPack File Using the Edit AutoPack feature on the AutoPack Control Center, you can edit an existing AutoPack file. This feature enables you to modify the contents of the.def file, which lists all properties of the AutoPack 5 18 Version 3.6

155 Editing an Existing AutoPack File file. The files listed in the definition file are those that are listed on the AutoPack Contents dialog. When you edit an existing AutoPack file, you must ensure that all software files exist in the same location as when the AutoPack was originally created. For example, if you previously created an AutoPack file for Microsoft Office 97 whose files were located in C:\temp, you must ensure that all files for Office 97 still exist in the C:\temp directory. The following steps describe how to edit an AutoPack file: Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 19

156 Editing an Existing AutoPack File 1. Press the Edit AutoPack button on the AutoPack Control Center window. The Open dialog is displayed. All available.def files are listed in the File name scrolling list. 1. Select the.def file you wish to edit and press the OK button. The AutoPack Properties window is displayed for the.def file that you are editing. This window is the same as the one that is displayed when you initially create an AutoPack file, as shown in Setting AutoPack File Properties on page In the Staging Directory field, enter the name of the working directory on the target machine to which the AutoPack profile is distributed. You can specify the same staging directory as the one you specified when creating the AutoPack file Version 3.6

157 Creating an AutoPack Profile 1. Once you have entered the path to the staging directory, you can reset the AutoPack s distribution properties, including information about the destination machine, the file mode, and any logging information. Follow the steps in the Setting AutoPack File Properties section for instructions about resetting these properties and rebuilding the AutoPack file. Creating an AutoPack Profile In the previous chapter, you created the Desktop Apps subregion within the Software Distribution policy region to house profile managers and file packages. In this section, you will create the PC Apps subregion within Software Distribution to contain AutoPack profiles and platform-specific profile managers. Complete the following steps to create a subregion to house the Office97 - NT40 and Office97 - Win95 AutoPack profiles. 1. Ensure that the managed resources are set correctly in the Software Distribution policy region. To do so, select Managed Resources... from the Properties menu.the Set Managed Resources dialog is displayed. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 21

158 Creating an AutoPack Profile In the previous chapter, you added the FilePackage, ProfileManager, and QueryLibrary resources. You must have the AutoPack resource available when creating and distributing AutoPack profiles. Select AutoPack from the Available Resources scrolling list and press the left arrow button to move this resource to the Current Resources scrolling list. Press the Set & Close button. 1. In the Software Distribution policy region, create a subregion called PC Apps. Create profile managers in the PC Apps subregion for Microsoft Office 97 and any other PC applications you may want to install in the future. To create a subregion, select Subregion... from the Create menu. The following Create Policy Region dialog is displayed: 5 22 Version 3.6

159 Creating an AutoPack Profile After creating the subregion, its icon is displayed in the Policy Region dialog. 1. In the PC Apps subregion, create a profile manager to house AutoPack profiles and subscribers. Double-click on the PC Apps icon to display the Policy Region window. 1. To create a profile manager in which the Microsoft Office 97 AutoPack profiles will reside, select ProfileManager... from the Create menu in the policy region. TME 10 displays the Create Profile Manager dialog. Software Deployment Using AutoPacks a. Enter Office97 in the Name/Icon Label field. TME 10 Software Distribution User s Guide 5 23

160 Creating an AutoPack Profile a. Do not select the Dataless Endpoint Mode radio button. The Office97 profile manager must be a database profile manager so that it can distribute to other profile managers. a. Press the Create & Close button. 1. TME 10 adds the Office97 profile manager in the PC Apps subregion. Double-click on the Office97 icon to display the Profile Manager window. Create an AutoPack profile for each Windows operating system to which an AutoPack file will be distributed. Recall that an AutoPack file is created on the same operating system as the target machine to avoid file contention between different versions of Windows. In this scenario, you must create the Office97 - NT40 and Office97 - Win95 AutoPack profiles in order to distribute Office 97 to Windows NT and 95 machines Version 3.6

161 Creating an AutoPack Profile To create an AutoPack profile, select Profile... from the Create menu. The Create Profile dialog is displayed. In the Name/Icon Label field, enter the name of the profile and select AutoPack from the Type scrolling list. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 25

162 Creating an AutoPack Profile TME 10 displays the icon in the Profile Manager window. 1. In Creating FrameMaker File Packages on page 4-4, you created several platform-specific profile managers that represent each type of machine in the TMR. The same profile managers can subscribe to the Office97 profile manager to distribute to Windows machines in NoonTide s network. Drag-and-drop the 95Machs and NTMachs profile managers from the Desktop Apps policy region to the Office97 profile manager. These profile managers contain NoonTide s Windows 95 and NT machines Version 3.6

163 Creating an AutoPack Profile The following icons are displayed in the Profile Manager window. Software Deployment Using AutoPacks Later, you can distribute an AutoPack profile simply by dragging and dropping it onto its corresponding profile manager or on individual machines that subscribe to the Office97profile manager. 1. Set the AutoPack profile s source file. This example describes how to set profile properties for Office97 - NT40. Repeat this step to set AutoPack profile properties for the Office97 - Win95 AutoPack profile. TME 10 Software Distribution User s Guide 5 27

164 Creating an AutoPack Profile Double-click on the Office97 - NT40 AutoPack profile icon to display the Set AutoPack Properties window. Complete the following steps: a. In the Managed Node field, specify the managed node where the source file (the AutoPack file) will reside once it is copied from the prep machine ladybug. a. Enter the full path and file name where you want the AutoPack file to reside in the Path field. This path and file name do not have to match the path and file name of the AutoPack file on the prep machine Version 3.6

165 Distributing Office 97 a. Because you are copying the AutoPack file from ladybug, a PC managed node, select the Copy file from PC managed node radio button. This enables the bottom half of the dialog, as follows: Software Deployment Using AutoPacks Distributing Office 97 a. In the PC Managed Node field, enter ladybug, which is the name of the prep machine on which you created the AutoPack file. a. In the Path field, enter the path to the AutoPack file, C:/temp/officeNT4.pak. Note that you must specify the drive and full path to the.pak file. a. Press the Save & Close button to save the profile and return to the Profile Manager window. TME 10 copies the officent4.pak file from the prep machine, ladybug, to the pescado managed node. After creating the Office97 - NT40 profile, you can distribute it to all Windows NT subscribers. Distributing an AutoPack installs the software and makes the necessary system configuration changes on the TME 10 Software Distribution User s Guide 5 29

166 Distributing Office 97 target machine. Either drag an AutoPack profile and drop it onto the corresponding profile manager, or distribute an AutoPack profile using the Distribute AutoPack dialog. 1. In the Office97 profile manager, distribute the Office97 - WinNT AutoPack profile by dragging and dropping it onto the NTMachs. OR Select Distribute... from the Office97-NT40 AutoPack profile icon menu to display the Distribute AutoPack dialog. All of the profile managers that are subscribed to the Office97 profile manager are listed in the Available Subscribers scrolling list. The plus sign (+) indicates that the listed subscriber is a profile manager. By double-clicking on the profile manager name, you can expand the list to view all subscribers to this profile manager. 1. Expand the NTMachs profile manager and move Windows NT machines to the Distribute AutoPack To scrolling list. diamond, electron, lapis, and pearl are Windows NT 4.0 machines in the NoonTide environment and, therefore, will get the current version of Microsoft Office 97 (see Network 5 30 Version 3.6

167 Architecture on page 3-4 for machine configuration information). Distributing Office 97 Note that the managed resource type for each subscribing machine is listed next to the machine name. In this example all subscribers to the NTMachs profile manager are managed nodes and show (MN) as the object type. 1. To distribute the Office97-NT40 AutoPack profile to these machines, press the Distribute & Close button. Software Deployment Using AutoPacks TME 10 Software Distribution User s Guide 5 31

168 Distributing Office 97 TME 10 Software Distribution sends the AutoPack profile to each specified target machine. On each client system, in turn, the AutoPack agent works with the lcfd on endpoints and the PC agent on PC managed nodes to unpack and install the AutoPack profile. When an AutoPack profile arrives on the client, the following steps generally take place: On endpoints, the lcfd and fps_install method parse the AutoPack file that was created by the AutoPack Control Center, install the program files into the directories specified, and load system files into a temporary staging area. OR On PC managed nodes, the PC agent parses the AutoPack file, installs the program files into the directories specified, and loads system files into a temporary staging area. The AutoPack agent then transfers the system files from the staging area, installs the system files into the exact locations specified by the AutoPack file, and applies system changes specified in the.chg file, such as updating.ini files or registry items. Having distributed each AutoPack profile to all PCs in the NoonTide enterprise, Microsoft Office 97 is ready for use Version 3.6

169 III Performing Software Distribution Operations This section contains chapters that detail procedures create and distribute TME 10 Software Distribution profiles. The chapters also contain conceptual and instructional information about file packages, AutoPacks, and configuration programs. Use these chapters to fully learn about available options on the Software Distribution dialogs as well as about command line syntax and usage. Chapter 6 Profile Setup Creating a Software Distribution Profile Desktop Command Line Cloning a Profile Desktop Command Line Setting the Profile Subscribers Drag and Drop Desktop Command Line Deleting a Profile Desktop Command Line Chapter 7 File Package Properties Defining and Editing File Package Properties Desktop Command Line Exporting and Importing File Package Definitions TME 10 Software Distribution User s Guide

170 Performing Software Distribution Operations Desktop Command Line Creating File Packages from an Application Management Package Invoking the winstruct_file Command Distributing the Application Chapter 8 File Package Options Configuration Programs Before Program After Program Removal Program After Removal Program Commit Program On Error Program Input Files Multiple Configuration Programs and Input Files Return Status of Configuration Programs Running Configuration Programs in the Background Processing Arguments to Configuration Programs Encoding and Decoding Distribution Data Setting UNIX File Package Options Desktop Command Line Setting NetWare File Package Options Desktop Command Line Setting PC File Package Options Desktop Command Line Version 3.6

171 Performing Software Distribution Operations Chapter 9 File Package Operations Distributing a File Package Drag and Drop Desktop Command Line Calculating the Size of a File Package Desktop Command Line Pulling a File Package Removing a File Package Desktop Command Line Setting Timeout Values for a Distribution Configuration Script Timeout Repeater Manager Timeout High-level TCP Timeout Gateway Session Timeout Distribution Processes Distributing File Packages Distributing Nested File Packages First Chapter 10 AutoPack Properties and Operations Setting AutoPack Profile Properties Calculating the Size of an AutoPack Distributing an AutoPack Profile Drag and Drop Desktop Command Line Removing an AutoPack TME 10 Software Distribution User s Guide

172 Performing Software Distribution Operations Version 3.6

173 6 6Profile Setup AutoPacks are supported only on Windowbased PCs. Before using TME 10 Software Distribution to deploy software, you must create file packages and AutoPack profiles to house the application or data to be distributed. Creating a Software Distribution profile only creates the object in which data to be distributed is defined. You must also set the subscribers that will receive the distribution. This chapter includes procedures for creating, cloning, and deleting profiles, as well as for setting profile subscribers. Once you perform these procedures, you can define the contents of a file package and an AutoPack. Chapter 7, File Package Properties and Chapter 10, AutoPack Properties and Operations fully describe the procedures needed to create, define, and distribute files packages and AutoPacks. TME 10 supports file packages and AutoPacks only in the context of profile managers. Therefore, you must perform all tasks that involve setting up these profiles (such as creating, cloning, or moving) in a profile manager. For more information on creating and using profiles and profile managers, see the TME 10 Framework User s Guide. Profile Setup Creating a Software Distribution Profile To distribute software and data, you must create a Software Distribution profile to represent the application or files. Software Distribution provides two profiles: the file package and the AutoPack. You can create these profiles from within a profile manager. TME 10 Software Distribution User s Guide 6 1

174 Creating a Software Distribution Profile The following table shows the context and authorization role required to perform this task. Operation Context Required Role Create a file package or AutoPack Profile manager senior or super Desktop You can perform this task from the TME 10 desktop or from the command line. Use the following steps to create a Software Distribution profile from the desktop: 1. Add the AutoPack, FilePackage, and ProfileManager resources to the policy region s list of managed resources. Create a profile manager in which the profile will reside. For the purposes of the procedures in this chapter, all profile managers are created in the dataless mode by enabling the Dataless Endpoint Mode radio button on the Create Profile Manager dialog: For instructions on adding resource types to and creating dataless mode or database mode profile managers in a policy region, see the TME 10 Framework User s Guide. 6 2 Version 3.6

175 Creating a Software Distribution Profile 1. From a policy region, double-click on a profile manager icon to display the Profile Manager window. Profile Setup TME 10 Software Distribution User s Guide 6 3

176 Creating a Software Distribution Profile 1. Select Profile... from the Create menu in the Profile Manager window to display the Create Profile dialog. 1. Enter a unique name for the profile in the Name/Icon Label field that describes the file package or AutoPack. Tivoli recommends that you avoid using characters other than alphanumeric characters, a dash (-), an underscore (_), and the caret symbol (^). Also, the profile name must not exceed 32 characters. If you intend to create profiles for different versions of a software package, Tivoli recommends that you include the name and version of the file package, separated by a caret (^), in the profile name. For example, you could create profiles with the following names to represent different versions of the PS_docs file package: PS_docs^1.0 PS_docs^2.5 PS_docs^2.6 Using this format enables UserLink for TME 10 Software Distribution to distinguish between multiple versions of the same file package. 1. Select AutoPack or FilePackage from the Type scrolling list. 6 4 Version 3.6

177 Creating a Software Distribution Profile Note: If either resource type is not available, you must add it as a managed resource of your policy region. For more information on this procedure, see the TME 10 Framework User s Guide. 1. Press the Create & Close button to create the new profile and return to the Profile Manager window. An icon representing the newly-created file package (PS_docs^2.6) or AutoPack (Lotus_Notes^4.5) is displayed in the Profile Manager window. Profile Setup Command Line Because profiles must reside in a profile manager, you must create a policy region and profile manager in which to create the file package or AutoPack. To create policy regions and profile managers, see the TME 10 Framework Reference Manual for information on the wcrtpr, wcrtprfmgr, and wsetpm commands. TME 10 Software Distribution User s Guide 6 5

178 Cloning a Profile Cloning a Profile To use the command line to create the PS_docs^2.6 file package profile in the Source profile manager, enter the following command: FilePackage PS_docs^2.6 Creates the file package in the Source profile manager. FilePackage Creates a file package. PS_docs^2.6 Specifies PS_docs^2.6 as the name of the file package. To create the Lotus_Notes^4.5 AutoPack profile in the Source profile manager, enter the following command: AutoPack Lotus_Notes^4.5 Creates the AutoPack in the Source profile manager. AutoPack Creates an AutoPack. Lotus_Notes^4.5 Specifies Lotus_Notes^4.5 as the name of the AutoPack. For information about the wcrtprf command, see the TME 10 Framework Reference Manual. You can make an exact copy (except for the name) of a file package or AutoPack by cloning it. This feature is especially useful if you have multiple applications with similar properties. Note that cloning a Software Distribution profile differs from cloning other TME 10 application profiles. Other profiles distribute descriptions used to create accounts and system monitors. Only the policy and distribution defaults are copied to the cloned profile, not the actual profile records. However, Software Distribution profiles include 6 6 Version 3.6

179 Cloning a Profile information about, and paths to, data that will be distributed from one location to another. Cloning a file package or AutoPack copies all information pertaining to this data. Because Software Distribution policy is not profile-based, it is not copied to the new profile. Note: In addition to policy, file package attributes are not copied to new file packages set file package attributes using the wsetfpattr command. However, the src_host attribute is copied. The following table shows the context and authorization role required to perform this task: Operation Context Required Role Clone a profile Profile manager senior or super You can perform this task from the TME 10 desktop or from the command line. Profile Setup TME 10 Software Distribution User s Guide 6 7

180 Cloning a Profile Desktop Use the following steps to clone a file package or AutoPack: 1. From a policy region, double-click on a profile manager icon to display the Profile Manager window. 1. Single-click on the profile to be cloned and select Profiles -> Clone... from the Edit menu to display the Clone Profile dialog. Enter the name for the new profile in the Name/Icon Label field. Also, select the profile manager in which the new profile will reside. 6 8 Version 3.6

181 Cloning a Profile 1. Press the Clone & Close button to create the cloned profile and return to the Profile Manager window. Software Distribution displays the icon of the new profile. Profile Setup TME 10 Software Distribution User s Guide 6 9

182 Cloning a Profile Command Line To use the wcrtprf command to clone the PS_docs^2.6 file package, which creates a similar file package that can be modified and used to distribute Version 3.0 of the Postscript documentation, enter the following command: \ FilePackage PS_docs^3.0 where: Clones the PS_docs^2.6 file package. You must when specifying the file package Specifies the Source profile manager to contain the new file package. FilePackage Specifies the type of profile to clone. PS_docs^3.0 Specifies the name of the file package as PS_docs^3.0. Do not use an object path (/Regions/...) or a registered name (@name) here. Simply specify the new name. To clone the Lotus_Notes^4.5 AutoPack, enter the following command: AutoPack Lotus_Notes^4.6 where: Clones the Lotus_Notes^4.5 AutoPack. You must when specifying the AutoPack Specifies the Source profile manager to contain the new AutoPack. AutoPack Specifies the type of profile to clone Version 3.6

183 Setting the Profile Subscribers Lotus_Notes^4.6 Specifies the name of the AutoPack as Lotus_Notes^4.6. Do not use an object path (/Regions/...) or a registered name (@name) here. Simply specify the new name. For more information about using the command line to clone profiles, see the wcrtprf command in the TME 10 Framework Reference Manual. Setting the Profile Subscribers Before you can perform a profile operation, you must set the subscribers (the profile managers, endpoints, managed nodes, PC managed nodes, and NetWare managed sites to which it distributes) for the profile manager in which the profile resides. Although the following procedures use a dataless endpoint mode profile manager to illustrate how to set profile subscribers, these steps also apply for setting subscribers in the database mode. All managed nodes, endpoints, PC managed nodes, and NetWare managed sites can subscribe to a dataless profile manager. Profile managers, however, can only subscribe to database profile managers. See the TME 10 Framework User s Guide for mode information about database mode and dataless mode profile managers. The following table shows the context and authorization role required to perform this task: Operation Context Required Role Subscribe resources to a profile manager Profile manager senior or super Profile Setup Drag and Drop You can perform this task using drag and drop, from the TME 10 desktop, or from the command line. To subscribe a profile manager, endpoint, managed node, PC managed node, or NetWare managed site to a profile manager, drag and drop its TME 10 Software Distribution User s Guide 6 11

184 Setting the Profile Subscribers Desktop icon onto the icon of the profile manager containing the profile to be distributed. This icon is added in the Subscribers area of the Profile Manager window. Use the following steps to add subscribers to the profile manager: 1. From a policy region, double-click on a profile manager icon to display its Profile Manager window Version 3.6

185 Setting the Profile Subscribers 1. Select Subscribers... from the Profile Manager menu to display the Subscribers dialog. 1. Select a subscriber from the Available to become Subscribers scrolling list and press the left arrow button to move the subscriber to the Current Subscribers scrolling list. To remove subscribers from the profile manager, remove them from the Current Subscribers scrolling list by selecting the subscriber and pressing the right arrow button. 1. Press the Set Subscriptions & Close button to set the new subscriptions and return to the Profile Manager window. The Profile Setup TME 10 Software Distribution User s Guide 6 13

186 Setting the Profile Subscribers modified subscriptions are added to the profile manager s list of subscribers Version 3.6

187 Setting the Profile Subscribers Note: If you remove a resource from a subscriber list, the Unsubscribe Subscribers displays the following dialog: The message in the Unsubscribe Subscribers dialog does not apply to file packages because Software Distribution does not stop a distribution at a subscribing profile manager or the next level of subscribers. Press the Unsubscribe button to unsubscribe and return to the Profile Manager window. Command Line To use the wsub command to add the balder endpoint as a subscriber to the Source profile manager, enter the following Specifies the profile manager to which to Subscribes the balder endpoint to the specified Source profile manager. For more information about the wsub command, see the TME 10 Framework Reference Manual. Profile Setup TME 10 Software Distribution User s Guide 6 15

188 Deleting a Profile Deleting a Profile When you delete a file package or AutoPack, it is removed from the TME 10 database and its icon is removed from the profile manager. Deleting a profile does not delete the source files or directories or the distributed files or directories on the subscribers. Note: If you delete a file package or AutoPack for which you have scheduled a distribution, removal, or commit operation, you must delete the job from the Scheduler. Deleting a profile does not automatically delete the job. See the TME 10 Framework User s Guide for more information on using the Scheduler. You can also remove previously distributed file packages and AutoPacks from targets. This operation is the opposite of a distribution. However, it does not remove the original file package, AutoPack, or source files. See Removing a File Package on page 9-16 for more information about deleting profiles from subscribers. The following table shows the context and role required to delete a profile: Operation Context Required Role Delete a profile from a subscriber Profile manager senior or super You can perform this task using the TME 10 desktop or the command line Version 3.6

189 Deleting a Profile Desktop Use the following steps to delete a file package or AutoPack: 1. From a profile manager, select the profile icons to delete and select Profiles -> Delete... from the Edit menu to display the Delete Profiles dialog. This dialog prompts you to confirm the deletion. Note: You cannot recover a deleted profile. The message in the Delete Profiles dialog does not apply to file packages or AutoPacks because Software Distribution does not let you stop a distribution at a subscribing profile manager and the next level of subscribers. Command Line 1. To confirm the deletion, select the Delete button. Software Distribution deletes the profile and displays the profile manager without it. To use the wdel command to delete the PS_docs^2.6 file package and remove its icon from the profile manager, enter the following command: Profile Setup wdel /Regions/"Software Distribution"/Source/PS_docs^2.6 where: /Regions/"Software Distribution"/Source/PS_docs^2.6 Specifies the object path of the file package to delete. You can specify object paths or registered names of TME 10 objects such as profiles and profile managers. TME 10 Software Distribution User s Guide 6 17

190 Deleting a Profile For more information about the wdel command, see the TME 10 Framework Reference Manual Version 3.6

191 7 7File Package Properties File Package Properties After creating a file package profile, as described in Creating a Software Distribution Profile in Chapter 6, you must set file package properties for each file package to specify information about the software or data that will be distributed. TME 10 Software Distribution enables you to set file package properties using the TME 10 desktop, the command line, or by exporting and importing files. File package properties define the following information about the file package that you are sending: Source host from which the source files and directories are distributed. Destination directory to which all files are distributed. Files, directories, and other file packages to be distributed. General options, including whether to append the entire source path to a destination path, whether to stop the distribution if an error occurs, whether to descend into directories at the source, and whether to compress the data before it is distributed to the targets. File mode at the destination. Log information and notification behavior about the file package distribution. Platform-specific options to handle symbolic links, user and group ownership of files on the UNIX platform, and options to run programs at selected points in the distribution process for TME 10 Software Distribution User s Guide 7 1

192 Defining and Editing File Package Properties each target platform. These options allow you to define different distribution behavior for different platforms. In addition, you can include a description of the software in the file package and change its name in the File Package Name field. After specifying the file package properties, you can distribute it to the target subscribers. Distributing the file package copies the files and directories from the source host to the specified destination directory on each target subscriber. The files and directories on the target subscribers will have the same owner, group membership, mode, and modification time as the corresponding files and directories on the source host (unless specified otherwise). Defining and Editing File Package Properties A File Package Properties window shows a file package with any pre-set policy region defaults. From this window you can set options and add files, directories, and file packages to make up the contents of the file package. The following procedure describes in detail how to set each of the properties and options on the dialog. The following table shows the context and authorization role needed for this task: Operation Context Required Role Set or edit file package properties File package admin, senior or super You can perform this task from the TME 10 desktop, from the command line, or by using the export and import capabilities. 7 2 Version 3.6

193 Desktop Defining and Editing File Package Properties Use the following steps to define a file package: 1. From a policy region, double-click on a profile manager icon to display the Profile Manager window. File Package Properties TME 10 Software Distribution User s Guide 7 3

194 Defining and Editing File Package Properties 1. Double-click on a file package icon to display the File Package Properties window. The File Package Properties window shows the file package name, the files, directories, and nested file packages to be included, as well as the current file package option settings. The option settings displayed in this window are the default file package properties. 7 4 Version 3.6

195 Defining and Editing File Package Properties 1. Add optional information about the file package using the following steps: a. From the File Package Properties window, select Optional Information... from the Edit menu to display the Edit Optional Information dialog. File Package Properties a. Use the text fields to add any descriptive information related to the file package. To track information not listed in the Edit Optional Information dialog, you can add additional fields to the dialog using the TME 10 Application Extension Facility (AEF). See the TME 10 AEF User s Guide for more information on customizing dialogs. a. Press the Set & Close button to save the changes and return to the File Package Properties window. TME 10 Software Distribution User s Guide 7 5

196 Defining and Editing File Package Properties You do not need to specify a source host if your file package contains only nested file packages. 1. Set the source host of the file package. The Source Host... field displays the name of the managed node on which the file package source files reside. The machine you specify as the source host must be a managed node in the TMR. In the Source Host... field, enter the name of the host on which the file package s source files reside. OR Press the Source Host... button to display the Select Source Host browser dialog containing a list of available managed nodes. Complete the following steps to select the source host: a. Select a source host from the Hosts list. a. Press the Select & Close button to select the host and return to the File Package Properties window. See the TME 10 Framework User s Guide for additional information on using browser dialogs such as the Select Source Host dialog. 7 6 Version 3.6

197 Defining and Editing File Package Properties Also, to understand how database consistency is affected when you delete or change the name of a host that is a source host for a file package, see the TME 10 Software Distribution Reference Manual. 1. Add the directories and files to be distributed to the Source Directories & Files scrolling list. A file package entry in this field can be any of the following: The path of a file. Directories and file names may contain wildcard characters. The supported wildcard characters are similar to that of the Bourne shell, such as the following characters: * Matches any string, including the null string.? Matches any single character. [...] Matches any one of the enclosed characters. Also, a backslash (\) may be used as a directory delimiter in the path of a file name. The path of a directory. TME 10 Software Distribution distributes the directory and its contents if the Descend into directories check box is selected in the General Options section. If you wish to distribute all contents of the /tmp/hpux directory but do not want hpux added to the destination path, specify /tmp/hpux/ as the source directory (with the trailing slash). Finally, if you do not select the Descend into directories option, only the directory is distributed. Note: TME 10 Software Distribution supports the UNIX /. path name convention, which specifies that all contents of the directory are to be included, only if you select the Descend into directories check box during the distribution. A command to execute at distribution. You can use an imported file package definition to define a command in this manner. The command must be enclosed in grave accents (`), such as `find /source/bin/hpux -type f -print`. File Package Properties TME 10 Software Distribution User s Guide 7 7

198 Defining and Editing File Package Properties Note that you can specify a value for the src_relpath keyword to set a relative path to source host files and directories. Software Distribution adds the path specified by this keyword to the beginning of the program paths or of the input files. Set the src_relpath keyword by editing the file package definition file or by setting the S option to the wsetfpopts command. See the TME 10 Software Distribution Reference Manual for more information about setting keywords. When specifying source files or directories, you can specify one or more options for each. Options affect the file name, directory name, or shell command for which they are specified and alter the way the file or directory is processed. The options are as follows: d g G m M o s t u U Specifies the destination path and overrides the value for both the default_dest and xxx_platform_prefix keywords. The last path component from the source path is concatenated to the destination path to form the path. If the source is a directory, all paths in the hierarchy are also modified. Specifies the file GID as a name or number. Specifies the directory GID as a name or number. Specifies the file chmod options, in octal values only. Specifies the directory chmod options, in octal values only. Specifies whether to descend into directories and override the descend_dirs keyword. Valid values are descend and nodescend. Overrides the src_relpath keyword and specifies a path on the source host from which to obtain the file and directory. Sets the modification time given in the format of the date command. Specifies the file UID as a name or number. Specifies the directory UID as a name or number. 7 8 Version 3.6

199 Defining and Editing File Package Properties Specify an option in the following format after the file name, directory path, or shell command: option=value Do not include spaces around the equal sign (=). List all options on the same line. For example, suppose you specify the following options in the file package definition: File Package Properties /etc/hosts d=/usr/safe /etc/passwd d=/tmp README.txt s=/usr/local d=/etc If you have specified the following keywords in the keywords section of the file package definition: default_dest=/ keep_paths=n src_relpath=/ the README.txt file is obtained from the /usr/local directory and the specified files are distributed as follows: /usr/safe/hosts /tmp/passwd /etc/readme.txt In addition, the following examples are valid entries: /etc/passwd d=/backups/etc u=root /bin/miscdir U=201 G=30 o=descend /bin/file_ex t= m=0600 Software Distribution does not immediately verify the existence of the file and directory paths included in the file package. Rather, specified files and directories are verified when the file package is distributed. If the paths are not valid at distribution time, Software Distribution stops the distribution if the Stop distribution on error option is enabled or continues the distribution if this option is disabled. (Set the Stop distribution on error option when you specify a before configuration program.) TME 10 Software Distribution User s Guide 7 9

200 Defining and Editing File Package Properties Notes: All file and directory entries should be full paths (not relative paths), unless you have specified the src_relpath keyword. Specify paths using forward slashes (/), regardless if the file or directory resides on a PC. Use double quotation marks ( ) around any entry that contains embedded spaces or an equal sign (=). You cannot specify an option in conjunction with an entry that contains a wildcard character. Because some PCs limit file names to eight characters and file name extensions to three characters, you must specify all files that will be distributed or processed on a PC target in this format. If you specify a file to be distributed or removed whose name is too long, Software Distribution will truncate the file name on the PC target. Environment variables are not allowed. You cannot include a file or directory named TRAILER!!! in the file package, because this is the POSIX-compliant cpio end-of-archive file marker. See the TME 10 Software Distribution Reference Manual for more information about valid conventions for adding files and directories to the file package definition list Version 3.6

201 Defining and Editing File Package Properties To add a file, directory, or command to the list, type the entry in the text field below the Directories & Files... button and press the Return key. The file, directory, or command is added to the scrolling list. OR Press the Directories & Files... button to display the Select Directories & Files dialog. File Package Properties The Select Directories & Files dialog provides a view of the directory structure on the source host. Using this browser dialog, you can select directories and files to add to a file package. To add a directory or file using this dialog, complete the following steps: a. Double-click on the directory name in the Directories scrolling list to list the files and directories contained in that directory. Repeat this step until you find the desired directory. a. Select a file from the Files scrolling list. TME 10 Software Distribution User s Guide 7 11

202 Defining and Editing File Package Properties a. Press the Select & Close button to add the file to the file package, close the Select Directories & Files dialog, and return to the File Package Properties window. The entries in the Source Directories & Files field are distributed in the order in which they appear in the list (top to bottom). Once you have added files and directories to a file package, you may want to change the distribution order or remove a selection. - To change the order of distribution, select an entry and use the up or down arrow buttons to change its location in the list. If you select multiple entries, they are moved as a group (maintaining their original order in relation to each other) above the item that appeared highest (if moving up) or below the item that appeared lowest (if moving down) in the list. - To remove files or directories from the list, select one or more entries and press the Remove button. 1. Add nested file packages to the Nested File Packages scrolling list. You can only nest file packages that reside in policy regions in which you have at least the admin authorization role. You cannot create a circular nest (for example, package FP1 includes package FP2, which includes FP1). Drag and drop a file package icon onto another to nest a file package. This action adds the first file package as a nested file package entry to the second. The nested file package name is added to the bottom of the file package s Nested File Package scrolling list. To add a nested file package to the current file package from the desktop, input the name of the file package in the text field below the File Packages... button and press the Return key. The file package is added to the Nested File Packages scrolling list. OR 7 12 Version 3.6

203 Defining and Editing File Package Properties Press the File Packages... button to display the Select File Packages dialog. This dialog provides a list of the file packages available in TME 10. Note that all file packages, including those that reside in other profile managers, are available. See the TME 10 Framework User s Guide for additional information on using file browser dialogs such as the Select Directories & Files dialog. The file packages you select are displayed in the Nested File Packages scrolling list on the File Package Properties window. By default, nested file packages are processed after the parent file package. See the nested_first keyword in the TME 10 Software Distribution Reference Manual for information about processing a nested file package before its parent. See Distribution Processes on page 9-27 for an example distribution of a file package with this keyword set. The entries in the Nested File Packages scrolling list are arranged in order of distribution (top to bottom). Once you add nested file packages, you may want to change the distribution order or remove a selection. To change the order of distribution, select an entry and use the up or down arrow buttons to change its location in the list. If you select multiple entries, these move as a group (maintaining their original order in relation to each other) above the item that appeared highest (if moving up) or below the item that appeared lowest (if moving down) on the list. To remove nested file package entries, select one or more entries from the list and press the Remove button. Note: You can only add 50 levels of nested directories to a file package. To understand how database consistency is affected when you delete or change the name of a nested file package, see the TME 10 Software Distribution Reference Manual. File Package Properties TME 10 Software Distribution User s Guide 7 13

204 Defining and Editing File Package Properties 1. Use the General Options check boxes to select miscellaneous distribution characteristics of the file package. Select the Stop distribution on error check box to immediately stop distribution to a target if an error occurs (the distribution continues for other targets). If you do not select this box, errors are logged as specified in the Log Information Options section and the distribution continues, if possible. Select the Descend into directories check box to distribute all subdirectories and files in a source directory. The hierarchy of the directories in the source directory is distributed to the remote directory. If you do not select this box, an empty directory (of this name) is created on the target machines if a directory by that name does not already exist. If you select the Descend into directories check box, no directory included in the file package can have more than 50 levels of subdirectories. If so, you must change the file package so that this option is not specified and explicitly add entries for all the files and directories in the hierarchy. For example, suppose you want to distribute the /source/bin/hpux directory, which contains the f1 file, the f2 file, and the dir1 directory (containing the f3 file). If you select this option and distribute the /source/bin/hpux directory to the /tmp directory, the files are copied to the target machines, resulting in the following hierarchy: /tmp/hpux/f1 /tmp/hpux/f2 /tmp/hpux/dir/f3 If you do not select the Descend into directories check box, the /tmp/hpux directory is created but it is empty Version 3.6

205 Defining and Editing File Package Properties Note: If you wish to distribute the files in a directory but not the subdirectories, deselect this option and specify the source directory as follows: /tmp/hpux/*. If you wish to distribute all contents of the /tmp/hpux directory but do not want hpux added to the destination path, specify /tmp/hpux/ as the source directory. Select the Append source path to remote path check box to append the full path of each source file or directory to the remote path during distribution. If you do not check this box, only the directory or file name is added to the remote path. Continuing with the previous example, suppose you select this option and distribute the /source/bin/hpux directory to the /tmp directory on the targets. The files are copied to the target machines, resulting in the following hierarchy: /tmp/source/bin/hpux/f1 /tmp/source/bin/hpux/f2 /tmp/source/bin/hpux/dir/f3 If you do not select the Append source path to remote path check box, the files are copied to the target machines, resulting in the following hierarchy: /tmp/hpux/f1 /tmp/hpux/f2 /tmp/hpux/dir/f3 Select the Perform compression on distribution check box to compress the data in a file package before distributing it. In general, compressing data is a good idea because it saves enterprise bandwidth when distributing. The data is uncompressed once it reaches the target. If you do not select this box, Software Distribution does not compress the data before distributing the file package. Note: This option causes Software Distribution to distribute the file package data in compressed format. The source files, however, are not modified. File Package Properties TME 10 Software Distribution User s Guide 7 15

206 Defining and Editing File Package Properties 1. Use the File Mode at Destinations options to control the file permissions given to distributed files on the targets. Press the Preserve mode of source files radio button to set the file permissions at each target to those of the source files. Note: If you press the Preserve mode of source files radio button with an entry in the chmod options field, the field is cleared. Press the Change mode of source files to radio button to change the permissions of the file package files on each target. If you check this option, you must specify a valid chmod octal option in the chmod options field. Software Distribution supports only the absolute octal mode for the chmod command. See your operating system s chmod manual page for more information. Note: For distribution to PCs, the only valid chmod values are r (4) and rw (6). 1. Use the Log Information Options check boxes to control the TME 10 Software Distribution logging activity. In addition to these logging options, information is logged if you install and configure the TME 10 Enterprise Console integration product provided with Software Distribution. See Chapter 13, TEC Integration for more information. Use the following options to configure information logging. A report of the success or failure of the file package operation is available using all three options. However, specific information about errors encountered during an operation is only available in the log file. Tivoli suggests that you always specify a log file. Select the Send to Software Distribution notice group check box to have Software Distribution post a notice, including an indication of success or failure of the operation for each target, to the Software Distribution notice group when a file package operation occurs. You must subscribe to the Software Distribution notice group to view the notices. Select the Send to check box to have Software Distribution send , including an indication of success 7 16 Version 3.6

207 Defining and Editing File Package Properties or failure of the operation for each target, to the specified address when a file package operation occurs. You must enter a mail path or an alias that is valid on the TMR server of the TMR in which the file package was created. See the TME 10 Framework Planning and Installation Guide for more information about configuring in your TMR environment. You can specify more than one mail path or alias, separated by commas. Select the Send to log file on check box to have Software Distribution place log information in the specified file when a file package operation occurs. An entry is made to the log each time a file package is distributed, committed, or removed. Log information in the log file includes the following information: - Problems encountered at the source host, such as files not found. - Subscribers that were down during the distribution. - Return status of before, after, removal, after removal, commit, and on error (configuration) programs. This return status as reported in the log file is not the same as the exit status of the program. See the TME 10 Software Distribution Reference Manual for an explanation of return codes for configuration programs. - New directories created as a result of distribution. - An indication of the success or failure of each target. To send information to a log file, complete the following steps: - Type a host name in the text field beside the Host... button on which the log file is located. You can also press File Package Properties TME 10 Software Distribution User s Guide 7 17

208 Defining and Editing File Package Properties the Host... button to display the Select Log Host browser dialog. The log file must be on a managed node. If you do not specify a host, the TMR server is assumed Version 3.6

209 Defining and Editing File Package Properties - In the Path... field, type the full path to the log file or press the Path... button to display the Select Log File dialog. File Package Properties By default, Software Distribution overwrites the log file for each distribution of the file package. To append to the log file, use the a argument of the wsetfpopts command. See Command Line on page 7-20 and the TME 10 Software Distribution Reference Manual for more information on setting the append_log keyword with this command. For information on how database consistency is affected when you delete or change the name of a machine that is a log host, see the TME 10 Software Distribution Reference Manual. 1. Save the file package. Select Save from the File Package menu to apply all options set on the File Package Properties window, platform-specific dialogs, and other intermediate dialogs. If you use Reset from the Edit menu, the settings on the File Package Properties window, platform-specific dialogs, and all other intermediate dialogs will revert to their last saved values. TME 10 Software Distribution User s Guide 7 19

210 Defining and Editing File Package Properties Command Line If you import a file package definition from the File Package menu, those changes are automatically saved. 1. Select Close from the File Package menu to return to the Profile Manager window. Use the wsetfpcontents command to set other file package properties in addition to those set using the desktop. See the TME 10 Software Distribution Reference Manual for a complete list of available file package property options. To set the source host and source directories and files for the HP_bin file package, enter the following command: wsetfpcontents -F where: Changes the source host to pescado. F /source/flists/hp_bin Sets the source directories and files to those listed in the /source/flists/hp_bin Specifies the file package to modify. To use the wsetfpopts command to specify /app/install/sourcefiles/ as the source directory for all relative paths used in the file package definition, enter the following command: wsetfpopts -T unix -S where: T unix Sets the option for all UNIX-specific file packages. S /app/install/sourcefiles/ Specifies the source directory that is assigned to the src_relpath keyword in the file package definition Specifies the file package to modify Version 3.6

211 Exporting and Importing File Package Definitions To use the wsetfpopts command to append messages to the /logfiles/wordprocess.hp log file, descend into directories during distribution, and post notices to the Software Distribution notice group for the HP_bin file package, enter the following command: wsetfpopts -T gen -a y -d y \ -L /logfiles/wordprocess.hp -P where: T gen Enables you to use keywords that are not platform-specific on the command line. a y Specifies to append information to the log file. d y Specifies to descend into the source directory and distribute all contained directories and files. Sets the log host to pescado. L /logfiles/wordprocess.hp Specifies to log errors to the /logfiles/wordprocess.hp file. P y Posts any error, distribution, removal, or commit notices to the Software Distribution notice Specifies the file package to modify. File Package Properties For more information about using the command line to set file package properties, see the wsetfpcontents and wsetfpopts commands in the TME 10 Software Distribution Reference Manual. Exporting and Importing File Package Definitions In addition to using the TME 10 desktop or the command line to set file package properties, you can use the export and import capabilities to edit file package settings. This capability enables you to save the file package properties and options in a file called the file package definition. Using a text editor, you can set general and platform-specific properties that are available from the desktop and those that are not. You can then import the revised file package definition into a file package. TME 10 Software Distribution User s Guide 7 21

212 Exporting and Importing File Package Definitions The following are examples of situations for which the export and import features are particularly well-suited: If you want to create a file package containing an extensive list of files, you can add the file list to the file package definition file with a text editor, and import it into Software Distribution. This is generally faster and easier than using the dialogs. If you want to create several file packages with similar properties and contents, you can use one file package definition as a template for creating the others, and import the completed descriptions into Software Distribution. If you must provide a copy of file package definitions to your software providers, who in turn can supply the descriptions with software deliveries. If you need to set advanced features that are not available using the desktop. For information on data formats of the file package definition and for advanced features not available through the dialogs, see the TME 10 Software Distribution Reference Manual. The following table shows the context and authorization role required to perform this task: Operation Context Required Role Export a file package definition Import a file package definition File package File package user, admin, senior, or super admin, senior or super You can perform this task using the TME 10 desktop or the command line Version 3.6

213 Desktop Exporting and Importing File Package Definitions Use the steps on the following pages to export and import a file package definition. 1. From a Profile Manager window, double-click on a file package icon to display its File Package Properties window. File Package Properties TME 10 Software Distribution User s Guide 7 23

214 Exporting and Importing File Package Definitions 1. Select Export... from the File Package menu to display the Export File Package Definition dialog. If you export a file package to a directory, a new file is created that contains the file package definition. The Export File Package Definition dialog provides a view of the file systems on the managed nodes. You can traverse the file system hierarchy to view the files within directories and subdirectories using this browser dialog. a. Select the host machine and file to which to export and save the file package definition. You must have write permission to this file or directory. OR Specify a directory path and file name in the Set Path field. a. Press the Export & Close button to save the file and return to the File Package Properties dialog. Note: You must press the Export or the Export & Close button to save the exported text file. Using the Return key to execute this operation will result in an error. 1. Edit the file package definition using a text editor Version 3.6

215 Exporting and Importing File Package Definitions 1. Select Import... from the File Package menu to display the Import File Package Definition dialog. File Package Properties The Import File Package Definition dialog provides a view of the directory structure on the managed nodes. You can traverse the file system hierarchy to view the files within directories and subdirectories using this browser dialog. The file that you select using this dialog is the file from which the file package definition is imported. You must have read permission to this file. TME 10 Software Distribution User s Guide 7 25

216 Exporting and Importing File Package Definitions Command Line To use the wexprtfp command to export the HP_bin file package definition to the HP_export.fp file on the managed node pescado, enter the following command. Note that the HP_export.fp file will be created if it is not already available. where: Saves the file package definition to the /tivoli/data/hp_bin/hp_export.fp file on managed node Specifies file package from which to export the file package definition. To use the wimprtfp command to import the HP_bin file package definition from the HP_import.fp file, enter the following command: where: Specifies the /tivoli/data/hp_bin/hp_import.fp file from which to import the file package definition on managed node specifies file package into which to import the file package definition. For more information about using the command line to export and import a file package definition, see the wexprtfp and wimprtfp commands in the TME 10 Software Distribution Reference Manual Version 3.6

217 Creating File Packages from an Application Management Package Creating File Packages from an Application Management Package TME 10 Software Distribution includes support for Version 2.0 of the Application Management Specification (AMS) standards. The AMS standard defines a syntax for data that describes how to manage the hardware and software components of a desktop environment. Tivoli provides AMS-compliant tools, such as the Tivoli Module Designer, to create an application management package (AMP), which is a compressed file that contains all the description files for an application. To automate the process of loading management data specified in an AMP, Tivoli has included the winstruct command set with TME 10. Using the winstruct command, you can quickly set up the TME 10 environment to distribute, install, monitor, and maintain applications. See the TME 10 Framework User s Guide for detailed information about application management packages or about the winstruct command. Within the winstruct command set, Software Distribution supports the winstruct_file subcommand to read and extract file package data in an AMP into a staging area. In most cases, you will not need to execute winstruct_file independently this command is designed to work in conjunction with the winstruct set of commands to manage data in an AMP file. However, running the complete sequence of winstruct commands can be a time-consuming operation. In such instances, you can create a file package from an AMP directly by running winstruct_file from the command line. File Package Properties Invoking the winstruct_file Command The following example demonstrates the sequence of operations that occur when you directly execute the winstruct_file command on an AMP. In this example, the Tivoli Module Designer is used to create the FrameMkr AMP, which contains the description files to install Adobe FrameMaker on Windows NT machines. Executing the winstruct_file command on this AMP enables Software Distribution to extract all the necessary file package information to distribute FrameMaker to Windows NT subscribers. TME 10 Software Distribution User s Guide 7 27

218 Creating File Packages from an Application Management Package The following table provides the authorization role required to perform this task: Operation Context Role Create a file package directly from an AMP file Command line senior You can perform this task only from the command line by entering: winstruct_file -a /applications/amps/framemkr.amp \ -s /install/staging -D comp_src_dir1=cdrom1 \ -D comp_src_dir2=/src/app/comp_files where: a /applications/amps/framemkr.amp Specifies the path and file name of an AMP. s /install/staging Specifies a directory into which the winstruct_file command extracts the contents of the AMP. D comp_src_dir1=cdrom1 D comp_src_dir2=/src/app/comp_files Specifies the name of an environment variable and its value. You can specify multiple variables, but you must enter D for each variable and value pair. This winstruct_file command performs the following operations: Extracts the contents of the FrameMkr AMP into the /install/staging directory and reads the.aof,.gdf, and.cdf description files. Labels the instruction process with a unique version identifier that distinguishes this version of the AMP from other versions. You can specify a version identifier (also called an administrator tag) with the t argument on the winstruct_file command line. Since no administrator tag is specified with the t argument in this example, winstruct will supply Default for the tag string. Checks the Management Tool Extension group (an AMS group) for variable=value pairs and command line arguments for each 7 28 Version 3.6

219 Creating File Packages from an Application Management Package component in the AMP. This data determines the source directory (or directories) for the application files. The above winstruct_file syntax uses multiple D arguments to specify the location of the source files that make up a management-ready application. You can specify multiple variable and value pairs, but you must enter D for each pair. In this example, the winstruct_file command executes the following series of operations in the TMR to extract file package information from FrameMkr.amp: Creates the Applications policy region on the TME 10 desktop when you issue the command the first time. In this example, the name of the icon is Applications_pescado-region, where pescado-region is the name of the Tivoli Management Region (TMR). Each TMR has only one Applications policy region. Subsequent uses of any winstruct commands do not create additional Applications icons in a single TMR. Creates a unique secondary policy region for the imported FrameMaker application within the Applications policy region. The name of the icon in this example is PR_FrameMkr_Default_winnt_pescado-region, where FrameMkr and winnt are the application name and component name specified for the application when you create the AMP. Creates one or more profile managers within the secondary policy region that each contain a file package for distribution. In this example, the name of this icon is PM_FrameMkr_Default_winnt_pescado-region. Creates a file package in each profile manager to distribute application components. In this example, winstruct_file creates FP_FrameMkr_Default_winnt_pescado_region, which contains the file package description for installing FrameMaker on Windows NT machines. File Package Properties TME 10 Software Distribution User s Guide 7 29

220 Creating File Packages from an Application Management Package The following sequence of dialogs illustrates the series of icons that are created on the TME 10 desktop when you run this command: 7 30 Version 3.6

221 Creating File Packages from an Application Management Package Distributing the Application The winstruct_file command creates all the file package description files necessary to distribute and install FrameMaker. If you open the FP_FrameMkr_Default_winnt_pescado_region icon, the following File Package Properties dialog is displayed. File Package Properties The files listed in the Source Directories & Files field are extracted from the FrameMkr AMP. You can distribute this file package and all other components of the application as you would any other Software Distribution profile. In this example, the FrameMaker CD-ROM must be in your mounted drive, /cdrom. For instructions on how to distribute file packages, see Chapter 9, File Package Operations. TME 10 Software Distribution User s Guide 7 31

222 Creating File Packages from an Application Management Package 7 32 Version 3.6

223 8 8File Package Options TME 10 Software Distribution provides file package options to set platform-specific information for a file package. Setting these options enables you to control how the file package is distributed and installed on the subscriber. After you have created a file package and defined its properties, you must set these options for each platform type to which you will distribute the file package. See Chapter 7, File Package Properties, for information about defining properties for a file package. When setting file package options, you will define platform-specific options, including the following: Destination directory path, where the distributed files will reside on platform-specific subscribers User and group ownership of the distributed files on the subscribers Configuration programs to run before or after distributing a file package, before or after removing a file package, during a commit operation, or if an error stops a distribution or a removal operation Various other platform-specific settings, including symbolic link resolution on UNIX subscribers, content of messages broadcast to NetWare subscribers, and mandatory or optional installation settings on Windows and Windows 95 subscribers. File package options can be set from the TME 10 desktop or the command line. Keep in mind that setting platform-specific options is an intermediate step in defining the properties of the file package. File Package Options TME 10 Software Distribution User s Guide 8 1

224 Configuration Programs After setting these and all other options, you must then select Save from the File Package menu on the File Package Properties window to apply changes to the file package. This chapter describes how Software Distribution uses configuration programs to perform a variety of operations during a file package distribution. It also provides procedures to define and set platform-specific file package options for UNIX, NetWare, OS/2, Windows, Windows 95, and Windows NT systems. Configuration Programs TME 10 Software Distribution uses configuration programs during a distribution to perform preprocessing or postprocessing operations when a file package is installed, such as file manipulations manipulate or dependency checks. The format of available configuration programs depends on the platform type of the subscribing machine. Available configuration programs for UNIX subscribers can be any type of executable C program, shell script, Perl script, and so on. On NetWare machines, available configuration programs for NetWare subscribers can be NetWare loadable modules (NLMs) or.ncf files. And for PCs, available configuration programs can be.bat,.exe,.com, or.cmd (for OS/2 only) files. The following list specifies different types of configuration programs that are available for subscribers across platforms: Before programs enable you to run programs before Software Distribution places the data described in that file package on the subscriber. After programs enable you to run programs after Software Distribution places the data described in that file package on the subscriber. Removal programs enable you to run programs before Software Distribution removes the data described in that file package from the subscriber. After Removal programs enable you to run programs after Software Distribution removes the data described in that file package from the subscriber. 8 2 Version 3.6

225 Configuration Programs Commit programs enable you to run programs when Software Distribution performs a commit operation for the file package on the subscriber. On Error programs enable you to run programs if an error stops the distribution or removal operation on the subscriber. The before, after, (upon) removal, and commit programs run on the subscriber and are available using the desktop, the command line, and the export and import capabilities. The source before and source after program options are only available using export and import or from the command line to set the appropriate keywords (src_before_xxx and src_after_xxx). In addition, you cannot specify after removal or on error programs from the desktop. These configuration programs are available by setting the yyy_after_removal_xxx and yyy_on_error_xxx keywords, where yyy is a platform-specific prefix. See the TME 10 Software Distribution Reference Manual for detailed information on configuration program keywords, file package definition files, and example programs. Notes: Because PCs limit file names to eight characters and file name extensions to three characters, you must use this convention to specify all files that will be processed on a PC subscriber in this format. If you specify a configuration target program or input file whose name is too long, Software Distribution will return an error when it tries to run the program or process the file. On Windows machines, you cannot launch an executable from a batch (.BAT) file. Instead, you must use the wrunprog command. See the TME 10 Software Distribution Reference Manual for detailed information about this command File Package Options TME 10 Software Distribution User s Guide 8 3

226 Configuration Programs Before Program The before program runs (as part of a file package distribution operation) before the files in the file package are placed on the subscriber. Software Distribution supports two kinds of before programs a source before program and a target before program. Source Before Program Runs once on the source managed node before the files in the file package are sent to any subscribers. This is useful if you need to perform a special operation on the source managed node or if you need to prepare the source files before they are sent to any subscribers. For example, suppose you have a file package containing files that reside on a CD-ROM and the drive is not mounted. Use a source before program to mount the CD-ROM containing the application files before Software Distribution begins to package the files for distribution to the subscriber. The source before program is an advanced feature that is only available through the export and import capabilities or from the command line. See the TME 10 Software Distribution Reference Manual for information about the src_before_xxx keyword in the file package definition. Target Before Program Runs on every subscriber of the distribution before any files in the file package are actually distributed. This is useful if you need to prepare the subscribers before the files in the file package are distributed, or to perform dependency checks prior to a distribution. You can specify a target before configuration program to stop distribution to a subscriber if this program does not exit successfully. For example, suppose you want to distribute a file package only if the subscriber has a certain amount of available disk space. Use a target before program to check the disk space availability on the subscriber. If sufficient disk space is available, the program exits successfully. Otherwise, the target before program exits with an error. 8 4 Version 3.6

227 Configuration Programs The target before program is a basic feature available through the platform-specific options dialogs on the File Package Properties window, as well as through the export and import capabilities and the command line. After Program An after program runs (as part of a file package distribution operation) after the files in the file package are placed on the subscriber. Software Distribution supports two kinds of after programs a target after program and a source after program. Target After Program Runs after the files in the file package are successfully placed on a subscriber. This is useful if you need to configure each subscriber after the files are placed there. For example, use a target after program to restart a database server after distributing updated database files. The target after program is a basic feature that is available through the platform-specific options dialogs on the File Package Properties window in the GUI, as well as through the export and import capabilities and from the command line. Source After Program Runs once on the source managed node after the files in the file package are distributed and after the target after programs have run on all subscribers. The source after program runs regardless of whether the distribution to all subscribers was successful or not. This is useful if you need to perform a special operation on the source managed node or if you need to configure the source files after they are sent to the subscribers. For example, if your source before program mounted a CD-ROM drive, use a source after program to unmount the CD-ROM drive after the application files are distributed to the subscribers. The source after program is an advanced feature that is only available using the export and import capabilities or from the command line. See the TME 10 Software Distribution Reference Manual for information about the src_after_xxx keyword in the file package definition. File Package Options TME 10 Software Distribution User s Guide 8 5

228 Configuration Programs Removal Program The removal program runs before the files in the file package are removed from the subscriber. For example, suppose you installed an application on each user s machine that you now want to remove. During the installation, you modified all users startup files to add the application s directory to the users paths. Use a removal program to modify the startup files to remove this application s directory from the paths. The removal program is a basic feature that is available through the platform-specific options dialogs on the File Package Properties window, as well as through the export and import capabilities and from the command line. After Removal Program The after removal program runs after the files in the file package are removed from the subscriber. For example, suppose you want to remove an application that you previously distributed using Software Distribution. After the removal operation, run an after removal program to change the system login message to indicate that the application is no longer available. The after removal program is an advanced feature that is only available through the export and import capabilities and from the command line. See the TME 10 Software Distribution Reference Manual for information about the yyy_after_removal_xxx keywords in the file package definition, where yyy is the platform-specific prefix. Commit Program A commit program runs when you perform a commit operation or after distribution when you perform a distribute and commit operation. You can use this configuration program to perform an operation on all subscribers at the time of or some time after distribution. This is useful if your subscribers are connected to networks of varying speed, yet you want the distributed information to be available on all subscribers at the same time. 8 6 Version 3.6

229 Configuration Programs For example, suppose your application is configured to obtain the pricing information from the files in the /product/pricing directory. This directory is symbolically linked to the /price_files/normal directory. When you distribute the new files, distribute them to a new directory, such as /price_files/sale. Because the files are not activated when the subscriber receives them, you are not concerned about when each subscriber receives them. Use the commit program to remove the symbolic link from /product/pricing to /price_files/normal and create a new symbolic link from /product/pricing to /price_files/sale. The commit program is a basic feature that is available through the platform-specific options dialogs on the File Package Properties window, as well as through the export and import capabilities and from the command line. On Error Program The on error program runs on a subscriber if a fatal error occurs during a distribution or removal operation. This program also runs on the subscriber if a non-fatal error occurs and you set the stop_on_error keyword to y. Use this program to perform error reporting or recovery actions. For example, you may want to use an on error program to send an event to the TME 10 Enterprise Console server, gather diagnostic information, or write to a log file. You can also use an on error program to restore any files created by before programs or by the distribution or removal operation. The on error program is an advanced feature that is only available through the export and import capabilities and from the command line. See the TME 10 Software Distribution Reference Manual for information on the yyy_on_error_xxx keywords in the file package definition, where yyy is the platform-specific prefix. File Package Options Input Files You can pass an input file to a configuration program, which enables you to supply data to the program as it runs. Input files also enable you to use a single program for multiple configuration programs (or for a TME 10 Software Distribution User s Guide 8 7

230 Configuration Programs program for multiple file packages), yet have that program perform different operations in each case. For example, you can create a common source before and after program to mount and unmount file systems for all of your file packages. The following example code demonstrates how an input configuration program can be used to determine which UNIX file systems to mount on the subscribing machine:!/bin/sh # # Save the type of configuration program being run for # later use BARC_TYPE=$1 # # Loop through all file mount specifications, performing # mounts and unmounts in order. Format is: DEVICE_NAME # MOUNT_NAME. If we are running in the context of a before # program, then do a mount. If we are running in the context # of an after program, then do an unmount. # if [ "$BARC_TYPE" = "before" ] then read inline while [! -z "$inline" ] do set $inline DEVICE=$1 FILESPEC=$2 /etc/mount "$DEVICE" "$FILESPEC" read inline done else if [ "$BARC_TYPE" = "after" ] then read inline while [! -z "$inline" ] do set $inline DEVICE=$1 FILESPEC=$2 /etc/umount "$DEVICE" "$FILESPEC" read inline done fi fi exit Version 3.6

231 Configuration Programs You can pass an input file to this configuration program that lists the file systems to mount. The contents of an example input file follow: /dev/dsk/0s1 /mnt /dev/dsk/0s2 /mnt2 /dev/dsk/0s3 /tivoli/drm/2/stevem /dev/dsk/0s4 /tivoli/platform /dev/dsk/0s5 /tivoli/drm/3/kat If the configuration program runs as the source before program, the file systems in the input file are mounted. If it runs as the source after program, the file systems are unmounted. (This script does not perform error checking.) Multiple Configuration Programs and Input Files You can specify multiple configuration programs of the same type to run on the subscriber. Additionally, you can designate input files for each configuration file. If you specify more than one configuration program of the same type, you must separate them with commas. Likewise, to specify input files for multiple programs, you must also separate them with commas. The programs must reside on the same subscriber or source and are processed in the order in which you specify them. If you specify multiple before programs and a program fails when you distribute the file package, subsequent programs will run if you have not enabled the Stop distribution on error option on the File Package Properties window (yyy_before_skip_non_zero=y). Enabling this option stops the distribution if a program fails and does not allow subsequent programs to run. If you specify multiple after programs and a program fails, Software Distribution does not run subsequent after programs or commit operations. Finally, if you specify multiple removal or commit programs and a program fails, Software Distribution does not run subsequent programs of that type and does not perform the corresponding file package operation. File Package Options TME 10 Software Distribution User s Guide 8 9

232 Configuration Programs Return Status of Configuration Programs UNIX Only The return status of a configuration program is written to the log file on a managed node specified by the Log Information Options section of the File Package Properties window. For configuration programs that are run on UNIX machines (including all source before and after programs), this return status as reported in the log file is not the same as the exit status of the program. Rather, the return status written to the log file is reported according to the semantics of the wait system call, which can vary depending on the architecture type of the file package source host. See the system documentation of the source host for information on the wait system call. Running Configuration Programs in the Background For Windows only. If you have installed Windows 95, you must create the _DEFAULT.PIF file. Refer to Windows 95 documentation for information about creating this file. If you are setting.bat,.exe, or.com options on a Windows or Windows 95 machine, you must edit the _DEFAULT.PIF file to run configuration programs in the background. This file controls the execution of.bat,.exe, or.com programs running on a DOS-compatible box. By default, configuration programs are launched in the foreground. If you specify that they must run in the background, these programs can terminate without user intervention. To run configuration programs in the background, double-click on the PIF Editor icon in the Main program manager group. Select Open... from the File menu to open the _DEFAULT.PIF file from the program directory. Select the Background and Close Window on Exit check boxes near the bottom of the window. Select Save from the File menu before exiting the editor. Modify this file for all Windows and Windows 95 machines that will receive file package distributions. If you cannot or do not wish to edit the _DEFAULT.PIF file, you can create a.pif file for each configuration program. To do so, double-click on the PIF Editor icon in the Main program manager group. Enter the full path to the configuration program, including the drive letter, in the Program Filename field. Select the desired options in the window, such as the Background check box, Close Window on Exit check box, and the Windowed check box. To save the.pif file, select Save As... from the File menu Version 3.6

233 Processing Arguments to Configuration Programs Processing Arguments to Configuration Programs Software Distribution passes command line arguments to configuration programs in the same way that commands invoked from the command line are passed their arguments. Currently, Software Distribution passes the following parameters to a configuration program: A literal string describing the configuration program type. The path to the input file, as specified in the yyy_xxx_input_path keywords. If an input file is not specified, a NULL literal string is passed. A literal string value of the ams_inst_sw_comp_handle keyword. This keyword specifies the AMS Installed Software Component Handle, which identifies the installed software component handle that is created for the software component by the Tivoli Developer s Toolkit. For more information about this keyword, see the manual page for the wsetfpopts command in the TME 10 Software Distribution Reference Manual. If a value is not specified for this keyword, a NULL literal string is passed. For example, if you set the following keywords in a file package description: File Package Options unix_after_prog_path= /tmp/user_conf_prog.sh unix_after_input_path= /tmp/user_conf_prog.in ams_inst_sw_comp_handle= Software Distribution will spawn an after configuration program with the following arguments: /tmp/user_conf_prog.sh after /tmp/user_conf_prog.in NULL It is possible that in future releases Tivoli will add other parameters to Software Distribution configuration programs. Therefore, Tivoli strongly recommends that configuration programs not perform a check for the exact number of parameters that are passed. If you need to check for missing arguments in a configuration program, Tivoli recommends the following script: if [ $# -lt 3 ]; then TME 10 Software Distribution User s Guide 8 11

234 Encoding and Decoding Distribution Data fi echo Missing arguments exit 1 Encoding and Decoding Distribution Data UNIX Only Software Distribution provides a means of encrypting and decrypting file package data or configuration scripts using user-defined filters. You can define processing filters by applying the following two keywords: postproc Specifies an encryption filter to encode data before the file package leaves the source host. preproc Specifies a decryption filter to decode encoded data as the file package arrives at the target. If you plan to use these encryption and decryption capabilities, you must specify a value for both postproc and preproc in your file package definition. For information about editing the file package description using the export and import capability, see Exporting and Importing File Package Definitions in Chapter 7. The TME 10 Software Distribution Reference Manual for provides descriptions and valid values for all Software Distribution keywords. Setting UNIX File Package Options This section describes how to set file package options for UNIX target machines. The following table shows the context and authorization role needed for this task: Operation Context Required Role Set or edit file package UNIX options File package admin, senior or super You can perform this task from the TME 10 desktop, from the command line, or by using the export and import capabilities Version 3.6

235 Desktop Setting UNIX File Package Options 1. From a profile manager, double-click on a file package icon to display the File Package Properties window. File Package Options The File Package Properties window shows the file package name, and the current file package definition and options settings. TME 10 Software Distribution User s Guide 8 13

236 Setting UNIX File Package Options 1. Select Platform-Specific Options -> Unix Options... from the Edit menu to display the File Package Unix Options dialog. 1. In the Destination Directory Path field, specify a destination path for distribution to UNIX subscribers. Type the full path to which to distribute the file package on UNIX subscribers. If you do not know the full path to the destination directory, press the ellipsis button (...) button to display a browser dialog that enables you to traverse the directory structure of the destination machine. If you do not specify a destination directory in the Destination Directory Path field, the file package is distributed to a default destination on the target machine. For more information about this default location, see Chapter 6, Troubleshooting, in the TME 10 Software Distribution Reference Manual Version 3.6

237 Setting UNIX File Package Options 1. Set the Resolution of Links options to establish how symbolic links are handled during file package distribution and removal. Select the Follow links to original files radio button to copy the original files (the files to which the symbolic links point) to the destination, rather than copying the symbolic links to the destination. Note: If you press the Follow links to original files radio button and the symbolic link points to a nonexistent file, neither the link nor the file is distributed for that entry. Select the Copy links as links radio button to create symbolic links to the original files at the destination. You cannot distribute a file package containing a symbolic link to a PC or NetWare server the subscriber must be a UNIX machine. Notes: If you are distributing a file package that contains symbolic links to UNIX and PC subscribers, do not select the Copy links as links option. The distribution to the PCs will fail. If the follow_links keyword is set to y (the default) and a symbolic link points to the parent directory of the subdirectory that contains the link (../ ) or another directory higher in the same directory branch, a circular definition results, causing an error and the distribution to fail. To prevent this error, set the follow_links keyword to n. 1. Set the User Ownership of Files on Subscribers options to control the ownership of the file package s files on the subscribers. Select the Preserve source file user ownership radio button to set the file ownership of the file package files to the same at the subscriber as that on the source host. File Package Options TME 10 Software Distribution User s Guide 8 15

238 Setting UNIX File Package Options Note: If you enter a name or user ID in the Enter User Login Name or UID field and press the Preserve source file user ownership radio button, the field is cleared. Select the Change to radio button to change the ownership of the file package files at the subscribers when the file package is distributed. If you select this option, you must specify a new user name or UID in the Enter User Login Name or UID field. User names specified here must be valid on the host from which you opened your TME 10 desktop. You can enter the decimal UID if your environment does not have uniform UIDs for all user names. Note: If you specify a symbolic user name in this field and this user name has a different numeric UID on a subscriber than on the host from which you opened the desktop, the files UIDs are set to the numeric UID of the user name as defined on the host from which you opened the desktop. The ability to change directory entries to a specified UID is also available. See the unix_default_dir_uid keyword in the TME 10 Software Distribution Reference Manual. 1. Set the Group Ownership of Files on Subscribers options to control the group ownership of the file package files on the subscribers. Select the Preserve source file group ownership radio button to set the group ownership of the file package files so that subscribers maintain the same group ownership setting as the source host. Note: If you enter a name or group ID in the Enter Group Name or GID field and press the Preserve source file group ownership radio button, the field is cleared. Select the Change to radio button to change the group ownership of the files at the subscribers when the file package is distributed. If you select this option, you must specify a new group name or GID in the Enter Group Name 8 16 Version 3.6

239 Setting UNIX File Package Options or GID field. The group you specify must be a valid on the host from which you opened your TME 10 desktop. Note: If you specify a symbolic group name in this field and this group name has a different numeric GID on a subscriber than on the host from which you opened the desktop, the files GIDs are set to the numeric GID of the group name as defined on the host from which you opened the desktop. The ability to change directory entries to a specified GID is also available. See the unix_default_dir_gid keyword in the TME 10 Software Distribution Reference Manual. 1. Set configuration program options by using the Run a Program buttons. These buttons display options that enable you to run configuration programs, which include C programs, shell scripts, Perl scripts, and so on, on subscribers before or after distributing software or data, before removing a file package, or during a commit operation. To run programs on a UNIX subscriber before or after a file package operation, complete the following steps: a. Press the program button that corresponds to the configuration program you wish to run. a. Specify the location of the configuration programs and input files using the Get program from radio buttons. If you press the Source Host radio button, Software Distribution copies each program from the source host to a temporary file on each subscriber. It then runs the programs on each subscriber before or after the file package operation is performed and removes each temporary file from each subscriber upon completion. If you press the Subscribers radio button, Software Distribution runs each program directly from the subscriber. a. In the Enter Program name field, enter the full path of a program to run. If you do not know the full path to the program, press the ellipsis (...) button to display a browser dialog that enables File Package Options TME 10 Software Distribution User s Guide 8 17

240 Setting UNIX File Package Options you to traverse the directory structure of the machine on which it resides. You must enter the name of a program that exists at the time of the operation. The program must be located on the managed node (source or subscriber) specified by the Get program from radio buttons. If you specify multiple programs, you must separate them with commas. Note: Software Distribution does not check for the existence of the programs on either the source host or subscribers until the time of the file package operation. If a program is not found at that time, Software Distribution logs an error. a. If you want to specify an input file with the configuration program, enter the full path in the Enter Input file name field. If you do not know the full path to the file, press the ellipsis (...) button to display a browser dialog that enables you to traverse the directory structure of the machine on which it resides. This input file must be located on the same managed node (source or subscriber) as the program indicated in the Enter Program name field. The input file contents are sent to the standard input stream of the program. If you have specified multiple programs of the same type, you can also specify multiple input files separated by commas. If one program in this list does not require an input file but subsequent programs do, you must specify the input files in the correct order and preceded by the same number of commas as the programs. Do not follow commas with spaces. For example, if you have specified /usr/prog1,/usr/prog2,/usr/prog3 in the Enter Program name field, and /usr/prog2 does not require an input file, you must specify the following in the Enter Input file name field: /usr/input1,,/usr/input Version 3.6

241 Setting UNIX File Package Options Note: If you want to specify an input file that resides in a different location than the specified configuration program, refer to the unix_xxx_input_from_src keyword in the TME 10 Software Distribution Reference Manual, where xxx is the program type. a. If you are running a before program, select the Skip distribution to a host on a non-zero exit code of program check box to skip distributing the file package to a subscriber if the program fails and returns a non-zero exit code. This option allows you to implement dependency checking so that file packages are distributed to subscribers only if dependencies are met. You can set or modify file package options, such as a timeout value for configuration programs specified in the file package, using the wsetfpopts command. See the TME 10 Software Distribution Reference Manual for wsetfpopts command syntax and usage. 1. Press the Set & Close button to apply the changes and dismiss the dialog. OR Press the Reset button to set all UNIX options of the file package to the values last saved to the file package. File Package Options Command Line To use the wsetfpopts command to set the UID and GID for all files and links in the PS_docs^3.0 file package distributed to a UNIX subscriber, enter the following command: wsetfpopts -T unix -g 150 -u where: T unix Enables you to set UNIX keywords using this command. g 150 Sets the GID to 150 for all files and links in the file package. TME 10 Software Distribution User s Guide 8 19

242 Setting UNIX File Package Options u 300 Sets the UID to 300 for all files and links in the file Specifies the file package to modify. To use the command line to create intermediate directories at the destination if they do not exist and to skip the distribution if the files in the file package are older than those at the UNIX subscriber, enter the following command: wsetfpopts -T gen -C y -o where: T gen Enables you to set non-platform-specific keywords with this command. C y Creates the intermediate directories. o y Does not distribute files if a newer version of the file exists on the Specifies the file package to modify. To use the wsetfpprgs command to run the /source/progs/b1.scrpt and /source/progs/b2.scrpt programs on the source host before distribution (set the src_before_prog_path keyword), enter the following command: wsetfpprgs -T src \ -b /source/progs/b1.scrpt,/source/progs/b2.scrpt -J y \ -j where: T src Enables you to set values for the source host keywords. b /source/progs/b1.scrpt,/source/progs/b2.scrpt Sets the /source/progs/b1.scrpt and /source/progs/b2.scrpt before programs for the source host Version 3.6

243 Setting UNIX File Package Options J y Specifies to retrieve the /source/progs/input_b1.txt input file (for the /source/progs/b1.scrpt program) from the source host. j /source/progs/input_b1.txt, Specifies the /source/progs/input_b1.txt input file for the /source/progs/b1.scrpt program. Because more than one program is specified, you must follow the /source/progs/input_b1.txt file with a comma (,) although the /source/progs/b2.scrpt program does not require an input Specifies the file package to modify. To use the command line to run the /tmp/error1.scrpt program on the subscriber if a file package operation fails due to an error (set the unix_on_error_prog_path keyword), use the following command: wsetfpprgs -T unix -f /tmp/error1.scrpt where: T unix Enables you to set UNIX options on the command line. f /tmp/error1.scrpt Sets the /tmp/error1.scrpt on error program for the UNIX Specifies the file package to modify. For information about using the command line to set file package options and configuration program options, see the wsetfpopts and wsetfpprgs commands in the TME 10 Software Distribution Reference Manual. File Package Options TME 10 Software Distribution User s Guide 8 21

244 Setting NetWare File Package Options Setting NetWare File Package Options This section describes how to set file package options for NetWare target machines. The following table shows the context and authorization role needed for this task: Operation Context Required Role Set or edit file package NetWare options File package admin, senior or super You can perform this task from the TME 10 desktop, from the command line, or by using the export and import capabilities Version 3.6

245 Desktop Setting NetWare File Package Options 1. From a profile manager, double-click on a file package icon to display the File Package Properties window. File Package Options The File Package Properties window shows the file package name, and the current file package definition and options settings. TME 10 Software Distribution User s Guide 8 23

246 Setting NetWare File Package Options 1. Select Platform-Specific Options -> NetWare Options... from the Edit menu to display the File Package NetWare Options dialog. 1. Use the Destination Directory Path field to specify a destination path for distribution to NetWare subscribers. In this field, type the full path to a volume on the NetWare subscribers to which to distribute the file package. Specify the destination path as VolumeName:/Path, where VolumeName is the NetWare volume name (for example, SYS, VOL1, or VOL2). Do not confuse the volume name with the drive that a NetWare client uses to remotely reference a volume 8 24 Version 3.6

247 Setting NetWare File Package Options Enable this option only if the target server is running Net- Ware 3.12 bindery emulation software. on the NetWare server from a PC. If you do not specify a volume, the default, volume 0, is used (SYS on most systems). For information on specifying a volume, see your NetWare documentation. If you do not specify a destination directory in the Destination Directory Path field, the file package is distributed to a default destination on the target machine. For more information about this default location, see Chapter 6, Troubleshooting, in the TME 10 Software Distribution Reference Manual. 1. Set login information. When you distribute a file package to a NetWare server, the PC agent running on the server must log in to the NetWare server before it can create or remove files (if it is running in restricted mode). Use the options in the Login Information section to log in to a NetWare 4.x server and emulate a NetWare 3.x server. If you select the Bindery emulation mode check box, Software Distribution will connect to all target NetWare servers as if they were NetWare 3.x servers (using bindery emulation mode). The NDS Tree and NDS Context fields are then disabled because they apply only to NetWare 4.x. If you do not select the Bindery emulation mode check box, you can specify a NetWare directory service tree in the NDS Tree field and the NetWare directory service context in the NDS Context field. The NDS tree and context that you specify here will override the defaults on the NetWare target. 1. Specify whether to disconnect locked files on the subscriber by pressing the Disconnect locked files check box. If you select this box, Software Distribution breaks the lock on any open files on the NetWare server and replaces those files during a distribution. 1. Specify broadcast messages. Removing or replacing files on a NetWare server can disrupt NetWare clients using those files, therefore, you can use the Broadcast Message To options to send a message to clients of the NetWare server subscribers. File Package Options TME 10 Software Distribution User s Guide 8 25

248 Setting NetWare File Package Options If you press the All Clients radio button, the message specified in the Message box is sent to all clients of NetWare server. If you press the Only clients with locks on files radio button, Software Distribution sends the specified message to only those clients using files (on the server) that will be removed or replaced by the distribution. 1. Set configuration program options by using the Run an NLM buttons. These buttons display options that enable you to run configuration programs, which include NetWare loadable modules (NLMs) or.ncf files, on subscribers before or after distributing software or data, before removing a file package, or during a commit operation. Refer to the TME 10 Software Distribution Reference Manual for information about NLM limitations. To run a configuration program on a NetWare subscriber before or after a file package operation, complete the following steps: a. Press the program button that corresponds to the configuration program you wish to run. a. Specify the location of the configuration programs and input files using the Get NLM from radio buttons. If you press the Source Host radio button, Software Distribution copies each program from the source host to a temporary file on each subscriber. It then runs the programs on each subscriber before or after the file package operation is performed and removes each temporary file from each subscriber upon completion. If you press the Subscribers radio button, Software Distribution runs each program directly from the subscriber. a. In the Enter NLM name field, enter the full path of a program to run. If you do not know the full path to the program, press the ellipsis (...) button to display a browser dialog that enables you to traverse the directory structure of the machine on which it resides. You must enter the name of a program, using forward slashes (/), that exists at the time of the operation Version 3.6

249 Setting NetWare File Package Options The program must be located on the host (source or subscriber) specified by the Get NLM from radio buttons. If you specify multiple programs, you must separate them with commas. Note: Software Distribution does not check for the existence of the programs on either the source host or subscribers until the time of the file package operation. If a program is not found at that time, Software Distribution logs an error. a. If you want to specify an input file with the configuration program, enter the full path in the Enter Input file name field. If you do not know the full path to the file, press the ellipsis (...) button to display a browser dialog that enables you to traverse the directory structure of the machine on which it resides. You must enter the path using forward slashes (/). This input file must be located on the same host (source or subscriber) as the program indicated in the Enter NLM name field. If you specified multiple programs, you can also specify multiple input files separated by commas. If one program in this list does not require an input file but subsequent programs do, you must specify the input files in the correct order and preceded by the same number of commas as the programs. Do not follow commas with spaces. For example, if you specified /usr/before1.exe,/usr/before2.exe,/usr/before3.exe in the Enter NLM name field, and /usr/before2.exe does not require an input file, you must specify the following in the Enter Input file name field: /usr/input1.txt,,/usr/input3.txt Note: If you want to specify an input file that resides in a different location than the specified configuration program, refer to the nw_xxx_input_from_src keyword in the TME 10 Software Distribution Reference Manual, where xxx is the program type. File Package Options TME 10 Software Distribution User s Guide 8 27

250 Setting NetWare File Package Options Command Line a. If you are running a before configuration program, select the Skip distribution to a host on a non-zero exit code of NLM check box to skip distributing the file package to a subscriber if the program fails and returns a non-zero exit code. This option allows you to implement dependency checking so that file packages are distributed to subscribers only if dependencies are met. You can set or modify file package options, such as a timeout value for configuration programs specified in the file package, through the wsetfpopts command. See the TME 10 Software Distribution Reference Manual for wsetfpopts command syntax and usage. 1. Press the Set & Close button to apply the changes and dismiss the dialog. OR Press the Reset button to set all NetWare options of the file package to the values last saved to the file package. To use the wsetfpopts command to add SYS:/bin to the beginning of all destination paths for the PS_docs^3.0 file package on a NetWare server, enter the following command: wsetfpopts -T nw -p where: T nw Enables you to set NetWare keywords using this command. p SYS:/bin Adds SYS:/bin to the beginning of all NetWare destination Specifies the file package to modify. To use the command line to perform a checksum parity check, post a notice to the Software Distribution notice group, and broadcast a 8 28 Version 3.6

251 Setting NetWare File Package Options message to all NetWare managed site clients during a file package distribution, enter the following command: wsetfpopts -T gen -x y -P where: T gen Enables you to set non-platform-specific keywords on this command line. x y Performs a checksum parity on the file package. P y Posts messages to the Software Distribution notice Specifies the file package to modify. To broadcast a message to all NetWare managed site clients, enter the following command: wsetfpopts -T nw -z y -Z "Starting file pack distribution" where: T nw Enables you to set NetWare options on this command line. z y Broadcasts the specified message to all NetWare managed site clients. Z Starting file pack distribution Broadcasts the message Starting file pack distribution to the distribution Specifies the file package to modify. File Package Options To use the wsetfpprgs command to run the /tmp/rm1.nlm and /tmp/rm2.nlm removal programs (with the /tmp/input1.txt file) from the source host for each target of the removal operation, enter the following command: wsetfpprgs -T nw -R y -r /tmp/rm1.nlm,/tmp/rm2.nlm -L y \ -l TME 10 Software Distribution User s Guide 8 29

252 Setting PC File Package Options where: T nw Enables you to specify programs to run on a NetWare subscriber on this command line. R y Specifies that the removal programs reside on the source host. r /tmp/rm1.nlm,/tmp/rm2.nlm Sets the path to two removal programs, /tmp/rm1.nlm and /tmp/rm2.nlm. L y Specifies that the /tmp/input1.exe file resides on the source host. l /tmp/input1.txt, Sets the path to the /tmp/input1.txt input file for the /tmp/rm1.exe removal program. The second removal program does not require an input file. However, you must place the comma (,) after the first input Specifies the file package to modify. For information about using the command line to set file package options and configuration program options, see the wsetfpopts and wsetfpprgs commands in the TME 10 Software Distribution Reference Manual. Setting PC File Package Options This section describes how to set file package options for Windows and OS/2 target machines. The following table shows the context and authorization role needed for this task: Operation Context Required Role Set or edit file package PC options File package admin, senior or super You can perform this task from the TME 10 desktop, from the command line, or by using the export and import capabilities Version 3.6

253 Desktop Setting PC File Package Options 1. From a profile manager, double-click on the file package icon to display the File Package Properties window. File Package Options The File Package Properties window shows the file package name, the current file package definition, and options settings. TME 10 Software Distribution User s Guide 8 31

254 Setting PC File Package Options 1. Select Platform-Specific Options -> Windows Options... from the Edit menu to display the File Package Windows Options dialog. 1. In the Destination Directory Path field, specify a destination path for distribution to Windows subscribers. Type the full path to which to distribute the file package on Windows subscribers. You must use forward slashes (/) when specifying the directory path Version 3.6

255 Setting PC File Package Options For Windows and Windows 95 subscribers only Be sure to include a drive letter as a part of the path in the Destination Directory Path field. If you do not specify a drive letter, such as C:/, the file package is distributed to the drive on the target system where the Tivoli code is installed. For managed nodes, this is the drive on which you have installed the managed node; for endpoints, it is the drive on which the lcfd directory is installed; and for PC managed nodes, it is the drive on which the PC agent is installed. If you do not specify a destination directory in the Destination Directory Path field, the file package is distributed to a default destination on the target machine. For more information about this default location, see Chapter 6, Troubleshooting, in the TME 10 Software Distribution Reference Manual. 1. Set distribution options using the File Package distribution is options to indicate whether the distribution will be optional or mandatory. Press the Mandatory radio button to automatically distribute the file package without providing an override option to the user at the subscriber. Press the Optional radio button to allow the end-user to choose whether or not to have the file package distributed to his or her machine. An optional distribution displays a pop-up dialog on the subscriber machine at distribution time. The end-user can then choose to accept the distribution or not. If the user chooses not to accept the distribution, distribution to other targets continues uninterrupted. If you press the Optional radio button, you must specify in the Display distribution warning for field the number of seconds the dialog is displayed on the subscriber. If the user does not respond in that amount of time, the file package is distributed. You must specify a value that is between 1 and 6000, inclusive. 1. In the BAT/EXE/COM Options section, set configuration program options using the Run a Script buttons. These buttons enable you to run your own.bat,.exe, and.com files on Windows subscribers before or after distributing software, before File Package Options TME 10 Software Distribution User s Guide 8 33

256 Setting PC File Package Options removing a file package, or when you perform a commit operation. Note: When setting file package options for Windows OS/2, the Run a Script buttons are in the CMD/BAT/EXE/COM Options section. To run a configuration program on a Windows subscriber before or after a file package operation, complete the following steps: a. Press the program button that corresponds to the configuration program you wish to run. a. Specify the location of the configuration programs and input files using the Get BAT/EXE/COM file from radio buttons. - If you select the Subscribers radio button, Software Distribution runs each program directly from the subscriber. Note that if you select this option, you will not enter values in the Enter BAT/EXE/COM file name and Enter Input file name fields. - If you select the Source Host radio button, Software Distribution copies each executable from the source host to a temporary file on each target. It then runs the executables on each target before or after the file package operation is performed and removes the temporary files from each target upon completion. In the Enter BAT/EXE/COM file name field, enter the full path of the executable file. If you do not know the full path to the program, press the ellipsis button (...) to display a browser dialog that enables you to traverse the directory structure of the machine on which it resides. You must enter the path using forward slashes (/) and the name of a file that exists at distribution time, located on the host (source or subscriber) specified by the Get BAT/EXE/COM file from radio buttons. If you want to specify multiple programs, you must separate them with commas Version 3.6

257 Setting PC File Package Options Note: Software Distribution does not verify that the executable file exists on the source host or targets until the time of the file package operation. If the file is not found, Software Distribution logs an error at that time. If you want to specify an input file with the program, enter the full path in the Enter Input file name field. If you do not know the full path to the file, press the ellipsis button (...) to button to display a browser dialog that enables you to traverse the directory structure of the machine on which it resides.you must enter the path using forward slashes (/). This input file must be located on the same host (source or target) as the program indicated in the Enter BAT/EXE/COM file name field. If you have specified multiple programs, you can also specify multiple input files separated by commas. If one program in this list does not require an input file but subsequent programs do, you must specify the input files in the correct order and preceded by the same number of commas as the programs. Do not follow commas with spaces. For example, if you have specified /usr/before1.exe,/usr/before2.exe,/usr/before3.exe in the Enter BAT/EXE/COM file name field, and /usr/before2.exe does not require an input file, you must specify the following in the Enter Input file name field: /usr/input1.txt,,/usr/input3.txt Note: If you want to specify an input file that resides in a different location than the program, refer to the win_xxx_input_from_src keyword in the TME 10 Software Distribution Reference Manual, where xxx is the program type. a. If you are running a before configuration program, select the Skip distribution to a host on a non-zero exit code of file check box to skip distributing the file package to a host if the program fails and returns a non-zero exit code. File Package Options TME 10 Software Distribution User s Guide 8 35

258 Setting PC File Package Options For Windows, Windows 95, and Windows NT subscribers only This option enables you to implement dependency checking so that file packages are distributed to subscribers only if certain dependencies are met. a. If you are running an after, removal, or commit configuration program, press one of the options below the Enter Input file name field. These options are displayed only when you select the After Distribution, Upon Removal, or During Commit button. Select one of the following options is you are running one of these configuration programs: - Press the Do Nothing radio button if you do not want Software Distribution to reboot the subscriber or restart the operating system. - Press the Reboot machine radio button to reboot the subscriber after the program runs. If you specified an after program and the program fails, the machine is not rebooted. - Press the Restart Windows radio button to restart Windows or Windows 95, or the Restart Windows NT radio button to restart Windows NT on the subscriber after the program runs. If an after program is specified and the program fails, the machine is neither restarted nor rebooted. You can set or modify file package options, such as a timeout value for configuration programs specified in the file package, through the wsetfpopts command. See the TME 10 Software Distribution Reference Manual for wsetfpopts command syntax and usage. 1. Press the Set & Close button to set the changes and dismiss the dialog. OR Press the Reset button to set all platform-specific options of the file package to the values last saved to the file package Version 3.6

259 Command Line Setting PC File Package Options To use the wsetfpopts command to add C:/BIN to the beginning of Windows destination paths and run the /SOURCE/PROGS/A.EXE after program for the PS_docs^3.0 file package, enter the following command: wsetfpopts -T win -a /SOURCE/PROGS/A.EXE -p C:/BIN where: T win Enables you to set Windows keywords on this command line. a /SOURCE/PROGS/A.EXE Sets the after program for Windows targets to the /SOURCE/PROGS/A.EXE file. p C:/BIN Adds C:/BIN to the beginning of Windows destination Specifies the file package to modify. File Package Options To compress the file package before distribution, enter the following command: wsetfpopts -T gen -c where: T gen Enables you to set non-platform-specific keywords on this command line. c y Compresses the file package before Specifies the file package to modify. TME 10 Software Distribution User s Guide 8 37

260 Setting PC File Package Options To use the wsetfpprgs command to reboot Windows machines after distribution, enter the following: wsetfpprgs -T win -o where: T win Enables you to set Windows options. o REBOOT Reboots the target machine after Specifies the file package to modify. To specify the /tmp/on_err1.exe and /tmp/on_err2.exe on error programs (which reside on the source host and require the /tmp/on_err1.txt and /tmp/on_err2.txt input files) for the example_fp file package, enter the following command: wsetfpprgs -T win -F -f /tmp/on_err1.exe,/tmp/on_err2.exe \ -G -g /tmp/on_err1.txt,/tmp/on_err2.txt where: T win Enables you to set Windows options. F Specifies that the on error programs reside on the source host. f /tmp/on_err1.exe,/tmp/on_err2.exe Sets the on error programs for the Windows target to /tmp/on_err1.exe and /tmp/on_err2.exe. The programs are processed in this order. G Specifies that the input files for the on error programs also reside on the source host. g /tmp/on_err1.txt,/tmp/on_err2.txt Sets the /tmp/on_err1.txt and /tmp/on_err2.txt input files for the specified on error programs. The order of these files corresponds to the order of the on error programs specified on the command Specifies the file package to modify Version 3.6

261 Setting PC File Package Options For information about using the command line to set file package options and configuration options, see the wsetfpopts command and the wsetfpprgs command in the TME 10 Software Distribution Reference Manual. File Package Options TME 10 Software Distribution User s Guide 8 39

262 Setting PC File Package Options 8 40 Version 3.6

263 9 9File Package Operations After creating a file package, appending files to it, and setting its platform-specific options, you can distribute the file package to its subscribers endpoints, managed nodes, PC managed nodes, NetWare managed sites, and other profile managers. When you distribute a file package, the files and directories specified in it are actually distributed to the target machines. In addition, you can perform the following operations, as described in this chapter: Calculate the size of a file package Download Software Distribution file packages and AutoPacks to UNIX, Windows, and OS/2 machines Remove a file package from its targets, which removes all distributed files and directories on those machines File Package Operations Distributing a File Package After you create a file package and set its properties and options, you can distribute it to the subscribers. To distribute a file package, consider the following scenarios: If the target is a managed node, TME 10 Software Distribution must be installed on the target s or the interconnected TMR s server. If the target is a PC managed node, TME 10 Software Distribution must be installed on the target s or the TME 10 Software Distribution User s Guide 9 1

264 Distributing a File Package interconnected TMR s server. The PC agent must also be installed on the target. If the target is an endpoint, TME 10 Software Distribution and the TME 10 Software Distribution Gateway must be installed on the target s or the interconnected TMR s server as well as on the endpoint gateway. If the target is a NetWare managed site, TME 10 Software Distribution must be installed on the target s or the interconnected TMR s server. The TME 10 NetWare repeater (TNWR) must be installed on the NetWare server. The PC agent must be installed on the NetWare server and on each of the NetWare managed site s clients. Also, before distributing a file package, consider the following distribution limitations of the Software Distribution process: UNIX Only If a file package specifies a log file, the ownership of the log file is set to the UID and GID of the administrator who performs the initial distribution. Before other administrators try to distribute the same file package containing the same log file, the values of the log_file_uid, log_file_gid, and log_file_mode keywords must be changed. See the TME 10 Software Distribution Reference Manual for more information about these keywords. Software Distribution verifies the destination directory at distribution time. If the specified directory does not exist, Software Distribution creates all components of that path by default. When you distribute the file package, the source directory and its contents are distributed beneath the directory specified in the Destination Directory Path field. (The Destination Directory Path field is located on each platform-specific options dialog.) For example, if you specify /src/test as the source directory, enter /home/test in the Destination Directory Path field, and distribute the file package, Software Distribution creates the test directory beneath the /home/test directory. The resulting directory on the subscriber is the /home/test/test directory. If you specify the destination directory as /home, the /home/test directory is created on the destination system. 9 2 Version 3.6

265 Distributing a File Package The following table shows the context and authorization role required for this task: Operation Context Required Role Distribute a file package File package admin, senior, or super You can perform this task using drag and drop, from the TME 10 desktop, and from the command line. Drag and Drop Desktop To distribute a file package using drag and drop, drag the file package icon and drop it onto an endpoint, managed node, PC managed node, NetWare managed site, or profile manager icon. The resource must subscribe to the profile manager containing the file package. Distributing a file package using drag-and-drop distributes all source files and directories included in the file package. Use the following steps to distribute a file package: Note: A database mode profile manager is used in this procedure, because its subscribers will include a profile manager and several managed nodes. If you plan to distribute to endpoint subscribers, you will need to create and use a dataless mode profile manager. For more information about operating a profile manager in either the dataless mode or the database mode, refer to the TME 10 Framework User s Guide. 1. Subscribe all targets that will receive a file package. From the Profile Manager dialog, complete the following steps: a. Select Subscribers... from the Profile Manager menu to display the Subscribers dialog. a. Move all targets from the Available to become Subscribers scrolling list to the Current Subscribers scrolling list. a. Press the Set Subscriptions & Close button to set these subscribers and return to the Profile Manager window. File Package Operations TME 10 Software Distribution User s Guide 9 3

266 Distributing a File Package 1. Double-click on the file package icon to display the File Package Properties window. 9 4 Version 3.6

267 Distributing a File Package 1. Select Distribute... from the File Package menu to display the Distribute File Package dialog. File Package Operations TME 10 Software Distribution User s Guide 9 5

268 Distributing a File Package 1. Select a distribution type from the Distribution Type list. The Distribution Only option only distributes the file package. Any specified commit programs are not run during this operation. The Distribution & Commit option distributes the file package and runs the specified commit programs on each subscriber. The Commit Only option only runs the specified commit program on each subscriber without distributing the file package. Note: The Commit Only option should not be used in conjunction with the Distribute entries with ANY changes option (see description below). If you select these two options together, the commit program will not run on the target. 1. Select a distribution option from the Distribution Options list. These options control which files in the file package are distributed. The Distribute all entries option distributes all files and directories in the file package. The Distribute entries with changed source files option distributes file package entries that have changed on the source host since the last successful distribution of the current file package. When a file package is successfully distributed, Software Distribution stores the time (as determined by the TMR server) of that distribution. Software Distribution does not save the list of subscribers to which the distribution was sent. When you perform a Distribute entries with changed source files operation, Software Distribution compares the time of the last successful distribution with the modification time of all entries in the file package (including those in any nested file packages). Software Distribution then distributes any entries in the file package that are more recent than the 9 6 Version 3.6

269 Distributing a File Package time of the last successful distribution of the file package in question. Consider the following example: suppose you create the TopFilePack file package that contains three nested file packages and you distribute it with the Distribute all entries option to the managed node electron. You then update a file in one of the nested file packages and distribute the file package with the Distribute entries with changed source files option to managed node pearl. Even though no previous successful distribution of the TopFilePack file package was made to pearl, Software Distribution only distributes the altered file. If you want to distribute a file package to a resource that was not a target of that file package s last distribution, you must use the Distribute all entries or Distribute entries with ANY changes options. The Distribute entries with ANY changes option distributes file package entries that were changed on the source host or subscribers. The source host sends information about each file in the file package to the subscribers to determine if the file types, sizes, modification times, owners, groups, modes, or checksums have changed. Each subscriber sends information back to the source host about which files have changed. The source host then determines which files have changed on itself. In addition, because files may change after contacting the subscribers and before the distribution, Software Distribution creates a snapshot of the file package. By default, the snapshot is created in the path obtained by the tempnam(3) library call. If you do not want the snapshot to reside in the location determined by the tempnam(3) library call, you can specify the staging area of this snapshot by using the w argument of the wsetfpattr command. See the TME 10 Software Distribution Reference Manual for information about this command. The snapshot is removed after the distribution. File Package Operations TME 10 Software Distribution User s Guide 9 7

270 Distributing a File Package If there is a difference between the files to be distributed and those on the source host or subscribers, Software Distribution distributes only the changed files. Notes: While this option does not send unchanged files from the source host to the subscribers (thereby conserving network bandwidth), it may lead to time-consuming distributions. If configuration programs are defined in the file package, they will be executed on the target whether or not changes have been made to the data files included in the file package. If the rm_extraneous keyword is sent to y and is used in conjunction with the Distribute entries with ANY changes option, all files in the destination directory will be deleted prior to the distribution and only files that have changed since the previous distribution will be installed. 1. Ensure that the Distribute File Package To scrolling list accurately reflects the subscribers to which to distribute the file package. By default, all subscribers in the profile manager are displayed in the Available Subscribers scrolling list. Perform the following actions using the scrolling lists: To move a subscriber to the Distribute File Package To scrolling list, choose one or more subscribers from the Available Subscribers scrolling list and press the left arrow button. To remove a subscriber, choose one or more subscribers from the Distribute File Package To scrolling list and press the Remove button. If the Available Subscribers scrolling list contains a profile manager, a plus sign (+) appears in front of its name. By double-clicking on the profile manager name, you can expand the list to view all subscribers to this profile manager. The managed resource type for each subscribing machine is 9 8 Version 3.6

271 Distributing a File Package listed next to the machine name. You can then add any of its subscribers to the Distribute File Package To scrolling list. Note: If you select a profile manager name in the Available Subscribers scrolling list, you must deselect it before double-clicking on it. The name of an expanded profile manager has a (dash) in front of it in the Available Subscribers scrolling list. To compress an expanded profile manager entry, double-click on the profile manager name. You can also use the Expand All or Compress All buttons to expand or compress all profile managers in the Available Subscribers scrolling list. If you have TME 10 Inventory installed, you can select subscribers by scanning the available endpoints, managed nodes, and PC managed nodes for certain criteria defined by a query in a query library. To run a query, press the Query button to display the Execute a Query dialog. File Package Operations This dialog lists the available query libraries that were created using TME 10 Framework. To execute a query, first select a query library from the Query Libraries scrolling list and press the Execute button to run the query on the configuration repository and return the names of the endpoints, managed nodes, and PC managed nodes that meet the criteria. This list automatically populates the Distribute File Package To scrolling list. TME 10 Software Distribution User s Guide 9 9

272 Distributing a File Package See the TME 10 Framework User s Guide for more information on creating and using queries. 1. Press the Preview button to see a list of files and directories you have selected to distribute. The files to be distributed are displayed in the File Package Distribution Preview area. The output in this area will be similar to the following: Unix target directory prefix: /tmp/unix NetWare target directory prefix: SYS:/NETWARE Windows target directory prefix: D:/WINDOWS / Dec 23 15:13: /tmp/default_dest/data.db The destination of the data.db file will be: /tmp/unix/tmp/default_dest/data.db at the UNIX target SYS:/NETWARE/tmp/default_dest/data.db at the NetWare target D:/WINDOWS/tmp/default_dest/data.db at the Windows target The file is distributed to the /platform_prefix_dir/default_dest_dir directory (as specified by the xxx_platform_prefix and default_dest keywords, where xxx denotes the operating system type). You cannot preview files or directories that will be included in the file package as a result of a configuration program. The preview operation does not execute these programs. If the contents of the file package depend on an operation in a configuration program, the preview operation will not accurately display the contents of the file package. For example, suppose you specify a before program that will mount a CD-ROM drive on which a file (to be distributed) resides, as follows: #!/bin/sh mount /dev/cdrom /src exit Version 3.6

273 Distributing a File Package The files on the mounted file system are not displayed during a preview operation because this program is not executed. For more information about distribution programs, see Configuration Programs on page 1-7. After previewing the file package contents, you can select the Clear button to clear the preview window. OR Select the Save to File... button to save the preview results to a file using the Save File Package Preview Data to a File browser dialog. You must have write permission to the file that you select. See the TME 10 Framework User s Guide for information on how to use file browser dialogs. 1. Press the Schedule... button to schedule operations at a future time or to automatically retry the distribution to any target for File Package Operations TME 10 Software Distribution User s Guide 9 11

274 Distributing a File Package which the distribution might fail. Software Distribution displays the Add Scheduled Job dialog. See the TME 10 Framework User s Guide for more information about creating tasks and jobs and using drag and drop to schedule a job Version 3.6

275 Distributing a File Package 1. Press the Distribute & Close button to begin distributing the file package to the selected subscribers and dismiss the Distribute File Package dialog. Note: The dialog is not dismissed until the distribution is complete and the operation stops. If the distribution fails for any of the subscribers, a pop-up dialog is displayed to inform you which subscribers failed during the distribution. This status is also displayed on the TME 10 desktop. Command Line To use the wdistfp command to distribute all of the files in the TopFilePack file package to the SolMachs profile manager, enter the following command: wdistfp where: a Distributes all files in the file package. d Specifies to perform only a Specifies to distribute the TopFilePack file Distributes the file package to the targets of the SolMachs profile manager. File Package Operations To use the command line to distribute and commit only those files that have changed on the source host in the TopFilePack file package to the SolMachs profile manager, enter the following command: wdistfp where: s Distributes only those files that changed on the source host. b Specifies to perform a distribute and commit. TME 10 Software Distribution User s Guide 9 13

276 Calculating the Size of a File Specifies to distribute the TopFilePack file Distributes the file package to the targets of the SolMachs profile manager. For more information about distributing file packages from the command line, see the wdistfp command in the TME 10 Software Distribution Reference Manual. Calculating the Size of a File Package Calculate the size of a file package to determine the total size (in bytes) of its included files, directories, and nested file packages. Note: The calculated size may be larger than the sum of the file package components due to Software Distribution data overhead. In addition, this size does not account for files or directories that are compressed during distribution. The uncompressed size of the files or directories is used to calculate the total. The following table shows the context and authorization role required for this task: Operation Context Required Role Calculate, set, or retrieve the size of a file package Profile manager s policy region admin, senior, or super You can perform this task from the TME 10 desktop or the command line Version 3.6

277 Calculating the Size of a File Package Desktop To calculate the size of a file package from the desktop, complete the following steps: 1. Select the desired file package from the Profile Manager window and select Calculate Size... from the file package icon menu. Software Distribution displays the following dialog: 1. The Calculate File Package Size dialog displays the name of the file package and its profile manager. Select the Calculate Size button to determine and display the file package size (in bytes). Software Distribution stores this information as an attribute of the file package. File Package Operations Command Line To use the wsetfpattr command to set (not calculate) the size of the TopFilePack file package to bytes from the command line, enter the following command: wsetfpattr -S where: S Sets the size of the file package to Specifies to set the size of the TopFilePack file package. Once you calculate (using the desktop) or set (using the command line) the file package size, you can retrieve this value using the wgetfpattr TME 10 Software Distribution User s Guide 9 15

278 Pulling a File Package command. For example, to retrieve the size of the TopFilePack file package, enter the following command: wgetfpattr where: S Retrieves the size of the file Specifies to retrieve the size of the TopFilePack file package. For more information on the wsetfpattr and wgetfpattr commands, see the TME 10 Software Distribution Reference Manual. Pulling a File Package File package requests are not supported for NetWare machines. Using UserLink for TME 10 Software Distribution, your end-users can retrieve, or download, Software Distribution profiles, which include file packages and AutoPacks, using the TME 10 UserLink interface. This interface enables an end-user to complete the following operations: Selectively download new software applications and data, or update existing software. Download software packages that were not received at a prior distribution time. File packages and AutoPacks are downloaded from a managed node in your TMR. Chapter 11, UserLink for TME 10 Software Distribution, describes the new UserLink for TME 10 Software Distribution utility and provides instructions for creating, distributing, and using UserLink for TME 10 Software Distribution. Removing a File Package You can remove distributed file packages from targets. This operation is the opposite of a distribution. For example, you may want to remove file packages if the software does not perform as expected or if you are upgrading the software application. You can easily remove an old 9 16 Version 3.6

279 Removing a File Package version of a software package before distributing the new version, rather than writing over the old version. Removing a file package does not remove the original file package from the source host or its object from the TME 10 database. You can also delete a file package. Deleting a file package does not delete the source files or directories, or the distributed files or directories, on the subscribers. This operation simply deletes the file package from the TME 10 database and its icon from the desktop. See Deleting a Profile on page 6-16 for more information about deleting a file package. The following table shows the context and role required to remove a file package from a subscriber: Operation Context Required Role Remove a file package Profile admin, senior, or super You can perform this task from the TME 10 desktop or the command line. File Package Operations TME 10 Software Distribution User s Guide 9 17

280 Removing a File Package Desktop Use the following steps to remove a file package from one or more subscribers: 1. Double-click on the icon of the file package you want to remove. Software Distribution displays the File Package Properties window Version 3.6

281 Removing a File Package 1. Select Remove from Hosts... from the File Package menu to display the Remove File Package dialog. 1. Ensure that the Remove File Package From scrolling list accurately reflects the subscribers from which to remove the file package. By default, all subscribers of the profile manager are displayed in the Available Subscribers scrolling list. To move a subscriber to the Remove File Package From scrolling list, select one or more subscribers from the Available Subscribers scrolling list and press the left arrow button. To remove a subscriber, choose one or more subscribers from the Remove File Package From scrolling list and press the Remove button. If a profile manager is listed in the Available Subscribers scrolling list, a plus sign (+) appears in front of its name. By double-clicking on the profile manager name, you can expand the list to view all subscribers to this profile manager. The managed resource type for each subscribing machine is listed next to the machine name. You can then add any of its subscribers to the Remove File Package From scrolling list. File Package Operations TME 10 Software Distribution User s Guide 9 19

282 Removing a File Package A dash (-) appears in front of the expanded profile manager. Note: If a profile manager is selected in the Available Subscribers scrolling list, you must deselect it before double-clicking on it. To compress an expanded profile manager entry, double-click on the profile manager name. You can also use the Expand All or Compress All buttons to expand or compress all profile managers in the Available Subscribers scrolling list. If you have TME 10 Inventory installed, you can select subscribers by scanning the available endpoints, managed nodes, and PC managed nodes for certain criteria defined by a query in a query library. To run a query, press the Query button to display the Execute a Query dialog. This dialog lists the available query libraries that were created using TME 10 FrameWork. To execute a query, select a query library from the Query Libraries scrolling list and press the Execute button to run the query on the configuration repository and return the names of the endpoints, managed nodes, and PC managed nodes that meet the criteria. This list automatically populates the Remove File Package From scrolling list. See the TME 10 Framework User s Guide for more information on creating and using queries Version 3.6

283 Removing a File Package 1. Select the Remove Empty Directories check box if you want Software Distribution to remove directories left empty after the file package is removed from a host. If you do not select the Remove Empty Directories check box, only files and directories contained in the file package are removed. Notes: - Selecting the Remove Empty Directories check box only removes directories associated with the parent file package. To remove directories associated with files in nested file packages, use the file package export and import capability to set the rm_empty_dirs keyword to y in each of the nested file packages. - If you distribute a file package containing directories or files to an existing, non-empty directory at the target, when you remove this file package from that target using the Remove Empty Directories option, a message similar to the following is logged to the log file: uninstall: /etc: Directory not empty where /etc is the existing, non-empty directory at the target into which some of the file package contents were distributed. Although the error message indicates that the remove operation failed, the file package s directories and files are removed from the target hosts. 1. Press the Remove & Close button to remove the file package from the subscribers and return to the File Package Properties window. If the removal fails for any subscriber, a list of subscribers where the removal failed is displayed. File Package Operations Command Line To use the wrmfp command to remove the PS_docs^2.6 file package and all of its nested file packages from all targets to which it was distributed, enter the following command: wrmfp TME 10 Software Distribution User s Guide 9 21

284 Setting Timeout Values for a Distribution where: d Leaves empty directories on the target that are not specified in the file Specifies to remove the PS_docs^2.6 file package. For more information about using the wrmfp command to remove file packages, see the TME 10 Software Distribution Reference Manual. Setting Timeout Values for a Distribution TME 10 provides server- and client-level timeout parameters that enable you to specify a time interval after which either the server or client interrupts a distribution. Setting timeout parameters can avoid hung distributions caused by the following problems: Looping or hanging scripts, including all configuration scripts or the type that require user intervention, such as closing a pop-up status window. Down nodes, including systems that are in the process of rebooting, offline, or completely disconnected from the network. Communication problems, such as breaks in the communication channel during distribution. Tivoli highly recommends that you set distribution timeouts before distributing a Software Distribution profile. These include the following: Configuration script timeout sets the progs_timeout keyword in the file package definition to specify a timeout value for configuration programs running on the client. Repeater manager timeout sets the T argument in the wrpt syntax statement to specify a server-level timeout value for all repeaters in a TMR. This value is stored on the repeater manager and designates the time each repeater must wait for each target to return distribution results after all data has been sent. High-level TCP Timeout sets the stat_intv parameter to specify a timeout value for connections between a repeater and its managed nodes and PC managed nodes. This value is set 9 22 Version 3.6

285 Setting Timeout Values for a Distribution individually for each repeater with the t option to the wrpt command. Gateway session timeout sets set_session_timeout parameter to specify a timeout value for connections between a gateway and its endpoints. This value is set individually for each gateway through the wgateway command. Depending on the timeout parameters you choose to implement in your distribution environment, you can set each timeout parameter from the command line. Additionally, you can set progs_timeout by defining a value for this keyword in the file package definition file. Default values for each timeout parameter are given in the corresponding manual page reference. Configuration Script Timeout The progs_timeout keyword sets a client-level timeout value for all configuration programs specified in the file package definition. The timeout applies separately to each configuration script and is reset as each script begins on an individual target. The value that you apply for progs_timeout should be entirely dependent on the type of operation that the script will perform on the client system. Tivoli recommends that you set the progs_timeout keyword to at least twice the amount of time that the longest script will take to run on the slowest system in your TMR. For example, consider the case in which you must check for disk space availability on the client machine before installing a file package. You can specify a before configuration script to execute this type of system check. Setting the progs_timeout keyword prior to distributing the file package enables you to control the distribution by causing the configuration program to terminate if it is unable to complete successfully or if it hangs. You can set the progs_timeout keyword by exporting and importing a file package definition, or by setting the progs_timeout keyword through the v option in the wsetfpopts command, as follows: File Package Operations wsetfpopts -T unix -v TME 10 Software Distribution User s Guide 9 23

286 Setting Timeout Values for a Distribution The v option sets a 300 second timeout value on all configuration programs specified in the TopFilePack file package. Therefore, if any configuration script is unable to complete its operation in five minutes, Software Distribution terminates the configuration program and returns a distribution error. For more information about using the export and import capability to set keywords in a file package definition, see Exporting and Importing File Package Definitions in Chapter 7. Additional information about a file package definition and the wsetfpopts command syntax is available in the TME 10 Software Distribution Reference Manual. Repeater Manager Timeout The repeater manager timeout specifies a server-level timeout value for all repeaters in a TMR. Set with the T option to the wrpt command, this timeout is stored on the repeater manager. It specifies how long each repeater node will wait for distribution status after sending the entire data stream to a target managed node or PC managed node. If the target does not respond in the allotted time, the repeater logs a distribution error and terminates its connection to the target machine. The repeater manager timeout does not apply to distributions from one repeater to another. The repeater manager timeout is set only on the repeater manager and determines a general timeout that applies to all repeaters in the entire TMR. For interconnected TMRs, you must set a timeout for each repeater manager separately. If you specify a repeater manager timeout, the timer governed by this parameter starts only after the file package is distributed to the target system. Therefore, packet-transfer time and before script configurations are not included in the measurement. If the server-level timeout is triggered, the repeater manager interrupts the connection to hanging target machines and logs an operation error. In a distribution environment where you specify a repeater manager timeout but do not specify a configuration script timeout, the repeater manager timeout is passed to each target machine as the default progs_timeout value. Tivoli suggests that you set the repeater manager timeout to a value that allows sufficient time for all configuration scripts that are launched on the client to complete. Also, if you are planning on 9 24 Version 3.6

287 Setting Timeout Values for a Distribution specifying both a configuration script timeout and a repeater manager timeout, ensure that the repeater manager timeout allows ample time for the client-level timeout to complete before it triggers its own timeout. A system error results if the repeater manager timeout is less than the progs_timeout value specified for the distribution. You can set the repeater manager timeout by configuring the T option to the wrpt command, as follows: wrpt -T 600 The T option sets a 600 second timeout value on configuration scripts that run on managed nodes and PC managed nodes in the environment. In this case, each repeater in the TMR will wait ten minutes for each of its associated target managed nodes and PC managed nodes to respond after it finishes a file package transfer. If the target system does not respond in the allotted time, the timeout is triggered, the file package distribution to this individual target is canceled, and an internal error message is logged. For more information about setting a repeater manager timeout value in the TMR, see the wrpt command syntax and usage in the TME 10 Framework Reference Manual. File Package Operations High-level TCP Timeout The stat_intv parameter specifies a timeout value for connections between a repeater and its managed nodes or PC managed nodes. The duration of the connection includes the time it takes to distribute each data packet to the target system. The stat_intv value sets a time after which a blocked connection between the repeater and the client system is terminated. If the repeater stops transmitting data to the client for an interval that exceeds the stat_intv setting, the session is terminated. Setting a high-level TCP timeout is especially useful when systems with unreliable networks experience network hangs that go undetected by the operating system TCP/IP stack. The high-level TCP timeout forces a timeout error on these connections so that the distribution can proceed to other clients. Tivoli recommends that you set the stat_intv parameter to a value greater than the time it will take the longest configuration script to run on the target. TME 10 Software Distribution User s Guide 9 25

288 Setting Timeout Values for a Distribution You can set the stat_intv parameter individually for each repeater with the t option to the wrpt command, as follows: wrpt -t machine-b stat_intv=300 The t stat_intv parameter sets a 300 second timeout value on connections between the repeater and managed nodes or PC managed nodes. In this case, the connection is terminated if no data is transmitted for five minutes from the repeater to the target. For more information about setting a stat_intv timeout value on a repeater, see the wrpt command syntax and usage in the TME 10 Framework Reference Manual. Gateway Session Timeout The set_session_timeout parameter specifies a timeout value for connections between a gateway and its endpoints. This value determines the amount of time a gateway allows an endpoint to receive the distribution data before terminating the session. The set_session_timeout parameter provides the same functionality for connections between a gateway and its endpoints as stat_intv does for connections between a repeater and it s managed nodes or PC managed nodes. During a data transfer from a gateway to an endpoint, if the endpoint stops receiving data for a period longer than the value set by the set_session_timeout parameter, the gateway terminates the distribution to that endpoint and records a timeout error. Note that the progs_timeout setting overrides the set_session_timeout setting if progs_timeout is set in the file package definition to control configuration scripts running on an endpoint. You can set the set_session_timeout parameter individually for each gateway by setting the set_session_timeout parameter in the wgateway command, as follows: wgateway odin set_session_timeout 600 The set_session_timeout parameter sets a 600 second timeout value on connections between the gateway, odin, and its endpoints. In this example, odin stops transmitting data if no data is received by the endpoint for ten minutes Version 3.6

289 Distribution Processes For more information about setting a gateway session timeout value for a gateway in the TMR, see the wgateway command syntax and usage in the TME 10 Framework Reference Manual. Distribution Processes Many options are available when creating a file package that affect how a file package distribution is performed. Such options include configuration programs, keywords that change the default behavior of file package operations (such as the nested_first keyword), and Software Distribution s use of multiplexed distribution (MDist) to distribute software to subscribers. The following examples may help you follow the order of operations that take place during distribution processes. See the TME 10 Framework Planning and Installation Guide for more information about MDist. Consider the file package structure illustrated by the following figure: File Package A (parent file package) File Package Operations File Package B (nested file package) File package B is nested in the parent file package A. Both file packages include source before, source after, (target) before, and (target) after configuration programs. The distribution examples in the following sections are based on this figure. TME 10 Software Distribution User s Guide 9 27

290 Distribution Processes Distributing File Packages TME 10 Software Distribution performs the following steps when it distributes file package A: 1. Runs the source before programs for file package A. If source before input files are specified, each source before program receives that input file as standard input. If multiple source before programs are specified, Software Distribution runs the programs in the order specified. Software Distribution logs the return value of the source before program(s) to the log file, if specified. 1. Initiates a connection from file package A s source host to the subscribers. If the subscribers are in a remote TMR or if additional repeaters are configured for the subscribers, Software Distribution initiates a connection from the source host to the repeaters. Using repeaters enables Software Distribution to provide a WAN-smart distribution model. A file package must cross network links only once rather than once for each target on the other side of the network link. To understand the significance of repeaters, to set up additional repeaters, or to change the default repeater configuration in your TME 10 environment, see the MDist information in the TME 10 Framework Planning and Installation Guide and the wrpt manual page in the TME 10 Framework Reference Manual. 1. Generates file package A to be sent to the subscribers. The beginning of this file package consists of the (target) before or after programs and their input files that were specified as residing on the source host. These programs are followed by file package A s files and directories. As Software Distribution generates this data, it sends it to the subscribers (directly or using the repeaters). 1. Runs the (target) before programs for file package A. If input files were specified, Software Distribution runs this program with its input file on the subscriber. If multiple programs are specified, Software Distribution runs the programs in the order specified Version 3.6

291 Distribution Processes If the before programs reside on the source host, Software Distribution extracts the programs and their input files from the incoming file package, places them in temporary files on the subscriber, and runs them. For UNIX subscribers, the programs receive the input files through standard input. For PC subscribers, the programs receive the input files path names as the second argument to the program. Software Distribution logs the return value of each before program to the log file, if specified, then removes any temporary before programs and input files. 1. Unpacks file package A at the target: Software Distribution distributes the files and directories included in file package A. 1. Runs the (target) after programs for file package A. If input files were specified for the after programs, Software Distribution runs the programs with the input files on the subscriber. If multiple programs are specified, Software Distribution runs the programs in the order specified. If the after programs reside on the source host, Software Distribution extracts the programs and their input files from the incoming file package, places them in temporary files on the subscriber, and runs them. For UNIX subscribers, the programs receive the input files through standard input. For PC subscribers, the programs receive the input files as the second argument to the program. Software Distribution logs the return value of each before program to the log file, if specified, then removes any temporary before programs and input files. 1. Runs the source after programs for file package A. If you specified source after input files, the source after programs receive the input files through standard input. Software Distribution runs the programs in the order specified. Software Distribution logs the return value of the source after programs to the log file, if specified. 1. Runs the source before programs for file package B. If input files were specified, each source before program receives that input File Package Operations TME 10 Software Distribution User s Guide 9 29

292 Distribution Processes file as standard input. If multiple source before programs were specified, Software Distribution runs the programs in the order specified. Software Distribution logs the return value of the source before program(s) to the log file, if specified. 1. Packages the directories and files for file package B and sends it to the distribution targets. The beginning of the file package consists of the (target) before or after programs and their input files that were specified as residing on the source host. These programs are followed by file package B s files and directories. As Software Distribution generates this data, it sends it to the subscribers (directly or using the repeaters). 1. Runs the (target) before programs for file package B. If input files were specified for the before programs, Software Distribution runs the programs with the input file on the subscriber. If multiple programs are specified, Software Distribution runs the programs in the order specified. If the before programs reside on the source host, Software Distribution extracts the programs and their input files from the incoming file package, places them in temporary files on the subscriber, and runs them. For UNIX subscribers, the programs receive the input files through standard input. For PC subscribers, the programs receive the input files path names as the second argument to the program. Software Distribution logs the return value of each before program to the log file, if specified, then removes any temporary before programs and input files. 1. Unpacks file package B at the target. Software Distribution distributes the files and directories included in file package B. 1. Runs the (target) after programs for file package B. If input files were specified for the after programs, Software Distribution runs the programs with the input files on the subscriber. If multiple programs are specified, Software Distribution runs the programs in the order specified Version 3.6

293 Distribution Processes If the after programs reside on the source host, Software Distribution extracts the programs and their input files from the incoming file package, places them in temporary files on the subscriber, and runs them. For UNIX subscribers, the programs receive the input files through standard input. For PC subscribers, the programs receive the input files as the second argument to the program. Software Distribution logs the return value of each before program to the log file, if specified, then removes any temporary before programs and input files. 1. Runs the source after programs for file package B. If you specified input files, the source after programs receive the input files through standard input. If multiple programs are specified, Software Distribution runs the programs in the order specified. Software Distribution logs the return value of the source after programs to the log file, if specified. If an on error program(s) is specified and a fatal error occurs during the distribution (or if a non-fatal error occurs and stop_on_error=y), Software Distribution runs the on error programs on the subscriber. If commit programs are specified, Software Distribution processes them after the after programs. In addition, when operations are performed on multiple subscribers, Software Distribution does not run a before program on the first subscriber and wait for that program to finish before running the before program on subsequent subscribers. It runs the programs on all subscribers at the same time. When you remove a file package from a target, Software Distribution processes the removal programs, removes the files and directories from the subscriber, and processes after removal programs. If an on error program is specified, it runs after an error stopped the removal operation. File Package Operations TME 10 Software Distribution User s Guide 9 31

294 Distribution Processes Distributing Nested File Packages First The following sequence of events takes place if the nested_first keyword is set for file package A. Note that while the nested_first keyword affects the order in which file packages are processed, configuration programs are launched in the same manner as when distributing a single file package before configuration programs run prior to installing the distributed software and after configuration programs run following the installation. Software Distribution will distribute file package A and its nested file package as follows: 1. Runs the source before programs with their input files for file package B. Because the nested_first keyword is set for nested file package B, it and all of its configuration programs are processed before its parent file package, A. 1. Initiates a connection from file package A s source host to the subscribers. If the subscribers are in multiple TMRs or if repeaters are configured for the subscribers, Software Distribution initiates a connection from the source host to the repeater in the remote TMRs. 1. Generates file package A to be sent to each distribution target. The beginning of this file package consists of file package B s before or after programs and their input files that were specified as residing on the source host. These programs are followed by file package B s files and directories, and its after programs and input files. As Software Distribution generates this data, it sends it to the subscribers (directly or using the repeaters). 1. Runs the before programs and their input files for file package B. 1. Unpacks file package B at the target. Software Distribution distributes the files and directories included in file package B. 1. Runs the after programs and the input files for file package B. 1. Runs the source after programs and the input files for file package B after Software Distribution distributes the file package to all subscribers. 1. Runs the source before programs and the input files for file package A Version 3.6

295 Distribution Processes 1. Runs the before programs and the input files for file package A. 1. Unpacks file package A at the subscribers. 1. Runs the after programs and input files for file package A. 1. Runs the source after programs and input files for file package A. File Package Operations TME 10 Software Distribution User s Guide 9 33

296 Distribution Processes 9 34 Version 3.6

297 10 10AutoPack Properties and Operations An AutoPack is a TME 10 Software Distribution profile that provides a simple and convenient way to create installable images for Windows-based PCs managed by TME 10. Using the AutoPack Control Center, you can create an AutoPack file that includes all scripts necessary to install and run a shrink wrapped application, such as Microsoft Word or Netscape Navigator, on a PC in your TME 10 environment. The AutoPack Control Center automatically determines the files that need to be distributed to the target machine and handles all Windows installation issues. With Software Distribution s AutoPack technology, you no longer need to manually script system changes required by a software package. Chapter 5, Software Deployment Using AutoPacks and the TME 10 Software Distribution AutoPack User s Guide both provide detailed information about creating and editing the properties of an AutoPack file using the AutoPack Control Center utility. After building an AutoPack file, you can distribute it via an AutoPack profile to all Windows-based subscribers NT managed nodes, endpoints, PC managed nodes, NetWare managed site clients, and other profile managers. When you distribute the AutoPack profile, the application files contained in the AutoPack file are distributed to the target machines. This chapter addresses how to set properties for, calculate the size of, and distribute an AutoPack profile. It also describes how to remove an AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 1

298 Setting AutoPack Profile Properties AutoPack from client machines, which removes all distributed files and directories on those machines and reverses any system changes performed by the AutoPack. Setting AutoPack Profile Properties Before an AutoPack profile is used to distribute an AutoPack file to your targets, you must set the AutoPack profile s properties. These properties include the name that you assign to the AutoPack profile and, more importantly, the path of the AutoPack file that you are referencing. Refer to Chapter 6, Profile Setup, for instructions about creating, cloning, and deleting profiles. As with file packages, the source host for distributing AutoPacks must be located on any managed node in your TME 10 environment. This is necessary because Software Distribution cannot initiate a profile distribution from a PC managed node or an endpoint. Therefore, to set AutoPack profile properties, complete one of the following: Manually copy the AutoPack file to a managed node if the prep machine on which it was created is not part of the TME 10 environment. Specify the AutoPack file s host and path in the managed node in the Set AutoPack Properties window if the AutoPack file was created on or copied to a managed node. Copy the AutoPack file from an endpoint, managed node, or PC managed node location in the TME 10 environment. Note: You cannot access an AutoPack file from a PC that is not managed by your TMR, such as from a NetWare managed site s client or from a prep machine that is not a managed node, endpoint, or PC managed node. In these cases, you must manually copy the AutoPack file from the client to a managed node and then complete the steps defined below Version 3.6

299 Setting AutoPack Profile Properties The following table shows the context and authorization role required for this task: Operation Context Required Role Set or edit AutoPack profile properties AutoPack admin, senior or super You can perform this operation only from the TME 10 desktop. Use the following steps to set or edit the properties of an AutoPack. 1. From the profile manager, double-click on an AutoPack icon to display the Set AutoPack Properties window. AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 3

300 Setting AutoPack Profile Properties 1. In the Managed Node field, type the name of the managed node where the AutoPack file resides. Type the full path to the file in the Path field. You can specify an AutoPack file that exists on a managed node, or you can specify a file to which the AutoPack file will be copied from an NT managed node, endpoint, or PC managed node. OR Press the ellipsis (...) button to display the Set AutoPack File Location dialog. This dialog provides a view of the available managed nodes and their directory structures. Use this browser dialog to select a managed node and AutoPack file. To select a file from the Set AutoPack File Location dialog, follow these steps: a. Select one of the listed managed nodes in the Hosts scrolling list Version 3.6

301 Setting AutoPack Profile Properties a. Double-click on the directory name in the Directories scrolling list to list the files and directories contained in that directory. Repeat this step until you find the desired file. a. Select a file from the Files scrolling list. a. Press the Set File & Close button to add the file to the Source File field, and close this dialog. 1. If you are copying an AutoPack file from a PC that is part of your TMR, you must specify the TME 10 machine from where the file will be copied as follows: a. Select the Copy file from PC managed node radio button to sensitize the Copy From section of the window. Type the name of the PC managed node where the AutoPack file resides in the PC Managed Node field. OR Press the ellipsis button (...) to open the Select AutoPack File browser dialog, which enables you to navigate through the directory tree to select a file. a. Select the Copy file from managed node radio button to sensitize the Copy From section of the window. Type the name of the managed node where the AutoPack file resides in the Managed Node field. OR Press the ellipsis button (...) to open the Select AutoPack File browser dialog, which enables you to navigate through the directory tree to select a file. a. Select the Copy file from Endpoint radio button to sensitize the Copy From section of the window. Type the name of the endpoint where the AutoPack file resides in the Endpoint Name field. The ellipsis button (...) option is not valid for endpoints. OR AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 5

302 Setting AutoPack Profile Properties Press the ellipsis (...) button in the AutoPack File section to display the Select AutoPack File dialog. This dialog provides a view of the available NT managed nodes or PC managed nodes and their directory structures. Use this dialog to select an AutoPack file to copy to the managed node selected in the AutoPack File section of the dialog. To select a file from the Select AutoPack File dialog, complete the following steps: a. Select one of the listed NT managed nodes or PC managed nodes in the Hosts scrolling list. a. Double-click on the directory name in the Directories scrolling list to list the files and directories contained in that directory. Repeat this step until you find the desired file. Note: If you need to access directories on another drive, enter N:\ in the Path Name field, where N is the desired drive letter, and press the Return key. a. Select a file from the Files scrolling list Version 3.6

303 Calculating the Size of an AutoPack a. Press the Set File & Close button to add the file to the Source File field, and close this dialog. The selected machine and file are displayed in their respective fields in the Set AutoPack Properties window. 1. Select the Save & Close button to save the AutoPack and return to the profile manager window. If you specified a file in the Copy From section of the dialog, it is copied to the specified AutoPack file location when you save the AutoPack profile s properties. If a file exists in the specified AutoPack file location, it is overwritten with the one copied from the NT managed node, or PC managed node. After setting AutoPack profile properties, you can distribute the AutoPack to its subscribers. See Chapter 6, Profile Setup, for instructions about distributing profiles to subscribers. AutoPack Properties and Operations Calculating the Size of an AutoPack Calculate the size of an AutoPack to determine the total size (in bytes) of its included application files. Note that the calculated size may be larger than the sum of the AutoPack components due to TME 10 Software Distribution data overhead. It also may not reflect the disk TME 10 Software Distribution User s Guide 10 7

304 Calculating the Size of an AutoPack space needed on the targets to install the application. The calculated size is primarily useful to gauge network load and distribution time. The following table shows the context and authorization role required for this task: Operation Context Required Role Calculate the size of an AutoPack Profile manager s policy region admin, senior, or super You can perform this task from the TME 10 desktop only. To calculate the size of an AutoPack from the desktop, complete the following steps: 1. Select Calculate size... from the AutoPack icon popup menu. Software Distribution displays the Calculate AutoPack Size dialog: 1. Press the Calculate Size button to determine and display the AutoPack size (in bytes). 1. Press the Close button to close this dialog Version 3.6

305 Distributing an AutoPack Profile Distributing an AutoPack Profile After you create an AutoPack profile and edit its properties, you can distribute it to the subscribers. Distributing an AutoPack installs the software and makes the necessary system configuration changes on the target machine. Consider the following distribution requirements: If the target is an NT managed node, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server, and the AutoPack agent must be installed on the target. If the target is an endpoint, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server, and the Software Distribution Gateway must be installed on the endpoint gateway. The AutoPack agent is automatically installed on the endpoint when the endpoint is installed. If the target is a PC managed node, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server. Both the PC agent and AutoPack agent must be installed on the target. If the target is a NetWare managed site, Software Distribution must be installed either on the target TMR server or on an interconnected TMR server. Both the Tivoli NetWare repeater (TNWR) and PC agent must be installed on the NetWare server. And both the PC agent and AutoPack agent must be installed on the NetWare managed site s clients. See Chapter 2, Installation, or the TME 10 Software Distribution AutoPack User s Guide for instructions about installing the AutoPack Control Center and the AutoPack agent. See the TME 10 Framework Planning and Installation Guide for information about installing the Tivoli NetWare Repeater (TNWR) and PC agent. Refer to the TME 10 Software Distribution AutoPack User s Guide for information about problems you may encounter as the result of how you created the AutoPack file. AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 9

306 Distributing an AutoPack Profile Note: Older versions of the AutoPack agent cannot parse an AutoPack file that is generated by the new AutoPack Control Center. If the following error appears in the PC agent error log after distribution, install a new version of the AutoPack agent on the client system and redistribute the AutoPack profile: 12/15/97 10:43:09 [E] Expecting target_dir = at \ line 3, but found target_dir=c: The following table shows the context and authorization role required for this task: Operation Context Required Role Distribute an AutoPack TME 10 Software Distribution profile admin, senior, or super Drag and Drop You can perform this task using drag and drop, from the TME 10 desktop, or from the command line. To distribute an AutoPack using drag and drop, drag the AutoPack icon and drop it onto a subscriber icon: a subscriber can be an NT managed node, endpoint, PC managed node, NetWare managed site, or profile manager. The resource must subscribe to the profile manager containing the AutoPack Version 3.6

307 Distributing an AutoPack Profile Desktop Use the following steps to distribute an AutoPack: 1. Select Distribute... from the AutoPack icon s pop-up menu to display the Distribute AutoPack dialog. 1. Ensure that the Distribute AutoPack To scrolling list accurately displays the subscribers to which to distribute the AutoPack. Perform the following actions using the scrolling lists: To move a subscriber to the Distribute AutoPack To scrolling list, choose one or more subscribers from the Available Subscribers scrolling list and press the Left arrow button. By default, all subscribers in the profile manager are displayed in the Available Subscribers scrolling list. To remove a subscriber, choose one or more subscribers from the Distribute AutoPack To scrolling list and press the Remove button. If the Available Subscribers scrolling list contains a profile manager, a plus sign (+) appears in front of its name. You can double-click on a profile manager name to display TME 10 endpoints, NT managed nodes, PC managed nodes, NetWare AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 11

308 Distributing an AutoPack Profile managed site clients, and other profile managers that subscribe to that profile manager. You can then add any of its subscribers to the Distribute AutoPack To scrolling list. Note: If you select a profile manager name in the Available Subscribers scrolling list, you must deselect it before double-clicking on it. The name of an expanded profile manager has a dash (-) in front of it in the Available Subscribers scrolling list. To compress an expanded profile manager entry, double-click on the profile manager name. Use the Expand All or Compress All buttons to expand or compress all profile managers in the Available Subscribers scrolling list. If you have TME 10 Inventory installed, you can select subscribers by scanning the available endpoints, NT managed nodes, and PC managed nodes for certain criteria defined by a query in a query library. To run a query, press the Query button to display the Execute a Query dialog. This dialog lists the available query libraries that were created using Framework. Select a query library from the Query Libraries scrolling list, then press the Execute button to run the query on the TME 10 configuration repository and return the names of the endpoints, NT managed nodes, and PC managed nodes that meet the criteria. This list automatically populates the Distribute AutoPack To scrolling list Version 3.6

309 Distributing an AutoPack Profile See the TME 10 Framework User s Guide for more information on creating and using queries. 1. Press the Schedule... button to schedule operations at a future time or to automatically retry the distribution to any target for which the distribution might fail. Software Distribution displays the Add Scheduled Job dialog. AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 13

310 Removing an AutoPack Command Line See the TME 10 Framework User s Guide for more information about creating tasks and jobs, and about using drag and drop to schedule a job. 1. Press the Distribute & Close button to begin distributing the AutoPack to the selected subscribers and dismiss the dialog. Note: The dialog is not dismissed until the distribution is complete and the operation stops. If the distribution fails for any of the subscribers, a popup dialog is displayed to inform you which subscribers failed during the distribution. This status is also displayed on the TME 10 desktop. To use the wdistrib command to distribute the Office97 AutoPack to the NTMachs profile manager, enter the following Specifies to distribute the Office97 Distributes the AutoPack to the subscribers of the NTMachs profile manager. For more information about distributing from the command line, see the wdistrib command in the TME 10 Framework Reference Manual. Removing an AutoPack You can remove AutoPacks that you have distributed to targets. You might remove an AutoPack, for example, if the software does not perform as you expected. You can easily remove an old version of a software package before distributing the new version, rather than writing over the old version. Removing an AutoPack from a client does not remove the original AutoPack from the source host or the original AutoPack s profile from the TME 10 database Version 3.6

311 Removing an AutoPack You can also delete an AutoPack profile from a profile manager. Deleting an AutoPack profile does not delete the AutoPack source file or the distributed files on the targets. This operation simply removes the AutoPack profile from the TME 10 database and deletes its icon from the desktop. See Deleting a Profile on page 6-16 for more information about deleting an AutoPack. The following table shows the context and role required to remove an AutoPack from a subscriber: Operation Context Required Role Remove an AutoPack Profile admin, senior, or super You can perform this task only from the TME 10 desktop. Use the following steps to remove an AutoPack from one or more subscribers using the desktop: 1. Select Remove from hosts... from the AutoPack icon s pop-up menu to display the Remove AutoPack dialog. AutoPack Properties and Operations All subscribers of the AutoPack s profile manager are displayed in the Available Subscribers scrolling list. TME 10 Software Distribution User s Guide 10 15

312 Removing an AutoPack 1. Ensure that the Remove From Hosts scrolling list accurately displays the subscribers from which to remove the AutoPack. To add a subscriber to the Remove From Hosts scrolling list, select one or more subscribers from the Available Subscribers scrolling list and press the Left arrow button. By default, all subscribers of the profile manager are displayed in the Available Subscribers scrolling list. To remove a subscriber, choose one or more subscribers from the Remove From Hosts scrolling list and press the Remove button. If a profile manager is listed in the Available Subscribers scrolling list, a plus (+) appears in front of its name. You can double-click on a profile manager to display names of clients that subscribe to that profile manager. You can then add any of its subscribers to the Remove From Hosts scrolling list. A dash (-) appears in front of the expanded profile manager. Note: If a profile manager is selected in the Available Subscribers scrolling list, you must deselect it before double-clicking on it. To compress an expanded profile manager entry, double-click on the profile manager name. You can also use the Expand All or Compress All buttons to expand or compress all profile managers in the Available Subscribers scrolling list. If you have TME 10 Inventory installed, you can select subscribers by scanning the available endpoints, NT managed nodes, and PC managed nodes for certain criteria Version 3.6

313 Removing an AutoPack defined by a query in a query library. To run a query, press the Query button to display the Execute a Query dialog. This dialog lists the available query libraries that were created using TME 10 Framework. To select a query to run, first select a query library from the Query Libraries scrolling list. After you select the desired query, press the Execute button to run the query on the TME 10 configuration repository and return the names of the endpoints, NT managed nodes, and PC managed nodes that meet the criteria. This list automatically populates the Remove From Hosts scrolling list. See the TME 10 Framework User s Guide for more information on creating and using queries. 1. Press the Remove & Close button to remove the AutoPack from the subscribers and close this dialog. If the removal fails for any subscriber, a dialog displays a list of subscribers where removal failed. AutoPack Properties and Operations TME 10 Software Distribution User s Guide 10 17

314 Removing an AutoPack Version 3.6

315 IV Additional Features This section contains chapters about setting up and using UserLink for TME 10 Software Distribution, enabling and using the Software Distribution history tracking feature, as well as about installing and configuring the TME 10 Enterprise Console integration with Software Distribution. It also contains chapters that describe how to create and distribute file package blocks and how to set up NetWare managed sites. Chapter 11 UserLink for TME 10 Software Distribution Activating UserLink for Software Distribution Creating a TME 10 Administrator for UserLink Desktop Command Line Using UserLink for TME 10 Software Distribution Notifying Users about UserLink Configuring the Status Dialog Chapter 12 Historical Database Feature The Configuration Repository The Query Facility Updating the Repository Enabling the Historical Database Feature Disabling the Historical Database Feature Creating SWDIST_QUERIES Query Library Running SWDISTDATA_QUERY Desktop Command Line Modifying SWDISTDATA_QUERY TME 10 Software Distribution User s Guide

316 Additional Features Chapter 13 TEC Integration Installation The tecad_sd.conf File Software Distribution Classes Chapter 14 File Package Blocks Fpblock Commands Using Fpblocks Chapter 15 NetWare Managed Sites Configuring NetWare Managed Sites Creating a NetWare Managed Site Desktop Command Line Editing NetWare Managed Site Properties Desktop Command Line Removing an Unavailable Client Desktop Command Line Additional Commands for NetWare Managed Sites Version 3.6

317 11 11UserLink for TME 10 Software Distribution This tool is not supported for NetWare OS UserLink for TME 10 Software Distribution enables an end-user on UNIX, Windows, OS/2, and AS/400 endpoints to retrieve Software Distribution profiles using the TME 10 UserLink interface. This interface enables an end-user to complete the following operations: Selectively download new software applications and data, or update existing software. Download software packages that were not received at a prior distribution time. The benefits of UserLink for TME 10 Software Distribution are easily recognized in today s increasingly mobile network computing environment. As the use of laptops and remote computing grows, the end-user is frequently disconnected from his organization s network. With the UserLink interface, this user can securely log on to the network to connect to the server, obtain a current list of available Software Distribution profiles, and retrieve necessary profiles at his convenience. Not only does this capability free you from performing repeated profile distributions to ensure that each endpoint client receives the software, it also provides your end-users with access to information or software upgrades without waiting for the next scheduled distribution. UserLink for TME 10 Software Distribution provides the same service to endpoints as the version of UserLink that is available for PC UserLink for TME 10 Software Distribution TME 10 Software Distribution User s Guide 11 1

318 Activating UserLink for Software Distribution managed nodes, in which the UserLink browser connects to the UserLink/DHCP service (usrlnkd). However, UserLink for Software Distribution differs from other versions of UserLink in the following ways: UserLink for Software Distribution is available specifically for UNIX, Windows, and OS/2 endpoints using Tivoli s lightweight client architecture. UserLink for Software Distribution uses a new web-based TME 10 UserLink interface. As a result, an end-user can request file package and AutoPack distributions using an industry-standard, Java-enabled Internet browser, such as Netscape Navigator or Microsoft Internet Explorer. UserLink for Software Distribution uses a different communication protocol to connect to the server. With UserLink for Software Distribution, the TME 10 UserLink browser communicates directly with the server oserv, which forwards the request to the TME 10 HTTP daemon (HTTPd). The HTTPd processes the client request and outputs information in HTML form about available Software Distribution profiles to which the user is subscribed. This information is then displayed on the client browser. For more information about the HTTPd and network communications, refer to the TME 10 Framework Planning and Installation Guide. Activating UserLink for Software Distribution Enabling UserLink for TME 10 Software Distribution on an end-user machine involves the following steps: Setting up preliminary UserLink files on the endpoint TME 10 Framework installs these files when you configure a client machine as an endpoint. Installing support for a UserLink authentication realm TME 10 Software Distribution enables this support when you install Software Distribution, Version 3.6, on the TMR server. Activating user access to UserLink for Software Distribution by assigning a UserLink administration role to a TME 10 administrator Version 3.6

319 Activating UserLink for Software Distribution Creating a TME 10 Administrator for UserLink In order to grant end-users network privileges to access UserLink for TME 10 Software Distribution, you must create a TME 10 administrator for UserLink and add the new SWDist_end_user role. Enabling access privileges will allow end-users to securely connect to the TMR server and download Software Distribution profiles to which they are subscribed. After you have installed TME 10 Software Distribution, Version 3.6, you can use either the TME 10 desktop or the command line to create the TME 10 administrator for UserLink. When you create this administrator, Tivoli sets up an administrator object with access to UserLink and enables you to add login names to grant access to authorized users. Note that you can specify login access by individual user identifications (UID) or by a common UID that you have set up for a group of users. In either case, you must have a valid set of UIDs for your environment. The following procedure briefly demonstrates how to create a TME 10 administrator specifically for UserLink for Software Distribution. It also shows how to initialize a list of authorized users for this TME 10 administrator. See the TME 10 Framework User s Guide for more information about creating and using TME 10 administrators in your TMR environment. The following table provides the authorization roles required to perform this task: UserLink for TME 10 Software Distribution Operation Context Role Create and add users to the UserLink administration role Administrators resource senior TME 10 Software Distribution User s Guide 11 3

320 Activating UserLink for Software Distribution Desktop Use the following steps to create the UserLink administration role: 1. Select Create Administrator from the Administrator icon pop-up menu to display the Create Administrator dialog. a. Enter the name of the administration role in the Administrator Name/Icon Label text field. a. Enter a user login name (not a numeric user ID) in the User Login Name text field. The user login name must be a valid login name. a. Enter the administrator s group name (not a numeric group ID) in the Group Name text field Version 3.6

321 Activating UserLink for Software Distribution 1. Press the Set TMR Roles button to set the TMR roles for the new administrator and display the Set TMR Roles dialog. Currently, TME 10 Software Distribution and TME 10 Inventory are accessible through the UserLink interface. You can enable access to one or both of these applications by adding the appropriate administration role. Note that you should enable both roles if users will have access to both applications in the web interface. In this example, only access to UserLink for TME 10 Software Distribution is enabled through the SWDist_end_user role. For information about setting up and using UserLink for TME 10 Inventory, see the TME 10 Inventory User s Guide. Complete the following steps to set the UserLink administration role: a. Choose the SWDist_end_user role from the Available Roles scrolling list and press the left arrow button. This role is moved from the Available Roles scrolling list to the Current Roles scrolling list. OR You can also double-click on SWDist_end_user in the Available Roles scrolling list to automatically move it to the Current Roles scrolling list. UserLink for TME 10 Software Distribution TME 10 Software Distribution User s Guide 11 5

322 Activating UserLink for Software Distribution a. Press the Set & Close button to accept your changes and return to the Create Administrator dialog. Note: Tivoli automatically authorizes all users who are assigned the senior, super, user, and admin roles access to UserLink. For example, if you have assigned psmith with the user role, do not add this user name in the Set Login Names dialog psmith will be able to access UserLink from any system with a valid login. 1. Press the Set Logins button to set the login names for users who will be able to access UserLink for TME 10 Software Distribution. The Set Login Names dialog is displayed. Complete the following steps to add login names: a. To add a login name, enter the user s login name in the Add Login Name text field and press the Enter key. Note: The login name must be a valid user ID in your environment. Tivoli recommends that all login names be qualified for a specific machine. This helps ensure the security and integrity of your distributed system by limiting the locations from which a desktop or CLI command may be initiated. The new login name is added to the Current Login Names scrolling list Version 3.6

323 Command Line Activating UserLink for Software Distribution a. If you want to add more than one login, repeat this step for each login that you wish to add. a. Press the Set & Close button to accept your changes and return to the Create Administrator dialog. To use the wcrtadmin command to create a TME 10 administrator specifically for UserLink for TME 10 Software Distribution, enter the following command. wcrtadmin -l adent -l jchen -l mgarza -l wwarren \ UserLink where: l adent l jchen l mgarza l wwarren Sets up a TME 10 login for each user specified. The login parameter must be a valid login name not a numeric user ID. UserLink Specifies the UserLink for Software Distribution administration role. Enter this parameter exactly as shown to ensure that the authorization is set correctly. UserLink for TME 10 Software Distribution To add login names to the UserLink administrator after creating it, enter the following command: wsetadmin -l tford -l ngupta UserLink where: l tford l ngupta Adds the specified logins. UserLink Specifies the name of the TME 10 administrator whose properties are changed. See the TME 10 Framework Reference Manual for information about wcrtadmin and wsetadmin command syntax and usage. Rather than entering each new login name individually through the TME 10 dialog TME 10 Software Distribution User s Guide 11 7

324 Using UserLink for TME 10 Software Distribution or with the wsetadmin command, you may want to create a script to automate this process. Using UserLink for TME 10 Software Distribution After you have created the TME 10 administrator for UserLink for Software Distribution, authorized end-users can view and download new or updated Software Distribution profiles to which they are subscribed using the TME 10 UserLink interface. You will have to notify users to connect to UserLink for TME 10 Software Distribution each time new file package or AutoPack profiles are available that you wish them to download. End-users connect to UserLink for Software Distribution by opening the X:\etc\Tivoli\C\userlink.htm file with a Web browser, where X specifies the drive on which the endpoint code is installed. This displays the primary TME 10 UserLink access page Version 3.6

325 Using UserLink for TME 10 Software Distribution Note: This sample page shows the English version of the TME 10 UserLink access page. When instructing users to launch the userlink.htm page, ensure that they are asked to open the correct language-specific file. In this case, including the /C directory in the path name launches the English version. Opening the X:\etc\Tivoli\jp_JP\userlink.htm file starts the Japanese version, and so on. See the TME 10 Software Distribution Release Notes for a current listing of supported languages for this release. The primary access page provides a UserLink for TME 10 link that dynamically loads information for all UserLink interfaces to TME 10 applications that are installed on the client system. UserLink for TME 10 Software Distribution is available from the secondary access page as illustrated in the following diagram: UserLink for TME 10 Software Distribution When a user selects the UserLink for TME 10 Software Distribution link, the browser authenticates the user s login name and password, and if successful, queries the server and generates a list of file package TME 10 Software Distribution User s Guide 11 9

326 Using UserLink for TME 10 Software Distribution and AutoPack profiles to which this user s machine is subscribed. The user can then download any of the available profiles for his machine. Notifying Users about UserLink Instruct users to complete the following steps to connect to and use UserLink for Software Distribution: 1. Connect to TME 10 UserLink by opening the X:\etc\Tivoli\en_US\userlink.htm file with a Web browser. The primary access page is displayed. If you have not already bookmarked the TME 10 UserLink web page, create a bookmark so that you can easily and directly access TME 10 UserLink Version 3.6

327 Using UserLink for TME 10 Software Distribution 1. Select the UserLink for TME 10 link to open the secondary access page. This page provides an interface to all Tivoli applications that you are authorized to use. UserLink for TME 10 Software Distribution 1. Select the UserLink for TME 10 Software Distribution link to connect to the TME 10 Software Distribution interface. TME 10 displays the following Username and Password Required authentication dialog: TME 10 Software Distribution User s Guide 11 11

328 Using UserLink for TME 10 Software Distribution Enter your user name and password in the text fields. If you are unsure about or need to verify your user name and password, contact your system administrator. 1. The UserLink for TME 10 Software Distribution web page is displayed if UserLink successfully connects to the network. The following properties are listed for each software package: Package Name The name of the file package or AutoPack, which contains the software, as defined during its creation. Size The size of the software package (in bytes). This information is available to the UserLink browser if your system administrator performed an operation to calculate file package size when creating it. Contact your system administrator if this information is not available Version 3.6

329 Using UserLink for TME 10 Software Distribution Version The version of the software package available for you to download. This versioning information is available to the UserLink browser if your system administrator specified it when creating the software package. 1. Choose the software packages that you wish to download by selecting the corresponding check box in the Select column. Press the Reset button at any time to clear all selections and resume choosing packages you wish to download. 1. To start downloading the chosen file packages, press the Install button. The UserLink browser connects to the server and starts to download the selected package. 1. On Windows-based systems, UserLink for TME 10 Software Distribution displays the following dialog to track download status. UserLink for TME 10 Software Distribution During a distribution, the status dialog tracks what percentage of software has downloaded, the status of the distribution, and the remaining distribution time. Closing the status dialog stops tracking the distribution progress it does not stop the distribution itself. TME 10 Software Distribution User s Guide 11 13

330 Using UserLink for TME 10 Software Distribution 1. When the download is complete, UserLink for TME 10 for Software Distribution displays the following status page to inform you if the download completed successfully or if it failed. 1. Close the UserLink browser by selecting Exit from the File menu. Contact your system administrator if the distribution fails, or if you would like more information about using UserLink for TME 10 Software Distribution. Configuring the Status Dialog Windows Only By default, status tracking runs automatically on Windows endpoints to track the progress of distributions each time an end-user downloads a Software Distribution profile. You can create a UserLink.ini file that will enable you to configure parameters in the status tracking feature Version 3.6

331 Using UserLink for TME 10 Software Distribution To create this file, open a text editor, such as Notepad, and create the following UserLink.ini file in the X:\etc\Tivoli\ directory, where X specifies the drive on which the endpoint code is installed. Showstatus=1 Set the Showstatus keyword to 1 to display the status dialog. Set the Showstatus parameter to zero (0) to deactivate the status tracking feature if your users do not want to display download status on the endpoint. StatusTimeout=0 Set the StatusTimeout keyword to specify a timeout value for the status dialog after a distribution has completed or if the process is hung. Specify a value in seconds; the default is zero (0) seconds, which displays the status dialog until the user closes the dialog box, restarts Windows, or if the distribution ends. Tivoli strongly recommends that you leave StatusTimeout set to 0 so that the dialog remains open to display problems that may have occurred with the distribution. UserLink for TME 10 Software Distribution TME 10 Software Distribution User s Guide 11 15

332 Using UserLink for TME 10 Software Distribution Version 3.6

333 12 12Historical Database Feature This feature requires TME 10 Inventory. TME 10 Software Distribution provides a historical database feature that automatically updates the TME 10 Inventory configuration repository with information about file packages, AutoPacks, and file package blocks (fpblocks) that have been installed on or removed from TME 10 clients. Using the TME 10 Framework query facility, you can retrieve information from the configuration repository concerning successful or failed Software Distribution operations that have occurred in your TMR. The historical database feature frees you from having to write scripts to periodically update the configuration repository when software is distributed or removed in your TME 10 environment. This chapter provides a brief conceptual overview of the TME 10 Framework query facility and the configuration repository that Software Distribution shares with TME 10 Inventory. It also describes how to enable the Software Distribution historical database capability and how to access information from the configuration repository. In order to use this Software Distribution feature, you must already have installed and be familiar with TME 10 Inventory as well as with the Framework query facility. Refer to the TME 10 Inventory User s Guide and the TME 10 Framework User s Guide for more information regarding each of these products. Historical Database Feature TME 10 Software Distribution User s Guide 12 1

334 The Configuration Repository The Configuration Repository Inventory and Software Distribution store information in the configuration repository, which is a relational database management system (RDBMS) that holds information about system configurations in your TME 10 environment. Inventory provides the scripts necessary to create the configuration repository as well as to install the configuration repository schema. TME 10 Inventory must be installed before information about distributions can be stored in the configuration repository. Software Distribution updates the configuration repository with new or updated information about file packages, AutoPacks, and fpblocks that have been installed on or removed from target machines in your environment. Note: The configuration repository is separate from the actual TME 10 object database. For more information about the configuration repository, see the TME 10 Framework User s Guide. The Query Facility The TME 10 Framework query facility, which consists of query libraries and queries, enables you to use SQL query functions to access information stored in the configuration repository. In the TME 10 environment, a query library is used to create and manage TME 10 queries, which specify which view or table to search within the repository and what information to retrieve. A view enables you to easily access information from one or more tables, and consists of derived instances from a single table or from the relational joining of multiple tables. TME 10 Inventory has several pre-defined views and queries that you can use to easily access information from the configuration repository without having to create a specific query library or individual queries. Software Distribution provides a script to populate a unique query library, named SWDIST_QUERIES, with pre-defined views, tables, and queries. For more information about the query library and queries, refer to the TME 10 Framework User s Guide and the TME 10 Inventory User s Guide Version 3.6

335 Updating the Repository Updating the Repository TME 10 Software Distribution stores and updates information in the following tables in the configuration repository: INSTALLED_SW_COMPONENT Stores the history of Software Distribution operations. Specifically, it stores information about the machine on which an operation was performed (such as a file package distribution or removal), the time at which this operation occurred, the name of the profile that was distributed or removed, and the result of the operation. SOFTWARE_COMPONENT Stores information about software names and versions that have been distributed or removed, and links this information to profile identifications. SOFTWARE_FILEPACK Stores information about software file package identification and relates this information to a file package, AutoPack, or file package block and the source host. Each of these tables is updated after a successful or unsuccessful operation. Note, however, that not all columns in these tables are necessarily updated after an operation. You can retrieve information from these tables about the results of specific distribution or removal attempts by running the query, SWDISTDATA_QUERY, against the pre-defined view, SWDISTDATA_VIEW. Information about the Software Distribution view, query, and tables is provided in the TME 10 Inventory User s Guide. Inventory also provides the TME 10 Configuration Repository schematic poster, which illustrates table and column associations in the configuration repository. Historical Database Feature Enabling the Historical Database Feature The historical database feature is installed with TME 10 Software Distribution Historical Database, Version 3.6, which enables Software TME 10 Software Distribution User s Guide 12 3

336 Enabling the Historical Database Feature Distribution to access and update the configuration repository. This feature is already available if you installed the TME 10 Software Distribution Historical Database, Version 3.6, component from the Install Product dialog during the initial installation process. See Chapter 2, Installation for instructions if you have not yet installed the Historical Database feature. Note: The Historical Database feature requires TME 10 Inventory. You must already have TME 10 Inventory installed to complete the following procedures. Before Software Distribution information about target machines can be stored in the configuration repository, you must run an Inventory hardware scan on each target machine that will receive file package, AutoPack, and fpblock distributions. An Inventory profile scans each target machine and populates the configuration repository with new or updated information about each target. Complete the following steps on any target machines that will receive file package, AutoPack, and fpblock distributions, but have not been scanned: 1. Create an Inventory profile. The TME 10 Inventory User s Guide describes how to create an Inventory profile. 1. Customize the Inventory profile to include only a hardware scan. By default, an Inventory profile scans the target machine for both software and hardware information. To track Software Distribution operations, however, only a hardware scan is needed, and customizing the profile to scan only for hardware configuration data will save time. The TME 10 Inventory User s Guide describes how to customize an Inventory profile. 1. Distribute the Inventory profile to each target machine that will receive file packages, AutoPacks, and fpblocks. For Software Distribution s purposes, only those target machines for which you want to track distribution information need be scanned. The TME 10 Inventory User s Guide describes how to distribute an Inventory profile to target machines Version 3.6

337 Disabling the Historical Database Feature Disabling the Historical Database Feature You can disable and then re-enable the historical database feature from the command line to control when distribution information is posted to the configuration repository. The feature is automatically enabled when you install the TME 10 Software Distribution Historical Database. Tivoli suggests that you disable this feature prior to deploying a file package for which you do not want to track distribution statistics. Re-enable the feature to resume tracking distribution information in the configuration repository. The following table provides the authorization role required to perform this task: Operation Context Required Role Disabling and re-enabling the historical database feature Command line senior or super You can perform this task only from the command line by entering the following command: wswdistrim {-c -d} where: c Re-enables the historical database feature. d Disables the historical database feature. For more information about the wswdistrim command usage and syntax, see the TME 10 Software Distribution Reference Manual. Historical Database Feature Creating SWDIST_QUERIES Query Library In the TME 10 environment, a query library facility provides a way to create, manage, and logically organize TME 10 queries. For example, you could create a query library to hold queries that selectively retrieve information about each Software Distribution profile type. TME 10 Software Distribution provides the swdist_queries.sh script that you can run to automatically install a query library and a pre-defined query. TME 10 Software Distribution User s Guide 12 5

338 Creating SWDIST_QUERIES Query Library This script creates the SWDIST_QUERIES query library and populates it with the pre-defined query SWDISTDATA_QUERY. Run the swdist_queries.sh script in the TMR from which you want to query the configuration repository. Because queries and query libraries must have unique names in a TMR, you can have only one set of the Software Distribution queries in a TMR or in a set of interconnected TMRs. For information about creating additional query libraries and queries, see the TME 10 Inventory User s Guide. The following table provides the authorization roles required to perform this task: Operation Context Required Role Create Software Distribution queries Policy region senior or super Complete the following steps to create the SWDIST_QUERIES query library and the Software Distribution query: 1. Select the policy region in which you want to create the query library that will contain the Software Distribution query library. 1. Add the QueryLibrary managed resource type to the policy region. See the TME 10 Framework User s Guide for more information about adding managed resources to a policy region. 1. Copy the script swdist_queries.sh from the $BINDIR/TME/COURIER/SCRIPTS/ directory on the TMR server to a temporary directory. 1. From the directory in which the script now resides, log in as a Tivoli administrator Version 3.6

339 Running SWDISTDATA_QUERY 1. Run the swdist_queries.sh script by entering the following command: swdist_queries.sh region name where: region Specifies the name of the policy region in which the query library will be created. name Specifies the name of the new query library. Specifying a name here is optional; if you do not designate a name, the query library will be named SWDIST_QUERIES. TME 10 adds the new query library in the designated policy region as follows: Running SWDISTDATA_QUERY The following steps briefly describe the process of running a query from the SWDIST_QUERIES query library and of saving the query results to standard output or a file. Historical Database Feature TME 10 Software Distribution User s Guide 12 7

340 Running SWDISTDATA_QUERY The following table provides the authorization role required to perform this task: Operation Context Required Role Run a query Query library senior or super Desktop You can perform this task from either the TME 10 desktop or the command line. Complete the following steps to run the predefined query, SWDISTDATA_QUERY, from the SWDIST_QUERIES query library. 1. Double-click on the SWDIST_QUERIES query library icon to display the SWDIST_QUERIES dialog. This query library contains the predefined query, SWDISTDATA_QUERY. TME 10 displays the following query library dialog: 12 8 Version 3.6

341 Running SWDISTDATA_QUERY 1. To run this query, right-click on the SWDISTDATA_QUERY icon and select the Run Query... button. OR Right-click on the SWDISTDATA_QUERY icon and select Edit Query... to open the Edit Query dialog. From this dialog, press the Run Query button. The Run Query dialog is displayed, showing the results of the SWDISTDATA_QUERY in tabular form. The following example dialog illustrates a portion of the results that are displayed: Historical Database Feature TME 10 Software Distribution User s Guide 12 9

342 Running SWDISTDATA_QUERY 1. You can save the results of the query from the Run Query dialog by completing the following steps: a. On the Run Query dialog, press the Export... button. The Export Query Results dialog is displayed. a. In the Host field, enter the name of the machine on which you would like to save the results file. a. In the File field, enter a directory and name for the query results file. OR Press the ellipses (...) button to browse the file system. a. Select one of the Delimiter options to specify how to separate entries in the query results file. If you want to use a delimiter other than a comma or a tab, select Custom and enter a delimiter in the field. a. Select the Print Headers check box if you want the output file to include the query name and the names of the columns. a. Press the Save & Close button to create the file Version 3.6

343 Command Line Modifying SWDISTDATA_QUERY Use the wrunquery command to run SWDISTDATA_QUERY and either display the results to standard output or save the results to a file. Enter the following command: wrunquery -n -h pescado -f /tmp/query.txt -d ";" / SWDISTDATA_QUERY where: n Omits headers from the results file. h pescado Specifies pescado as the name of the machine on which to store the file. f /tmp/query.txt Specifies /tmp/query.txt as the location and name of the query results file. d ";" Specifies a semi-colon as the delimiter. SWDISTDATA_QUERY Specifies the name of the query to be run. For more information about the wrunquery command, see the TME 10 Inventory User s Guide. Modifying SWDISTDATA_QUERY As illustrated in the Run Query dialog on page 12-9, SWDISTDATA_QUERY retrieves and posts an extensive list of Software Distribution information that includes data about machine name and identification, profile type and identification, source host name, whether the operation completed successfully, and the time of completion. You can also create a customized query based on the parameters defined in SWDISTDATA_QUERY. Customizing a query enables you to search for more specific information concerning software distributions and removals in your TME 10 environment. An example of how to create a custom query follows. The TME 10 Inventory User s Guide provides detailed descriptions of how to create, edit, and run queries. Historical Database Feature TME 10 Software Distribution User s Guide 12 11

344 Modifying SWDISTDATA_QUERY The following query example in this section briefly demonstrates how to create a new query that retrieves information about failed AutoPack distributions. Several of SWDISTDATA_QUERY s parameters are used in setting up this customized query. In order to keep the example brief, only fields that are specific to customizing this search are described. See the TME 10 Inventory User s Guide for more detailed instructions and examples. The following table provides the authorization role required to perform this task: Operation Context Required Role Edit a query Query library senior or super You can perform this task from either the TME 10 desktop or the command line Version 3.6

345 Modifying SWDISTDATA_QUERY Desktop Complete the following steps to edit SWDISTDATA_QUERY from the TME 10 desktop: 1. In the SWDIST_QUERIES query library, select Query from the Create menu. The Create Query dialog is displayed. Historical Database Feature 1. In the Query Name field, enter AutoPack_Dist_Failed 1. In the Description field, enter Failed AutoPack distributions. 1. Select inventory from the Repository menu. TME 10 Software Distribution User s Guide 12 13

346 Modifying SWDISTDATA_QUERY 1. In the Table/View Name field, enter SWDISTDATA_VIEW and press the Set button to populate the Available Columns field. 1. Use the left arrow button to move the following columns from the Available Columns scrolling list to the Chosen Columns scrolling list: TME_OBJECT_LABEL SOFTWARE_COMPONENT_NAME FILEPACK_TYPE INSTALLED_FILEPACK_TIME ACTION_COMPLETED 1. To create the SQL statement to query for AutoPack distributions and removals, complete the following steps to add a condition in the Where Clause field: a. In the Column Name field, enter FILEPACK_TYPE. You can also press the (...) ellipses button and select FILEPACK_TYPE from the list of column names. This list displays the columns in the Chosen Columns scrolling list. a. Leave equals (=) as the logical operator. a. Press the ellipses (...) button in the Column Value section. Select AUTOPACK and press the Close button. a. Press the Add button to add the first criteria to the Where Clause field. a. In the Column Name field, enter ACTION_COMPLETED. a. In the Column Value field, enter DISTRIBUTED-FAILED. a. Press the Add button to add the second criteria to the Where Clause field Version 3.6

347 Modifying SWDISTDATA_QUERY 1. Press the Create button to save the query. Press the Run Query button to query from this dialog. OR Press the Create & Close button to return to the query library window. Right-click on the SWDIST_AutoPack icon and select the Run Query... button. TME 10 Inventory returns the following results: Command Line Use the following command to create the example AutoPack query: wcrtquery -d "Failed AutoPack distributions" \ -r inventory -v SWDISTDATA_VIEW -c TME_OBJECT_LABEL \ -c SOFTWARE_COMPONENT_NAME -c FILEPACK_TYPE \ -c INSTALLED_FILEPACK_TIME -c ACTION_COMPLETED \ -w "(FILEPACK_TYPE='AUTOPACK')" \ -w "(ACTION_COMPLETED='DISTRIBUTION-FAILED')" \ SWDIST_QUERIES AutoPack_Dist_Failed For more information about the wcrtquery command, see the TME 10 Inventory User s Guide. Historical Database Feature TME 10 Software Distribution User s Guide 12 15

348 Modifying SWDISTDATA_QUERY Version 3.6

349 13 13TEC Integration This feature requires Version 3.6 of TME 10 Software Distribution, TME 10 Enterprise Console Server, and TME 10 Enterprise Console. TME 10 Software Distribution TEC Integration enables Software Distribution to send events to the TME 10 Enterprise Console s event server when a Software Distribution operation is performed. In the TME 10 environment, an event is classified as any significant change in the state of a system resource, network resource, or network application. After the TEC Integration product is installed, Software Distribution automatically generates events based on its operations successful or failed distributions, commit operations, or removals and sends these events to the TEC event server. This provides a means for centrally collecting Software Distribution events and triggering actions that can be treated in the same fashion as events from other sources or even be correlated with other events. This chapter explains how to install and enable the Software Distribution TEC Integration product component. It also provides a description of the Software Distribution event configuration file and event classes. You must be familiar with the Enterprise Console application and its manuals, specifically the TME 10 Enterprise Console User s Guide, and the TME 10 Enterprise Console Adapters Guide. These materials provide conceptual and instructional information about events, event adapters, and classes. TEC Integration Installation To install and use the TME 10 Software Distribution TEC Integration product, you must first have Version 3.6 of TME 10 Software TME 10 Software Distribution User s Guide 13 1

350 Installation Distribution, TME 10 Enterprise Console, and the TME 10 Enterprise Console Server installed in your TMR. If you are upgrading these products from a previous version, you also must upgrade the RDBMS database installation. Installing a current version of TME 10 Enterprise Console without updating the database may lead to problems with viewing events in the event console. Refer to the TME 10 Enterprise Console User s Guide for more information about installing and using the TME 10 Enterprise Console server and console, and about upgrading the RDBMS database. Prior to installing and using Software Distribution TEC Integration, you must create an event console on the TME 10 desktop, as follows: 1. From the TME 10 desktop, select Event Console... from the Create menu. The Create Event Console dialog is displayed. 1. Select the event server on which the event console will reside from the Available Hosts scrolling list and press Create. An event console icon is placed on the desktop Version 3.6

351 Installation Complete the following steps to install and use Software Distribution TEC Integration: 1. Follow the directions described in Chapter 2, Installation to install the TEC Integration product on the event server in the TMR. When you install the TEC Integration, the Install Options dialog is displayed. This dialog enables you to set a rule base to manage events. Installing the TEC Integration product installs the tecad_sd.baroc file to the $DBDIR/TME/COURIER directory. In the Install Options dialog, you can either enter a rule base that you have defined or you can choose the currently active rule base. Note that you cannot edit the default rule base you must create a new rule base if you want to add event classes and rules that are not part of the default rule base. You can import the Software Distribution class definitions from the tecad_sd.baroc file located in the $DBDIR/TME/COURIER/ directory on the TEC server. Note that Software Distribution does not supply a predefined rule set. For information about creating and using rule bases, see the TME 10 Enterprise Console Rule Builder s Guide. TEC Integration TME 10 Software Distribution User s Guide 13 3

352 Installation 1. After the TEC Integration product is successfully installed, you must stop and restart the event server to activate the Software Distribution event classes. To stop and restart the server from the TME 10 desktop, complete the following steps: a. Right-click on the EventServer icon and select the Shut Down button. a. To restart the event server after it has successfully shut down, right-click on the EventServer icon and select the Start-up button. For more information about starting and stopping the event server from the TME 10 desktop or from the command line, see the TME 10 Enterprise Console User s Guide. 1. Edit the tecad_sd.conf file as follows to include any event filtering instructions. This file is installed with Software Distribution and is located in the $DBDIR/.sd_tec/ directory. The tecad_sd.conf file is discussed in greater detail in The tecad_sd.conf File on page Version 3.6

353 Installation 1. Select Assign Event Groups... from the event console s icon menu. The Assign Event Groups dialog is displayed. Complete the following steps to assign the Software Distribution group: a. Ensure that the Software Distribution event group is listed in the Assigned Event Groups scrolling list. To move this event group, select Software Distribution from the Unassigned Event Groups list and press the right arrow button. a. Highlight the Software Distribution event group in the Assigned Event Group scrolling list and choose the appropriate administration roles. Press the Set & Close button to save and close this dialog. 1. To view the events sent to this event console, select Monitor... from the event console s icon menu. The TME 10 Enterprise TEC Integration TME 10 Software Distribution User s Guide 13 5

354 Installation Console window containing the Software Distribution event source is displayed. 1. To view the event notices, press the Software Distribution event group button. The Software Distribution window is displayed Version 3.6

355 The tecad_sd.conf File The tecad_sd.conf File The Software Distribution window lists all TME 10 Software Distribution events in the scrolling list. These events are described fully in Software Distribution Classes on page The tecad_sd.conf configuration file for Software Distribution TEC Integration initially has the following default keyword entries: ServerLocation= ConnectionMode=connection_oriented ServerPort=0 The keywords are as follows: ServerLocation Specifies the or a fully qualified identifier if multiple TEC servers are running in an interconnected TMR environment. To obtain the event server identifier, enter the following command from the command line: wlookup -ar EventServer See the TME 10 Framework Reference Manual for more information about the wlookup command. ConnectionMode Specifies the connection mode to use to connect to the event server. Valid values are connection_less, connection_oriented, CO, and co. The default value is connection_oriented, which specifies that the connection with the event server is maintained for all events sent. A new connection is established only if the initial connection is lost. When connection_less is specified or used by default, a new connection is established (and discarded) for each event that is sent. ServerPort Specifies the fixed reception port number on which the TEC server listens for connection and adapter input. This keyword value should be set to 0 (the default TEC Integration TME 10 Software Distribution User s Guide 13 7

356 The tecad_sd.conf File value) on UNIX systems unless the portmapper is not available on the server. If the TEC server is an NT box, the ServerPort should be set to the value of the tec_recv_agent_port entry in the.tec_config file. See the TME 10 Enterprise Console Adapters Guide for more infortunium about the server port specification on Windows NT machines. If the port number is not specified, the value is retrieved by calling the portmapper. ServerPort can contain up to eight values, separated by commas. Specify one port number regardless of the number of ServerLocation values specified. However, if you specify more than one port number, you must specify a corresponding port number for each ServerLocation value. The default is 0. By default, Software Distribution sends all events to the event server. You can optionally specify event filters that indicate which events should not be sent. You can specify as many event filter entries as needed. To do so, you can include a Filter entry in the tecad_sd.conf file, as follows: Filter Specifies how events are filtered. Filter statements are used by the FilterMode entry to determine which events should be discarded. An event matches a Filter statement if each slot=value in the Filter statement is identical to the corresponding slot=value in the event. A Filter statement must contain the event class and can include any other slot=value that is defined for the event class. The format of the Filter statement is: Filter:Class=classname;slot=value;...;slot=value Each Filter statement must be contained in a single, 512 character (maximum) line and cannot contain spaces. The class name specified for an event filter entry must match a defined class name see Software Distribution Classes on page 13-9 for a listing of classes for Software Distribution Version 3.6

357 Software Distribution Classes For example, you can include the following entry in the tecad_sd.conf file to discard all events generated when the removal operation begins. Filter:Class=Remove_Start; The filtering behavior can be modified by using the environment variable FilterMode. By default, FilterMode is set to OUT. By adding FilterMode=IN to the configuration file, only the events that match the filters are delivered to the event server. See the TME 10 Enterprise Console Adapters Guide for detailed information about filtering. If you make any changes to the tecad_sd.conf file, you must stop and restart the event server for the changes to take effect. Software Distribution Classes This list of classes is provided for reference only. Do NOT edit the tecad_sd.baroc file. The following table lists the class name of all events defined by Software Distribution. Specifically, these classes are defined in the tecad_sd.baroc file. When you install the Software Distribution TEC Integration, these classes are compiled and included in the event server s rule base. Use this listing to understand how Software Distribution events are mapped to Enterprise Console events. The following events are defined in the tecad_sd.baroc file. See the TME 10 EIF User s Guide for more information about the syntax of.baroc files. Distribution_Start Event Slots Notes severity distribution_id fp_name fp_size distribution_operation distribution_type num_targets sub_source By default, severity = HARMLESS and sub_source = courier. TEC Integration TME 10 Software Distribution User s Guide 13 9

358 Software Distribution Classes Remove_Start Event Slots Notes More_Failed_Targets severity distribution_id fp_name fp_size distribution_operation distribution_type num_targets sub_source fp_name sub_source targets_failed targets_failed02 targets_failed03 targets_failed04 targets_failed05 targets_failed06 targets_failed07 targets_failed08 targets_failed09 targets_failed10 targets_failed11 targets_failed12 targets_failed13 targets_failed14 By default, severity = HARMLESS and sub_source = courier. This class is used when the targets_failed slot in any class causes the event to exceed 4 KB. This event is generated until the list of failed targets is complete. By default, sub_source = courier Version 3.6

359 Software Distribution Classes Distribution_Error Dist_All_Failed Commit_All_Failed Dist_Commit_All_Failed Remove_All_Failed Dist_Some_Failed Event Slots Notes Commit_Some_Failed distribution_id sub_source fp_name number_successful number_failed targets_failed targets_failed02 targets_failed03 targets_failed04 targets_failed05 targets_failed06 targets_failed07 targets_failed08 targets_failed09 targets_failed10 targets_failed11 targets_failed12 targets_failed13 targets_failed14 severity msg severity msg severity msg severity msg severity msg severity msg All Software Distribution error classes inherit from this class. By default, sub_source = courier. By default, severity = FATAL. This class inherits from Distribution_ Error. By default, severity = FATAL. This class inherits from Distribution_ Error. By default, severity = FATAL. This class inherits from Distribution_ Error. By default, severity = FATAL. This class inherits from Distribution_ Error. By default, severity = MINOR. This class inherits from Distribution_ Error. By default, severity = MINOR. This class inherits from Distribution_ Error. TEC Integration TME 10 Software Distribution User s Guide 13 11

360 Software Distribution Classes Dist_Commit_Some_Failed Remove_Some_Failed Dist_Failed Commit_Failed Dist_Commit_Failed Remove_Failed Dist_Successful Commit_Successful Dist_Commit_Successful Remove_Successful Event Slots Notes severity msg severity msg severity msg severity msg severity msg severity msg severity msg severity msg severity msg severity msg By default, severity = MINOR. This class inherits from Distribution_ Error. By default, severity = MINOR. This class inherits from Distribution_ Error. By default, severity = WARNING. This class inherits from Distribution_ Error. By default, severity = WARNING. This class inherits from Distribution_ Error. By default, severity = WARNING. This class inherits from Distribution_ Error. By default, severity = WARNING. This class inherits from Distribution_ Error. By default, severity = HARMLESS. This class inherits from Distribution_ Error. By default, severity = HARMLESS. This class inherits from Distribution_ Error. By default, severity = HARMLESS. This class inherits from Distribution_ Error. By default, severity = HARMLESS. This class inherits from Distribution_ Error Version 3.6

361 14 14File Package Blocks File Package Blocks Using a variety of commands provided by TME 10 Software Distribution, you can create and distribute a snapshot of a file package called a file package block, or fpblock. A file package block is a static file containing the file package definition, file package attributes, source files and directories, and configuration programs of a specific file package. Storing information in this manner is also called archiving, depoting, or data warehousing, and is especially useful for performing the following operations: Securing data contained in file packages. After you create an fpblock, you cannot edit the contained files or directories. Transferring a file package to a machine on the remote side of a slow network connection, such as a wide area network (WAN). This enables faster, more efficient distributions to targets over a slow network connection. Storing a file package whose files on the source host may change frequently. This enables you to distribute identical copies of the file package to all targets at any time. Archiving a file package for later distribution. TME 10 Software Distribution User s Guide 14 1

362 Fpblock Commands Fpblock Commands You can create fpblocks from the command line only. The commands used to create and manipulate fpblocks are briefly described here. Refer to the TME 10 Software Distribution Reference Manual for a more detailed description of command syntax and arguments for the following commands: wcpfpblock wcrtfpblock wdistfpblock wrmfpblock Using Fpblocks Copies the fpblock from one managed node to other managed nodes. This command does not remove the original fpblock. Creates an fpblock that you can place on any number of specified managed nodes in any specified location. Distributes the files and directories in the fpblock to the specified targets. It also runs any before, after, or commit configuration programs within the fpblock. You can override some of file package options from the command line. The fpblock is distributed according to the same MDist rules as if the source host were the machine where the fpblock is stored. Removes the files in the fpblock from the specified targets. It also runs any target removal configuration programs within the file package block. To delete an fpblock, you must manually remove it from the managed node where it is stored. This command does not remove the original fpblock. Using file package blocks to distribute data is especially beneficial if you are distributing large amounts of data over a variety of network connections. Suppose, for instance, that you have a controlling TMR in London, England that distributes to smaller servers located around the world through a WAN connection. The servers are each connected 14 2 Version 3.6

363 Using Fpblocks by a LAN to many PC targets. This network configuration is illustrated in the following figure. File Package Blocks Because LANs are generally faster than WANs, you can distribute a file package from the controlling TMR to an fpblock on each of the servers. By distributing from fpblocks on the servers, you increase the performance of the distribution and ensure that the data in the fpblocks remains static between distributions at different times. For example, suppose you have a file package named Accting that you must distribute from your source host in England to targets around the world. After you create the file package, set its properties and options, specify its configuration programs and input files, and include the files and directories to be distributed, you can distribute the file package to an fpblock on the servers. From the controlling TMR, use the following wcrtfpblock command to create an fpblock for the Accting file package on the London, Tokyo, and New York servers: wcrtfpblock @"New York" where: a Creates the fpblock that includes all source files and directories of the file package. TME 10 Software Distribution User s Guide 14 3

364 Using Specifies to create the fpblock from the Accting file package. /apps/blocks/accting.fpb Specifies the full path of the file to which the fpblock is written on @"New York" Specifies the managed nodes on which the fpblock will reside. Note that double quotation marks ( ) are only required if a name has embedded spaces. When the /apps/blocks/accting.fpb file is created on the target, it contains the file package definition, file package attributes, configuration programs and input files, and the data in the files and directories that you specified for the file package. To distribute the file package to the targets, use the wdistfpblock command. For example, if you want to distribute the files in the /apps/blocks/accting.fpb file package block from the New York server to the Miami, Austin, and San Francisco targets, enter the following command: @"San Francisco" York":/apps/blocks/Accting.fpb Distributes the /apps/blocks/accting.fpb fpblock from the New York @"San Francisco" Specifies the managed nodes, Miami, Austin, and San Francisco, to which the file package contained in the fpblock will be distributed Version 3.6

365 Using Fpblocks The wdistfpblock command also enables you to set or override some keywords set when the fpblock was created. Thus, for the Austin target, if you want the log file to reside on the target and you do not want the distribution to stop if an error occurs, distribute the fpblock using the following command: wdistfpblock -o log_host=austin -o stop_on_error=n where: o log_host=austin Sets the log_host keyword of the file package, setting the log host to Austin. o stop_on_error=n Overrides the stop_on_error keyword of the file package, causing the distribution to continue if an error York":/apps/blocks/Accting.fpb Distributes the file package contained in the /apps/blocks/accting.fpb fpblock from the New York managed Specifies the Austin managed node to which the contained file package is distributed. File Package Blocks If a new managed node is added to the WAN and you want to distribute the Accting file package to its targets, you can use the wcpfpblock command to copy the /apps/blocks/accting.fpb fpblock from another server, if they are connected. Therefore, to copy the fpblock from the London server to the newly-created Delhi server, use the following command: \ TME 10 Software Distribution User s Guide 14 5

366 Using Fpblocks To remove an fpblock from a managed node, simply delete the fpblock file. To remove the fpblock in this example, you will delete the /apps/blocks/ Accting.fpb file. Copies the /apps/blocks/accting.fpb fpblock from the London managed node. /apps/blocks/accting.fpb Specifies the full path of the file to which the fpblock is Specifies the Delhi managed node to which the fpblock is copied. Finally, if you want to remove the Accting file package from a target, use the wrmfpblock command. Note that this command does not remove the fpblock from the managed node only the files and directories that you distributed using the wdistfpblock command. For example, if you want to remove the files and directories in the fpblock from the Austin and Miami targets, enter the following command: York":/apps/blocks/Accting.fpb Removes the files and directories distributed from the /apps/blocks/accting.fpb fpblock on the New York Specifies to remove the files and directories from the Miami and Austin managed nodes. For more information about the wcrtfpblock, wdistfpblock, wcpfpblock, and wrmfpblock commands, see the TME 10 Software Distribution Reference Manual Version 3.6

367 15 15NetWare Managed Sites Supported PC clients include Windows 3.x, Windows NT, and Windows 95 machines. To accommodate environments that rely on NetWare servers connected to PCs, TME 10 provides NetWare managed sites. A NetWare managed site enables profiles to be distributed through the NetWare server to one or more specified client PCs using either the IPX/SPX or the TCP/IP communication protocol. A Tivoli NetWare repeater, in turn, acts as a repeater site for distributions to these IPX/SPX and TCP/IP clients, providing an alternate fanout model to multiplexed distributions (MDist). Although NetWare managed sites distribute serially to client machines, the following are benefits to configuring a NetWare managed site: NetWare managed sites enable distributions to clients using the IPX/SPX protocol. In a NetWare environment with several IPX/SPX or TCP/IP clients, configuring several NetWare servers to distribute serially to sets of clients establishes a fanout distribution model that emulates a parallel distribution. See the TME 10 Framework Planning and Installation Guide for more information on MDist. To use a NetWare managed site with TME 10 Software Distribution, you must first create it in the desired policy region. Subscribe the NetWare managed site to the profile manager in which the file package or AutoPack resides. When you distribute the profile, TME 10 Software Distribution passes it to a staging area on the represented NetWare Managed Sites TME 10 Software Distribution User s Guide 15 1

368 Configuring NetWare Managed Sites NetWare server. The NetWare server then distributes the profile to the clients specified when you created the NetWare managed site. Note: The profile is not distributed to the NetWare server; that is, the files and directories distributed by the file package or AutoPack are not copied onto the NetWare server machine. This chapter discusses how to create and edit a NetWare managed site and its clients, and how to remove unavailable clients from a NetWare managed site. In addition, the available CLI commands that enable you to configure and modify files on the PC clients are outlined. Configuring NetWare Managed Sites If you want to distribute a profile to the Net- Ware server, in addition to its clients, you must also create a PC managed node to represent the Net- Ware server. Before creating and distributing to a NetWare managed site, you must install the Tivoli NetWare repeater (TNWR) and IP agent on the represented NetWare server. The TNWR is a server application that maintains a list of available clients for the server; this application enables you to distribute profiles to clients of the NetWare server. You must also install the IPX/SPX or IP agent on all PCs that are clients of the NetWare server. Consider the following diagram: UNIX Workstation Create a NetWare managed site on the server to represent the TNWR IP connection IPX/SPX & TCP/IP connections NetWare Server Install a Tivoli NetWare repeater and IP agent on NetWare server Distributions occur serially PCs with IPX/SPX and IP agents installed{ When you distribute a profile to a NetWare managed site, the NetWare managed site passes it and a list of subscribed clients to the NetWare 15 2 Version 3.6

369 Creating a NetWare Managed Site server using the TCP/IP protocol. The TNWR then uses the IPX/SPX or TCP/IP protocol to distribute to its clients. See the TME 10 Framework Planning and Installation Guide for information on deploying TNWRs and the appropriate PC agents, and for a description of how these components interact. Creating a NetWare Managed Site When you create a NetWare managed site, you must complete the following steps: Select the represented NetWare server. Select the desired clients, which will receive any file package or AutoPack distribution sent to the NetWare managed site. Set the staging area on the NetWare server, where the file package or AutoPack will reside prior to distribution to the clients. Set the log file, where processing and diagnostic information about file package or AutoPack distributions to the clients is stored. Also, before creating a NetWare managed site, you might want to consider the clients of the NetWare server. You can subscribe all or a subset of the clients to the NetWare managed site. If you choose to subscribe a subset of clients, you can create multiple NetWare managed sites to represent one NetWare server and different client subsets. You must create multiple NetWare managed sites to represent the NetWare server and subsets of clients of different machine types. For example, if you distribute a file package that is intended for Windows 95 machines and the NetWare managed site cannot discern that it is a Windows 95 file package, it will send the file package to all of the NetWare managed site s clients, regardless of the machine type. NetWare Managed Sites TME 10 Software Distribution User s Guide 15 3

370 Creating a NetWare Managed Site The following table provides the context and authorization role required for this task: Operation Context Required Role Create a NetWare managed site Policy region install_client Desktop You can perform this task from the TME 10 desktop or from the command line. Use the following steps to create a NetWare managed site: 1. Double-click on the policy region in which you want to create the NetWare managed site. TME 10 displays the Policy Region window. 1. Add the NetWareManagedSite resource to the policy region s list of managed resources. For information on adding resource types to a policy region, see the TME 10 Framework User s Guide Version 3.6

371 Creating a NetWare Managed Site 1. Select NetWareManagedSite... from the policy region s Create menu to display the Create NetWare Managed Site dialog. NetWare Managed Sites 1. Enter the name of the NetWare managed site to be created in the NetWare Managed Site Label field. 1. In the NetWare Managed Site Location field, enter the name of a managed node on which the NetWare managed site s object (icon) will reside. 1. In the Log File Path field, enter the full path to a log file to which the NetWare managed site writes diagnostic information during file package distribution. You must enter the path using forward slashes (/). This file resides on the managed node on which the NetWare managed site was created. The default path is set by the nw_def_log_file default policy. TME 10 Software Distribution User s Guide 15 5

372 Creating a NetWare Managed Site 1. In the NetWare Server Name field, enter the name of the NetWare server from which to create the NetWare managed site. If you do not know the host name, enter the NetWare server s IP address in the NetWare Server IP Address field. You do not have to enter both. 1. In the Staging Area Path field, enter the path to a staging area on the NetWare server. You must enter the path using forward slashes (/). The file package or AutoPack will reside in this staging area prior to distribution to the clients. If you do not enter a path here, the staging area set by the nw_def_staging_area default policy is used. Note: The staging area on the NetWare server must be a volume large enough to accommodate the profiles. To estimate the space required, determine the maximum size of the profile you will distribute and multiply by two. This should allow for enough overhead to enable a successful distribution. Tivoli recommends you use a reserved volume that has little file-server activity in order to guarantee available space for ongoing file distribution activity. If you use the SYS volume, you must ensure the minimum available space for the profiles. 1. Subscribe clients to the NetWare managed site by moving client names from the Available Clients scrolling list to the Selected Clients scrolling list. You can subscribe all available clients by pressing the Subscribe All Clients radio button. If you press this button, the NetWare Clients scrolling lists are disabled. The clients are listed by their name, machine type, communication protocol, and machine ID, as follows: client1;windows;spx;wlxb6p795mx715zv1wdb The machine ID is a unique ID assigned to the client by the PC agent Version 3.6

373 Creating a NetWare Managed Site Note: You must press (disable) the Subscribe All Clients radio button to change the NetWare server name or IP address. To move a client to the Selected Clients scrolling list, choose an item from the Available Clients list and press the left arrow button. To remove a client from the Selected Clients list, choose an item and press the right arrow button. 1. Press the Create & Close button to create the NetWare managed site and return to the Policy Region window. NetWare Managed Sites Command Line To create a NetWare managed site called popeye-win from the popeye NetWare server in the pescado-region policy region, enter the following command: wcrtnwms -n popeye -s SYS:/SYSTEMS -a popeye-win \ pescado-region where: n popeye Specifies the popeye NetWare server from which the NetWare managed site is created. TME 10 Software Distribution User s Guide 15 7

374 Editing NetWare Managed Site Properties s SYS:/SYSTEMS Specifies the staging area, SYS:/SYSTEMS, where the profile will reside on the NetWare managed site. a Configures the NetWare managed site to distribute profiles to all clients. popeye-win Specifies the name of the NetWare managed site to be created. pescado-region Specifies the pescado_region policy region in which the NetWare managed site will reside. See the TME 10 Framework Reference Manual for more information on the wcrtnwms command. Editing NetWare Managed Site Properties Edit the properties of a NetWare managed site to change the following options: List of available clients Name Location of the log file Staging area You cannot change the server from which the managed site was created. The following table provides the context and authorization role required for this task: Operation Context Required Role Edit NetWare managed site properties Policy region admin You can perform this task from the TME 10 desktop or from the command line Version 3.6

375 Editing NetWare Managed Site Properties Desktop Use the following steps to edit a NetWare managed site: 1. Double-click on the icon of the NetWare managed site whose properties you want to edit. TME 10 displays the Edit NetWare Managed Site Properties dialog. NetWare Managed Sites 1. To rename the NetWare managed site, change the name in the NetWare Managed Site Label field. The new name will be displayed below the NetWare managed site icon. 1. To change the log file to which the NetWare managed site writes diagnostic information, enter a full path in the Log File Path field. You must enter the path using forward slashes (/). This file will reside on the managed node on which the NetWare managed site was created. The NetWare managed site writes diagnostic information to this file during file package distribution. TME 10 Software Distribution User s Guide 15 9

376 Editing NetWare Managed Site Properties Command Line 1. To change the directory in which a file package resides before distribution to the clients, enter a new directory name in the Staging Area Path field. You must enter the path using forward slashes (/). Note: The staging area on the NetWare server must be a volume large enough to accommodate the profiles. To estimate the space required, determine the maximum size of the profile you will distribute and multiply by two. This should allow enough space for the distribution. Tivoli recommends that you use a reserved volume that has little file-server activity in order to guarantee available space for ongoing file distribution activity. If you use the SYS volume, you must ensure the minimum available space for the profiles. 1. To change the list of clients to which the NetWare managed site distributes file packages, perform one of the following actions: Press the Subscribe All Clients radio button to distribute file packages to all of the NetWare clients. Choose the specific clients using the NetWare Clients scrolling lists. 1. Press the Apply & Close button to change the NetWare managed site properties and close the Edit NetWare Managed Site Properties dialog. Before setting properties from the command line, you can retrieve the properties of a NetWare managed site using the wgetnwms command, as follows: wgetnwms -s popeye-win where: s Retrieves the full path to the staging area on the NetWare managed site. popeye-win Specifies to the retrieve the properties of the popeye-win NetWare managed site Version 3.6

377 Removing an Unavailable Client To set properties from the command line, use the wsetnwms command. For example, to set the staging area for the popeye-win NetWare managed site, enter the following command: wsetnwms -s SYS:/FPS -a popeye-win where: s SYS:/FPS Sets the staging area on the NetWare managed site to the SYS:/FPS directory. a Configures the NetWare managed site to distribute file packages to all clients. popeye-win Sets the properties for the popeye-win NetWare managed site. See the TME 10 Framework Reference Manual for more information on the wgetnwms and wsetnwms commands. Removing an Unavailable Client If a client is removed from a NetWare server, it becomes unavailable to its corresponding NetWare managed site(s). In this case, you can remove unavailable subscribed clients from the NetWare managed site. Note: Removing an unavailable client from a NetWare managed site s list of clients is not the same as removing a client from a NetWare server. See the TME 10 Framework Planning and Installation Guide for information about removing a client from a NetWare server. The following table provides the context and authorization role required for this task: NetWare Managed Sites Operation Context Required Role Remove a NetWare managed site client Policy region install_client You can perform this task from the TME 10 desktop or from the command line. TME 10 Software Distribution User s Guide 15 11

378 Removing an Unavailable Client Desktop If a subscribed client becomes unavailable, the NetWare managed site displays the Remove Unavailable Clients dialog when you double-click on the NetWare managed site to which it was subscribed. All clients that are inaccessible are listed in the Remove scrolling list. To remove all of the listed clients from the subscriber list, press the Remove & Close button. If you want to retain one or more of the unavailable clients for later distributions, move the client name from the Remove scrolling list to the Retain scrolling list using the right arrow button. When you press the Remove & Close button, all clients displayed in the Remove scrolling list will be removed from the NetWare managed site s list of subscribers. The changes are reflected in the NetWare Clients scrolling lists on the Edit NetWare Managed Site Properties dialog. Note: If a client becomes available after you remove it from the client list, it will be listed in the Available Clients scrolling list the next time you display the Edit NetWare Managed Site Properties dialog Version 3.6