Certification Guide Series IBM Tivoli Provisioning Manager Express For Software Distribution V4.1 Sg247247

Front cover
Certification Guide Series

IBM Tivoli Provisioning Manager Express for Software Distribution V4.1
Helps you become a certified Tivoli Provisioning Manager Express Explains the certification path and prerequisites you require Includes best practices for Software Distribution
Vasfi Gucer Bernd Arnold Leif Egeholm Nielsen Giorgio Claudio Sommariva
ibm.com/redbooks
International Technical Support Organization Certification Guide Series: IBM Tivoli Provisioning Manager Express for Software Distribution V4.1 October 2006
SG24-7247-00
Note: Before using this information and the product it supports, read the information in Notices on page xv.
First Edition (October 2006) This edition applies to Version 4, Release 1, Modification 1 of IBM Tivoli Provisioning Manager Express for Software Distribution product.
Copyright International Business Machines Corporation 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii The team that wrote this IBM Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Chapter 1. Certification overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 IBM Professional Certification Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.1 Benefits of certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.2 Tivoli Software Professional Certification . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2.1 Test 879 objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.2 To get 15% discount on the Certification . . . . . . . . . . . . . . . . . . . . . . 8 1.3 Recommended resources for study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.3.1 Courses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3.2 Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Chapter 2. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.1 IBM Tivoli Provisioning Manager Express for Software Distribution components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1.1 IBM Tivoli Provisioning Manager Express for Software Distribution components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1.2 Inventory components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.2 Infrastructure deployment considerations . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.2.1 Communication protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.2.2 Small and medium environments . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.3 Large environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.3 Customization considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.4 Hardware and software specifications and recommendations . . . . . . . . . 20 2.4.1 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.4.2 Administrative console requirements . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4.3 Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Copyright IBM Corp. 2006. All rights reserved.
iii
2.4.4 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Chapter 3. Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1 Server installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.1.1 Server installation: typical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.1.2 Server installation: custom setup . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.1.3 Server installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3.2 Installing the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 3.2.1 Installing the agent: typical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.2.2 Installing the agent: advanced setup. . . . . . . . . . . . . . . . . . . . . . . . . 38 3.2.3 Verifying agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 3.2.4 Installing an agent as an unattended command line installation . . . . 43 3.2.5 Uninstalling the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.2.6 Verifying the server uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.2.7 Uninstalling the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.2.8 Verifying agent uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Chapter 4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 4.1 Server properties files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 4.1.1 The common.properties file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.1.2 The isic.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.1.3 The sdc.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 4.1.4 The ldap.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 4.1.5 The log4j.properties file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 4.2 Configuring the agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 4.2.1 sdc.conf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 4.2.2 Auto-update of client files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 4.2.3 SDClocal.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Chapter 5. Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 5.1 Accessing the Administrative console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.2 Managing user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 5.2.1 Authority roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 5.2.2 Adding a new user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 5.2.3 Deleting a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.2.4 Searching for a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 5.2.5 Modifying a users group membership . . . . . . . . . . . . . . . . . . . . . . 105 5.2.6 Updating user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.3 Managing user groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.3.1 Adding a new group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.3.2 Deleting a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 5.3.3 Searching for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.3.4 Updating a group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.3.5 Updating user information in a specific group . . . . . . . . . . . . . . . . . 112
iv
Certification Guide Series: IBM Tivoli Provisioning Manager Express for Software Distribution V4.1
5.3.6 Adding or deleting (modifying) a user to a group . . . . . . . . . . . . . . 113 5.3.7 Adding or deleting (modifying) a software package or bundle for a specific group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5.4 Managing packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.4.1 Prerequisites for managing packages . . . . . . . . . . . . . . . . . . . . . . . 117 5.4.2 Adding a new software package to the library . . . . . . . . . . . . . . . . 124 5.4.3 Deleting a software package from the library . . . . . . . . . . . . . . . . . 131 5.4.4 Searching the library for a software package . . . . . . . . . . . . . . . . . 133 5.4.5 Updating software package information in the library . . . . . . . . . . . 135 5.4.6 Software package definition information . . . . . . . . . . . . . . . . . . . . . 136 5.4.7 Creating a digital certificate file for a secure package. . . . . . . . . . . 146 5.5 Managing software bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 5.5.1 Adding a new software bundle to the library . . . . . . . . . . . . . . . . . . 147 5.5.2 Deleting a software bundle from the library. . . . . . . . . . . . . . . . . . . 151 5.5.3 Searching the library for a bundle . . . . . . . . . . . . . . . . . . . . . . . . . . 152 5.5.4 Updating software bundle information in the library . . . . . . . . . . . . 154 5.5.5 Software bundle definition information . . . . . . . . . . . . . . . . . . . . . . 154 5.6 Managing purchase orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 5.6.1 Adding a purchase order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 5.6.2 Deleting a purchase order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 5.6.3 Searching for a specific purchase order . . . . . . . . . . . . . . . . . . . . . 158 5.6.4 Updating a purchase order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 5.7 Managing distribution lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 5.7.1 Distribution list information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 5.7.2 Adding a distribution list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 5.7.3 Deleting a distribution list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 5.7.4 Searching for a distribution list . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 5.7.5 Changing (modifying) the distribution list description . . . . . . . . . . . 169 5.7.6 Searching for a machine in a specific distribution list . . . . . . . . . . . 169 5.8 Managing machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5.8.1 Deleting a machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5.8.2 Searching for a machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 5.9 Managing evaluations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 5.9.1 Adding an evaluation from the Distributions menu . . . . . . . . . . . . . 174 5.9.2 Adding and evaluating from the Assets menu. . . . . . . . . . . . . . . . . 178 5.9.3 Deleting an evaluation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.9.4 Searching for an evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.9.5 Update evaluations created from the Dists menu . . . . . . . . . . . . . . 182 5.9.6 Update evaluations created from the Assets menu . . . . . . . . . . . . 182 5.10 Managing tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 5.10.1 Adding a task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 5.10.2 Deleting a task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 5.10.3 Update a task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Contents
5.10.4 Running a task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 5.11 Managing schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 5.11.1 Scheduling information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 5.11.2 Adding a schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 5.11.3 Searching for a specific schedule . . . . . . . . . . . . . . . . . . . . . . . . . 197 5.11.4 Deleting a schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 5.12 Managing logs and standard reports. . . . . . . . . . . . . . . . . . . . . . . . . . . 199 5.12.1 Software Distribution log entry details . . . . . . . . . . . . . . . . . . . . . . 199 5.12.2 Viewing a Software Distribution log. . . . . . . . . . . . . . . . . . . . . . . . 200 5.12.3 Searching for a distribution log . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 5.12.4 Deleting a distribution log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 5.12.5 Standard report categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 5.12.6 Viewing package reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 5.12.7 Searching for a package to report. . . . . . . . . . . . . . . . . . . . . . . . . 206 5.12.8 Viewing a machine report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 5.12.9 Searching for a machine to report . . . . . . . . . . . . . . . . . . . . . . . . . 209 5.12.10 Viewing a schedule report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 5.12.11 Viewing an assets summary report . . . . . . . . . . . . . . . . . . . . . . . 213 5.12.12 Searching for a schedule to report . . . . . . . . . . . . . . . . . . . . . . . 214 5.13 Managing custom reports (queries). . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 5.13.1 Adding a custom report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 5.13.2 Adding a custom report starting from a standard report . . . . . . . . 216 5.13.3 Deleting a custom report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 5.14 Managing catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 5.14.1 Client catalog overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 5.14.2 Accessing the catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 5.14.3 Creating a portable catalog, exporting and importing libraries between two servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 5.15 Working with assets and user information. . . . . . . . . . . . . . . . . . . . . . . 240 5.15.1 Assets and user information tables . . . . . . . . . . . . . . . . . . . . . . . . 241 5.15.2 Registering assets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Chapter 6. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 6.1 Server log information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 6.2 Server database information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 6.3 Client log information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 6.4 Enabling server debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 6.5 Enabling agent debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 6.6 Command line option eGather2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 6.7 Command line option callHome2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Chapter 7. Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 7.1 Identifying a requirement to apply a patch or an upgrade . . . . . . . . . . . . 264
vi
7.2 Retrieving patch or upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 7.3 Applying patches or upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 7.4 Verifying functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Chapter 8. Sample Certification Test questions. . . . . . . . . . . . . . . . . . . . 267 8.1 Sample questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Appendix A. Sample folder structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Contents
vii
viii
Figures
2-1 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 4-1 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 5-26 5-27 Communication protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Web site Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 E-mail Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Action Authority Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Scheduling window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Password Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Form Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Security Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Server Address window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Proxy settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 The Edit Properties page in the administrator console . . . . . . . . . . . . . 53 Welcome page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Administrator and client login page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Add User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 All Users list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Delete users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 User delete confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 User search title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 User advanced search page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Edit user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 My Assets page with New Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Add Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Add Group: success message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 List Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Delete group confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 List Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Group search page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Group Management: description update . . . . . . . . . . . . . . . . . . . . . . . 111 Group Management: User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 User Management: update user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Group Management: User List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Edit user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Group Management: Package Access List . . . . . . . . . . . . . . . . . . . . . 116 Add Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Install tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Target tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Platform tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Upload tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
ix
5-28 5-29 5-30 5-31 5-32 5-33 5-34 5-35 5-36 5-37 5-38 5-39 5-40 5-41 5-42 5-43 5-44 5-45 5-46 5-47 5-48 5-49 5-50 5-51 5-52 5-53 5-54 5-55 5-56 5-57 5-58 5-59 5-60 5-61 5-62 5-63 5-64 5-65 5-66 5-67 5-68 5-69 5-70
Successful package addition message . . . . . . . . . . . . . . . . . . . . . . . . 131 List Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Package delete confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Search packages by name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Search packages by OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Update Package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Add Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Update Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Packages list for bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Adjust Package Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Successful bundle addition message. . . . . . . . . . . . . . . . . . . . . . . . . . 150 List Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Delete confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 List Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Bundle Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Bundle Search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Add Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Purchase Order information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Successful purchase order addition message . . . . . . . . . . . . . . . . . . . 157 Delete confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 List Purchase Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Purchase Order Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Purchase Order Search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Update Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Distribution Management: Add Distribution . . . . . . . . . . . . . . . . . . . . . 163 Distribution Management: Selectable Targets . . . . . . . . . . . . . . . . . . . 164 Distribution Management: Selectable Search . . . . . . . . . . . . . . . . . . . 164 Distribution Management: Dynamic Targets . . . . . . . . . . . . . . . . . . . . 165 Distribution Management: Invalid Targets . . . . . . . . . . . . . . . . . . . . . . 165 Distribution Management: Successful message . . . . . . . . . . . . . . . . . 166 Distribution Management: Delete Distributions . . . . . . . . . . . . . . . . . . 166 Delete confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Distribution Management: List Distributions. . . . . . . . . . . . . . . . . . . . . 167 Distribution Management: Search distributions . . . . . . . . . . . . . . . . . . 168 Distribution Management: Search results . . . . . . . . . . . . . . . . . . . . . . 168 Distribution Management: Edit Distribution . . . . . . . . . . . . . . . . . . . . . 169 Distribution Management: Selectable Search . . . . . . . . . . . . . . . . . . . 170 Distribution Management: Selectable Targets . . . . . . . . . . . . . . . . . . . 171 Machine Management: List Machines . . . . . . . . . . . . . . . . . . . . . . . . . 172 Machine Management: Machines Search . . . . . . . . . . . . . . . . . . . . . . 173 Add Evaluation General tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Add Evaluation SD option Condition tab . . . . . . . . . . . . . . . . . . . . . . . 176 Add Evaluation no SD option Condition tab . . . . . . . . . . . . . . . . . . . . . 177
5-71 5-72 5-73 5-74 5-75 5-76 5-77 5-78 5-79 5-80 5-81 5-82 5-83 5-84 5-85 5-86 5-87 5-88 5-89 5-90 5-91 5-92 5-93 5-94 5-95 5-96 5-97 5-98 5-99 5-100 5-101 5-102 5-103 5-104 5-105 5-106 5-107 5-108 5-109 5-110 5-111 5-112 5-113
Evaluation Management: Evaluation addition success message . . . . 177 Assets list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Add evaluation from Assets menu: general tab . . . . . . . . . . . . . . . . . . 178 Add Evaluation from Assets menu: condition tab . . . . . . . . . . . . . . . . 179 Evaluation list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Delete confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Evaluations search tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Evaluation Management: Evaluation Search results . . . . . . . . . . . . . . 181 Evaluation Management: update evaluations . . . . . . . . . . . . . . . . . . . 182 Adding a new task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Adding a new task, extended fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Adding a new task, successful message . . . . . . . . . . . . . . . . . . . . . . . 186 Delete Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Delete Task: success message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Edit Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Edit task page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Schedule Management: Add Schedule . . . . . . . . . . . . . . . . . . . . . . . . 195 Schedule Management: Add Schedule package . . . . . . . . . . . . . . . . . 196 Schedule Management: Add Schedule message . . . . . . . . . . . . . . . . 196 Schedule Management: List Schedules. . . . . . . . . . . . . . . . . . . . . . . . 197 Schedule Management: Search schedule . . . . . . . . . . . . . . . . . . . . . . 198 Delete confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Log Management: List Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Log Management: Log Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Log Management: Log Search results . . . . . . . . . . . . . . . . . . . . . . . . . 201 Log Management: Log Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Standard report categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Package Management: List Packages. . . . . . . . . . . . . . . . . . . . . . . . . 205 Package Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Package Management: Distribution report search . . . . . . . . . . . . . . . . 207 Machine Management: List Machines . . . . . . . . . . . . . . . . . . . . . . . . . 208 Machine Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Machine Management: Machine Search . . . . . . . . . . . . . . . . . . . . . . . 210 Schedule Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Schedule Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Assets Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Schedule Summary Report Search . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Reports: Edit SQL page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Reports: Saving custom report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Reports: All Assets report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Reports: Delete a column from a standard report . . . . . . . . . . . . . . . . 217 All Custom reports page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Software Distribution Catalog functions . . . . . . . . . . . . . . . . . . . . . . . . 219
Figures
xi
5-114 5-115 5-116 5-117 5-118 5-119 5-120 5-121 5-122 5-123 5-124 5-125 5-126 5-127 5-128 5-129 5-130 5-131 5-132 5-133 5-134 5-135 5-136 5-137 5-138 5-139 5-140 5-141 5-142 5-143 5-144 5-145 6-1 6-2 A-1 A-2 A-3
Software Distribution Catalog Login. . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Software Distribution Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Desktop Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Add Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Package List for Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Bundle List for Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Successful export list addition message . . . . . . . . . . . . . . . . . . . . . . . 226 List Exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Edit Export list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 OutputXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Import XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Import Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Security Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 CD Catalog Exporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 CD exporter icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 CD Catalog Exporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 CD export package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 CD Catalog Exporter progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Portable Catalog files view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Mandatory Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Package Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Install In Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Package file download progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Install In Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Purchase Order Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Cancel installation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Invalid information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 max_processed_revision column recording scans on agent . . . . . . . . 241 Register a new asset window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Upload an asset scan window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Manually add an asset window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Properties files page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 log4j.properties properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Separate folders for software packages . . . . . . . . . . . . . . . . . . . . . . . 276 Single folder for software packages . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Separate folders for each operating system . . . . . . . . . . . . . . . . . . . . 278
xii
Examples
3-1 3-2 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 4-16 4-17 4-18 4-19 4-20 4-21 4-22 4-23 4-24 4-25 4-26 4-27 4-28 4-29 4-30 4-31 4-32 4-33 4-34 6-1 6-2 tpmx.log entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 sdcagent.log entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Archive versions of properties files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 True or false values in the demographic form . . . . . . . . . . . . . . . . . . . . 55 Valid values for the 18 fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 isic.properties: e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 isic.properties: e-mail and reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 isic.properties: e-mail template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 isic.properties: upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 isic.properties: files and directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Asset match properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Query performance properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Authority configuration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Probe properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Database asset revision properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Scheduled agent properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Database cleanup properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Password properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Asset registration configuration properties. . . . . . . . . . . . . . . . . . . . . . . 74 Security compliance verification configuration properties . . . . . . . . . . . 75 e-mail engine properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 System maintenance properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 sdc.properties: General environment and DB settings . . . . . . . . . . . . . 81 sdc.properties: Purchase order management . . . . . . . . . . . . . . . . . . . . 82 sdc.properties: Directory Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 sdc.properties: LDAP enabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 sdc.properties: Machine identification . . . . . . . . . . . . . . . . . . . . . . . . . . 84 sdc.properties: Package path prepopulate values . . . . . . . . . . . . . . . . . 84 sdc.properties: Evaluation query update . . . . . . . . . . . . . . . . . . . . . . . . 85 ldap.properties: Basic LDAP configuration . . . . . . . . . . . . . . . . . . . . . . 86 Encrypting ldap connection password . . . . . . . . . . . . . . . . . . . . . . . . . . 87 ldap.properties: Group data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 ldap.properties: User authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 log4j.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Example sdc.conf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Sample SDClocal.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 eGather2 -listprobes to list all available probes . . . . . . . . . . . . . . . . . . 257 eGather2 -level 1 runs eGather2 with only the level 1 probes . . . . . . . 258
xiii
6-3 6-4 6-5 6-6
eGather2 -silent run eGather2 in silent mode without output. . . . . . . . 259 callHome2 -1minute to wait one minute to run the upload . . . . . . . . . . 260 callHome2 -reload -debug turns debugging on . . . . . . . . . . . . . . . . . . 261 callHome2 -status to see the status of the uploads . . . . . . . . . . . . . . . 261
xiv
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described 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: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.
xv
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX AIX 5L Cloudscape DB2 DB2 Universal Database e-business Hosting e-business on demand eServer i5/OS IBM ibm.com iSeries NetView POWER5 Redbooks Redbooks (logo) Tivoli Tivoli Enterprise Tivoli Enterprise Console WebSphere xSeries
The following terms are trademarks of other companies: Java, JDBC, JRE, J2SE, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Active Directory, Excel, Internet Explorer, Microsoft, Windows NT, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Xeon, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
xvi
Preface
IBM Tivoli Provisioning Manager Express for Software Distribution V4.1 is an easy-to-use, comprehensive solution for software distribution, patch, inventory, and asset management. This Web-based solution is designed for ease of use and implementation, so that you can quickly begin to manage the PCs in your enterprise. Tivoli Provisioning Manager Express for Software Distribution V4.1 is implemented with both a client agent on the managed PCs and a centralized data repository. The product is specifically targeted for the small-to-medium business (SMB) market. This IBM Redbook is a study guide for Tivoli Provisioning Manager Express for Software Distribution V4.1 and is aimed at the people who want to get an IBM Professional Certification for this product. The Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification is offered through the Professional Certification Program from IBM. It is designed to validate the skills that technical professionals, who work in the implementation of the Tivoli Provisioning Manager Express for Software Distribution V4.1 product, require. This book provides a combination of theory and practical experience required for a general understanding of the subject matter. It also provides sample questions that help in the evaluation of personal progress and provide familiarity with the types of questions that you can encounter in the exam. This publication does not replace practical experience, and it is not designed to be a stand-alone guide for any subject. Instead, it is an effective tool, which you can combine with educational activities and experience, to use as a preparation guide for the exam. For your convenience, the structure of the chapters are based on sections of the Tivoli Provisioning Manager Express for Software Distribution V4.1 Implementation Certification test, such as planning, installation, administration, and so on. Therefore, studying each chapter helps you prepare for one section of the exam.
xvii
The team that wrote this IBM Redbook

This IBM Redbook was produced by a team of specialists from around the world working at the International Technical Support Organization (ITSO), Poughkeepsie Center. Vasfi Gucer is a Project Leader at the International Technical Support Organization, Austin Center. He worked for IBM Turkey for 10 years and has been with the ITSO since January 1999. He has more than 10 years of experience in the areas of systems management, networking hardware, and software on mainframe and distributed platforms. He has worked on various Tivoli client projects, as a Systems Architect, in Turkey and the US. He writes extensively and teaches IBM classes worldwide on Tivoli software. Vasfi is also an IBM Certified Senior Information Technology (IT) Specialist. Bernd Arnold is a certified Senior Systems Management Professional working for IBM Global Integrated Technology Delivery in Germany. He has more than 15 years of experience in the IT Industry and has been working for IBM Germany since 1995. Currently he is an IT Architect in the On demand Data Centre Services program in Global Technology Integration and Management Competency. He has been a lead architect on several large Universal Management Infrastructure and Tivoli implementations in Europe. Before this, he was working for an IBM e-business Hosting as a lead architect for Systems Management and he was a Europe, Middle East, and Africa Service Manager for the Central Tools local area network (LAN). He is responsible for solution architecture and solution deployment in strategic outsourcing and also for providing governance and leadership guidance to e-business Hosting and IBM e-business on demand customer projects. Bernd received a Bachelor of Science degree in electronics engineering at the University of Engineering in Ulm. Leif Egeholm Nielsen is an IBM Certified IT Architect in Operations Architecture. He has worked for IBM Denmark since 1994, mainly with systems management for distributed systems. He has worked with Tivoli solutions since 1997 and been lead architect on several large Tivoli implementations in the Nordics, specifically with focus on Tivoli Framework, Inventory, and Software Distribution. Leif currently works in IBM Global Technology Services. He works in the strategy and design group that provides technical directions for delivery of IT services to strategic outsourcing customers. Leif is also an active member of the innovation community in IBM Denmark. He has previously been to Austin several times to participate in the production of ITSO Redbooks, ITSO Workshop material, and
xviii
product certifications. Leif holds a Bachelor of Science degree in Mechanical Engineering from the Danish Academy of Engineering. Giorgio Claudio Sommariva is an IBM Advisory IT Architect working in IBM Global Technology Services Division in Segrate (Italy) for 4 years. His skills include IBM Tivoli Monitoring V5.1, IBM Tivoli Configuration Manager 4.2.x, IBM Tivoli Remote Control 3.8, IBM Tivoli NetView 7.1.x, IBM Tivoli Enterprise Console 3.8, IBM Tivoli Provisioning Manager 3.1, and IBM Tivoli Provisioning Manager Express for Software Distribution 4.1.1. His areas of expertise include system management architectures and Information Technology Infrastructure Library compliant services design. Thanks to the following people for their contributions to this project: Arzu Gucer, Editor International Technical Support Organization, Poughkeepsie Center Kristin Wall Gibson IBM USA Elizabeth Purzer IBM USA Timothy Brown IBM USA
Become a published author

Join us for a two to six week residency program. Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers. Your efforts help increase product acceptance and client satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Find out more about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html
Preface
xix
Comments welcome
Your comments are important to us! We want our IBM Redbooks to be as helpful as possible. Send us your comments about this or other IBM Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an e-mail to: redbook@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
xx
Chapter 1.
Certification overview
This chapter provides an overview of the skills you require to obtain an IBM Advanced Technical Expert certification. This chapter designs the following sections to provide a comprehensive review of specific topics that are essential for you to obtain the certification: IBM Professional Certification Program Tivoli Provisioning Manager Express for Software Distribution V4.1Certification Recommended resources for study
1.1 IBM Professional Certification Program

Having the right skills for the job is critical in the growing global marketplace. IBM Professional Certification, designed to validate skill and proficiency in the latest IBM solution and product technology, can help provide a competitive edge. The IBM Professional Certification Program Web site is available at: http://www.ibm.com/certify/index.shtml The Professional Certification Program from IBM offers a business solution for skilled technical professionals seeking to demonstrate their expertise to the world. The program is designed to validate your skills and demonstrate your proficiency in the latest IBM technology and solutions. In addition, professional certification helps you excel at your job by giving you and your employer confidence that your skills have been tested. Your ability to deliver higher levels of service and technical expertise than non-certified employees, help you move on a faster career track. Professional certification puts your career in your control. The certification requirements are difficult, but they are not overwhelming. It is a rigorous process that differentiates you from everyone else. The mission of IBM Professional Certification is to: Provide a reliable, valid, and fair method of assessing skills and knowledge. Provide IBM with a method of building and validating the skills of individuals and organizations. Develop a loyal community of highly skilled certified professionals who recommend, sell, service, support, and use IBM products and solutions. The Professional Certification Program from IBM has developed certification role names to guide you in your professional development. The certification role names include IBM Certified Specialist, IBM Certified Solutions/Systems Expert, and IBM Certified Advanced Technical Expert for technical professionals who sell, service, and support IBM solutions. For technical professionals in application development, the certification roles include IBM Certified Developer Associate and IBM Certified Developer. An IBM Certified Instructor certifies the professional instructor. The Professional Certification Program from IBM provides you with a structured program leading to an internationally recognized qualification. The program is designed for flexibility by allowing you to select your role, prepare for and take tests at your own pace, and, in some cases, select from a choice of elective tests that are best suited to your abilities and requirements. Some roles also offer a
shortcut by giving credit for a certification obtained in other industry certification programs. You can be a network administrator, systems integrator, network integrator, solution architect, solution developer, value-added reseller, technical coordinator, sales representative, or educational trainer. Regardless of your role, you can start charting your course through the Professional Certification Program from IBM, today.
1.1.1 Benefits of certification

Certification is a tool that helps you to objectively measure the performance of a professional on a given job, at a defined skill level. Therefore, it is beneficial for individuals who want to validate their own skills and performance levels, their employees, or both. For optimum benefit, the certification tests must reflect the critical tasks required for a job, the skill levels of each task, and the frequency with which you require to perform a task. IBM prides itself in designing comprehensive, documented processes that ensure that IBM certification tests remain relevant to the work environment of potential certification candidates. In addition to assessing job skills and performance levels, professional certification can also provide such benefits as: For employees: Promotes recognition as an IBM certified professional Helps to create advantages in interviews Assists in salary increases, corporate advancement, or both Increases self-esteem Provides continuing professional benefits Measures the effectiveness of training Reduces course redundancy and unnecessary expenses Provides objective benchmarks for validating skills Makes long-range planning easier Helps to manage professional development Aids as a hiring tool Contributes to competitive advantage Increases productivity Increases morale and loyalty
For employers:
Chapter 1. Certification overview
For IBM Business Partners and consultants: Provides independent validation of technical skills Creates competitive advantage and business opportunities Enhances prestige of the team Contributes to IBM requirements for various IBM Business Partner programs
Specific benefits can vary by country (region) and role. In general, after you become certified, you receive the following benefits: Industry recognition Certification may accelerate your career potential by validating your professional competency and increasing your ability to provide solid, capable technical support. Program credentials As a certified professional, you receive your certificate of completion and the certification mark associated with your role for use in advertisements and business literature. This certificate is sent to you through e-mail. You can also request a hardcopy certificate, which includes a wallet-size certificate. The Professional Certification Program from IBM acknowledges the individual as a technical professional. The certification mark is for the exclusive use of the certified individual. Ongoing technical vitality IBM Certified professionals are included in mailings from the Professional Certification Program from IBM.
1.1.2 Tivoli Software Professional Certification

The IBM Tivoli Professional Certification program offers certification testing that sets the standard for qualified product consultants, administrators, architects, and partners. The program also offers an internationally recognized qualification for technical professionals seeking to apply their expertise in today's complex business environment. The program is designed for those who implement, buy, sell, service, and support IBM Tivoli solutions and want to deliver higher levels of service and technical expertise. Whether you are a Tivoli client, partner, or technical professional wanting to put your career on the fast track, you can start on the road to becoming a Tivoli Certified Professional today.
Benefits of being Tivoli certified

Tivoli certification provides the following benefits: For the individual: IBM Certified certificate and use of logos on business cards Note: Certificates are sent by e-mail. However, you can request for a paper copy of the certificate along with a laminated wallet card if you send an e-mail to the following address: mailto:certify@us.ibm.com Recognition of your technical skills by your peers and management Enhanced career opportunities Focus for your professional development For the IBM Business Partner: Confidence in the skills of your employees Enhanced partnership benefits from the IBM Business Partner program Billing your employees out at higher rates Strengthens your proposals to customers Demonstrates the depth of technical skills available to prospective customers
For the client: Confidence in the service due to professionals handling your implementation Ease of hiring competent employees to manage your Tivoli environment Enhanced return on investment (ROI) through more thorough integration with Tivoli and third-party products Ease of selecting a Tivoli Business Partner that meets your specific requirements
Certification checklist
Here is the certification checklist: 1. Select the certification that you want to pursue. 2. Determine which test or tests are required by reading the certification role description.
3. Prepare for the test, using the following resources provided: Test objectives Recommended educational resources Sample or assessment test Other reference materials Opportunities for experience Note: These resources are available from each certification description page, and also from the test information page. 4. Register to take a test by contacting one of our worldwide testing vendors: Thomson Prometric Pearson Virtual University Enterprises (VUE) Note: When providing your name and address to the testing vendor, specify your name exactly as you want it to be displayed on your certificate. 5. Take the test. Be sure to keep the Examination Score Report provided upon test completion as your record of taking the test. Note: After taking a test, your test results and your demographic data, including name, address, e-mail, and phone number are sent from the testing vendor to IBM for processing. Allow two to three days for transmittal and processing. After all the tests required for a certification are passed and received by IBM, your certificate is issued. 6. Repeat steps three through five until all required tests are successfully completed for the desired certification role. If additional requirements are required, such as an other vendor certification or exam, follow the instructions on the certification description page to submit these requirements to IBM. 7. After you complete your certification requirements, you are sent an e-mail asking you to accept the terms of the IBM Certification Agreement before receiving the certificate.
8. Upon acceptance of the terms of the IBM Certification Agreement, an e-mail is sent to you, which contains the following electronic deliverables: A Certification Certificate in PDF format, which you can print in either color, or black and white A set of graphic files of the IBM Professional Certification mark associated with the certification achieved Guidelines for the use of the IBM Professional Certification mark 9. To avoid unnecessary delay in receiving your certificate, ensure that IBM has your current e-mail on file by keeping your profile up to date. If you do not have an e-mail address on file, your certificate is sent through postal mail. After you receive a certificate by e-mail, you can contact IBM to request for a hardcopy certificate at the following mail address to be sent to you by postal mail: mailto:certify@us.ibm.com Note: IBM reserves the right to change or delete any portion of the program, including the terms and conditions of the IBM Certification Agreement, at any time without notice. Some certification roles offered through the IBM Professional Certification Program require recertification.
1.2 Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification
We can categorize the certification process as follows: Job role description or target audience: A Tivoli Certified Consultant: A technical professional of Tivoli Provisioning Manager Express for Software Distribution V4.1 is responsible for planning, installation, configuration, operations, administration, and maintenance of a Tivoli Provisioning Manager Express for Software Distribution V4.1 solution. This individual is expected to perform these tasks with limited assistance from peers, product documentation, and support resources. To attain the IBM Certified Deployment Professional - Tivoli Provisioning Manager Express for Software Distribution V4.1 certification, candidates must pass a test. Required prerequisites: Strong working knowledge of Tivoli Provisioning Manager Express for Software Distribution V4.1 infrastructure components Working knowledge of operating system, and networking and firewall concepts
Basic knowledge of supported databases Basic knowledge of protocols, including Hypertext Transfer Protocol (HTTP) Core requirement: In order to be certified you must select Test 879 - Tivoli Provisioning Manager Express for Software Distribution V4.1: Test 879 objectives Test 879 sample test Test 879 recommended educational resources Number of questions: 49 Duration in minutes: 60 Format: Multiple choice Required passing score: 65% (32 out of 49)
1.2.1 Test 879 objectives

For the most updated objectives of the Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification test, go to the Tivoli Certification Web site at the following address and click the Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification Test link: http://www.ibm.com/certify/certs/
1.2.2 To get 15% discount on the Certification

You can receive a 15% discount on the Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification, if you take the test at any Thomson Prometric testing center. Just remember to use the code 15T879.
1.3 Recommended resources for study

Courses and publications are offered to help you prepare for the certification tests. We recommend the courses, but they are not required before taking a certification test. If you want to purchase Web-based training courses or are unable to locate a Web-based course or classroom course at the time and location you desire, contact one of our delivery management teams at: Americas mailto:tivamedu@us.ibm.com EMEA mailto:tived@uk.ibm.com
AP mailto:tivtrainingap@au1.ibm.com Note: Course offerings are continuously being added and updated. If you do not see the courses listed in your geography, contact the delivery management team.
1.3.1 Courses
Course names and course numbers vary depending on the education delivery arm used in each geography. Refer to the Tivoli software education Web site to find the appropriate course and education delivery vendor for each geography. General training information is also available at IBM IT Training at: http://ibm.com/training
1.3.2 Publications
Before taking the test 879, which is for the Tivoli Provisioning Manager Express for Software Distribution V4.1 implementation, we recommend that you review Tivoli Provisioning Manager Express for Software Distribution V4.1 guides and IBM Redbooks. You can refer to the following guides: Version 4.1.1 - IBM Tivoli Provisioning Manager Express Installation Guide, SC32-0175 Version 4.1.1 - IBM Tivoli Provisioning Manager Express Administrators Guide, SC32-0172 Version 4.1.1 - IBM Tivoli Provisioning Manager Express for Inventory Users Guide, SC32-0174 Version 4.1.1 - Client Catalog User's Guide, SC32-0173 For the online publications of Tivoli Provisioning Manager Express for Software Distribution V4.1, refer to the following address at: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/c om.ibm.itpmesd.doc/toc.xml
IBM Redbooks for Tivoli Provisioning Manager Express for Software Distribution
You might want to refer to the IBM Redbook titled Deployment Guide Series: IBM Tivoli Provisioning Manager Express V4.1 for Software Distribution, SG24-7236. This book focuses on the planning and deployment of Tivoli Provisioning Manager Express for Software Distribution V4.1 in production environments. The target audience for this book are IT specialists who want to work on new Tivoli Provisioning Manager Express for Software Distribution V4.1 installations.
10
Chapter 2.
Planning
To successfully install an IBM Tivoli Provisioning Manager Express for Software Distribution V4.1 you require a proper architectural planning and requirements collection. This chapter summarizes the various core IBM Tivoli Provisioning Manager Express for Software Distribution components and some infrastructure deployment considerations for communication protocols, for small, medium, and large environments. This chapter provides hardware and software specifications, recommendations, and requirements, and discusses different customization considerations. This chapter includes the following topics: IBM Tivoli Provisioning Manager Express for Software Distribution components Infrastructure deployment considerations Customization considerations Hardware and software specifications and recommendations
11
2.1 IBM Tivoli Provisioning Manager Express for Software Distribution components
IBM Tivoli Provisioning Manager Express for Software Distribution is divided into two major core products: IBM Tivoli Provisioning Manager Express for Software Distribution IBM Tivoli Provisioning Manager Express for Inventory IBM Tivoli Provisioning Manager Express for Inventory is a subset of IBM Tivoli Provisioning Manager Express for Software Distribution. The software distribution and patch capabilities are not included. However, IBM Tivoli Provisioning Manager Express for Software Distribution product includes the IBM Tivoli Provisioning Manager Express for Inventory product capabilities.
2.1.1 IBM Tivoli Provisioning Manager Express for Software Distribution components
The administrative console to manage the server and the Software Distribution Catalog to deliver software to the client machines are the functions of the Tivoli Provisioning Manager Express for Software Distribution.
Server
The server is the control center that manages software packages, bundles, groups, users, logs, reports, and schedules. The IBM Tivoli Provisioning Manager Express for Software Distribution server has the following components: Administrators console You can use this browser-based interface to manage the process of the IBM Tivoli Provisioning Manager Express for Software Distribution. Administrators can manage multiple catalogs for different users, groups, or business units. They can also add, delete, and modify software packages, create bundles, reports and perform the task management and scheduling. Embedded version of IBM WebSphere Application Server: Express 6.02 IBM Java 2 SE SDK Version 1.4.2 This industry-standard, platform-independent programming language is part of the IBM Tivoli Provisioning Manager Express for Software Distribution server. The default server location is: C:\Program Files\IBM\Tivoli\TPMX\SERVER
12
Database
IBM Tivoli Provisioning Manager Express for Software Distribution installs IBM Cloudscape Version 5.1, which is a 100% Java SQL database provided along with WebSphere Application Server Express. This database provides a quick installation and integration solution. Cloudscape is an embedded relational database-management system. This component allows IBM Tivoli Provisioning Manager Express for Software Distribution to store and maintain the package metadata and log information. You can copy the database structure, which is the tpmxdb directory and all of its sub-contents, without stopping the service. The copied tpmxdb structure is useful to replicate problems from one server environment into another, and can be utilized by support. It is a good practice to periodically make a backup copy of the tpmxdb structure. The default database location is as follows: C:\ProgramFiles\IBM\Tivoli\TPMX\SERVER\db\tpmxdb The Cloudscape database that is installed by default only allows one connection at a time and the database access is restricted to a single user. The IBM Tivoli Provisioning Manager Express for Software Distribution can also use other SQL databases that support Java Database Connectivity (JDBC) connections, if an enterprise database is required or an existing SQL database is already available. IBM Tivoli Provisioning Manager Express for Software Distribution can utilize other SQL databases with minimal changes to the installation. IBM Tivoli Provisioning Manager Express for Software Distribution is designed to work with any standard-based SQL server that provides connectivity through JDBC. Other SQL databases that meet the enterprise required are: IBM DB2 Oracle Microsoft SQL Server PostgreSQL Note: We recommend the IBM DB2 Universal Database for large implementations. Details concerning the configuration changes required to use DB2 can be found on the Web at: http://w3-103.ibm.com/software/xl/portal/!ut/p/_s.7_0_A/7_0_LT?nb=ca &ni=tivoli&ca=ondemandmanagement&pr=ovisioningmanagerexpress Configuring IBM Tivoli Provisioning Manager Express for Software Distribution to use another database instead of the embedded IBM Cloudscape V5.1, is considered an advanced topic and is not part of the exam.
Chapter 2. Planning
13
Agent
The Software Distribution Agent has two main features: The Software Distribution Agent controls the installation of software pull packages that require administrative rights to install and schedule pushes of software. C:\Program Files\IBM\Tivoli\TPMX\Agent\sdcagent.jar is the java file that launches the software distribution agent. The Software Distribution Catalog application is a Java-based application that presents a catalog of software packages to the user. From this catalog, the user can select a software package for installation. The software package is downloaded to the client and automatically installed. C:\Program Files\IBM\Tivoli\TPMX\Agent\sdcclient.jar is the java file that launches the software distribution catalog. The client agent runs as a service that checks the server periodically at specified intervals to find the next scheduled installation package. It is a local installer for the Software Distribution Catalog if a software package requires secure installation. The client applet runs either from the browser as a Java WebStart application or as a stand-alone Java application. It presents all software packages for which a particular user has access privileges. Users can select and install software packages from an online catalog. When the user selects a software package, the catalog shows detailed data about the software package. Note: The Software Distribution Agent runs in the background. There is no administrator or user interface. Because the client agent runs as a service. It can be disabled through the Services Administrators Tools function of the Windows Control Panel. By default, the client agent is set to start automatically. The client agent is listed in the list of services as: IBM Tivoli Provisioning Manager Express - Inventory Agent IBM Tivoli Provisioning Manager Express - Software Distribution Agent
Remote file shares

If network bandwidth over a wide area network (WAN) is an issue, IBM Tivoli Provisioning Manager Express for Software Distribution provides the ability to store the software packages on remote files shares that are geographically close to the clients. Note: The remote file shares can be preexisting file servers or they can consist of an infrastructure that is already in place.
14
2.1.2 Inventory components

A complete IBM Tivoli Provisioning Manager Express for Inventory solution includes the same components as the IBM Tivoli Provisioning Manager Express for Software Distribution, from the server point of view. However, the IBM Tivoli Provisioning Manager Express for Inventory program agent is different from the IBM Tivoli Provisioning Manager Express for Software Distribution agent. The components for the Inventory solution are: Microsoft Windows 2000 or 2003 Server SQL database with JDBC support Java Web server IBM Tivoli Provisioning Manager Express for Inventory IBM Tivoli Provisioning Manager Express for Inventory program agent IBM and non-IBM systems are supported using the IBM Tivoli Provisioning Manager Express for Inventory program agent. The agent reads information from the Windows Registry, the Windows Management Instrumentation (WMI), and the system management BIOS (SMBIOS) of a client computer. After collecting the data from the computer, the Tivoli Provisioning Manager Express for Inventory program creates a file with all the information in it. This file can include: Processor type and speed Memory size PCI devices Logical disk information Operating system information Device drivers Installed software Regional settings IBM Tivoli Provisioning Manager Express for Inventory also accommodates portable computers. The collected inventory information can be stored locally. When network connectivity is restored, the inventory information is sent to the server database.
Chapter 2. Planning
15
Note: IBM Tivoli Provisioning Manager Express for Inventory program agent is divided into two major functions. The eGather2 function The eGather2 function performs the inventory scan, packs the data, and places it in a compressed file on the agent itself. The callHome2 function The callHome2 function is to call the egather2 function and upload the scanned date to the IBM Tivoli Provisioning Manager Express for Software Distribution server.
2.2 Infrastructure deployment considerations

When designing and deploying a Tivoli Provisioning Manager Express for Software Distribution infrastructure, you must consider several factors. Some of the factors include the following items: Number of packages that you manage Average package size Number of clients Number of distributions Frequency of inventory scans Hardware configurations Network topology Network bandwidth Pay careful attention to the network topology. Place the Software Distribution server or servers as close to the clients as possible. Connect the servers to the fastest backbone available, preferably 100 Mbps Ethernet or 1 Gbps Ethernet. The setup of the IBM Tivoli Provisioning Manager Express for Software Distribution environment is important for administrators. The administrator must collect the following information about their network topology and general environment setup: Are target machines behind firewalls? Does this require a proxy server? Are target machines going to access the server from low bandwidth network connections? Is the environment going to use directory sharing? Are there existing file share servers that can be reused?
16
Are the user IDs on the target machines created as restricted users? Is Microsoft Active Directory or Lightweight Directory Access Protocol (LDAP) being used for user authentication? How are the packages going to be grouped or categorized? How is the agent going to be rolled out? This is critical information about the topology of your machine infrastructure to determine what software distribution features and methods you can use for the most effective implementation. Document all functional and non-functional requirements prior to the implementation planning phase. IBM Tivoli Provisioning Manager Express for Software Distribution can be integrated with Microsoft Active Directory for user authentication and group membership replication. This can greatly simplify the grouping of packages and distributions based on organizational unit. This integration also eliminates a key client pain point: the requirement of users to remember another ID and password. Note: It is not possible to setup an IBM Tivoli Provisioning Manager Express for Inventory environment to configure all IBM Tivoli Provisioning Manager Express for Software Distribution agents to perform multiple scans at the same time and refresh scans at 9 p.m.
2.2.1 Communication protocols

If the server pushes out software packages to clients that have the Software Distribution client agent installed, or if the server allows clients to pull packages and install them through the Software Distribution Catalog, then the Server to Agent communication is always HTTP. HTTP is the only supported communication protocol at the moment. Sometimes, there is a proxy server used between the IBM Tivoli Provisioning Manager Express for Software Distribution agent and server. The server is Web-based and you can access it with the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console via HTTP in the Microsoft Internet Explorer Version 6.0 or higher.
Chapter 2. Planning
17
The communication protocol between IBM Tivoli Provisioning Manager Express for Software Distribution and the SQL databases is JDBC. See Figure 2-1.
Figure 2-1 Communication protocols
2.2.2 Small and medium environments

IBM Tivoli Provisioning Manager Express for Software Distribution server can handle up to 5000 clients, depending on size and frequency of distributions, in a typical architecture for small and medium environments. The server pushes out software packages to clients that have the Software Distribution client agent installed or allows clients to pull packages and install them through the Software Distribution Catalog.
18
2.2.3 Large environments

If you have a larger environment, then you can use multiple installations of IBM Tivoli Provisioning Manager Express for Software Distribution servers. The IBM Tivoli Provisioning Manager Express for Software Distribution program provides the export and import function to simplify the replication of the metadata associated with software packages and bundles from one server to another. Another solution is to use multiple IBM Tivoli Provisioning Manager Express for Software Distribution servers and a load balancer right in front. For large enterprise environments, we recommend either IBM WebSphere Edge Server V2 or WebSphere Application Server V5 Edge Components (both include IBM Network Dispatcher) to provide load balancing among several Web servers. Customization is required on the server side, so that only one instance of the Software Distribution database exists. You require to use a database other than the default Cloudscape database that is shipped with the product. The Cloudscape database that is installed by default only allows one connection at a time. We recommend IBM Universal Database (UDB) for large implementations.
2.3 Customization considerations

To integrate IBM Tivoli Provisioning Manager Express for Software Distribution ships with a built-in version of the Cloudscape database and WebSphere Express into an existing clients infrastructure. you can easily customize IBM Tivoli Provisioning Manager Express for Software Distribution. In general, the following is required to integrate IBM Tivoli Provisioning Manager Express for Software Distribution into an existing infrastructure: Java programming language Version 1.4.2 or later A relational database system supporting SQL and JDBC Each of these prerequisites is available on a large number of platforms and from several different vendors.
Chapter 2. Planning
19
2.4 Hardware and software specifications and recommendations

The following sections describe the various hardware and software specifications of the Tivoli Provisioning Manager Express for Software Distribution.
2.4.1 Server
For the best performance, we recommend the following system requirements for the Tivoli Provisioning Manager Express for Software Distribution server computer: Dual Intel Xeon processors at least a 550 MHz Intel or AMD processor A minimum of 512 MB of memory (we recommend 1 GB) 15,000 RPM Ultra320 Small Computer System Interface (SCSI) hard drives with Redundant Array of Independant Disks (RAID) controller at least 3 GB of hard disk space for the operating system and required applications plus 2 MB per client. DVD-ROM drive 500 MB free hard disk space for server installation Additional space as required for IBM Tivoli Provisioning Manager Express for Software Distribution package repository Multiple network interface cards (NICs) that support Transmission Control Protocol/Internet Protocol (TCP/IP) A fixed IP address to assign to the Web application server and, if required, a fixed subnet mask address and default gateway address Internet Explorer Version 6 or higher for local console administration Embedded version of IBM WebSphere Application Server: Express 6.02 (included in software) Java J2SE SDK/Runtime (included in IBM Tivoli Provisioning Manager Express for Software Distribution) IBM Cloudscape database 5.1 (included in software) or later to export captured data to any SQL-compliant database
20
2.4.2 Administrative console requirements

The IBM Tivoli Provisioning Manager Express for Software Distribution server is supported on the following operating systems that support a Web browser HTTP: Microsoft Windows 2000 Server with Service Pack 4 or later Microsoft Windows 2000 Advanced Server Microsoft Windows 2000 Data Center Server Microsoft Windows XP Pro w/SP2 or later Microsoft Windows 2003 Enterprise/Standard R2 Microsoft Windows Server 2003 Standard Microsoft Windows Server 2003 Enterprise Microsoft Windows Server 2003 Data Center Note: You must note the following points: If IBM Java Runtime Error (JRE) Version 1.4.2 with Java Web Start is not installed on the Windows machine, a message is shown. Java WebStart is required. Please click here to download and install the Java application on your system. You must close and restart the browser before reloading this page for the Access Catalog button to be displayed. It is expected that in the future releases of IBM Tivoli Provisioning Manager Express for Software Distribution program, Linux is also supported.
2.4.3 Load Balancer

Regarding the Load Balancer for the large environments solution, we recommend the following system requirements for best performance: Dual IBM POWER5 technology-based processors, 1.9 GHz 1 GB of ECC RAM 15,000 RPM Ultra320 SCSI hard drive DVD ROM drive Multiple network interface cards IBM AIX 5L V5.1 or higher
Chapter 2. Planning
21
2.4.4 Client
IBM Tivoli Provisioning Manager Express for Software Distribution and IBM Tivoli Provisioning Manager Express for Inventory have certain client and server requirements.
Client requirements
The following are the client requirements: Microsoft Windows NT 4.0 or Windows 9X, 2000, 2000 Pro, 2000 Server, 2000 Advanced Server or 2000 Data Center Server, XP or XP Pro, 2003 Enterprise or Standard or Server 2003 Standard, Enterprise or Data Center Network connection (TCP/IP) Java JRE 1.4 and later (included in software) Tivoli Provisioning Manager Express for Software Distribution agent Tivoli Provisioning Manager Express for Inventory program agent Microsoft Internet Explorer 6.0 (or later) Web browser if access to Web site is required CD drive for installing the client agent using the Tivoli Provisioning Manager Express for Software Distribution media. You can also install the Agent using a USB Memory stick. You can download a suitable install package from the Web site to any client for subsequent transfer to desired media. Internet connection for downloading and installing the client agent using the Web A network card that supports TCP/IP
22
Chapter 3.
Installation
This chapter provides all the information you require to install and uninstall IBM Tivoli Provisioning Manager Express for Software Distribution on a server, and to install and uninstall the IBM Tivoli Provisioning Manager Express for Software Distribution Agent on a client machine. This chapter covers the following topics: Server installation tasks Server installation and verification Agent installation and verification Agent installation as an unattended command line installation Server uninstallation and verification Agent uninstallation and verification
23
3.1 Server installation tasks

For the detailed installation steps for IBM Tivoli Provisioning Manager Express for Software Distribution server 4.1.1, refer to Version 4.1.1 - IBM Tivoli Provisioning Manager Express Installation Guide, SC32-0175, and the Deployment Guide Series: IBM Tivoli Provisioning Manager Express V4.1 for Software Distribution, SG24-7236. This chapter summarizes the IBM Tivoli Provisioning Manager Express for Software Distribution installation requirements and installation and uninstallation procedures for server and agent, focusing only on the key installation, uninstallation, and customization steps and parameters. You must install the following components to accomplish an IBM Tivoli Provisioning Manager Express for Software Distribution installation: Install the embedded version of IBM WebSphere Application Server Express V6.0.2. Include the IBM JRE Version 1.4.2 and Cloudscape V5.1 database in the WebSphere installation. Install the IBM Tivoli Provisioning Manager Express for Software Distribution Web application as a WebSphere profile, and create and populate the Cloudscape database. The following are the background tasks being performed right after the installation procedure: Installing profile (TPMXPROFILE) Installing the WebSphere Enterprise Application Resource.war file (tpmx.war) Creating configuration settings based on installation parameters Application waits on this screen for a while (depending on system speed) Creating database connection Configuring the application to use the Cloudscape database Installing WebSphere service Starting the WebSphere service. This may take some time, depending on the system, as the database is created and populated. Note: If you do not meet all of the installation requirements during the server installation of IBM Tivoli Provisioning Manager Express for Software Distribution program, the installation fails. A Windows message window opens indicating that you have not fulfilled the prerequisites.
24
3.1.1 Server installation: typical

The IBM Tivoli Provisioning Manager Express for Software Distribution is an easy-to-install product and the typical (quick) installation is straightforward to perform. Insert the IBM Tivoli Provisioning Manager Express for Software Distribution program installation CD. In most cases, the Launchpad installation program starts automatically and goes through the installation procedure. Selecting the Quick setup type only asks a set of questions and uses default values for all other settings. Note: The information required before beginning the installation of IBM Tivoli Provisioning Manager Express for Software Distribution server are: Server administration ID and password IP address and host name for the IBM Tivoli Provisioning Manager Express for Software Distribution server
3.1.2 Server installation: custom setup

A custom installation option provides more features than a quick installation and allows you to configure more of the settings that assume default values when using quick installation process. To perform a custom install, select Custom in the setup window. Custom setup type initiates a series of panels to collect detailed configuration information for the following categories: Web site settings E-mail settings Action authority settings Scheduling Password settings Form settings Security settings
Web site Settings window

The values Figure 3-1 shows are used to establish the WebSphere Application Server: Server name for asset scans is picked up automatically or you use the IP address. Note: The box labeled server name for asset scans is the fully qualified domain name of the server. Server port is set by default to 80.
Chapter 3. Installation
25
Server (Web) URL is the URL for the server and is set by default to tpmx. The URL for uploading asset scans is generated automatically from the server name for asset scans, the server port, and the server (Web) URL. The administrators e-mail address for reporting problems is the e-mail address of the administrator for reporting problems and where e-mails generated by the system is sent.
Figure 3-1 Web site Settings window
E-mail Settings window

The values supplied in this panel are used to establish the e-mail services that the IBM Tivoli Provisioning Manager Express for Software Distribution functions utilize. You can leave it to the default setting, which is to leave these disabled. Quick install uses these parameters.
26
If you choose to enable the e-mail support, select the Enable e-mail functions box in the e-mail settings window and input the following e-mail settings as Figure 3-2 shows: Simple Mail Transfer Protocol (SMTP) server name or IP address is the address for the SMTP server you are using for e-mail. The return e-mail address is the address to which users respond after receiving certain e-mail requests in the return e-mail address field. In some cases, this is the same as the administrators e-mail address. E-mail must be in e-mail format. Select the check box marked Enable SMTP authentication to enable the SMTP server to authenticate the SMTP user ID and password. Type the SMTP user ID if you have enabled the SMTP server authentication. Type the SMTP password if you have enabled the SMTP server authentication.
Figure 3-2 E-mail Settings window
27
Action Authority Settings window

With the Action Authority Settings window, you can associate specific tasks with specific user accounts and authority roles. All Users, Super-User and Admin, or Administrator Only are the three kind of categories you could select to authorize a specific user account to perform a specific task. Each user ID in Software Distribution is a member of one of the following groups. Each group has permissions associated with it: User Superuser Administrator Note: The authority roles established here only affect the Inventory functions. The specific tasks list that Figure 3-3 shows, is as follows: Update user passwords to allow specific user account to update a user password. Update user details to allow specific user account to update the user details. Change asset owner to allow specific user account to change the asset owner of an asset. Add or delete a user to allow specific user account to add and delete users. Add or delete a group to allow specific user account to add and delete groups. Customize reports to allow specific user account to customize reports. Search to allow specific user account to use the search function. Manage tasks to allow specific user account to manage tasks. Reprocess scanned asset files to allow specific user account to reprocess scanned asset files. For additional information about user accounts, refer to 5.2, Managing user IDs on page 100 or refer to Version 4.1.1 - IBM Tivoli Provisioning Manager Express for Inventory Users Guide, SC32-0174.
28
See Figure 3-3 for better understanding of the specific tasks list mentioned on the previous page.
Figure 3-3 Action Authority Settings window
Scheduling window
In the Scheduling window shown in Figure 3-4, you have two scheduling options. The values supplied in this window control the interval of communication between the Inventory agent and the server. Select Automatically upload revised asset information if you want the client agent to automatically upload revisions of asset information about a fixed schedule. The upload interval in days is set by default to 90. Select Automatically run specific reports and send e-mails if you want the server to automatically perform tasks on a set schedule. In this panel: Check for scheduled tasks every is the frequency that the server must check for scheduled tasks in minutes, hours, or days. Specify the interval units to be used when scheduling tasks globally specifies the interval unit to be used when setting a task frequency in minutes, hours, or days.
29
See Figure 3-4.
Figure 3-4 Scheduling window
Password Settings window

In the Password Settings window shown in Figure 3-5, you can define how to manage and create user account passwords that are required to access the IBM Tivoli Provisioning Manager Express for Software Distribution program. The following values supplied, in this panel control, the password security requirements for all user IDs, which are created to access the application: Password Control Settings Select Encrypt password stored in the Database if you want passwords encrypted. Select Allow user to reuse passwords to determine how often a user can reuse a password (always, never, after xxx days). Select Expire new passwords, so users must change password during first logon to produce a requirement for users to establish their own password after receiving the application-generated password. Select Expire passwords after XX days to specify the number of days a password is accepted. The default is 186 days.
30
Password Creation Rules Select Enable password rule checking, so that the creation of passwords adheres to the following rules: Must contain is the type of characters a password must have, such as non-numeric, numeric, or non-alphanumeric. The default is set to non-numeric and numeric. Minimum length is for the minimum number of characters in the password. The default is set to 6. Maximum length is for the maximum number of characters in the password. The default is set to 15. Maximum number of matching sequential characters specifies the maximum number of sequential password characters that can match. The default is set to 2. Maximum number of sequential characters reused from previous password is the maximum number of sequential password characters that you can reuse in a new password. The default is set to 3.
Figure 3-5 Password Settings window
31
Form Settings window

The Form Settings window, shown in Figure 3-6, displays fields you can select when you require them in order to successfully add an asset or user to the database. These are the fields that users must complete during the asset registration process before adding an asset or uploading an asset scan: Asset Demographics Form Owner is selected by default. Asset Tag, Department, Location, Asset Type, Description, Floor, and Status are optional. User Demographics Form Name, Password, Location, User ID are selected by default. Address, Department, E-Mail, EmployeeID, Country, Nickname, Title, Town, Postal Code, Office phone number, and Mobile phone number are optional.
Figure 3-6 Form Settings window
32
Security Settings window

In the Security Settings window shown in Figure 3-7, you can choose to have the following options enabled. Use the values supplied to establish the client workstation security parameters which can be detected and monitored by the IBM Tivoli Provisioning Manager Express for Software Distribution program. Configure the server to verify client compliance with certain security settings that company security policies require: Select the Verify that all file shares on client computers are password-protected check box, if you want the IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that all file shares on client computers are password-protected each time the asset is revised. Select the Verify that all Windows screen savers are password-protected check box, if you want the IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that the Windows screen saver password is set on all client computers each time the asset is revised. Select the Verify that all power on passwords are enabled check box, if you want the IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that the Windows power on passwords are enabled. Select the Verify that all hard disk drive passwords are enabled check box, if you want the IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that the Windows hard disk drive passwords are enabled. Select the Windows accounts require passwords check box, if you want the IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that the Windows account password is required. Select the Required antivirus application check box, if you want the IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that the required antivirus application is installed on all client computers each time the asset is revised. Select the Required firewall application check box if you want IBM Tivoli Provisioning Manager Express for Software Distribution program to check and verify that the required firewall application is installed on all client computers each time the asset is revised.
33
See Figure 3-7.
Figure 3-7 Security Settings window
3.1.3 Server installation verification

There are several tasks you require to perform to verify if the IBM Tivoli Provisioning Manager Express for Software Distribution application installed successfully.
Accessing the administrative console

Open your browser and type the following: http://server_name/tpmx In this previously mentioned browser entry: server_name is the value entered during installation. If the port was changed from 80, enter the following: http://server_name:port/tpmx If the context root was changed during installation, enter the new context root value in place of tpmx.
34
The Welcome window opens. This is the primary access point for the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console. Users can access the Software Distribution Agent installer, the Software Distribution Catalog through Java WebStart, or log in to the console to view inventory data about their assets. Administrators have access to all the Software Distribution resources after logging in to the console. If you select Manage Assets, you can see the login panel to access the console. The display of the Welcome and Login panels confirms that the WebSphere Application Server has been successfully installed, configured, and started. Log in as the default administrator with the user ID admin and the password password. If you log in for the first time as an admin on the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console, you must change the admin password. Logging in with the admin user ID indicates that the Cloudscape database was successfully created and populated.
Verifying the WebSphere service

You can also verify the WebSphere Express application service by viewing the services under computer management. Perform the following steps to verifying the running of WebSphere service: 1. Open the Windows services applet and select Start Settings Control Panel. 2. Select Administrative Tools Services and locate the service. 3. Verify that the following service is running: IBM WebSphere Application Server V6 - Tivoli Provisioning Manager 4. Close the services utility.
35
Checking the server log file

The logging information shown in Example 3-1 is available in the following location: C:\ProgramFiles\IBM\Tivoli\TPMX\SERVER\TPMX.log
Example 3-1 tpmx.log entries
26-Jul-2006,13:46:25 [DBChecker] - 100% complete. Database population completed 26-Jul-2006,13:46:37 [DBChecker] - Completed importing e-mail template translations
Viewing the application log file in the administrative console

To see if there are common installation errors in the application log in the IBM Tivoli Provisioning Manager Express for Software Distribution Server installation, perform the following steps: 1. Log in as the default administrator user with the user ID admin and the password password. 2. Select Admin View Application Log and look for errors. Note: After the installation of IBM Tivoli Provisioning Manager Express for Software Distribution server, you can configure general environment and database settings for the server properties in the following file: C:\ProgramFiles\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-I NF\classes\isic.properties See 4.1.2, The isic.properties file on page 58 for further information about this file.
3.2 Installing the agent

To install the agent, you must have a good understanding of how the IBM Tivoli Provisioning Manager Express for Software Distribution Agent program interacts with the IBM Tivoli Provisioning Manager Express for Software Distribution server. You must install the IBM Tivoli Provisioning Manager Express for Software Distribution server before the built-in database is populated with information that the client agent provides. You must install the IBM Tivoli Provisioning Manager Express for Software Distribution agent on any machine in which you would like to collect inventory data or deliver software applications.
36
Attention: IBM Tivoli Provisioning Manager Express for Software Distribution includes an InstallShield installation executable that combines the installation of the Inventory and Software Distribution agents. When using only Tivoli Provisioning Manager Express for Inventory, the InstallShield installation executable only installs the inventory agent service. The installation process is virtually identical. The method used to install the client agent depends on the strategy you have for using it. Some enterprises might require an unattended installation. Others can install the client agent on IBM and non-IBM computers using the IBM Tivoli Provisioning Manager Express for Software Distribution CD. The executable is also available to users within your enterprise on the Web whenever they log in to the IBM Tivoli Provisioning Manager Express for Software Distribution program. It is also possible to install the agent via the agent installer package, if you are logged in to the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console and automatically register your client to the same console that you are currently logged in to. For this, you require the administrative rights on the client machine. All access methods execute the same installer. Note: Before you begin, ensure that the installer is provided with the IBM Tivoli Provisioning Manager Express for Software Distribution server name or IP address. The server port is set to 80 by default.
3.2.1 Installing the agent: typical

The IBM Tivoli Provisioning Manager Express for Software Distribution agent is an easy-to-install product and the typical (quick) installation is straightforward to perform. Insert the IBM Tivoli Provisioning Manager Express for Software Distribution program installation CD. In most cases, the Launchpad installation program starts automatically and goes through the installation procedure. If you select the quick setup type, it only asks a set of questions and uses default values for all other settings. The installation program TPMXSD_SETUP.EXE is the software package that installs the Software Distribution Agent and the Software Distribution Catalog application on the client.
37
3.2.2 Installing the agent: advanced setup

Selecting the advanced setup type initiates the following series of panels to collect detailed configuration information: Destination folder Server address Proxy settings Scheduler settings
Destination Folder window

In the Destination Folder window you can accept the following destination folder or you can click Change to select your own destination folder: C:\Program files\IBM\Tivoli\TPMX\Agent\
Server Address window

In the Server Address window shown in Figure 3-8, several options are available. The following values specified in the server address window allow the user to define the source server name, port, and server context: You can type the IP address next to the Server host name, for example 207.142.131.236, or you can type the Server's host name, for example server.yourcompany.com. You can enter the port number of the server next to the Port field. Port is set to 80 by default. Enter the appropruate value next to the Server context field. Server context is set to tpmx by default.
38
See Figure 3-8 for further clarification.
Figure 3-8 Server Address window
Proxy settings window

If the agent requires access to the IBM Tivoli Provisioning Manager Express for Software Distribution server through a proxy server, values specified in this window shown in Figure 3-9 allow the user to define any of the following proxy settings: Select the Use a proxy server check box to activate the proxy server settings window. Use the Proxy server field to define the proxy server. Use the Port field to define the communication port to the proxy server. Select the Proxy requires authentication check box to enable a special user authentication on the proxy server.
39
Enter the user ID in the User ID field to define the user for the special user authentication on the proxy server. Enter the password in the Password field to define the password for the special user authentication on the proxy server.
Figure 3-9 Proxy settings window
Scheduler settings window

You can set the agent to contact the server during a specified time or leave it to select a random time. Values specified in the Scheduler setting window allow the user to define the time frame in which the IBM Tivoli Provisioning Manager Express for Software Distribution agent communicates with the server. Modify the time range, Between and And, as required.
3.2.3 Verifying agent installation

The IBM Tivoli Provisioning Manager Express for Software Distribution agent installation can be verified by an administrator on the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console, or by the user on the client machine.
40
Verifying as an administrator
To verify the installation as an administrator, perform the following steps: 1. Access the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console as follows: a. Log in as the default administrator with the user ID admin and the password password. b. From the top menu bar, select Dists All Machines. 2. Verify that the client machine has auto registered and the time stamp is up to date.
Verifying as a user
You can verify the IBM Tivoli Provisioning Manager Express for Software Distribution agent and services by browsing the services under Computer Management. To verify the services, perform the following steps: 1. Open the Control Panel and select Start Settings Control Panel. 2. Open the Windows Services applet and select Administrative Tools Services. 3. Verify that the following services are running: IBM Tivoli Provisioning Manager Express - Inventory Agent IBM Tivoli Provisioning Manager Express - Software Distribution Agent 4. Close the services utility. The startup logging information of the IBM Tivoli Provisioning Manager Express for Software Distribution agent, shown in Example 3-2, can also be in the following file on the client machine: C:\Program Files\IBM\Tivoli\TPMX\Agent\logs\sdcagent.log
Example 3-2 sdcagent.log entries
Jul 17, 2006 2:47:47 PM INFO : ******* Jul 17, 2006 2:47:47 PM INFO : ******* 2006 ******* Jul 17, 2006 2:47:47 PM INFO : *******
V 4.1.1 ******* (c) Copyright IBM Corp. 2004, SDC Agent Started *******
41
Perform the following steps to access a Software Catalog: 1. Open a Web browser. 2. In the Address bar, type one of the following: http://server_name/tpmx Here, server_name is the name of the IBM Tivoli Provisioning Manager Express for Software Distribution server. http://server_IP_address/tpmx Here, server_IP_address is the IP address of the IBM Tivoli Provisioning Manager Express for Software Distribution server. 3. Press Enter. The home page opens. Note: You can save the IBM Tivoli Provisioning Manager Express for Software Distribution home page as one of your browser favorites for future use. 4. Click Access Catalog. The Security Warning window opens. Note: Verify that the security warning window displays IBM and that the publisher authenticity is verified by VeriSign, Inc. 5. Click Start. The IBM Tivoli Provisioning Manager Express for Software Distribution Catalog Login window opens. However, you may see the IBM Tivoli Provisioning Manager Express for Software Distribution Catalog - Desktop Integration window. 6. Click Yes to place an IBM Tivoli Provisioning Manager Express for Software Distribution catalog icon on desktop for easier access. Click No if an icon is already present on your desktop. Click Ask Later to defer it to a later time. Note: IBM Tivoli Provisioning Manager Express for Software Distribution uses Java Web Start technology to launch software catalog. You can launch the catalog either from an icon on the desktop or from Software Delivery Center welcome page by clicking Access Catalog. The Software Delivery Center client installation is complete when the Login window opens.
42
You can further test the client in any of the following ways: If the administrator provided you with a user name and password for a Software Distribution Catalog, type the user name and password in the fields provided, and click Login. If the administrator instructed you to create your own user name and password, do the following: a. Click Create New User. b. Type the user name you want to use and enter information in the required fields. c. In the Password field, type the password you want to use. d. In the Confirm field, type your password again. You must type the password exactly as you typed it in the Password field. e. Click OK. A catalog opens. Note: Catalog for new users might not have any software packages or bundles listed. In most cases, the administrator must assign a new user to a specific group before the user can install software from a catalog. You have completed the testing of Software Distribution client, when the Catalog window opens. Note: After the installation of IBM Tivoli Provisioning Manager Express for Software Distribution agent, you can configure agent properties in the following file: C:\ProgramFiles\IBM\Tivoli\TPMX\AGENT\sdc.conf
3.2.4 Installing an agent as an unattended command line installation

You can customize the tpmxsd_setup.exe to execute a silent installation. A silent installation, also referred to as an unattended installation, ensures that the client agent is permanently installed on client computers without any user intervention.
43
The parameters that are available for you to execute on the command line are shown in Table 3-1.
Table 3-1 Command line properties for agent installation Property SERVER_HOSTNAME SERVER_CONTEXT SERVER_PORT CALLHOME_WINDOW_START CALLHOME_WINDOW_END Description The host name or IP address of the server. This property is required. DocRoot value for application server If the server runs on a nonstandard port, specify the port number here. Callhome selects a random time for its daily call to the server. By default this time is between 9:00 and 17:00 local time. To override this time window, specify the hour only in 24 hour format. Valid values are 0 to 23 where 0 means midnight. For debugging only. Set to 1 to tell callhome to write debug info to callhome.txt Hostname or IP address for the proxy server, if required. Port name for the proxy server The user ID, if the proxy requires authentication. The password, if the proxy requires authentication. The user ID and password, format user:password, encoded in base64. This overrides the user ID and password properties. Use this if you do not want to make the password easily visible. Remember, base64 is not encryption. Somebody that knows the algorithm can decode it and learn the password. The time, in minutes, between checks for scheduled distributions. Enable or disable functions in the user interface to create users and change passwords. Values are true or false. Default <blank> tpmx 80 9 17
CALLHOME_DEBUG PROXY_HOSTNAME PROXY_PORT PROXY_USER_ID PROXY_PASSWORD PROXY_AUTH_B64
0 <blank> <blank> <blank> <blank> <blank>
SWD_REFRESH_INTERVAL SWD_USER_MGMT_ENABLED
60 true
The following is the syntax of three commands for unattended command line agent installation: tpmxsd_setup.exe /s /v /qn SERVER_HOSTNAME=sd.server.company.com SWD_USER_MGMT_ENABLED=true SWD_REFRESH_INTERVAL=180"
44
In the previous syntax, servername is the network name or IP address of the server on which IBM Tivoli Provisioning Manager Express for Software Distribution is installed. The following code is an example of an msi silent installation. msiexec /i tpmxsd.msi /qn SERVER_HOSTNAME=servername The following are the msi silent installation options: /qn: silent install, no progress bar displayed /qb: silent install, progress bar in small dialog /qr: silent install, progress bar in large dialog
3.2.5 Uninstalling the server

IBM Tivoli Provisioning Manager Express for Software Distribution server installation can be uninstalled using a maintenance program. This program lets you remove the current installation. There are two possibilities to uninstall the server: Using the maintenance program Using the add/remove program from the control panel
Using the maintenance program

Perform the following steps to remove IBM Tivoli Provisioning Manager Express for Software Distribution server from the system: 1. To access this maintenance program, start the Launchpad for IBM Tivoli Provisioning Manager Express for Software Distribution depending on which install you want to perform maintenance on. When you start the Installshield wizard, a Welcome window opens. Insert the IBM Tivoli Provisioning Manager Express for Software Distribution installation CD and the Launchpad window opens. If it does not start, perform the following steps: a. Click Start Run. b. Type D:\lauchpad.exe, where d is the drive letter of the drive that contains the installation CD, and then click OK. 2. Select IBM Tivoli Provisioning Manager Express for Software Distribution (Server). 3. Select Click here to install IBM Tivoli Provisioning Manager Express for Software Distribution server. 4. Choose Remove from the Welcome to Maintenance window to remove all installed features.
45
5. Confirm when the uninstall window opens. 6. Choose OK to completely remove the selected application and all of its features. 7. Click Finish to complete the uninstall procedure.
Using the Add/Remove program from the control panel

Perform the following steps to remove IBM Tivoli Provisioning Manager Express for Software Distribution Server from the system: 1. Open the Windows Services applet and select Start Settings Control Panel Add/Remove Programs. 2. Select IBM Tivoli Provisioning Manager Express for Software Distribution. 3. Press the change/remove button. 4. Choose Remove from Welcome to Maintenance window to remove all installed features. 5. Confirm when the uninstall window opens. 6. Choose OK to completely remove the selected application and all of its features. 7. Click Finish to complete the uninstall procedure.
3.2.6 Verifying the server uninstallation

There are several tasks you must perform to verify the IBM Tivoli Provisioning Manager Express for Software Distribution application uninstalled successfully.
Verifying the removal of the WebSphere service

You can also verify the WebSphere Express application service from the view services under Computer Management. Perform the following steps to uninstall the running WebSphere service: 1. Open the Windows services applet and select Start Settings Control Panel. 2. Open the Administrative Tools Services and locate the service. 3. Verify that the following service is removed: IBM WebSphere Application Server V6 - Tivoli Provisioning Manager 4. Close the services utility.
46
Verifying program removal from the Add/Remove panel

You can also verify the IBM Tivoli Provisioning Manager Express for Software Distribution program if you view the Add/Remove program panel through the Control Panel. Perform the following steps to verify the removal of the IBM Tivoli Provisioning Manager Express for Software Distribution program: 1. Open the Windows Services applet and select Start Settings Control Panel Add/Remove Programs. 2. Check if the IBM Tivoli Provisioning Manager Express for Software Distribution is removed. 3. Close the Add\Remove Program window.
3.2.7 Uninstalling the agent

You can uninstall the IBM Tivoli Provisioning Manager Express for Software Distribution agent installation using a maintenance program. This program lets you remove the current installation and uninstalls both agents. There are three possibilities to uninstall the agent: Using the maintenance program Using the Add/Remove program from the control panel Using the tpmxsd_setup.exe
Using the maintenance program

Perform the following steps to remove the IBM Tivoli Provisioning Manager Express for Software Distribution agent from the system: 1. To access this Maintenance program, start the Launchpad for IBM Tivoli Provisioning Manager Express for Software Distribution depending on which install you want to perform maintenance on. When you start the Installshield wizard a Welcome window opens. 2. Insert the IBM Tivoli Provisioning Manager Express for Software Distribution installation CD and the Launchpad window opens. If it does not start, perform the following steps: a. Select Start Run. b. Type D:\lauchpad.exe, where d is the drive letter of the drive that contains the installation CD, and then click OK. 3. Select IBM Tivoli Provisioning Manager Express for Software Distribution (Agent). 4. Select Click here to install IBM Tivoli Provisioning Manager Express for Software Distribution agent.
47
5. Click Next. 6. Choose Remove to remove all installed features. 7. Confirm when uninstall window opens. 8. Choose OK to completely remove the selected application and all of its features. 9. Click Finish to complete the uninstall procedure.
Using the Add/Remove program from the control panel

Perform the following steps to remove IBM Tivoli Provisioning Manager Express for Software Distribution agent from the system: 1. Open the Windows services applet and select Start Settings Control Panel Add/Remove Programs. 2. Select IBM Tivoli Provisioning Manager Express for Software Distribution (Agent). 3. Press the Remove button. 4. The confirm uninstall window opens. Choose OK to completely remove the selected application and all of its features. 5. Close the Add/Remove Programs window.
Using the tpmxsd_setup.exe

Start the agent install window from the IBM Tivoli Provisioning Manager Express for Software Distribution Installation CD. 1. Insert the IBM Tivoli Provisioning Manager Express for Software Distribution Installation CD. 2. Start the Product CD, which is as follows: \TPMXSWDA\tpmxsd_setup.exe. 3. Click Next. 4. Choose Remove to remove all installed features. 5. Confirm when the uninstall window opens. 6. Choose OK to completely remove the selected application and all of its features. 7. Click Finish to complete the uninstall procedure.
48
3.2.8 Verifying agent uninstallation

There are several tasks that you must perform to verify that the IBM Tivoli Provisioning Manager Express for Software Distribution agents are uninstalled successfully.
Verifying the removal of agent services

You can verify this through the view services under Computer Management. Perform the following steps to uninstall the two agent services: 1. Open the Windows services applet and select Start Settings Control Panel. 2. Select Administrative Tools Services and locate the service. 3. Verify that the following services are removed: IBM Tivoli Provisioning Manager Express for Software Distribution: Inventory Agent IBM Tivoli Provisioning Manager Express for Software Distribution: Software Distribution Agent 4. Close the services utility.
Verifying program removal from the Add/Remove panel

You can also verify the IBM Tivoli Provisioning Manager Express for Software Distribution program if you view the Add/Remove program panel through the Control Panel. Perform the following steps to verify the removal of the IBM Tivoli Provisioning Manager Express for Software Distribution agent program: 1. Open the Windows services applet. Select Start Settings Control Panel Add/Remove Programs. 2. Check if the IBM Tivoli Provisioning Manager Express for Software Distribution (Agent) is removed. 3. Close the Add\Remove program window.
49
50
Chapter 4.
Configuration
This chapter provides information about how to configure the IBM Tivoli Provisioning Manager Express for Software Distribution product after you have installed it. The following topics are covered in this chapter: Server properties files Configuring the agents
51
4.1 Server properties files

The behavior of the IBM Tivoli Provisioning Manager Express for Software Distribution server is controlled through the properties files. This section describes the server properties files. There are five key configuration files that control how the IBM Tivoli Provisioning Manager Express for Software Distribution server operates: common.properties contains general system properties, including user demographics compliance and database connectivity settings. isic.properties contains settings specific to the inventory component and assets properties. ldap.properties contains settings specific to the optional integration with a Lightweight Directory Access Protocol (LDAP). log4j.properties contains settings specific to logging in the Java environment. sdc.properties contains settings specific to the software distribution component and the software catalog. You can modify the configuration files in one of the following two ways: Use the administrator console and select edit properties from the administrator menu. Open the file in a standard text file editor and make the changes. We recommend you to use the administration console to ensure format and values are consistent and valid. You are required to log in with a user account that has administrator authority to do this. In some situations you may have to make modifications through a text editor, as not all properties are available through the administration console. Note that there are slight differences when entering data through the administrator console and using a text editor. For instance, a colon (:) is preceded by a back-slash in the text file, and the back-slash used in Windows file systems between folders is written as forward slashed in the text file. When you are using the administrator console, the data you enter is without these translations. Also, note that the system makes automatic backup versions when you use the administrator console. If you make extensive changes via a text editor, you must take a backup yourself.
52
The default location of these configuration files is as follows: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\classes The actual location of these configuration files can differ, depending on specific installation choice and language version. See Figure 4-1.
Figure 4-1 The Edit Properties page in the administrator console
The following sections discuss each of the configuration files. For additional information please consult the Version 4.1.1 - IBM Tivoli Provisioning Manager Express Administrators Guide, SC32-0172. Many properties are based on true/false values. Some of these properties use 0/1 or yes/no instead of true/false. We recommend you to stick with the existing value-types. Note that not all values can or must be modified.
Chapter 4. Configuration
53
4.1.1 The common.properties file

This section describes the common.properties configuration file. You can use the common.properties file for the following three major functions: Controls general system settings for the server Controls database connection settings Controls user demographics compliance. The following are the relevant properties and their usage: authentication.LDAP=true | false This parameter defines whether the IBM Tivoli Provisioning Manager Express for Software Distribution server must authenticate users from an LDAP, or base it on the user database that is part of the IBM Tivoli Provisioning Manager Express for Software Distribution product. The default setting does not enable the LDAP authentication. authentication.LDAP.config=<filename> If you enable the LDAP authentication, the file specified here is used for the remaining LDAP configuration. The default value is ldap.properties. Under normal conditions, this value must be kept to its default. The contents of the ldap.properties file is further discussed in 4.1.4, The ldap.properties file on page 85. properties.backup.archive=<integer> By default, five versions of the properties files are kept in the archives. This field is used to define how many versions to keep. The properties file are stored in: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\classes When you apply a change by clicking the Submit button on the Properties page, the older versions of the properties file are incremented. If the oldest version has the incremental number equal to the previously given value, then it is discarded. An example of these files is shown in Example 4-1.
Example 4-1 Archive versions of properties files
Directory of C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\classes 07-08-2006 15:07 5.730 common.properties 28-07-2006 11:53 5.606 common.properties.1 26-07-2006 14:09 5.608 common.properties.2 26-07-2006 14:02 5.608 common.properties.3 26-07-2006 14:01 5.596 common.properties.4
54
26-07-2006 07-08-2006 28-07-2006 09-07-2006 26-06-2006 03-08-2006 09-07-2006 02-06-2006 26-06-2006
13:46 15:06 11:56 09:13 06:10 09:58 09:13 03:12 06:10
5.609 17.149 16.890 17.368 9.456 1.444 2.130 522 3.223
common.properties.5 isic.properties isic.properties.1 isic.properties.2 ldap.properties log4j.properties log4j.properties.1 oms.properties sdc.properties
The archiving functionality covers all properties files that are changed from the administrator console.
User demographics compliance

The term user demographics is used to specify information that pertains to a user, as opposed to an asset. You can use the user records to associate assets with specific users. You can use the demographics information to help in the identification of a specific user, for example support people use this information. All the fields in Example 4-2 take true or false values. A true value specifies that this is mandatory information in the end user demographics form. This form is used when a user logs in to the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console for the first time and selects the new user option.
Example 4-2 True or false values in the demographic form
users.title.required=false users.forename.required=true users.surname.required=true users.country.required=false users.userid.required=true users.address_1.required=false users.address_2.required=false users.e-mail.required=true users.town.required=false users.postcode.required=false users.nickname.required=false users.tel_no.required=false users.mob_no.required=false users.employeeid.required=false users.department.required=false users.location.required=false users.password.required=true
55
In addition to the predefined fields in Example 4-2, it is possible to add an additional nine fields to the form. These fields do not have a descriptive name associated with them, but they take a generic form such as the following, where X is a value from 1 through 9: user_info.customX.required The required-true/false changes take effect immediately without restarting the application, if you use the administrator console and click Submit. Note: The descriptive text shown in the new user form is defined in the file called ApplicationResources.properties, which is located in the installation directory, in the following folder: \SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\classes Look for the following lines: prompt.user_info.custom1=1 prompt.user_info.custom2=2 prompt.user_info.custom3=3 prompt.user_info.custom4=4 prompt.user_info.custom5=5 prompt.user_info.custom6=6 prompt.user_info.custom7=7 prompt.user_info.custom8=8 prompt.user_info.custom9=9 : : : : : : : : :
For example, the text could be as follows: prompt.user_info.custom1=Contact preference (Mail,IM,Phone): Do not change any other lines because it can cause unpredictable results. You must restart the IBM Tivoli Provisioning Manager Express for Software Distribution server service for these changes to take effect.
New user form design

The form presented to new users include 18 fields, which have 9 left and 9 right. These fields are used to input any of the mandatory or optional information as specified previously. The fields all take the form of users.display.left.x and users.display.right.x, with x being in the interval 0 through 8.
56
Example 4-3 shows valid values to put into any of the 18 fields.
Example 4-3 Valid values for the 18 fields
users.userid users.e-mail users.title users.forename users.surname users.initials users.nickname users.company users.location users.department users.floor users.room users.team users.org users.employeeid users.mailpoint users.address_1 users.address_2 users.town users.postcode users.country users.state users.tel_no users.mob_no user_info.custom1 user_info.custom2 user_info.custom3 user_info.custom4 user_info.custom5 user_info.custom6 user_info.custom7 user_info.custom8 user_info.custom9 Important: All 18 input fields must represent a valid entry. It is not allowed to have one or more fields void, because it results in an error when the end user tries to open the page. Also, make sure all required fields are displayed. The mandatory checking only applies to displayed fields.
57
Documentation filenames
The remaining part of the editable fields in the common.properties file is used to specify the filenames of the pdf files that are part of the documentation. The application no longer uses this information, because all documentation is now available via the Internet. The fields and the default values areas follows: file.tpmx.admin.guide=IBM_TPMX_Administrators_Guide.pdf file.tpmx.install.guide=IBM_TPMX_Installation_Guide.pdf file.tpmxi.users.guide=IBM_TPMX_for_Inventory_Users_Guide.pdf file.tpmxsd.users.guide= IBM_TPMX_for_Software_Distribution_Users_Guide.pdf file.tpmxi.quickstart.guide=IBM_TPMX_for_Inventory_Quick_Start_Guide.pdf file.tpmxsd.quickstart.guide= IBM_TPMX_for_Software_Distribution_Quick_Start_Guide.pdf
4.1.2 The isic.properties file

This section describes the isic.properties configuration file. These settings are mainly for the inventory part of the product. You can use the isic.properties file for the following nine major functions: 1. Define asset match, asset registration, and performance queries related properties. 2. Define e-mail, e-mail engine, and e-mail template related properties. 3. Define report related properties. 4. Define upload and authority related properties. 5. Define files and directories related properties. 6. Define new user and password related properties. 7. Define schedules and probes related properties. 8. Define database cleanup and system maintenance related properties. 9. Define security related properties. Important: schema=ASSET is the schema used for all database tables related to inventory. You must not change it.
58
E-mail related properties

Many of the features in IBM Tivoli Provisioning Manager Express for Software Distribution rely on e-mail. The basic configuration of e-mail is shown in Example 4-4.
Example 4-4 isic.properties: e-mail
#These properties are used for e-mailing via SMTP (Simple Mail Transport Protocol). e-mail.enabled=no smtp.server= #configure the following parameters if smtp authentication is required smtp.authentication=false smtp.userid= smtp.password= The following are some important e-mail related properties: e-mail.enabled=yes | no Use this value to enable or disable e-mailing. When enabled, the system can send e-mails to one or more users with specific information or requests. By default e-mails are not enabled. When you enable an e-mail, you must consider making the e-mail address a required field in the new user form. smtp.server=<server> This value specifies the smtp server for you to use for e-mails. If the smtp server is installed on the IBM Tivoli Provisioning Manager Express for Software Distribution server, use localhost as the value. Make sure to use a fully-qualified domain name if the smtp server is in a domain that is not in the IBM Tivoli Provisioning Manager Express for Software Distribution servers Domain Name System (DNS) suffix-list. smtp.authentication=true | false smtp.userid=<userid> smtp.password=<password> If the smtp server requires authentication, use these values to enable authentication and set a valid user ID and password.
59
E-mail and reporting related properties

With IBM Tivoli Provisioning Manager Express for Software Distribution, it is possible to generate reports and distribute to end users or administrators. You can use the properties listed in Example 4-5 to properly configure the formats of the reports.
Example 4-5 isic.properties: e-mail and reporting
#This is the default name that is used when a report is e-mailed out. file.e-mail.name=report.csv file.e-mail.mime.type=application/vnd.ms.excel #Encoding can be UTF-8, UTF-16BE or UTF16LE (Default) file.e-mail.encoding=UTF-16LE #Type can either be TSV (Tab Seperated Value) or CSV (Comma Seperated Value) file.e-mail.type=TSV The following are e-mail and reporting related properties: file.e-mail.name=<filename> This is the filename used for reports that are attached to e-mails. The system exports the report to a tab-separated or comma-separated file with this name and attaches it to the e-mail that is sent out. file.e-mail.mime.type=<mime type> Defines the mime type for you to use for the attached file with the report. Be careful only to use valid mime types that are compatible with either plain text or comma-separated values. file.e-mail.encoding=<UTF-8 | UTF-16 | UTF-16LE> Defines the encoding type used. Takes one of three possible values. The default value is UTF-16LE, which is also Windows standard for Excel files. file.e-mail.type=<TSV | CSV> Defines whether individual data in report files are separated by tabs or commas.
60
E-mail template related properties

When the IBM Tivoli Provisioning Manager Express for Software Distribution server generates e-mails, these values are used to provide consistent information to the end user, and any agent on the client that may require to perform automated feedback. See Example 4-6.
Example 4-6 isic.properties: e-mail template
#Used for anything such as CallHome or e-mail which requires a reference url. url=http\://tpmxserv\:80/tpmx #Static parameters used in e-mail templates and Callhome e-mail.from= e-mail.admin=administrator@tpmxserv.company.domain The following are some e-mail template related properties: url=<URL> Defines the main URL for the IBM Tivoli Provisioning Manager Express for Software Distribution server. This is used for any references put into e-mails. It may also be used for references, in case the client software require to return data to the IBM Tivoli Provisioning Manager Express for Software Distribution server based on its URL. e-mail.from=<mail address> Defines the e-mail address that end users can respond to when receiving mails from the system. e-mail.admin=<mail address> Defines the e-mail address that end users can respond to if they experience problems with the IBM Tivoli Provisioning Manager Express for Software Distribution system.
Upload properties
You can use the upload properties to determine how to format the uploaded data and how to process it. Some of the properties are also related to performance, for example how many items can be handled in the queues and what to do if the queue length is exceeded. See Example 4-7.
Example 4-7 isic.properties: upload
#These properties are for configuring the upload actions upload.process.xml=1 #The following line will only allow the processing of the xml at upload time if the queue length doesn't exceed the value.
61
upload.process.xml.max.queue=20 #The following will allow suitable tasks to utilise other background threads if possible for processing. default is if queue is less than 5 long. task.use.other.threads.queue.limit=5 #The following will automatically queue the background processing task if true of unprocessed assets if the queue goes over the max length above upload.autoqueue.process.xml.task=1 #The following three lines are to decide if we process the filescan at upload - similar to the above 3 upload.process.filescan=1 upload.process.filescan.max.queue=20 upload.autoqueue.process.filescan.task=1 #Log the current user, domainid and userkey against the hwKey/revision in the upload_history table upload.store.user.history=1 #The following are for configuring which parts (including the EG2 file) itself are saved to the FILESTORE table. upload.save.eg2file=0 upload.save.xmlfile=1 upload.save.syslog=1 upload.save.applog=1 upload.save.seclog=1 upload.save.filescan=1 upload.save.userxml=1 upload.save.attachments=1 upload.e-mail.forward=0 upload.send.receipt=1 save.file.use.gzip.compression=1 The following are properties of upload: upload.process.xml=<0 | 1> Defines whether the IBM Tivoli Provisioning Manager Express for Software Distribution server processes any incoming XML files. If set to 0 no new XML data is processed. upload.process.xml.max.queue=<integer> Defines how many assets can be in the processing queue. The default is 20. If you upload a new XML, and the queue is already at 20, the XML is either ignored or queued as another background task, depending on the setting of upload.autoqueue.process.xml.task.
62
upload.autoqueue.process.xml.task=<0 | 1> Defines whether the IBM Tivoli Provisioning Manager Express for Software Distribution server must queue incoming XML files to the background task, when the standard upload process has reached its maximum queue length. task.use.other.threads.queue.limit=<integer> This setting defines the number of assets that can be put into queue for being processed on the additional threads. By default this is set to 5, meaning that new assets can be put into the queue if there are less than 5 assets in the queue already. upload.process.filescan=<0 | 1> upload.process.filescan.max.queue=<integer> upload.autoqueue.process.filescan.task=<0 | 1> These three settings have the same meaning as the previous three settings, but only for the filescan data. upload.store.user.history=<0 | 1> Defines whether a history of uploads must be maintained in the database. If set, the user, domain ID, and user key are stored in the upload_history table. upload.save.eg2file=<0 | 1> Defines whether the eg2 file is saved to the FILESTORE table. upload.save.xmlfile=<0 | 1> Defines whether the XML file is stored to the FILESTORE table. upload.save.syslog=<0 | 1> Defines whether the syslog file is stored to the FILESTORE table. upload.save.applog=<0 | 1> Defines whether the application log is stored to the FILESTORE table. upload.save.seclog=<0 | 1> Defines whether the security log is stored to the FILESTORE table. upload.save.filescan=<0 | 1> Defines whether the file scan is stored to the FILESTORE table. upload.save.userxml=<0 | 1> Defines whether the user XML is stored to the FILESTORE table. upload.save.attachments=<0 | 1> Defines whether attachments are stored to the FILESTORE table.
63
upload.e-mail.forward=<0 | 1> Defines whether the upload must be forwarded to another server for processing. If set, uploaded data is forwarded. upload.send.receipt=<0 | 1> Defines whether a return receipt must be sent when an upload is received. save.file.use.gzip.compression=<0 | 1> When set, any files saved into the database are compressed to save space.
Files and directories settings

The properties Example 4-8 shows are related to tasks that require to know which directory or filename to look for, and which file formats are to be used for export files.
Example 4-8 isic.properties: files and directories
#For the getFiles task, we need to tell the task engine where the file directory is located. eg2.file.directory=C\:/Program Files/IBM/Tivoli/TPMX/SERVER/gathered eg2.file.delete=true #For the DBBackup task, we need to tell the task engine where the backup root directory is located. backup.file.directory=c\:/tpmx/backup backups.to.keep=3 #Decide whether to keep the existing table data when restoring database from backups (0 = no, 1 = true) restore.keep.existing.data=1 #For the export data task...we need to know where the csv files will be deposited. export.data.directory=C\:/Program Files/IBM/Tivoli/TPMX/SERVER/exports #Encoding can be UTF-8, UTF-16BE or UTF16LE (Default) file.export.encoding=UTF-16LE #Type can either be TSV (Tab Seperated Value) or CSV (Comma Seperated Value) file.export.type=TSV #For administrator uploading files to the server, configure these parameters file.upload.password=tpmxupload file.upload.directory=C\:/Program Files/IBM/Tivoli/TPMX/SERVER/uploads
64
Following are properties of files and directory settings: eg2.file.directory=<directory> Specifies the directory on the IBM Tivoli Provisioning Manager Express for Software Distribution server where EG2 files are stored when they are uploaded from clients. Note: Use this directory if you have collected a large number of EG2 files from PCs that are not connected to the IBM Tivoli Provisioning Manager Express for Software Distribution server (assume you have performed offline scans by other means). Place the EG2 files in this directory, then run the task Process Files in Configured Folder. This causes all the EG2 files to be processed and entered into the database. The default folder is as follows: C:/Program Files/IBM/Tivoli/TPMX/SERVER/gathered. eg2.file.delete=<true | false> Specifies whether you must delete EG2 files from the configured folder after they have been processed by the Process Files in Configured Folder task. This setting does not apply to general process of uploaded EG2 files. backup.file.directory=<directory> backups.to.keep=<integer> restore.keep.existing.data=<true | false> These three properties have no effect. Backups are taken by simply copying the directory that holds the database. You can do this while the server is running. These properties perform restores by stopping the server and transferring the copied database files to the same directory. This is specified in Database on page 13. export.data.directory=<directory> Specifies the directory where CSV files are stored when generated by a CSV_FILE task. file.export.encoding=<UTF-8 | UTF-16 | UTF-16LE> Specifies the encoding type used for exported files. Similar to e-mail reports, the default is UTF-16LE, which is also a Windows standard for Excel files. file.export.type=<TSV | CSV> Defines whether individual data in report files are separated by tabs or commas.
65
file.upload.password=<password> Specifies the password the administrators use for uploading files to the server. The administrators can use this feature to upload one or more files from systems that have browser access to the Tivoli Provisioning Manager Express for Software Distribution server, but the IBM Tivoli Provisioning Manager Express for Software Distribution agent must not be installed. file.upload.directory=<directory> Specifies the directory used for files uploaded by administrators. Default value is C:/Program Files/IBM/Tivoli/TPMX/SERVER/uploads (assuming default installation values).
Asset match properties

You can use these properties to define how IBM Tivoli Provisioning Manager Express for Software Distribution must recognize an existing asset when XML data is being processed. These settings are very important to adjust, so that assets are not displayed more than once in the database, while, at the same time, assets must not overwrite each others data. The ideal setting is to use only the assettag for identification. However, this requires all assets to have 100% unique assettags. You must be certain that all assets in your enterprise have unique assettags and that all processes support this. See Example 4-9.
Example 4-9 Asset match properties
#Settings for uploading assets. Helps to recognise the assets or not from the assettag. Use only if the assettag is totally unique! match.on.assettag=true match.on.computername.if.valid.serial.or.uuid.stored=true The following are the asset match properties: match.on.assettag=<true | false> Specifies whether uploaded assets are recognized only based on the asset tag. It set, the assettags must be 100% unique. match.on.computername.if.valid.serial.or.uuid.stored=<true | false> Specifies whether uploaded assets are recognized if the database already has an entry for the same computer name, and if the serial number or uuid are the same.
66
Query performance parameters

These properties are used to protect the database system from overload due to queries. You must not change the default values unless you experience performance problems. See Example 4-10.
Example 4-10 Query performance properties
#Max results is a setting to stop huge queries being run and overloading the system. Setting to -1 will disable it. query.max.results=100000 #Search engine settings search.limit.results=0 # If limited, setting this much above 500 could upset the database as it builds a long sql string! max.keys=500 The following are the properties of query performance parameters: query.max.results=<integer> Specifies maximum number of rows in the result of a query before the query is cancelled. This value is mainly to prevent the system from overloads. The value -1 disables this feature. search.limit.results=<0 | 1> Defines whether search results must be limited. max.keys=<integer> If you have enabled the search limit results, then this value specifies how many rows of data are returned.
Authority parameters
All users are defined as either user (U), superuser (S), or administrator (A). The properties Example 4-11 shows from the isic.properties defines the minimum authority level a user must have in order to access the associated functions.
Example 4-11 Authority configuration properties
#Action authority settings update.password.auth=S update.details.auth=S change.asset.owner.auth=S add.user.auth=S all.user.auth=S all.asset.auth=S all.custom.reports.auth=A query.builder.auth=S
67
search.auth=S task.auth=A reprocess.auth=A group.auth=A view.group.auth=U delete.user.auth=A e-mail.report.authority=U edit.printer.auth=A
Probe properties
The probe is the component on the clients that scans the system for information and puts it into the XML file. Example 4-12 shows the properties of probe.
Example 4-12 Probe properties
#Control settings for eGatherer probe eg.fields=-level5 -hidden eg.demographics.fields=-level0 -hidden The following are probe properties: eg.fields=<parameters> You can use this field to specify the command line parameters to use for the inventory agent when it runs a standard scan on the client. The command line parameters are specified in 6.6, Command line option eGather2 on page 255. eg.demographics.fields=<parameters> This field defines the parameters for the probe when it is returning only demographic information.
Database asset revisions

The database can keep one or more revisions of data for any asset. Use these properties to control the number of revisions. Remember to size the database with this in mind. Keeping many revisions takes up more space. See Example 4-13.
Example 4-13 Database asset revision properties
#Database settings for no of revisions to hold for each uploaded asset. asset.revisions=3 asset.keep.baseline=true
68
Following are properties of database asset revisions: asset.revisions=<integer> This field defines how many revisions of an asset must be kept in the database. The default is 3. asset.keep.baseline=<true | false> Defines if the first scan of an asset must be kept as a baseline (default).
Schedules properties
The following fields from the isic.properties are set for the scheduled agent settings. Note that some of these values are set on the server, even though they actually define how the client must operate. See Example 4-14.
Example 4-14 Scheduled agent properties
scheduled.upload=true update.client.files=true scheduled.upload.interval=90 scheduled.upload.queue.threshold=500 scheduled.upload.queue.lookup.threshold=800 scheduled.update.demographics=true scheduled.demographics.check.interval=90 scheduled.launch.on.startup=1 scheduled.interval=60 scheduled.interval.period=minutes scheduled.task.period=hours scheduler.use.queue=true task.process.xml.max.queue.length=20 task.process.files.max.queue.length=20 task.process.filescan.max.queue.length=20 task.process.software.security.length=100 The following are some properties of schedule agents: scheduled.upload=<true | false> Defines whether the agent automatically uploads information to the server. update.client.files=<true | false> Defines if files on the clients must be updated automatically if new versions are available on the server. Default is true.
69
scheduled.upload.interval=<integer> Specifies the interval, in days, between automatic upload of asset information from clients to the server. If the value is -1 it means disabled. The default value is 90 days. scheduled.upload.queue.threshold=<integer> Specifies the maximum queue size on the server for uploads. The default value is 500. If an agent tries to upload information, but the queue size exceeds this value, the data is not uploaded. However, if the scheduled.upload.queue.lookup.threshold is not exceeded, the asset is registered in the database. scheduled.upload.queue.lookup.threshold=<integer> Specifies the maximum queue size for uploaded assets to be registered. the default value is 800. If an agent tries to upload information, but the queue size exceeds this value, the data is not uploaded and the asset is not registered in the application log. scheduled.update.demographics=<true | false> Specifies whether demographics information must be uploaded periodically. This only applies if the LARA agent is installed as part of an IBM SO engagement. scheduled.demographics.check.interval=<integer> Specifies the interval, in days, between demographics information being checked for updates to be uploaded. The default value is 90 days. scheduled.launch.on.startup=<0 | 1> Defines whether the scheduler must start automatically when you start the IBM Tivoli Provisioning Manager Express for Software Distribution server. Typically, the scheduler must start on server startup. scheduled.interval=<integer> Specifies the interval between the checking of the scheduler regarding tasks to run. The measure is defined in the next field. The default is 60 minutes. scheduled.interval.period=<minutes | hours | days> Specifies the unit of time to use for the scheduler intervals. Default is minutes. scheduled.task.period=<minutes | hours | days> Specifies the unit of the time to use when scheduling tasks. The default value is hours. scheduler.use.queue=<true | false> Specifies whether the scheduler must use the queue to process tasks, or run them in its own thread.
70
task.process.xml.max.queue.length=<integer> Specifies the maximum number of processes at a time. More processes are stored for later processing. A process can be a task, an upload, or an e-mail. task.process.files.max.queue.length=<integer> Specifies maximum number of EG2 files to process at a time. If the number is exceeded, new EG2 files are stored in the configure directory and processed as running processes are completed. task.process.filescan.max.queue.length=<integer> Specifies the number of filescan EG2 files to process at a time. If the number is exceeded, new EG2 files are stored in the configure directory and processed as running processes are completed. task.process.software.security.length=<integer> Specifies the maximum of security tasks to run at a time.
Database cleanup properties

Use these properties to keep the database clean by clearing old log files. See Example 4-15.
Example 4-15 Database cleanup properties
#DBCleaner is a looping utility to clean up log files based on age of entries (in days). #Frequency is in days. #To disable cleaning, set the value to -1 dbcleaner.launch.on.startup=1 dbcleaner.frequency=1 dbleaner.interval.period=days server.log.max.age=60 tx.log.max.age=60 task.log.max.age=60 transfers.history.max.age=360 user.access.max.age=720 The following are some database cleanup properties: dbcleaner.launch.on.startup=<1 or -1> Specifies if the database cleaner utility must launch at startup. The default value is 1. dbcleaner.frequency=<integer> Specifies the interval between the cleanups. If set to -1 the cleanup is disabled.
71
dbleaner.interval.period=<mins | hours | days | months> Specifies the unit of time to use for the frequency. The default value is days. server.log.max.age=<integer> Specifies maximum age, in days, to keep entries on the server log (server_log table). The default value is 60 days. tx.log.max.age=<integer> Specifies maximum age, in days, to keep entries on the transaction log (tx_log table). The default value is 60 days. task.log.max.age=<integer> Specifies maximum age, in days, to keep entries on the tasks log (task_log table). The default value is 60 days. transfers.history.max.age=360 Specifies maximum age, in days, to keep entries on the transfer table. The default value is 360 days. user.access.max.age=<integer> Specifies maximum age, in days, to keep entries on the access table. The default value is 720 days.
New user properties

This single property relates to the page shown to new users where they can create their own accounts: logon.newuser=true The logon.newuser=<true | false> is a parameter you can use to specify whether new users must be able to create their own account. If this value is set to false, then the new user check box does not open on the login page.
Password properties
These properties are used to control how passwords must be constructed. See Example 4-16.
Example 4-16 Password properties
password.encrypt=yes password.reuse=no expire.new.password=true password.timeout=true password.timeout.period=186 password.period=1000 password.check=true
72
password.must.have.non.numeric=true password.must.have.numeric=true password.must.have.non.alphanumeric=false password.min.length=6 password.max.length=15 password.max.matching.sequential.chars=2 password.max.previous.chars=3 The following are some password properties: password.encrypt=<yes | no> Specifies whether the passwords are stored in the database in SHA-1 (Secure Hash Algorithm) encrypted format. The default value is yes. We recommend that you do not change this. password.reuse=<yes | no> Specifies whether the end user may reuse a previously stored password again. The default value is no. expire.new.password=<true | false> In case a new password is generated by the system, this value specifies whether the user must change it at next log in. The default value is true. password.timeout=<true | false> Specifies whether passwords expire or not. The default value is true. password.timeout.period=<integer> Specifies the password expiration period in days. The default is 186 days. password.period=<integer> Specifies the number of days old passwords are kept in the database. Old passwords cannot be reused if the password.reuse parameter is set to yes. The default value is 1000 days. password.check=<true or false> This value enables or disables whether passwords comply to the rules, as defined in the following parameters. The default value is true. password.must.have.non.numeric=<true or false> Specifies that new passwords must have at least one non-numeric character. The default value is true. password.must.have.numeric=<true or false> Specifies that the new password must have at least one numeric character. The default value is true.
73
password.must.have.non.alphanumeric=<true or false> Specifies that the new password must have at least one non-alphanumeric character. The default value is false. password.min.length=<integer> Specifies the minimum number of characters in a valid password. Default is 6. password.max.length=<integer> Specifies the maximum number of characters in a valid password. The default value is 15. password.max.matching.sequential.chars=<integer> Specifies the maximum number of identical characters in a sequence that is allowed in a new password. The default value is 2. Note: When setting the property value to 2, it is allowed to have three sequential characters (for example, 3sssfgu). Presumably the counter starts with 0 instead of 1 which causes this calculation. password.max.previous.chars=3 Specifies the maximum number of identical characters in a sequence that you can reuse from the old password. For example, if a previously used password (within the limit of passwords stored in the database) was 1plotter, the new password may not be 1plxyzgh or 2plocixyz as both these passwords contain tree sequential characters that were in an old password.
Asset registration properties

The following fields from the isic.properties are used to define which field requires data when the user defines a new asset from the new asset form. See Example 4-17.
Example 4-17 Asset registration configuration properties
# Form control (User stuff is moved to the common pages. asset.assettag.required=false asset.description.required=false asset.assettype.required=false asset.owner.required=true asset.department.required=false asset.floor.required=false asset.location.required=false asset.status.required=false asset.manufacturer.required=true
74
asset.model.required=true asset.serial.required=true # asset_info form control asset.company.required=false asset.room.required=false asset.address_1.required=false asset.address_2.required=false asset.town.required=false asset.postcode.required=false asset.country.required=false asset.state.required=false asset.desk.required=false For all of these properties, define with true or false whether the data is required to complete an asset registration.
Security policy properties

The following fields from the isic.properties are set to establish the security verification requirements. During a security audit task, these values are used to identify weaknesses in the assessed systems. See Example 4-18.
Example 4-18 Security compliance verification configuration properties
power.on.password.required=no hdd.password.required=no win.file.sharing=0 win.screensaver=0 win.screensaver.timeout=30 win.password=0 win.min.pw.length= win.max.pw.age= win.gina.version=1 win.gina.dll=UVMGINA.DLL app.antivirus.name.1= app.antivirus.ver.1= app.antivirus.name.2=Norton AntiVirus Corporate Edition app.antivirus.ver.2=7.6.1 app.antivirus.name.3=Symantec AntiVirus app.antivirus.ver.3=9% app.firewall.name.1= app.firewall.ver.1= app.firewall.name.2=Integrity Client app.firewall.ver.2=3.5.175.057
75
The following are some security policy properties: power.on.password.required=<yes | no> Specifies whether you require a power-on password to pass security assessment. The default value is no. hdd.password.required=<yes | no> Specifies whether you require a hard disk password to pass security assessment. The default value is no. win.file.sharing=<0 | 1> Specifies whether the security audit task must check that all file shares are password protected. win.screensaver=<0 | 1> Specifies whether the security audit task must check that the screen saver is password protected. win.screensaver.timeout=<integer> Specifies the maximum allowed time in minutes of inactivity before the screen saver activates itself. The default value is 30 minutes. If set to -1 the audit check is disabled. You must set the property win.screensaver to 1 before the screen saver timeout value is checked. win.password=<0 | 1> Specifies whether all active users on client system must have a password in order to pass a security audit. The default value is 0. win.min.pw.length=<0 | integer> Specifies the minimum length that all passwords on a client system must have to pass security audit. If set to 0 or null, no checking is done. win.max.pw.age=<0 | integer> Specifies the maximum password age on client systems to pass security audit. If set to 0 or null, no checking is done. win.gina.version=<0 or 1> Specifies whether the security audit must check client systems for appropriate installed GINA. The default value is 1. win.gina.dll=<dll filename> Specifies the appropriate GINA DLL filename. Default is UVMGINA.DLL.
76
app.antivirus.name.1=<name as identified in add/remove programs> app.antivirus.ver.1=<version> Specifies the name and version of the first, of upto three antivirus products that you require to check for. Note, the version can be specified as 7.% to specify any 7.something versions (% is used as a wildcard). app.antivirus.name.2= app.antivirus.ver.2= app.antivirus.name.3= app.antivirus.ver.3= Similar to the first example. In order to pass the Check Asset Security task, you must identify at least one of the specified AntiVirus products. app.firewall.name.1=<name as identified in add/remove programs> app.firewall.ver.1=<version> Specifies the name and version of the first, of up to two firewall products that you require to check for. Note, the version can be specified as 3.% to specify any 3.something versions. app.firewall.name.2= app.firewall.ver.2= Similar to the first example. In order to pass the Check Asset Security task, you must identify at least one of the specified firewall products.
E-mail engine properties

The e-mail engine properties specify how e-mails are received and sent. See Example 4-19.
Example 4-19 e-mail engine properties
#These properties are for the e-mail receiving and processing engine via POP (Post Office Protocol) e-mail.receive.enabled=yes pop3.server.1=localhost pop3.userid.1=ASSET-DEPOT pop3.inbox.1=Inbox pop3.password.1=ad #You can receive from as many pop3 accounts as you like...just increment the last digit from the parameters.must be sequential from 1. #pop3.server.2=tpmx.greenock.uk.ibm.com
77
#pop3.userid.2=mailin #pop3.inbox.2=Inbox #pop3.password.2=xxxx e-mail.delete.processed.e-mail=0 e-mail.delete.other.e-mail=0 e-mail.file.send.receipt=1 #Spam filtering - these matchers will delete e-mail that has 'spam' attributes in the titles or bodies as indicated e-mail.spam.filter=1 e-mail.spam.title.1=Returned mail e-mail.spam.title.2=out of the office e-mail.spam.title.3=out of the office e-mail.spam.content.1=permanent fatal errors e-mail.spam.content.2=out of the office e-mail.spam.content.4=viagra e-mail.spam.content.5=bank account e-mail.spam.content.6=bank details upload.e-mail.forward.address=mailin@tpmx.greenock.uk.ibm.com upload.delete.after.forward=0 upload.delete.after.receipt=0 The following are e-mail engine properties: e-mail.receive.enabled=<yes | no> Specifies whether the IBM Tivoli Provisioning Manager Express for Software Distribution server receives mails from the pop3 accounts. pop3.server.1=localhost Specifies the IP address or host name of the first pop3 server that you can accept mails from. Use localhost for a pop3 server located on the IBM Tivoli Provisioning Manager Express for Software Distribution server. pop3.userid.1=<userid> Specifies the user ID to use for authentication. pop3.inbox.1=<mailbox name> Specifies the name of the inbox. pop3.password.1=<password> Specifies the password that you can use for authentication.
78
Note: You can define several pop3 servers by adding the previous four parameters with the last number incremented. The pop3 parameters must start with the numeric 1 and then be incremented. For example, it is not allowed to have only one pop3 server defined and use the parameters pop3.server.2, the sequence numbers must start with 1. e-mail.delete.processed.e-mail=< 0 | 1> Specifies whether e-mails must be deleted after they have been processed. The default value is 0. e-mail.delete.other.e-mail=0 Specifies whether the system must delete e-mails that cannot be recognized, for example, those e-mails that have format or content that cannot be processed automatically. The default value is 0. e-mail.file.send.receipt=1 Specifies whether the system must send return receipts. The default is 1. e-mail.spam.filter=1 The system contains a simple spam filter. This property specifies whether the system must enable the spam filter. The default is 1. Any e-mails with title or content that matches one of the following fields is automatically deleted. e-mail.spam.title.1=Returned mail e-mail.spam.title.2=out of the office e-mail.spam.title.3=out of office e-mail.spam.content.1=permanent fatal errors e-mail.spam.content.2=out of the office e-mail.spam.content.4=viagra e-mail.spam.content.5=bank account e-mail.spam.content.6=bank details
upload.e-mail.forward.address=mailin@tpmx.greenock.uk.ibm.com Specifies an e-mail address to forward uploaded data to, if set. upload.delete.after.forward=0 Specifies whether uploaded e-mails must be deleted after they have been forwarded. upload.delete.after.receipt=0 Specifies whether uploaded e-mails must be deleted after they have been forwarded and a receipt has been received.
79
System maintenance properties

These properties are used for special maintenance scenarios. See Example 4-20.
Example 4-20 System maintenance properties
callhome.file.directory=apps/client serialised.queue.object=c\:/queuedata.dat master.server.address=localhost/AssetDepot update.server.files=1 update.client.files=1 swl.sigenabled=2 The following are system maintenance properties: callhome.file.directory=<relative directory> Specifies a relative directory to be used by the servlet that distributes files to clients via callhome. The default is apps/client and typically, you must not change it. serialised.queue.object=<path filename> Specifies a directory and filename where you can write the queue data to. This can be useful if you require to shut down a busy server and drain all its queues. The default is c:\queudata.dat. master.server.address=<address> Specifies the location from which the server is required to get the master files. For example localhost/AssetDepot. update.server.files=<1 | 0> Specifies whether to update server files from the master server. Default is 1. update.client.files=1 Specifies whether to update client files from the master server. Default is 1. swl.sigenabled=<1 | 2 | 3> Specifies the software licensing policy. 1 means signature bank, 2 means Tivoli signature file, and 3 means both.
80
4.1.3 The sdc.properties file

This section describes the sdc.properties configuration file. You require to restart the server for any changes in this file to take effect. You can use sdc.properties file for the following five major functions: 1. 2. 3. 4. 5. Controls the purchase order management Controls the directory download file transfer Controls the package definition default values Controls the general environment and database settings Enables LDAP and defines location of LDAP configuration file
General environment and database settings

This section primarily contains system settings that you must not modify. See Example 4-21.
Example 4-21 sdc.properties: General environment and DB settings
Keep all attributes in lower case unless already in mixed case. # Note that most settings that are either true or false; 1,true,yes as TRUE, 0,false,no as FALSE. # The default context path for jndi (Tomcat). For Websphere leave this blank as it automatically adds it. #jndi.context=java:comp/env # Database properties. The context is what is referenced in the web.xml / server.xml file for the app server # The default value is jdbc/tpmxdb #datasource.context=jdbc/tpmxdb # Properties file used for messages in the isic pages. application.resources=com.ibm.webd.server.properties.app-resources schema=SDC # Define menu system query query.menu.static.items=107 all.groups.query=17 all.users.query=12 selected.user.query=2 #Next property is the number of processors in the system...this is used to create the number of worker threads. queue.processors=2 queue.max.length=1000 # Password control parameters. The default value is true # Encrypt password in SHA-1 password.encrypt=true
81
Purchase order management

This section configures the automated import of purchase order data. See Example 4-22.
Example 4-22 sdc.properties: Purchase order management
# Automatic Purchase Order update parameters. # purchase.autoupdate.offsets unit is hour. purchase.autoupdate=false. purchase.autoupdate.path=C:/Program Files/IBM/Tivoli/TPMX/ Server/Purchase.txt purchase.autoupdate.offset=4 purchase.autoupdate.seperator=tab The following are properties of purchase order management: purchase.autoupdate=<false | true> When purchase.autoupdate=true, the file specified in purchase.autoupdate.path is read at regular intervals as specified in the offset parameter. purchase.autoupdate.path=<path> The information contained in the file specified is automatically loaded into the Purchase Order tables in the Tivoli Provisioning Manager for Software Distribution database. The format of the file is: Purchase Order Number<tab>Part Number<tab>EmployeeID<tab>Description Here each line represents a new database entry. The field separator is tab as defined by the value assigned to purchase.autoupdate.seperator. purchase.autoupdate.offset=<integer> The interval in hours at which the purchase file is read. Default is 4 hours. purchase.autoupdate.seperator=tab Specifies the separator between data in the purchase file. Default is tab and you must not change it.
82
Directory Download
The threshold value in which Tivoli Provisioning Manager for Software Distribution changes the Directory Download package process from creating a compressed-zip file(_IGS.SDC), to creating a filelist file (_IGS_SDC_FileList) and transferring files individually is shown in Example 4-23.
Example 4-23 sdc.properties: Directory Download
# Multi-file Transfer parameters. # dirFTP.threshold, default value is 10485760 (10 binary MB). # the sum of the space consumed by a directory is greater than the threshold. # then the files will be transferred one at a time. If less than the threshold. # then the files will be zipped and transferred. dirFTP.threshold=10485760
Enable LDAP
This section enables LDAP and defines the location of the configuration file. See Example 4-24.
Example 4-24 sdc.properties: LDAP enabling
# Define SDC to use LDAP for user authentication # if this is set false(default value), SDC uses its own authentication. # use config file to define LDAP parameters. authentication.LDAP=false authentication.LDAP.config=ldap.properties The following are properties to enable LDAP: authentication.LDAP=<false | true> The property specifies whether the software distribution catalog utilizes LDAP for authentication, or uses its own authentication mechanism. authentication.LDAP.config=<filename> This property specifies the filename that contains the properties for utilizing LDAP. Do not change the default value of ldap.properties.
83
Machine identification key

This section defines how to determine machine uniqueness. After you establish this, you must not change the value without deleting the existing machine definitions. See Example 4-25.
Example 4-25 sdc.properties: Machine identification
# Define machine identification key # The value can be one of : HOSTNAME, UUID # When set to HOSTNAME, machine uniqueness is determined by the Hostname/Computer Name field. # When set to UUID, machine uniqueness is determined by the UUID field. # When UUID is determined on the client, unknown or invalid UUID's will # default to the value of the primary network adapter MAC address. # The default value is : UUID machine.key=UUID
Default path values for package definitions

This section defines the context root and the common path to package resources. The values supplied prepopulate the package definition fields when creating a new package. See Example 4-26.
Example 4-26 sdc.properties: Package path prepopulate values
#define DocRoot for TPMX server, the default is tpmx docRoot.name=tpmx # all the below pathes will be prefix with '/{$docRoot}' # # Define ROOT Path for download package # the path should look like /tpmx/packages package.root.path=/packages # Define ROOT path for detail file detail.root.path=/packages #Define ROOT path for icon file icon.root.path=/packages #Define ROOT path for target directory targetDirectory.root.path=C:\\ #Define ROOT path for Prerequired Program preReqProgram.root.path=/packages
84
#Define ROOT path for Preinstall program preInstall.root.path=/packages #Define ROOT path for Postinstall program postInstall.root.path=/packages
Evaluation query update frequency

This section defines the amount of time before the evaluation is re-run to include new machines. The evaluation only updates the database table when the offset time has expired and a client machine is requesting the associated distribution list. When there is no client activity the database does not update. See Example 4-27.
Example 4-27 sdc.properties: Evaluation query update
#Define Dynamic Evaluation Query last run offset, minute based # default value is 30 minutes envaluation.lastRun.offset=30
SplashMessage
This is not part of the properties configuration files. The splash message is a feature to display the html content of the file /sdc/help/SplashMessage.html in a pop-up message box for 10 seconds at client catalog login. The feature works simply by the file being present. If a file exists, then it is displayed.
4.1.4 The ldap.properties file

This section describes the ldap.properties configuration file. These properties only take effect if LDAP authentication is enabled in the common.properties files as described in 4.1.1, The common.properties file on page 54. You can use the ldap.properties file for the following four major functions: 1. It controls the basic LDAP configuration settings 2. It provides user-to-group association and determines user memberships of specific groups. It also creates these groups in IBM Tivoli Provisioning Manager Express for Software Distribution, and therefore, it controls access to the software distribution catalog.
85
3. It provides user authentication when end users log in to IBM Tivoli Provisioning Manager Express for Software Distribution. 4. It imports groups from LDAP to IBM Tivoli Provisioning Manager Express for Software Distribution. The configuration file contains significantly more parameters than are presented in the administration console. In general, you must not change these values.
Basic LDAP configuration

This section describes the parameters that pertain to the connection between the Tivoli Provisioning Manager Express for Software Distribution server and the LDAP system. See Example 4-28.
Example 4-28 ldap.properties: Basic LDAP configuration
ldap.connectionName=userid@ActDirTest.SDC.COM ldap.connectionPassword=password #ldap.connectionPassword=7|ws0igrTdpwA= #The directory URL used to establish an LDAP connection. #ldap.connectionURL=ldap://ldap.server.com ldap.connectionURL=ldap://isdc-actdirtest.ActDirTest.SDC.COM # define the secondary LDAP server name, if the primary is down we can use alternate # LDAP server for authentication. #ldap.alternateURL= # Set debug level ldap.debug=2 The following are basic LDAP configuration properties: ldap.connectionName=<userid> Specifies the user ID for you to use for establishing a read-only connection to the LDAP server. If no user ID is specified, the connection attempts to make an anonymous connection. User ID must be in the format user@domain.com. ldap.connectionPassword=<password> Specifies the password for you to use for authentication when establishing a connection to the LDAP. The password may either be in readable format or encrypted.
86
To generate an encrypted password, a utility is available from the server installation directory. Follow this guide to create an encrypted password: a. Start a command prompt and navigate to the following: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\lib b. Enter the following command: java -cp .\sdcserver.jar com.ibm.webd.server.common.Encrypt password c. The output is the encrypted password. See Example 4-29.
Example 4-29 Encrypting ldap connection password
C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\lib> java -cp .\sdcserver.jar com.ibm.webd.server.common.Encrypt mypassword Encrypted Password : 10|CYXnQ2vYn0/0IgA= Decrypted Password : mypassword ldap.connectionPasswordEncrypted=<true | false > Specifies whether the connection password is encrypted. ldap.connectionURL=<ldap URL> ldap.alternateURL=<ldap URL> Specifies the primary and, optionally, a secondary LDAP server to use for authentication. You must specify the LDAP server as a URL, for example, see the following: ldap://ldapserver.itso.ibm.com ldap.debug=<1 .. 5> Specifies a debug level for the LDAP authentication component. The default value is 2. The log file is located in the following: c:\program files\ibm\tivoli\tpmx\server\logs
87
Group data from LDAP

The Software Distribution component can search the directory tree for group memberships. You can use the group memberships to create groups in Tivoli Provisioning Manager Express for Software Distribution. Use the parameters in this section to determine which group memberships the Software Distribution component looks at and which it ignores. These parameters are LDAP attributes that the Software Distribution component must read when searching for group names. If groupName or groupSearch is not defined, Software Distribution does not query LDAP for group information. Example 4-30 searches for groups in the ou and distinguishedNames attributes. Note that you can have multiple entries for each parameter.
Example 4-30 ldap.properties: Group data
ldap.groupName=ou ldap.groupName=distinguishedName ldap.groupDescription=description ldap.groupNameTrim=false ldap.groupBase=ou=austin,dc=ActDirTest,dc=SD,dc=COM ldap.groupSearch=(ou=U*) ldap.groupSubtree=false The following are properties of group data from LDAP: ldap.groupName=distinguishedName Specifies the name of the LDAP field that contains group names. It is possible to have more than one entry, in case group names are found in more than one field in the LDAP. ldap.groupDescription=description Specifies the name of the LDAP field that contains group descriptions. ldap.groupNameTrim=<true | false> Specifies whether the group name must be trimmed. Default is false. ldap.groupBase=<base> Specifies the base LDAP directory entry for looking up group information. If left unspecified, the default is to use the top-level element in the directory context.
88
ldap.groupSearch This is the LDAP filter expression used for performing group searches. With this parameter, you can filter results from the ldap.groupName parameter. For example, if all your user groups are ou with a name that begins with the letter U, you can enter the following value and filter out any other ou groups returned from the ldap.groupName parameter: ldap.groupSearch=(ou=U*) ldap.groupSearch=(objectClass=group) ldap.groupSubtree=<true | false> If set to true, Software Distribution searches recursively through the subtree of the element specified in the ldap.groupBase parameter for groups associated with a user. If left unspecified, the default value of false causes only the top level to be searched (a non-recursive search).
User authentication via LDAP

The following parameters define how the end user must authenticate when attempting to log in to Software Distribution when LDAP is enabled. See Example 4-31.
Example 4-31 ldap.properties: User authentication
ldap.digest=SHA ldap.userPassword=password ldap.userEmail=userPrincipalName ldap.userGroupName=memberOf #ldap.userRealm= ldap.principalPattern={0}@ActDirTest.SDC.COM #ldap.userRoleName=cn #ldap.userRoleBase=dc=ActDirTest,dc=SDC,dc=COM #ldap.userRoleSearch=(member={0}) #ldap.userRoleSubtree=true #Either use pattern for LDAP authentication #ldap.userPattern=dn=cn={0},ou=austin, dc=ActDirTest,dc=SD,dc=COM #or use search for LDAP authentication ldap.userBase=dc=users, dc=internal, dc=domain, dc=com ldap.userSearch=(userPrincipalName={0}@users.internal.domain.com) ldap.userSubtree=true
89
The following are properties of user authentication via LDAP: ldap.digest=<SHA | MD2 | MD5> LDAP uses the digest hashing algorithm, SHA,MD2 (message digest algorithm-2), or MD5 only. The default value is SHA. If the LDAP servers return a password, Software Distribution uses the digest algorithm to hash the user input password and compares it with the password it receives from the LDAP server. If no password is returned from the LDAP server, Software Distribution uses the user name and password that the end user provides, to authenticate with LDAP (bind). ldap.userPassword=<password attribute> Specifies the LDAP attribute that contains the password. ldap.userEmail=<mail address> Specifies the LDAP attribute that contains the e-mail address of the user. ldap.userGroupName=memberOf Specifies the attribute in the user's directory entry containing values for the names of roles associated with this user. You may use this in conjunction with the roleName attribute. If left unspecified, all roles for a user derive from the role search. Default value is memberOf. ldap.userRealm=<realm> If user authentication takes place using bind, this optional value defines the realm. An example value could be as follows: ldap.userRealm=users.company.domain.com ldap.principalPattern=<pattern> This is a pattern for constructing the user principal for using LDAP authentication. Some LDAP servers require e-mail addresses, such as userid@domain.com, and others require the user ID only. The end users user ID, which the user enters in the login window, substitutes the string {0}. For example: ldap.principalPattern={0}@internal.company.com #ldap.userRoleName=cn #ldap.userRoleBase=dc=ActDirTest,dc=SDC,dc=COM #ldap.userRoleSearch=(member={0}) #ldap.userRoleSubtree=true These four values are used to further define search parameters for getting all groups the user belongs to in addition to the userGroupName.
90
For userRoleSearch, you can use two variables: {0} is the DN for the user {1} is the username. If left unspecified, a role search does not take place and roles are taken only from the attribute in the users entry specified by the userRoleName property. ldap.userPattern=<pattern> This is one of the two methods to find users in the directory. This method is more suitable when user information resides in only one or two locations in the directory tree as it avoids having to traverse the entire directory. Each pattern represents one of the user's directory entries. In order to search for the user name in multiple places, you can specify multiple locations. Each pattern must then be surrounded with parentheses. For example: ldap.userPattern=(cn={0},ou=users1,o=myorg)(cn={0},ou=users2,o=myorg ) This example results in Software Distribution looking in ou=users1,o=myorg, and then ou=users2,o=myorg for the user name passed in from the authentication process. The standard LDAP "OR" search format may also be used, for example: ldap.userPattern=(|(cn={0},o=myorg)({0})) Note that, as in this example, you can do both context-less and fully-typed log ins using this technique. The variable {0} is used to indicate where the user name is inserted. ldap.userBase=<directory base> ldap.userSearch=<pattern> ldap.userSubtree=<true | false> These three parameters comprise of the second method to find users in the directory. With this method, a base directory branch is specified and all user searches start here. The search can either be recursed or be limited to the base. This is the preferred method when user information is in multiple locations, for example based on organizational relationship. ldap.userBase specifies the initial branch where you can start the search. If this is not specified, the search defaults to the top level of the directory. ldap.userSearch specifies the filter expression to use for searching. For example: ldap.userSearch=(userPrincipalName={0}@users.internal.domain.com) ldap.userSubtree specifies whether the search must keep to the base or traverse through underlying branches of the directory.
91
4.1.5 The log4j.properties file

This section describes the log4j.properties configuration file. The properties are used to specify the details of logging for individual parts of the environment. You can use log4j.properties file for the following two major functions: 1. Setting the debug level for java programs. 2. Controlling the logging parameters. You must restart the server must for these changes to take effect. Example 4-32 shows the essential part of the log4j.properties file.
Example 4-32 log4j.properties
#Create a new logger called rootLogger, set to WARN amd write to both the console and file appenders log4j.rootLogger=WARN, A1,Rolling #Print only messages of level INFO or above in the package com.ibm. log4j.logger.com.ibm=INFO #A1 is set to be ConsoleAppender sending its output to System.out log4j.appender.A1=org.apache.log4j.ConsoleAppender log4j.appender.A1.layout=org.apache.log4j.PatternLayout log4j.appender.A1.encoding=UTF-8 #Print the date in ISO 8601 format log4j.appender.A1.layout.ConversionPattern=%d{dd-MMM-yyyy,HH\:mm\:ss} [%t] - %m%n #Rolling writes to "c:/program files/IBM/Tivoli/TPMX/SERVER/tpmx.log" log4j.appender.Rolling=org.apache.log4j.RollingFileAppender log4j.appender.Rolling.File=C\:/Program Files/IBM/Tivoli/TPMX/SERVER/tpmx.log log4j.appender.Rolling.encoding=UTF-8 log4j.appender.Rolling.MaxFileSize=2MB log4j.appender.Rolling.MaxBackupIndex=7 log4j.appender.Rolling.layout=org.apache.log4j.PatternLayout log4j.appender.Rolling.layout.ConversionPattern=%d{dd-MMM-yyyy,HH\:mm\: ss} [%t] - %m%n Example 4-32 shows a logger being defined with output to two named objects. One for the console (named A1) and one for a rolling log file (named Rolling). Next, the level of logging is defined for the package com.ibm.
92
The next two sections define the details for each of the logs. The definitions for the file log include the filename, file size, and maximum number of backup versions. You can specify the file size as KB or MB, for example 500 KB or 2 MB. When the file size is reached, a new log file is created. The older log files are renamed with a dot-sequence appended to the filename. The higher the number, the older log file. As the log file number reaches the maximum, as specified in the property MaxBackupIndex, the oldest log file is simply discarded. The logging levels are ALL,DEBUG,INFO,WARN,ERROR,FATAL,OFF. A more detailed explanation of logging services is available from the Apache project on the Web at: http://logging.apache.org/log4j/docs
4.2 Configuring the agents

This section describes how to configure the behavior of the agents. Client configuration is set in two configuration files, which are created at installation time based on server settings and client-specific data. The client global configuration settings are established in the sdc.conf file on the target system. The client local configuration settings are established in the SDClocal.conf file on the target system. Both files are located in the agent installation directory, which defaults to: C:/Program Files/IBM/Tivoli/TPMX/Agent
4.2.1 sdc.conf
Example 4-33 is a sample sdc.conf file.
Example 4-33 Example sdc.conf
com.ibm.sdc.server.host=tpmxserv.company.com com.ibm.sdc.server.port=80 com.ibm.sdc.server.protocol=http com.ibm.sdc.agent.offset=60 com.ibm.sdc.logDir=C\:\\Program Files\\IBM\\Tivoli\\TPMX\\Agent\\logs com.ibm.sdc.client.docRoot=/tpmx # Uncomment to enable debug mode
93
# # # # # # # # #
com.ibm.sdc.agent.debug=true Uncomment to remove Create New User and Change Password buttons com.ibm.sdc.client.userMgmtEnabled=false Uncomment to disable the bundles tab com.ibm.sdc.client.bundlesEnabled=false Uncomment to remove the Exit button (for applet mode) com.ibm.sdc.client.hideExit=true Uncomment to remove the Menu Bar (for applet mode) com.ibm.sdc.client.hideMenu=true
The following are properties for sdc.conf: com.ibm.sdc.server.host=<hostname, FQDN or IP> Specifies the Tivoli Provisioning Manager Express for Software Distribution server, either by a host name, a fully-qualified domain name, or by the IP address. com.ibm.sdc.server.port=<port> Specifies the portnumber the Tivoli Provisioning Manager Express for Software Distribution server listens on. Default is 80 and you must not change it under normal circumstances. com.ibm.sdc.server.protocol=<protocol> Default protocol is http and you must not modify it. com.ibm.sdc.agent.offset=<integer> This value specifies the frequency in minutes, at which the agent contacts the server to check for scheduled distributions. Default value is 60 minutes. Valid values are in the range of 1 through 999 minutes. com.ibm.sdc.client.logfile=<path and filename> This parameter specifies the location of the log file on the client. Default is: C\:\\Program Files\\IBM\\Tivoli\\TPMX\\Agent\\logs If you change the default value, you must also change it on the server, in the sdcclient.jsp file, in order for the Welcome page Access Catalog button to correspond. com.ibm.sdc.agent.debug=<true | false> Specifies whether debugging is enabled on the client. Default is false if the parameter is not specified.
94
com.ibm.sdc.client.userMgmtEnabled=<true | false> Specifies whether to enable or disable the create user and change password buttons in client login panel. By default this value is set to true. If LDAP is enabled, you must disable these buttons in the login page. com.ibm.sdc.client.bundlesEnabled=<true | false> Feature to remove bundles tab from client catalog. The default value is false.
4.2.2 Auto-update of client files

The Tivoli Provisioning Manager Express for Software Distribution system has a built-in feature to automatically update key client files if newer files exist on the Tivoli Provisioning Manager Express for Software Distribution server. By default this feature is enabled through the isic.properties property of update.client.files which is described in 4.1.2, The isic.properties file on page 58. When making a general change to sdc.conf, always verify functionality from a test system. Most importantly, verify that connectivity to the Tivoli Provisioning Manager Express for Software Distribution server is working, as this would otherwise cause a significant effort to re-establish. When the sdc.conf file has been tested on a client, place it in the following directory on the Tivoli Provisioning Manager Express for Software Distribution server: C:/Program Files/IBM/Tivoli/TPMX/SERVER/TPMXAPP.ear/tpmx.war/apps The configuration file propagates to clients as they complete their next scheduled checking.
4.2.3 SDClocal.conf
Example 4-34 is a sample SDClocal.conf file.
Example 4-34 Sample SDClocal.conf
com.ibm.sdc.agent.clientHost=workstationhostname # Uncomment and specify an alternate http server to download files # com.ibm.sdc.client.downloadURL= # Uncomment and specify user login id # com.ibm.sdc.client.login= # Uncomment and specify user login password # com.ibm.sdc.client.password=
95
The following are properties for SDClocal.conf: com.ibm.sdc.agent.clientHost=<hostname> The client local configuration file typically contains this previous line that identifies the client system. com.ibm.sdc.client.downloadURL=<server:port> Specifies an alternate http server to download files. When using this parameter, the agent downloads software files from this server. The Software Catalog is still read from the IBM Tivoli Provisioning Manager Express for Software Distribution server.
User ID and password

Two parameters are available to automate the login to the IBM Tivoli Provisioning Manager Express for Software Distribution server software catalog: com.ibm.sdc.client.login=<user id> com.ibm.sdc.client.password=<password> These parameters may also be used as arguments when starting the local software catalog.
Set user credentials

Two parameters are available to ensure access to file shares. You may use these for software packages that reside on file shares instead of on the IBM Tivoli Provisioning Manager Express for Software Distribution server: com.ibm.sdc.client.login.__ShareServer_ShareName=<user id> com.ibm.sdc.client.password.__ShareServer_ShareName=<password> Here, the __ (double underscore) is required before the fileshare server name and the _ (single underscore) is required before the name of the fileshare. When set on the command line or in SDClocal.conf file, these values are used to establish connection to the fileshare resources that the Universal Naming Convention (UNC) defines.
96
Chapter 5.
Administration
This chapter provides information about how to administer IBM Tivoli Provisioning Manager Express for Software Distribution server and to administer components of Software Distribution agents. This chapter covers the following: Accessing the Administrative console Managing user IDs Managing user groups Managing packages Managing software bundles Managing purchase orders Managing distribution lists Managing machines Managing evaluations Managing tasks Managing schedules Managing logs and standard reports Managing custom reports (queries) Managing catalogs Working with assets and user information
97
5.1 Accessing the Administrative console

You can manage the Tivoli Provisioning Manager Express for Software Distribution process using a Web browser to access the administration console. Only users who are designated with the authority of administrator can access the Software Distribution functions of the administrators console. Only an existing administrator can designate the administrator authority to a new or existing user name. Refer to 5.2.2, Adding a new user on page 101 for details. To access the log on page, perform the following steps: 1. Type http://server_name/tpmx (where server_name is the name of the Tivoli Provisioning Manager Express for Software Distribution server). The Welcome page shown in Figure 5-1 opens. 2. Click Manage Assets.
Figure 5-1 Welcome page
98
3. Enter your user name and password as Figure 5-2 shows. Click Logon. A prompt opens asking you to change the admin password when you log in for the first time. Note: The default administrator user name is admin and the default password is password.
Figure 5-2 Administrator and client login page
Both users and the administrator can log in to Software Distribution. Access to functions and menu items are determined by the users authority level. Only administrators can access Software Distribution functions. Users with other authorities provide access to the appropriate inventory functions.
Logging out of the Tivoli Provisioning Manager Express administration console

To log out, click Sign Out from the Tivoli Provisioning Manager Express for Software Distribution menu bar. The administration login window shown in Figure 5-2 opens again.
Chapter 5. Administration
99
5.2 Managing user IDs

Each user is required to obtain a user name and password in order to access the Software Distribution Catalog or to view Inventory data from the console. The User Management window shows a list of user names, user information, and group assignments. The following section describes the administrative tasks available for managing users.
5.2.1 Authority roles

There are three user authority roles available for Tivoli Provisioning Manager Express for Software Distribution and Inventory: User User works with asset information belonging only to the user. User can add assets, view asset history, compare and edit asset information, and process an asset transfer request. SuperUser SuperUser can perform all of the tasks of a User, in addition to more advanced functions such as developing specialized asset reports and viewing asset information across an enterprise. Administrator An Administrator can perform all the tasks of a User and Super-User and has the ability to modify asset information across an enterprise, e-mail asset information, schedule asset scans, and approve asset requests. You can configure and modify all these authority roles during the IBM Tivoli Provisioning Manager Express for Software Distribution Server installation. For more information see 3.1.2, Server installation: custom setup on page 25. Important: Software Distribution component of IBM Tivoli Provisioning Manager Express for Software Distribution only uses User and Administrator authority roles. The Software Distribution menu functions are only available to Administrator authority users. IDs designated as User or SuperUser only have access to Inventory functions from the console, but they are authorized to log in to the Software Distribution Catalog.
100
5.2.2 Adding a new user

To add a new user, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Users New to display the Add User form shown in Figure 5-3.
Figure 5-3 Add User
3. In the Add User form: Enter the User ID, e-mail address, and all the other mandatory fields marked with an asterisk (*). Enter the password and confirm it. The default mandatory fields are as follows: User ID E-mail address First Name Last Name Password Please retype password
101
Note: The default required fields can be modified if you update the common.properties configuration file. Select the check box to select the Do you wish to register an asset? option if Inventory is being used and you require to record an asset for the new user. Select the role for the user from the drop-down menu next to Authority. For more information about the authority roles, refer to 5.2.1, Authority roles on page 100. Select the group or groups of which the user wants to be member. 4. Click Submit. The user name is displayed in an All Users list shown in Figure 5-4. Note: When an Administrator logged into the console creates a new user, user authority and group membership can be established. When the User creates a new user from the Login panel, the authority cannot be modified and the user is only a member of the default group.
Figure 5-4 All Users list
5.2.3 Deleting a user

To delete a user, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Users All Users. The All Users list shown in Figure 5-4 opens again.
102
3. Select the check boxes next to the user names you want to delete, the action box is on the left panel as Figure 5-5 shows. Click Delete user from the Actions box or select Users Users Delete user.
Figure 5-5 Delete users
4. The users to be deleted are listed and you are prompted for a reason and asked for verification before proceeding as Figure 5-6 shows. 5. Enter the reason and select Yes from the drop-down menu. Click Submit to delete the user name. 6. The All Users list shown in Figure 5-4 on page 102 opens. You can also click Cancel for no action or Reset to clear all selections.
Figure 5-6 User delete confirmation
103
5.2.4 Searching for a user

To search for a specific user name, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. From the title bar, select Users and enter the user name in the Find field. See Figure 5-7.
Figure 5-7 User search title bar
3. Press Enter or click the right arrow to start the search. 4. Alternatively, from the title bar, click the Advanced link for additional search criteria. A new panel opens. See Figure 5-8.
Figure 5-8 User advanced search page
5. Select user from the Search type drop-down menu. 6. Select true or false from the case sensitive drop-down menu. 7. Enter you search criteria and click the Submit button.
104
Note: You do not require to use the wild card, such as percentage (%), when you are typing information in the field boxes. For example, if you are searching for a user whose name is in the Inventory, you can perform the search by typing ventor or %ventor% in the First Name field. 8. The new panel with the search results opens.
5.2.5 Modifying a users group membership

To modify a users group membership, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Users All Users. The List Users table shown in Figure 5-4 on page 102 opens. 3. Select the check box next to the user names you want to update as shown in Figure 5-5 on page 103. 4. Click Edit User from the Actions area or select Users Users Edit User. 5. Update the group in the groups table as necessary. See Figure 5-9. For further details about updating the user information, refer to 5.2.6, Updating user information on page 106. Click Submit. The List User table shown in Figure 5-4 on page 102 opens.
Figure 5-9 Edit user information
105
5.2.6 Updating user information

To update user information, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Users All Users. The List Users table shown in Figure 5-4 on page 102 opens. 3. Select the check box next to the user names you want to update as Figure 5-5 on page 103 shows. 4. Click Edit User from the Actions area or select Users Users Edit User. 5. Make the changes to the user information as Figure 5-9 shows. Click Submit. The List User table shown in Figure 5-4 on page 102 opens. The following fields and descriptions update the user information: User ID: User name (mandatory) E-mail address: Users e-mail address (mandatory) Title: (optional) First Name: Users forename (mandatory) Last Name: Users surname (mandatory) Preferred name: (optional) Employee ID: Corporate-assigned identification number (optional) Department: (optional) Password: Users initial password if creating ID, or updated password (mandatory) Number/Street: (optional) Building: (optional) Country: (optional) Zip code: (optional) Office Phone: (optional) Mobile Phone: (optional) Company: (optional) Location: (optional) Floor: (optional)
106
Please retype password: Confirmation of previously entered password (mandatory) Authority: Users authority level Note: You can customize all the fields labeled as optional at server installation time and, in the common.properties configuration file, at installation completed by the Tivoli Provisioning Manager administrator.
5.3 Managing user groups

Groups are used to categorize users and provide access to a set of packaged applications. A group definition consists of the group name and description, the designated users who are members of the group, and the designated software packages and bundles that are made available to the selected users. The Software Distribution Catalog uses the users group membership to determine the appropriate packages and bundles to be displayed for installation. The Group Management window shows a list of group names and their associated descriptions (List Groups table). For the Software Catalog group versus the Inventory group, the same groups are used for both the Software Distribution Catalog and Inventory. The only difference is that for Software Distribution purposes, groups also include membership for packages and bundles, along with users. Inventory groups only display user membership information. The Software Catalog groups menu selection enables the Administrator to modify the package, bundle, and user membership in one location.
5.3.1 Adding a new group

To add a new group, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. The My Assets page shown in Figure 5-10 opens. 2. On the My Assets page, select Users Software Catalog Groups New Group to display the Add Group form.
107
See Figure 5-10.
Figure 5-10 My Assets page with New Group
3. On the Add Group page, enter the name in the Name field and the description in the Description field for the group as Figure 5-11 shows. Click Add.
Figure 5-11 Add Group
4. The Add Group page opens with a message that says Group_name has been added successfully, as shown in Figure 5-12.
Figure 5-12 Add Group: success message
108
Note: You cannot create multiple groups with the same name. The Name field has a limitation of 32 characters, uniquely defined to distinguish group definitions. In addition, the field does not accept apostrophes or quotation marks. The Description field is an alphanumeric field that has a limitation of 128 characters and describes a group definition.
5.3.2 Deleting a group

To delete a group, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Software Catalog Groups All Groups. 3. From the List Groups table, select the check box next to the group name you want to delete as Figure 5-13 shows. Click Delete.
Figure 5-13 List Groups
4. In the conformation dialog box, click OK to delete the group, or click Annulla to return without making any changes to the database as Figure 5-14 shows.
Figure 5-14 Delete group confirmation
109
5.3.3 Searching for a group

To search for a group, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Software Catalog Groups All Groups. 3. Select the Search tab. The Search window opens as Figure 5-15 shows.
Figure 5-15 List Groups
4. Enter the name of the group in the Name field. The group name is case sensitive. Type the name exactly as the name is listed in the group list you are searching. If you are not sure of the spelling, you can use the percent symbol (%) as a wild card in place of one or more characters as Figure 5-16 shows.
Figure 5-16 Group search page
110
5.3.4 Updating a group

To change every groups information: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Software Catalog Groups All Groups. The List Groups table opens. 3. In the List Groups table, click the group name. 4. In the Update Group area, enter the necessary change to the description in the Description field as Figure 5-17 shows. Click Next at any time to continue to the next tab. Optionally, you can click Apply to make permanent changes to the database before selecting Next. Click Update to submit all the changes to the database, close the record, and return to the List Groups table.
Figure 5-17 Group Management: description update
5. Click the Packages tab to select or clear the packages to be included in the group. 6. Click the Bundles tab to select or clear the bundles to be included in the group. 7. Click the Users tab to select or clear the users to be included in the group. You can also update the user information if you select the user name. For further details about updating the user information, refer to 5.2.6, Updating user information on page 106. 8. Click Update. The List Groups table shown in Figure 5-13 on page 109 opens.
111
5.3.5 Updating user information in a specific group

To update the user information for a specific group, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Software Catalog Groups All Groups. 3. From the List Groups table, select the group name as shown in Figure 5-13 on page 109. 4. From the Update Group area, select the Users tab as shown in Figure 5-17 on page 111. 5. Click the user name from the User List for a specific group as Figure 5-18 shows.
Figure 5-18 Group Management: User List
112
6. Make the changes to the user information in the Update User area shown in Figure 5-19. Refer to 5.2.6, Updating user information on page 106 for details. Click Update. The List Groups table shown in Figure 5-13 on page 109 opens.
Figure 5-19 User Management: update user
5.3.6 Adding or deleting (modifying) a user to a group

You can use several ways to add or delete (modify) a user to a specific group. From the Group Management page, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Software Catalog Groups All Groups. 3. From the List Groups table, select the group name as shown in Figure 5-13 on page 109. 4. From the Update Group area, select the Users tab as shown in Figure 5-17 on page 111.
113
5. Click the check box next to the user that you want to add or remove from the specific group as shown in Figure 5-20.
Figure 5-20 Group Management: User List
6. Click the Update button to return to the Group Management panel or click the Apply button to apply the changes made and remain under the Users tab. From the Users Management page, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Users All Users. The List Users table shown in Figure 5-4 on page 102 opens. 3. Select the check box next to the user names you want to update as shown in Figure 5-5 on page 103. 4. Click Edit User from the Actions area or select Users Users Edit User.
114
5. Update the group in the groups table as necessary. See Figure 5-21. For further details about updating the user information, refer to 5.2.6, Updating user information on page 106. Click Submit. The List User table shown in Figure 5-4 on page 102 opens.
Figure 5-21 Edit user information
5.3.7 Adding or deleting (modifying) a software package or bundle for a specific group
To add or delete a software package or bundle for a specific group: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Users Software Catalog Groups All Groups. 3. From the List Groups table, select the group name as shown in Figure 5-13 on page 109.
115
4. From the Update Group area, click the Packages or Bundles tab, depending on which one you want to add or delete. The Package Access List in Figure 5-22 or the Bundle Access List for a specific group name opens.
Figure 5-22 Group Management: Package Access List
5. Select or clear the check box for the software package or bundle that you want to add to or delete from the group. Note: When adding packages or bundles from multiple pages, you must click Apply to save your changes before selecting the << arrow or >> arrow to navigate between the multiple pages. 6. Click Update. The List Groups table shown in Figure 5-13 on page 109 opens.
116
5.4 Managing packages

This section provides an overview of the tasks required to create a software package and check it into your Tivoli Provisioning Manager Express for Software Distribution library. The Software Distribution library is the main repository for software packages and bundles. Software packages and bundles referenced in the library are not made available to users until the Administrator creates catalogs for the pull software delivery method or schedules a push software delivery.
5.4.1 Prerequisites for managing packages

This section shows the necessary prerequisites you must observe when you are administering IBM Tivoli Provisioning Manager Express for Software Distribution.
Creating a folder structure for the software library

Any package, folder, and file intended for distribution that is stored on the Software Distribution server must be stored under the document root. The default document root is as follows: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war Your document root might be different depending on the options you selected during installation. In most cases, it is beneficial to use the \PACKAGES folder under the document root to help you organize the files associated with your packages. Under the \PACKAGES folder, you can organize your packages according to operating system, type of application, or any other characteristic that meets the requirements of your organization. It is a good idea to plan for your long-term organizational requirements before designing your folder structure. Appendix A, Sample folder structure on page 275 provides several samples to help you create your folder structure.
Creating software packages

Creating a software package involves the following tasks: 1. Creating the source files. Refer to Creating the source files on page 118 for details. 2. Determining where you want to store the source files for distribution. Refer to Determining where to store the source files on page 123 for details.
117
3. Adding software packages to the Software Distribution library through the administrators console. Refer to Adding the software package to Software Distribution library on page 124 for details.
Creating the source files

The first step to create a software package is creating the source files. Each package is associated with the following source files: The source software package file (mandatory) The icon file (optional) The details file (optional)
The source software package file (mandatory)

This file typically is created using a third-party packaging tool. Tivoli Provisioning Manager Express for Software Distribution supports any software package created by the following packaging tools: InstallShield Wise InstallManager WinZip Self-Extractor Microsoft Software Installer (MSI) For best results, develop the source package so that it installs silently, without user intervention. For further information about using these tools, refer to the documentation that the packaging tools provide. Optionally, the source software package can be in an unpacked format consisting of a folder structure containing of all the files required for installation or of data files for distribution. This method often uses .cmd or .bat script files to automate the installation requirements. Call all command references used in the batch files with absolute paths, such as Target Directory Field or Installation Directory Field. You must not assume the working directory. You can also include the following line in the batch file to establish the working directory from the called batch: cd %~p0
Microsoft Software Installer (MSI) support The download package type supports the installation of a single .msi executable.
The .msi exec gets called with the following command syntax: msiexec ALLUSERS=2 /i XXXX.msi <Parameters> Any additional flags specified in the Parameters field are appended to the base command.
118
Note: ALLUSERS=2 allows the installation to be completed to all users, instead of only the system. You can use a logical drive package type to support the installation of a .msi executables with Transform or Patch files. You must create a .cmd or .bat file. All command parameters in the .cmd or .bat file must reference the drive path variable. For example, the following lines would be in the .bat file, and DPDIR is set to the defined drive path and the DPDIR variable is used to provide the path to the executables: set DPDIR=%~dp0 msiexec ALLUSERS=2 /i %DPDIR%Entire Connection 3.1.1^1.0.msi TRANSFORMS=%DPDIR%Entire Connection 3.1.1^1.0.mst The Installation file field must call the .cmd or .bat file, using a Universal Naming Convention (UNC) or a mapped drive path. For example, as follows: \\FILESHARE\entire_connect\install.bat. Note: ALLUSERS=2 allows the installation to be completed to all users, instead of only the system. You must use the directory download package type to support the download of Transform or Patch files. You must create a .cmd or a .bat file. You must include all command parameters in the .cmd or .bat file and it must contain fully qualified paths. For example, the following line would be in the .cmd or .bat file: msiexec ALLUSERS=2 /i c:\entire_connect\Entire Connection 3.1.1^1.0.msi TRANSFORMS=c:\entire_connect\Entire Connection 3.1.1^1.0.mst The Installation Command field must call the .cmd or .bat file, relative to the target directory. For example, as follows: c:\targetdir\install.bat. Note: ALLUSERS=2 allows the installation to be completed for all users, instead of only the system.
119
The icon file (optional)

When a user selects a package from a catalog, the Tivoli Provisioning Manager Express for Software Distribution program displays basic information about the program, such as the file size and the amount of disk space required. If an icon file is provided, the icon is displayed next to the basic information. The icon image can be either a .gif or a .jpg file. Icons are displayed as 32 pixels by 32 pixels.
The details file (optional)

When a user selects a package from the catalog and wants more information than the basic information that is typically displayed, the user can click a Details button in the catalog to view the information in the details file. The details file must be in .txt format and can contain any information deemed useful by the Administrator. For example, if a readme.txt file is provided by the software vendor, the Administrator might choose to use the readme.txt file as the details file.
Providing security for LogicalDrive(Secure) packages on a file share server

In order for LogicalDrive(Secure) packages to work, the following registry key changes are required on the file share server where the logical drive share is located: Allow anonymous access (ANONYMOUS LOGON) and read permission to everyone. Enable NullSessionShare. Note: The file share server is the server where your software packages reside. Perform the following steps: 1. Select Start Run. 2. Type regedt32 and click OK. 3. In the Registry Editor window, navigate to the following: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver \parameters Perform the following steps: a. b. c. d. e. Click HKEY_LOCAL_MACHINE. Double-click SYSTEM. Double-click CurrentControlSet. Double-click Services. Scroll down and double-click lanmanserver.
120
f. g. h. i.
Double-click parameters. Move your cursor to the right side of the window. Double-click NullSessionShares: REG_MULTI_SZ:COMFG DFS$. In the edit multi-string window: i. Click the empty row under DFS$. ii. Type the name of the share where the LogicalDrive(Secure) packages reside. For example, win32. Note: The following example shows the absolute path for the share resource directory when the Software Delivery Center server and the file share server exist on the same machine, with win32 used as the entry for the registry key: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\ tpmx.war\sdc\packages\win32
j. Click OK to save the changes. 4. In the Registry Editor window, navigate to the following: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa Perform the following steps: a. b. c. d. e. f. Click HKEY_LOCAL_MACHINE. Double-click SYSTEM. Double-click CurrentControlSet. Double-click Control. Scroll down and double-click Lsa. Ensure that the following value is defined: restrictanonymous: REG_DWORD : 0 For Windows Server 2003, if this entry is missing, perform the following steps to add the restrictanonymous entry: i. ii. iii. iv. v. From the menu bar, click Edit. Click New. Click DWORD Value. In the Value Name field, type restrictanonymous (Value Data=0). Press Enter.
For Windows 2000, if this entry is missing, perform the following steps to add the restrictanonymous entry: i. From the menu bar, click Edit. ii. Click Add Value. iii. In the value name field, type restrictanonymous and select REG_DWORD for the Data Type.
121
iv. Click OK. v. In the Data field, type 0 and click OK. vi. Press Enter. g. Ensure that the following value is defined: everyoneincludesanonymous: REG_DWORD : 1 For Windows Server 2003, edit everyoneincludesanonymous as follows: REG_DWORD : 1 For Windows 2000, add the everyoneincludesanonymous value to the registry key as follows: i. From the menu bar, click Edit. ii. Click Add Value. iii. In the Value Name field, type everyoneincludesanonymous and select REG_DWORD for the Data Type. iv. Click OK. v. In the Data field, type 1 and click OK. vi. Press Enter. vii. Close the Registry Editor window. 5. Set the file share permissions for the resource directory. For Windows 2003 server, on the Share tab, perform the following steps: Set Share Permissions to include Read Permissions for Everyone. Add Groups or User name ANONYMOUS LOGON. Set Share Permissions to only include Read Permissions for ANONYMOUS LOGON. On the Security tab: Add Groups or User name ANONYMOUS LOGON. Set Share Permissions to include Read & Execute, List Folder Contents, and Read for ANONYMOUS LOGON. For Windows 2000, set Share permissions to only include Read permissions for Everyone. 6. Close all the windows. 7. Reboot the server.
122
Determining where to store the source files

After you create your source files, you have to determine where you want to store them for distribution. You can store the source files in either of the following places: On the Tivoli Provisioning Manager Express for Software Distribution server under the document root. The default document root is: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war Your document root may be different, depending on the options you selected during installation. Packages stored on the Software Distribution server are always downloaded to the client before being installed. When you add these packages to the library through the Administration console, you have to assign one of the following package types: Download(Open) A package created by a third-party packaging tool that is not identified by a digital signature. Download(Secure) A package created by a third-party packaging tool that is identified by a digital signature. DirectoryDownload An unpackaged set of files and folders. When this type of package is added to the library, the Software Distribution program automatically creates a compressed file containing these files and folders. It is important to note that unpackaged files and folders intended for distribution must reside on the Tivoli Provisioning Manager Express for Software Distribution server. On a shared network drive outside of the Tivoli Provisioning Manager Express for Software Distribution server. Throughout the remainder of this document, the term logical drive is used to describe this storage location. Packages stored on a logical drive are not downloaded to the client. They are installed directly from the designated file share through UNC or an existing mapped drive.
123
When you add these packages to the library through the Administration console, you have to assign one of the following package types: LogicalDrive(Open) A package created by a third-party packaging tool that is not identified by a digital signature. LogicalDrive(Secure) A package created by a third-party packaging tool that is identified by a digital signature. For further information about adding packages to the library, refer to 5.4.2, Adding a new software package to the library on page 124.
Adding the software package to Software Distribution library

After creating the source package, you must add it to the Software Distribution library through the Administration console. This process adds information in a database, including a pointer to the source files and text that is displayed in a catalog. You can use the Upload tab in the package definition to transfer the source files from the local system to their respective locations on the server. If the source files are deleted or moved from their original location after the entries have been added to the database, the Administrator must modify the software package information in the library to update the database. For details about adding a package to the library, refer to 5.4.2, Adding a new software package to the library on page 124.
5.4.2 Adding a new software package to the library

If a software package file is stored on the Software Distribution server, it must be placed in a folder under the document root, for example as follows: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXApp.ear\tpmx.war\packages Here, the following is the document root: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXApp.ear\tpmx.war If you have not already set up a folder structure for your library, refer to 5.4.1, Prerequisites for managing packages on page 117. For further information about the source files such as the package file, details file, and icon file referenced in this procedure, refer to 5.4.1, Prerequisites for managing packages on page 117.
124
Adding software package

To add a software package, perform the following steps: 1. Log in to the Administrative console. For more information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Open the administrators console and select Software Packages New Package. 3. On the General tab on the Package Management page, shown in Figure 5-23, perform the following steps: a. Enter the Name and Version in their respective fields. b. Enter the document root path to the details file in the Details field. c. Enter the document root path to the icon .gif file in the Icon Path field. d. Enter the maximum installation time in minutes for the software package to install to the client machine. e. Select Silent for the software package, so that it installs unattended (optional). f. Select Package Reboot, so that the software package initiates the reboot of the machine (optional). g. Select Client Reboot, so that the Tivoli Provisioning Manager Agent initiates the reboot of the machine (optional). h. Select Mandatory, so that the software package is essential and installs immediately upon startup of the Software Distribution Catalog (optional). i. Select Enable Deferral option so that the end user can choose to defer the mandatory package installation (optional). j. Select the Deferral Number to indicate the number of times the end user can choose to defer the mandatory package installation (optional). k. Select the Deferral Duration to indicate the interval until the next mandatory package installation attempt (optional). For more details about package definitions, refer to 5.5.5, Software bundle definition information on page 154. l. Click Next.
125
See Figure 5-23.
Figure 5-23 Add Package
4. On the Install tab shown in Figure 5-24, perform the following steps: a. Select the Package Type of the software package as Download, or Logical Drive, or Directory Download. b. Select Secure if the package requires Administrator rights to install. Note: The digital signature required for this option is automatically created when the software package is added to the catalog. c. Based on the package type selected, the next fields are defined as follows: Download - Installation File: Type the document root path to the installation file. - Installation Parameters: Type the installation parameters to be passed to the executable (optional).
126
Logical Drive - Installation File: Type the drive designation and path relative to the shared drive to be mapped to the client. - Installation Parameters: Type the installation parameters to be passed to the executable (optional).
Directory Download - Installation Directory: Type the document root path to the installation directory. - Installation Command: Type the installation command to be run after the delivery of the source directory (optional). - To remove the source directory from the client machine after executing the install command, select Remove Directory After Install (optional). Note: The executable file or source directory must be present when the package is created or updated. Download and Directory Download packages fail without the source file or directory on the server. Logical Drive secure packages display a warning message if Tivoli Provisioning Manger Express cannot access the designated mapped drive to create the digital certificate signature file.
d. Select Include MST / ISS File to activate the text field. Type the document root path to the MST file or ISS response file. e. Click Show Command to display a pop-up window containing the installation command syntax that executes on the client machine. f. Select Enable Process Tracking to track subprocesses of a software package (optional). g. Type in the Windows RegKey (registry key) or Stamp File in their respective fields. h. Select the Stamp Mode. i. Type the Stamp File Date, if using the Dated option from the Stamp Mode field. j. If using Purchase Orders to enable software package installation, select the Require Purchase Order option to enable the require purchase orders and then type the part number (optional). For more details about package definitions, refer to 5.5.5, Software bundle definition information on page 154. k. Click Next.
127
See Figure 5-24.
Figure 5-24 Install tab
5. On the Target tab, shown in Figure 5-25, perform the following steps: a. Type the temporary space required in MB. b. Type the target space required in MB. c. Type the target directory. d. Type the document root path to the prerequired program. e. Type the document root path to the preinstall program. f. Type the document root path to the post-install program. Note: If the post-install fails and returns a non-zero code, it causes the subsequent packages of a bundle to fail. For further information about this topic, refer to the Post-install Program entry in 5.4.6, Software package definition information on page 136.
128
g. Select Enable Network Speed Detection to require a minimum network speed for the package installation (optional). h. Select the Network Speed Allowed to specify the minimum network speed requirement for the package installation (optional). For further details about package definitions, refer to 5.5.5, Software bundle definition information on page 154. i. Click Next.
Figure 5-25 Target tab
6. On the Platform tab as Figure 5-26 shows, choose the target platforms (). Click Next.
Figure 5-26 Platform tab
129
7. On the Upload tab shown in Figure 5-27, perform the following steps: a. Click Browse or type the local path to the download package installation file or ZIP file of the directory download source tree, for it to be uploaded to the server and placed in the installation file location. b. Click Browse or type the local path to the package details file that is to be uploaded to the server and placed in the details file location. c. Click Browse or type the local path to the package icon .gif file that is to be uploaded to the server and placed in the details file location. d. Click Browse or type the local path to the package MST/ISS file that is to be uploaded to the server and placed in the MST/ISS file location. e. Select Add.
Figure 5-27 Upload tab
130
8. The Add Package area opens with a message that says Package_name has been added successfully. See Figure 5-28.
Figure 5-28 Successful package addition message
5.4.3 Deleting a software package from the library

To delete a software package, perform the following steps: 1. Log in to the Administrative console. For more information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Packages All Packages. 3. Select the check box next to the software package name you want to delete, as shown in Figure 5-29. 4. Click Delete.
131
See Figure 5-29.
Figure 5-29 List Packages
5. A dialog box displays the following message, as Figure 5-30 shows: You have selected to delete packages Select the delete method: - Package Definition Only - Package Definition and Contents The delete method selection enables you to preserve package resources, or to delete them while deleting the package definition. 6. Click Continue to delete a software package. The List Packages table shown in Figure 5-29 opens. Click Cancel for no action. Note: A software package can be deleted even if there are groups currently authorized to access the software package. However, it cannot be deleted if it is allocated to a scheduled distribution.
132
See Figure 5-30.
Figure 5-30 Package delete confirmation
5.4.4 Searching the library for a software package

To search for a specific software package name: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Packages All Packages. The List Packages table shown in Figure 5-29 on page 132. 3. Click the Search tab as shown in Figure 5-31. 4. You can search by name, type, or operating system. Perform any single or a combination of the following actions: In the Name field, type the software package name. The software package name is case-sensitive. Type the name exactly as the name is listed in the package list you are searching. If you are not sure of the spelling, use the percent symbol (%) as a wild card in place of one or more characters.
133
See Figure 5-31.
Figure 5-31 Search packages by name
5. In the supported OS field, select the operating system. See Figure 5-32.
Figure 5-32 Search packages by OS
Perform the following steps: a. For the Selectable option, select whether the packages to be searched are selectable or not. b. In the Page Size field, type the maximum number of entries per page for it to display. Click Search. c. The selected software package name opens in the List Packages table as Figure 5-29 shows.
134
5.4.5 Updating software package information in the library

To update a software package: 1. Log in to the Administrative console. For more information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Packages All Packages. 3. From the List Packages table, click the software package name as shown in Figure 5-29 on page 132. 4. In the Update Package area, make the changes to the software package definition information shown in Figure 5-33. See 5.5.5, Software bundle definition information on page 154 for further information. 5. Click Update. The List Packages table opens as shown in Figure 5-29 on page 132.
Figure 5-33 Update Package information
135
5.4.6 Software package definition information

Use the following fields and descriptions to create and edit software packages.
General tab
The General tab consists of the following fields: Name: Unique name of the software package. Version: Version number of the application. Family: Critical patch management information. Details: The path to the details file that opens when the user clicks the Details button in the Tivoli Provisioning Manager Express for Software Distribution catalog. Place all warnings and relevant information about the software package in this file. Note: The path name to the details file must be relative to the document root of the server. The default document root is /TPMx/packages. Your document root might be different depending on the options you chose during installation. Icon Path: The path to the software package icon that is displayed in the Software Distribution Catalog. The icon must be a .gif or .jpg file. The use of an icon is optional. Note: The path name to the file must be relative to the document root of the server. The default document root is /TPMx/packages. Your document root might be different depending on the options you chose during installation. Max Install Time (Min.): The maximum amount of time, in minutes, that the software package takes to install. The software package installation terminates if the installation does not complete within the specified time. Note: Specify a large enough value to account for network congestion, slow processors, or both. Specify zero for an unlimited installation time.
136
Silent: Indication by the packager or Administrator that the software package installs unattended. Select this option if the installation package is configured to install silently with no user intervention. If the software package is of the silent type, the Software Distribution Agent program is able to install the software package, even if the user is not logged in to the client. If the software package is of the non-silent type, which means that it requires user interaction, and the user is not logged in to the client, then any scheduled push of a non-silent installation package is delivered, but installation is delayed until the user logs in to the client. Package Reboot: The software package initiates a restart of the operating system at the end of the installation. Client Reboot: The Software Distribution Agent initiates a restart of the operating system at the end of the installation. Mandatory: The software package installs automatically upon startup of the Software Distribution Catalog. Enable Deferral option: The deferral option gives the end user the ability to defer the mandatory package installation (optional). Deferral Number: The Deferral Number is the number of times the end user can defer the mandatory package installation (optional). Deferral Duration: The Deferral Duration is the interval until the next mandatory package installation attempt (optional).
Install tab
The Install tab consists of the following fields: Type There are three types, as follows: Download This type of package consists of a single executable file that resides on the Software Distribution server. A package of this type is downloaded to the client machine before the installation begins and requires no Administrator rights to run or install the software. Note: When a software pull of this package type is initiated, the Software Distribution Agent is not involved with the installation of the software. The packages install even if the client agent is disabled.
137
Logical Drive This type of package consists of installing the executables that reside on a logical drive, which is a shared network drive outside the Software Distribution server. A package of this type is installed from a logical drive without downloading the software package and it requires no Administrator rights to run or install the software. Note: The Tivoli Provisioning Manager Express for Software Distribution process does not do the actual mapping of the drive. You must map the client to the logical drive that contains the software package before the installation process is initiated. When a pull process is used for a Logical Drive package type, the Software Distribution Agent is not involved in the installation process. The software packages install even if the client agent is disabled. Directory Download This type of package consists of an unpackaged application or a set of data files. The directory source must reside on the Software Distribution server under the document root. When the package is created or updated, depending on the total size of the source directory content, the Tivoli Provisioning Manager Express for Software Distribution program creates a file list (greater than 10 MB) or a compressed ZIP file (less than 10 MB). During a push or pull operation, the compressed ZIP file is downloaded to the client machine where the client application decompresses the package and restores the files to their original condition, or the files are transferred individually as per the file list. If an installation command is defined, an installation process takes place after the directory content is delivered. If you select Remove Directory After Install, all files and directories delivered in the package are removed from the client. Note: If you make changes to the content of the Directory Download package, you must open and update the package definition to automatically update either the compressed ZIP file (_IGS.SDC) or the file list file (_IGS_SDC_FileList) located in the source directory as specified in the Installation Directory field.
138
Secure When selected, the software package has Administrative rights for installation. The Software Distribution Agent performs the installation for either a push or pull distribution. Software Distribution automatically creates a digital signature upon creation of the Secure Download and Secure Logical Drive software packages. Note: Secure Logical Drive packages automatically create a digital signature file if the mapped drive is present on the server, as per the package definition at the time the package is created or updated. To create the digital signature manually, see 5.4.7, Creating a digital certificate file for a secure package on page 146. Installation File This is used to define the path to the package executable. The executable file must be present when the package is created or updated. Note: The Installation File field supports both back slashes and forward slashes. For Logical Drive package types, the Installation File field supports environment variables to allow multiple file shares. Supported extensions for the installation files are: .cmd .exe .msi .rpm .tar .vbs Null (no extension)
When used in conjunction with a package type Download, this path must be relative to the document root of the Tivoli Provisioning Manager Express for Software Distribution server and contain the executable the client downloads and installs from. For example, if the full path is as follows: c:\IBMTPMx\TPMxServer\TPMx\packages\XP\My_Package\SETUP.EXE, the relative path is /TPMx/packages/XP/My_Package/SETUP.EXE Note: Path names are case-sensitive. Make sure the path name you use matches exactly to the path name on your Tivoli Provisioning Manager Express for Software Distribution server.
139
When used in conjunction with a package type of Logical Drive, this path is the drive designation and share path to the mapped executable from which the client installs. For example, if you assume that the shared directory in the following path is packages: c:\IBMTPMx\TPMxServer\TPMx\packages\XP\My_Package\SETUP.EXE Then, in reference to this previous case, the mapped drive path is going to be: y:\XP\My_Package\SETUP.EXE. Note: The drive designation must match on server and client. Installation Parameters These are additional flags and parameters that are passed to the software package executable. Examples of parameters include: /s for a silent installation of InstallShield and Wise InstallSystem /qn for a silent installation of Microsoft Software Installer packages (.msi file extension) The parameters depend on the tool that you use to create the package. Refer to the documentation provided with the packaging tool for more information. Installation Directory Used with a package type of Directory Download. This is the relative path to the root folder of the application or data files stored on the Tivoli Provisioning Manager Express for Software Distribution server. Relative paths are relative to the document root. For example, if the full path to the root folder of a set of data files located on the Software Delivery Center server is: c:\IBMTPMx\TPMxServer\TPMx\packages\FILES\TEMPLATES Then, in reference to this previous case, the relative path is: /TPMx/packages/FILES/TEMPLATES. It is also important to understand that the last folder in the relative path is the starting point of the directory structure that is extracted to the client. For example, if you specify the TEMPLATES folder as follows: \TPMx\packages\FILES\TEMPLATES In this case, all files in the TEMPLATES folder and all subfolders under the TEMPLATES folder are extracted to the client target directory. Installation Command This command is used to start the installation of the software package from a Directory Download package. The command is based on the client system and is either a full path or relative to the Target Directory specified in the package definition.
140
Remove Directory after install Select this option to allow Software Distribution to clean up the source directory structure of the Directory Download package, on the client machine, after installation. All files and directories delivered in the package are removed from the client. Note: This field is only available for Directory Download. Enable Process Tracking Select this option to allow Tivoli Provisioning Manager Express for Software Distribution to track spawned subprocesses of a software package installation and remain active until all spawned child processes have completed. Show Command Click this button to open a pop-up window containing the installation command syntax that is executed on the client machine. This is useful when constructing complex MSI packages. Windows RegKey The appropriate string that matches the program name displayed in the Add/Remove Programs window. For example, to view the string in Windows 2000, select Start Settings Control Panel Add/Remove Programs. You must use the program name exactly as shown in the Add/Remove Programs window. The Tivoli Provisioning Manager Express for Software Distribution program uses this field to determine if a particular software package is already installed on the client. The Tivoli Provisioning Manager Express for Software Distribution program queries the Windows registry to determine what programs have been installed and listed in the Add/Remove Programs window. In some cases, when you look in the Add/Remove Programs window, it might not be obvious if there is an extra space at the end of the string or between words. The following method ensures that the value you place in the Windows RegKey field matches the value in the Add/Remove Programs window: a. Install the application on a test computer or go to a computer where the application is already installed. b. From the Windows desktop, select Start Run. The Run window opens. c. In the Open field, type regedit, and click OK. The Registry Editor window opens.
141
d. In the Registry Editor window, navigate to the following folder: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion /Uninstall e. In the left panel, click the appropriate application name. f. In the right panel, double-click DisplayName. The Edit String window opens. g. The string highlighted in the Value data field is the exact string you require to use in the Windows RegKey field. Copy and paste the string into a TXT file. h. Return to the Edit String window and click Cancel. Then, close the Registry Editor window. i. Open the Tivoli Provisioning Manager Express for Software Distribution administration console. Copy the complete string from the TXT file and paste it into the Windows RegKey field. Note: The administrator can specify either the Stamp File field or the Windows RegKey field. Use the Windows RegKey field unless the software package does not register itself in the Add/Remove Programs window. Stamp File The Stamp File indicates that the software package installed successfully on the client. The Tivoli Provisioning Manager Express for Software Distribution process checks for the existence of the stamp file after the completion of the software package installation. The stamp file is used as a means of getting a return code from the software package. The software package itself must create the stamp file after the software package has successfully installed. The software package must not create the stamp file if the application does not successfully install. The software package is responsible for writing the stamp file because there is no agreed upon standard among software vendors that indicates a particular installation was successful. Often, the installation program returns with a return code of zero for a successful installation, but this is not always the case. Therefore, each individual package must determine if the software installed successfully, and if so, it creates the software package stamp file. For this field, specify the full path for the stamp file that it has to check. Note: The administrator can specify either the Stamp File field or Windows RegKey field. Use the Windows RegKey field unless the software package does not register in the Add/Remove Programs window.
142
Stamp Mode or Stamp File Mode The Stamp File Mode must be set to one of the following types: Auto The Software Distribution client or agent automatically creates the stamp file after the installation program completes. Auto stamp file mode is provided for development and testing of software packages. Package The software package itself creates the stamp file after the software package has successfully installed. Dated Dated time stamp mode is used to instruct the Tivoli Provisioning Manager Express for Software Distribution process to check the time stamp of the stamp file in addition to the existence of the file. Stamp File Date This is the time stamp, which is date and time of the target stamp file When you select a Stamp Mode of Dated, the software package passes the stamp file check only if the last modified date of the stamp file matches the date specified. The date is specified in Java-epoch milliseconds, the number of milliseconds since the Java epoch, defined as midnight, January 1, 1970 GMT. These are the number of milliseconds that have elapsed since January 1, 1970 00:00. To generate the stamp file time stamp, run the following command from a Windows command prompt, where filename is the stamp file name: java -jar printstamp.jar filename Note: The printstamp.jar file is provided as part of the Software Distribution server software in the following folder: c:\ibmTPMx\TPMxserver\TPMx\apps\printstamp.jar Here, the default document root is: c:\ibmTPMx\TPMxserver\TPMx Your document root might be different depending on the options you choose during installation.
143
Require Purchase Order Select this option to associate a Part Number to a software package. This requires the end user to enter a valid Purchase Order/Employee Number combination for the package to begin installation. Part Number A unique number used to define the product.
Target tab
The Target tab consists of the following fields: Temp. Space Required (MB) This is the amount of temporary disk space, in megabytes, required to install the software package. This is typically the temporary space required to unpack a software package prior to installation. The drive that is checked is the same drive that the Java runtime environment on the client uses for temporary space and is typically specified by the environment variable tmp or temp. Note: If the drive letter that the Java runtime environment uses for temporary space is the same drive letter specified in the Target Directory field, then the values in the Temp. Space Required (MB) field and Target Space Required (MB) field are added together before the free space check is performed. Otherwise, two separate free space checks are performed. Target Space Required (MB) This is the amount of disk space, in megabytes, required to install the software package. The drive letter or logical volume on which to perform the free space check is specified by the entry in the Target Directory field. Target Directory The definition of this field depends on the type of package you are defining. When used with a package type of Directory Download, this is the path to the folder under which the source directory (as defined in the package) and its contents are delivered. For example: c:\Documents and Settings\All Users When used with package types of Download or Logical Drive, this is the drive letter on which the software package are installed. For example, c:\. This folder is checked for the required amount of free disk space prior to the installation of the software package.
144
Prerequired Program This is the path name of the prerequisite program that is run prior to installing the software package. If this program returns with a return code of zero, the Software Distribution program assumes that all of the prerequisites for this software package have been met. A non-zero return code indicates to the Software Distribution program that the prerequisites have not been met and the software package does not install. Preinstall Program A program or script that runs before the installation of the software package. Post-install Program This is a program or script that runs after the installation of the software package. If the software package is run from a software bundle or a multipackage installation, a non-zero return code causes subsequent software packages in the sequence not to run. Note: Postinstall Program is a text field, which has a limitation of 128 alphanumeric characters, uniquely defined to identify the program responsible for verifying post-requisite conditions on the target machine. Enable Network Speed Detection (optional) This requires a minimum network speed in order for the package installation to continue. If the minimum speed is not detected, the end user is notified and prompted to abort or continue the installation. Network Speed Allowed (optional) This establishes the minimum network speed required for the package installation to continue.
Platform tab
This Platform tab consists of a field called Target Platforms. Target platforms are the operating system platforms on which this software package can be installed. The Tivoli Provisioning Manager Express for Software Distribution program checks for the presence of the specified operating systems to determine if it must display the software package in the catalog. One or more operating systems can be specified by selecting the appropriate check box.
145
Upload tab
The Upload tab consists of the following fields: Package File Defines the path to the package Installation File, or ZIP file of the directory download source tree, on the local machine. The file is uploaded and delivered to the location on the server as specified in the Installation File field. Detail File Defines the path to the package Detail file on the local machine. The file is uploaded and delivered to the location on the server as specified in the Details field. Icon File Defines the path to the package Icon file on the local machine. The file is uploaded and delivered to the location on the server as specified in the Icon Path field. MST/ISS File Defines the path to the package MST/ISS response file on the local machine. The file is uploaded and delivered to the location on the server as specified in the MST/ISS File field.
5.4.7 Creating a digital certificate file for a secure package

Digital certificate signature files are generated automatically when a secure package is created or updated.
Download packages fail to create or update if the defined installation file is not
available on the server.
Logical Drive packages are created or updated, but display a warning message
indicating that the system could not locate the defined installation file if the designated mapped drive is not available. Note: When creating or updating Logical Drive (secure) packages, map the shared drive to the server as designated in the package definition.
146
You can manually create a digital certificate for software packages of type Logical Drive (secure) by performing the following steps: 1. Open a command prompt window. 2. Change to the \signatures folder located under the document root of the server. 3. Run the following command: java -jar ..\..\apps\sdcsigner.jar executable Here, executable is the relative path name to the software package executable. For example: java -jar ..\..\apps\sdcsigner.jar ..\..\packages\win32\winzip90\WinZip90M.exe
5.5 Managing software bundles

A software bundle is a group of software packages, with a defined installation sequence, which is to be delivered in one session. After creating the individual software packages, use the Software Distribution administration console to create a software bundle. Software bundles are optional. For details about creating a software bundle, refer to 5.5.1, Adding a new software bundle to the library on page 147.
5.5.1 Adding a new software bundle to the library

To add a new software bundle to the library, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Bundles New Bundle. 3. In the Add Bundle table shown in Figure 5-34, perform the following functions: Enter the name, description, and stamp file values. Important: The path to the stamp file must exist on the target machine. Select the Selectable option to define the bundle as optional and allow the end-user to remove individual packages or fail an installation without affecting the remaining packages in the bundle. Select the supported operating system for the bundle.
147
4. Click Add. For further details about bundle definitions, refer to 5.5.5, Software bundle definition information on page 154.
Figure 5-34 Add Bundle
5. On the Update Bundle panel, click Next as shown in Figure 5-35.
Figure 5-35 Update Bundle
148
6. On the Packages tab, select the packages that you want to add to the bundle definition as shown in Figure 5-36. Note: Select Apply to make changes permanent to the database for each page of packages/bundles. Select Update. Note: Only packages that match the supported operating system (OS) selection are displayed.
Figure 5-36 Packages list for bundle
149
7. From the Adjust Package Order area, adjust the package installation sequence in the bundle definition as shown in Figure 5-37. Click OK. Note: The screen shown in Figure 5-37 opens only if you click the Update button, it does not open if you click the Apply button.
Figure 5-37 Adjust Package Order
8. The Add Bundle area opens with a message that says Bundle_name has been added successfully, as shown in Figure 5-38.
Figure 5-38 Successful bundle addition message
150
5.5.2 Deleting a software bundle from the library

To delete a software package or bundle, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Bundles All Bundles. 3. Select the check box next to the bundle name you want to delete as Figure 5-39 shows. Click Delete.
Figure 5-39 List Bundles
4. You can search by name, or type. 5. A dialog box displays the following message, as shown in Figure 5-40: Do you really want to remove the selected entries?
Figure 5-40 Delete confirmation
6. Click OK to delete bundle name. The List Bundles table shown in Figure 5-29 opens. Click Cancel for no action to be carried out.
151
5.5.3 Searching the library for a bundle

To search for a specific software bundle name, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Bundles All Bundles. The List Bundles table shown in Figure 5-41 opens.
Figure 5-41 List Bundles
3. Click the Search tab shown in Figure 5-42. 4. You can search by name, type, or operating system. Perform any one or any combination of the following actions: In the Name field, type the software bundle name. The software bundle name is case-sensitive. Type the name exactly as the name is listed in the bundle list you are searching for. If you are not sure of the spelling, use the percent symbol (%) as a wild card in place of one or more characters. In the Supported OS field, select the operating system. For the Selectable option, select whether the packages to be searched are selectable or not. 5. In the Page Size field, type the maximum number of entries per page to display. 6. Click Search.
152
See Figure 5-42 for further clarification.
Figure 5-42 Bundle Search
7. The selected software bundle name is displayed in the Bundles search result page shown in Figure 5-43.
Figure 5-43 Bundle Search results
153
5.5.4 Updating software bundle information in the library

To update a software bundle, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Bundles All Bundles. The List Bundles table shown in Figure 5-39 on page 151 opens. 3. Click the software bundle name. The Update Bundle window opens. 4. Make the changes to the software bundle definition information. See 5.5.5, Software bundle definition information on page 154. 5. Click Next or Packages to display the list of available packages shown in Figure 5-36 on page 149. 6. Select the check box next to the software package name you want to add to the bundle. Note: When adding packages from multiple pages, you must select Apply to save your changes before selecting the << arrow or >> arrow. After selecting all the packages to add to the bundle, click Update. You are prompted to select the order of installation for the packages in the bundle shown in Figure 5-37 on page 150. 7. Select a software package name, and click Up or Down to move the packages into your desired order. Click OK to update the bundle. The List Bundles table shown in Figure 5-39 on page 151 opens.
5.5.5 Software bundle definition information

Use the following fields and descriptions to create and edit software bundles: Name This is the unique name of the software bundle. Description This is the description of the software bundle. Stamp File The stamp file indicates that the software bundle installed successfully on the target. The Software Distribution Agent checks for the existence of the stamp file to determine if the software bundle has previously been installed.
154
The stamp file is used as a means of indicating that the software bundle installation sequence has completed. The software bundle itself must create the stamp file after all of the software packages in the bundle have successfully installed. For this field, specify the full path of the stamp file that you want to create or verify. Note: The Software Distribution Agent installation includes a default location to create the bundle stamp files as follows: C:\Program Files\IBM\Tivoli\TPMX\Agent\StampFiles Selectable This acts as an indication of whether the end user can select the packages in the software bundle and clear them individually for installation. The end-user can deselect packages in a bundle marked selectable or, the end-user can fail an installation, without affecting the remaining packages in the bundle. By default (Selectable not selected), all packages in a bundle are required to be installed successfully in order for the bundle installation to be considered successful. Consider the following two cases: From the client catalog Selectable bundles enable end users to deselect individual packages from the installation. All selected packages attempt installation, regardless of any package failure. If Selectable is not checked, all packages in a bundle become a requirement and the end user cannot deselect them. A package failure aborts the remaining packages in the bundle. From an agent distribution The Selectable option allows all packages in a bundle to be installed, regardless of a failure. The bundle stamp file is created after all defined packages have been executed, regardless of success or failure. If Selectable is not checked, all packages become a requirement and any package failure aborts the bundle installation. The bundle stamp file is only created after the successful installation of all packages in the bundle definition. Supported OS packages are only available for inclusion into the bundle definition based on the selected Supported OS options.
155
5.6 Managing purchase orders

Use purchase orders to assign a Part Number to the software package applications. You also require end users to input a valid Purchase Order and Employee ID combination to initiate a pull distribution.
5.6.1 Adding a purchase order

To add a purchase order, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Purchase New Purchase Order to display the Add Purchase Order Form shown in Figure 5-44.
Figure 5-44 Add Purchase Order
156
3. Enter the Purchase Order Number, the Part Number for the associated package, the Employee ID of the end user, and any associated Description as shown in Figure 5-45. Click OK.
Figure 5-45 Purchase Order information
4. The Add Purchase Order page opens with a message that says Purchase_order_number has been added successfully as shown in Figure 5-46.
Figure 5-46 Successful purchase order addition message
The Purchase Order entry can also be completed automatically for multiple entries by enabling the purchase auto update parameter in the sdc.properties file.
157
5.6.2 Deleting a purchase order

To delete an existing purchase order, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Purchase All Purchase Orders. 3. From the List Purchase Orders table, select the check box next to the purchase order number you want to delete as shown in Figure 5-48 on page 159. Click Delete. 4. Click OK to delete the purchase order. See Figure 5-47. Click Cancel to return without making any changes to the database.
Figure 5-47 Delete confirmation
The List Purchase Order window that is shown in Figure 5-48 on page 159 opens.
5.6.3 Searching for a specific purchase order

To search for a specific purchase order, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Purchase All Purchase Orders. The List Purchase Orders table shown in Figure 5-48 opens. 3. Click the Search tab.
158
See Figure 5-48.
Figure 5-48 List Purchase Orders
4. You can search by Purchase Order Number, Part Number, or Employee ID as shown in Figure 5-49. You can perform any one or any combination of the following actions: In the Purchase Order Number field, type the purchase order number. Note: The purchase order number is case-sensitive. Type the purchase order number exactly similar to the one that you are searching for. If you are not sure of the spelling, use the percent symbol (%) as a wild card in place of one or more characters. In the Part Number field, type the part number of the software application with which the purchase is associated. In the Employee ID field, type the ID of the employee for whom you are searching. 5. In the Page Size field, type the maximum number of entries per page to display. 6. Click Search.
159
See Figure 5-49.
Figure 5-49 Purchase Order Search
7. The selected purchase order and associated information is displayed in the List Purchase Orders table as shown in Figure 5-50.
Figure 5-50 Purchase Order Search results
5.6.4 Updating a purchase order

To update purchase order information, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Software Purchase All Purchase Orders. The List Purchase Orders table shown in Figure 5-48 on page 159 opens.
160
3. From the List Purchase Orders table, click the purchase order number. 4. Make changes to the purchase order information as shown in Figure 5-51. Click OK.
Figure 5-51 Update Purchase Order
The List Purchase Orders window shown in Figure 5-48 on page 159 opens.
5.7 Managing distribution lists

From the Distribution Management page, you can view, add, edit, and delete distributions. A distribution list is a group of machines used as the target of a scheduled distribution. In creating the distribution list, the administrator adds a unique name to the definition of the distribution that distinguishes it from other distributions and, optionally, adds additional information about the distribution list in the Description field. The list of target machines can be manually selected in the Selectable Targets tab, or dynamically populated by selecting an Evaluation Name. This selected Evaluation Name is a logical query that searches the inventory data or machine data to include machines in the distribution list. By including an evaluation from the drop-down list, the Dynamic Targets tab is populated according to the conditions that were defined in the evaluation and it automatically adds machines to the Dynamic Targets tab when interpreted by Tivoli Provisioning Manager Express for Software Distribution. Also, as a result of not having the Software Distribution Agent installed, the Invalid Targets tab is populated with a list of machines that meet the conditions of the evaluation, but they do not show up in the Software Distribution machine table.
161
If you are not using an evaluation, then you must add the machines to the distribution list, manually, on the Selectable Targets tab. You can use the Selectable Search tab to populate the Selectable Targets tab for easier selection. When editing a distribution, you can make necessary changes to the definition of the distribution. You can modify the distributions description, evaluation name, or selectable targets for distribution of software to client machines. You can delete distribution lists, which are no longer required, from the Distribution Management page.
5.7.1 Distribution list information

The Add Distribution table displays the following fields and options: General tab Name This is the name of the distribution. Description This is a short description of the distribution. Evaluation Name You can use this to select evaluations, previously created logical queries, that automatically adds machines to the Dynamic Targets tab. Selectable Targets tab This tab has an option called Machine List for Distribution, which is a table that enables you to select machines to associate with a distribution list. Selectable Search tab Name Enter a machine name to limit a logical condition search. OS Select an operating system to limit a logical condition search. IP Address Enter an IP address to limit a logical condition search. Selected Only Limit the search to selected machines associated with the distribution. Page Size Use to limit entries displayed on a page from a search.
162
Dynamic Targets tab This tab has an option called Target Machine List for Evaluation, which is a table that automatically adds machines to the list that meets the logical conditions of the evaluation. Invalid Targets tab This tab has an option called Target Machine List for Evaluation, which is a table that automatically adds machines to the list that meets the logical conditions of the evaluation, but does not have the Software Distribution Agent installed on the client machine.
5.7.2 Adding a distribution list

To add a distribution list, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Distribution Lists New Distribution List to open the Add Distribution table. 3. If you are not using an evaluation, from the General tab, enter the required name in the Name field as shown in Figure 5-52. Optionally, include any additional information to further identify the distribution list in the Description field.
Figure 5-52 Distribution Management: Add Distribution
163
4. Click the Selectable Targets tab and add machines individually to the distribution list as shown in Figure 5-53.
Figure 5-53 Distribution Management: Selectable Targets
5. To locate a specific machine or set of machines, click the Selectable Search tab to perform a search as shown in Figure 5-54. You can make your selection from the resulting set of machines in the Selectable Targets tab, when the screen shown in Figure 5-53 opens again.
Figure 5-54 Distribution Management: Selectable Search
164
6. If an evaluation is being used, go to the General tab shown in Figure 5-52 on page 163 and enter the required name in the Name field. Optionally, include any additional information to further identify the distribution list in the Description field. 7. Select the Evaluation Name from the drop-down list to assign an evaluation to the distribution. As a result, machines automatically get added to the Dynamic Targets tab shown in Figure 5-55 or to the Invalid Targets tab shown in Figure 5-56 after completing the definition. Note: Machines might be manually included in a distribution under the Selectable Targets tab with or without an evaluation being used.
Figure 5-55 Distribution Management: Dynamic Targets
See Figure 5-56.
Figure 5-56 Distribution Management: Invalid Targets
165
8. Click Apply. The Edit Distribution page opens with a message that says Distribution_name has been added successfully, as shown in Figure 5-57.
Figure 5-57 Distribution Management: Successful message
5.7.3 Deleting a distribution list

To delete a distribution list, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Distribution Lists All Distribution Lists. The Distributions table shown in Figure 5-60 on page 167, opens. 3. Select the check box next to the distribution name you want to delete as shown in Figure 5-58. Click Delete.
Figure 5-58 Distribution Management: Delete Distributions
166
4. In the dialog box that is shown in Figure 5-59, click OK to delete the distribution definition. The Distributions table opens as shown in Figure 5-60 on page 167. Click Cancel for no action.
Figure 5-59 Delete confirmation message
5.7.4 Searching for a distribution list

To search for a specific distribution list name, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Distribution Lists All Distribution Lists. The List Distributions table opens as shown in Figure 5-60.
Figure 5-60 Distribution Management: List Distributions
3. Click the Search tab and the screen shown in Figure 5-61 opens.
167
4. On the Search tab: Enter the name of the distribution or leave the Name field blank to return all created distributions. The Name field value is case-sensitive, therefore, to return a valid search, type the exact name or perform a wild card search using the percent symbol (%) in the name field. For example, search for all distributions that start with A by typing A% in the Name field and clicking Search. In the Page Size field, enter the maximum number of entries that match your search criteria to display per page. 5. Click Search. See Figure 5-61.
Figure 5-61 Distribution Management: Search distributions
6. The resulting Distribution Lists open in the Distributions tab as shown in Figure 5-62.
Figure 5-62 Distribution Management: Search results
168
5.7.5 Changing (modifying) the distribution list description

To change the distribution list description, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Distribution Lists All Distribution Lists to open the List Distributions table shown in Figure 5-60 on page 167. 3. Select the distribution name to update, make the necessary changes to the Description, and click Apply to save the information as shown in Figure 5-63. Note: Click Apply for each page to make changes permanent to the database.
Figure 5-63 Distribution Management: Edit Distribution
4. Click OK. The List Distributions page opens as shown in Figure 5-60 on page 167.
5.7.6 Searching for a machine in a specific distribution list

To search for a machine in a specific distribution list, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Distribution Lists All Distribution Lists. The Distributions table shown in Figure 5-60 on page 167 opens.
169
3. Select a distribution list name to edit the distribution. 4. Click the Selectable Search tab as shown in Figure 5-64.
Figure 5-64 Distribution Management: Selectable Search
You can search by machine name, operating system, IP address, or selected machines associated with the distribution. Note: By default, the Selected Only box is selected, and only machines that have been manually selected are displayed on the Selectable Targets tab. If no machines were previously selected, the list of all available machines opens. Perform the search using any combination of the following criteria: In the Name field, type the name of the machine. Note: The Name field value is case-sensitive, therefore, type the exact name, or perform a wild card search using the percent symbol (%) in the Name field. In the OS field, select the operating system. In the IP field, enter the IP address. For the Selected Only option, select Selected Only to restrict the search to the existing selected machines of the distribution. 5. In the Page Size field, enter the maximum number of entries per page to display.
170
6. Click Search. The results of the search criteria opens in the Selectable Targets tab as shown in Figure 5-65.
Figure 5-65 Distribution Management: Selectable Targets
5.8 Managing machines

From the Machine Management page, the administrator receives a list of all the machines that are auto-registered with the Tivoli Provisioning Manager Express for Software Distribution server. The auto-registration occurs for the first time after you install the Software Distribution Agent service. Also, the service performs an update to the registration information at service startup time and every 24 hours thereafter. The administrator can perform deletes of machine registration and searches of all machines that are registered with the Tivoli Provisioning Manager Express for Software Distribution. The searches are performed by name, operating system, or start and end date, as necessary.
5.8.1 Deleting a machine

To delete a machine, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists All Machines. The List Machines table opens.
171
3. Select the check box next to the machine that you want to delete. Click Delete. A dialog box opens, which is similar to Figure 5-59 on page 167. 4. Click OK to delete the machine name. The List Machines table opens as shown in Figure 5-66 on page 172. Click Cancel for no action.
5.8.2 Searching for a machine

To search for a specific machine, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists All Machines. The List Machines table shown in Figure 5-66 opens.
Figure 5-66 Machine Management: List Machines
3. Click the Search tab. 4. Enter the name of the machine or leave the Name field blank to return all registered machines as shown in Figure 5-67. The Name field value is case-sensitive, therefore, to return a valid search, enter the exact name or perform a wild card search using the percent symbol (%) in the Name field. For example, search for all distributions that start with A by typing A% in the Name field and clicking Search.
172
See Figure 5-67.
Figure 5-67 Machine Management: Machines Search
On the other hand, you can use any logical conditions from the search table to search for auto-registered machines using the following criteria: In the Name field, enter the name of the machine. Note: The Name field value is case-sensitive, therefore, you require to enter the exact name, or perform a wild card search using the percent symbol (%) in the Name field. In the OS field, select the operating system. In the Start Date field, select the schedule start date, using the format yyyy-mm-dd, and the time. In the End Date field, select the schedule end date, using the format yyyy-mm-dd, and the time. 5. Click Search. The results of the search, with the name and its associated information (IP address, operating system, and date machine was registered), are displayed in the List Machines table on the Machines tab.
173
5.9 Managing evaluations

From the Evaluation Management page, you can view, add, edit, and delete evaluations. An evaluation is a process that the administrators use to establish a set of logical conditions that you can use to include a group of machines in a distribution list for software installation. You can manually define the evaluation, using either the Software Distribution machine data or the Inventory data to establish the logical set of conditions to create the query, or automatically generate it from an Inventory SQL query. After creating the evaluation, you can link it to a distribution list that you can use to define the set of machines participating in a scheduled distribution. When creating an evaluation, add a unique name to the definition of the evaluation that distinguishes it from other evaluations and provide any additional information in the Description field. The SD Only option allows the conditional statements to use only the Software Distribution machine data table. If you are not adding the evaluation from an Inventory report, you must establish the logical conditions for the query. When editing an evaluation, you can make any necessary changes to the evaluations Description, Case Sensitive status, SD Only option, and conditions. You cannot modify conditional statements generated from an Inventory Report. You can delete evaluations, which are no longer required, from the Evaluation Management panel.
5.9.1 Adding an evaluation from the Distributions menu

To add an evaluation, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Evaluations New Evaluation to display the Evaluation table. 3. In the Add Evaluation area on the General tab, enter the required name in the Name field as shown in Figure 5-68. Optionally, enter the description, select Case Sensitive, and select SD Only, as necessary.
174
The Case Sensitive option enables you to define if the condition uses case-sensitive criteria to find data. SD Only enables you to define if the condition uses only the Software Distribution machine data table.
Figure 5-68 Add Evaluation General tab
4. Click the Conditions tab and define the evaluation conditions as shown in Figure 5-70. Select a database field from the first drop-down list. In the corresponding text field, enter a search string from which to produce a matching list of machines. Apply the standard search criteria. Join multiple fields using the operand drop-down list. Text field strings can also contain additional operands (and, or, not). Click OK. After selecting the SD Only check box, the only tables you can search for are the following: Manufacturer Model Serial Number Computer Name Operating System IP Address
175
See the following Figure 5-69
Figure 5-69 Add Evaluation SD option Condition tab
Instead, if you de-select the SD Only check box you can search for the following conditions as shown in Figure 5-70: Manufacturer Model Serial Number Computer Name Operating System IP Address Subnet Software Driver Status Location Department Town Zip Code E-mail Country First Name Last Name Asset Type Asset Tag
176
See Figure 5-70.
Figure 5-70 Add Evaluation no SD option Condition tab
5. The Add Evaluation Condition page opens with a message that says Evaluation_name has been added successfully as shown in Figure 5-71.
Figure 5-71 Evaluation Management: Evaluation addition success message
177
5.9.2 Adding and evaluating from the Assets menu

Certain Inventory reports that contain the HW Key of the machines in the report include a link to Create Evaluation. By clicking this link, the SQL query that is used to generate the report is imported into the Condition statement of an Evaluation definition. To create an evaluation from these Inventory reports, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select, for example, Assets All Assets to display the assets list. The page shown in Figure 5-72 opens.
Figure 5-72 Assets list
3. Click the Create evaluation button, the page shown in Figure 5-73 opens.
Figure 5-73 Add evaluation from Assets menu: general tab
4. In the Add Evaluation area on the General tab, enter the required name in the Name field shown in Figure 5-73. Optionally, enter the description, and select Case Sensitive, as necessary. The Case Sensitive option enables you to define if the condition uses case-sensitive criteria to find data.
178
5. Click the Conditions tab. It displays the SQL query used for the report. You cannot edit this SQL query. In Figure 5-74, it represents the same query used to list all Assets report.
Figure 5-74 Add Evaluation from Assets menu: condition tab
6. Click OK to save the evaluation definition. The Add Evaluation Condition page opens with a message that says Evaluation_name has been added successfully, as shown in Figure 5-71 on page 177.
5.9.3 Deleting an evaluation

To delete an evaluation, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Evaluations All Evaluations. The List Evaluation table shown in Figure 5-77 on page 181 opens.
179
3. Select the check box next to the evaluation name you want to delete as shown in Figure 5-75. Click Delete.
Figure 5-75 Evaluation list
4. From the dialog box shown in Figure 5-76, click OK to delete the evaluation definition. Click Cancel for no action.
5.9.4 Searching for an evaluation

To search for a specific evaluation name, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Evaluations All Evaluations. The List Evaluation table opens as shown in Figure 5-75.
180
3. Click the Search tab as shown in Figure 5-77.
Figure 5-77 Evaluations search tab
4. In the Search tab: Enter the name of the evaluation or leave the Name field blank and to return all created evaluations as shown in Figure 5-77. The Name field value is case-sensitive, therefore, to return a valid search, type the exact name or perform a wild card search using the percent symbol (%) in the Name field. For example, search for all evaluations that start with A by typing A% in the Name field and clicking Search. Select the SD Only option so that only evaluations in which SD Only has been selected are displayed. In the Page Size field, enter the maximum number of entries to display per page for the search results. 5. Click Search. The result of the search is displayed in the Evaluations tab shown in Figure 5-78.
Figure 5-78 Evaluation Management: Evaluation Search results
181
5.9.5 Update evaluations created from the Dists menu

If the evaluation has been created using the Dist menu, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Evaluations All Evaluations. The List Evaluation table opens as shown in Figure 5-75. Click the name of the evaluation you want to update. 3. On the General tab, the only fields you can update are Description, SD only and Case Sensitive options as shown in Figure 5-79.
Figure 5-79 Evaluation Management: update evaluations
4. Click on the Conditions tab and modify the current conditions as necessary. See Figure 5-69 on page 176. 5. Click OK to save changes.
5.9.6 Update evaluations created from the Assets menu

If the evaluation has been created using the Assets menu: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Evaluations All Evaluations. The List Evaluation table opens as Figure 5-75 shows. Click the evaluation name you want to update.
182
3. On the General tab the only fields you can update are Description, SD only and Case Sensitive options. See Figure 5-79 on page 182. 4. On the Conditions tab you cannot modify anything. For further details see 5.9.2, Adding and evaluating from the Assets menu on page 178. 5. Click OK to save the changes.
5.10 Managing tasks

Tasks are background processes that are run on the Tivoli Provisioning Manager Express for Software Distribution. An example of a task is an action that runs a specific report, attaches the report to an e-mail, and sends the report to a target user or group of users. Another example is a task that can automatically collect client computer asset data at specific intervals. Tasks are typically performed by an administrator. You can run them once or set them to run automatically at set intervals. You can invoke them from the Tasks menu in the Tivoli Provisioning Manager Express for Inventory menu bar or by using the Task Scheduler. The Task Scheduler automatically checks for scheduled tasks. The task types that are available are as follows: E-mail This task type sends an e-mail, using a defined or customized template, to specified users with up to two reports attached. Processlog This processes log files into the database for all non-processed assets. Logreports This schedules a defined Log Report, and need to create a Log Report. Gete-mail This processes the 'in basket' defined in the isic.properties file for receiving e-mails that contain EG2 files, CSV files, or updated information that is in the correct format to be inserted into the database. Getfiles This processes IBM Tivoli Provisioning Manager Express for Inventory Agent EG2 files in a specific directory defined in isic.properties file by the variable eg2.file.directory.
183
Processall This processes all XML data in the FileStore table into the database, if it has not already been processed. Proceslatest This processes all the latest revisions of XML data in the FileStore table into the database, even if it has already been processed. Checkprocessed This checks the validity of all the processed tags on the FileStore table v Tag = Y means data has been processed into the database v Tag = N means data has not been processed into the database. Reprocessall This reprocesses all assets and revisions of XML data into the database. Checksecurity This checks the assets for security compliance using the profile defined in isic.properties. Rechecksecurity This reruns the security task for all assets including those already checked. Checksoftwarelicence This checks all the software installed on assets, including filescan files, for licensable products. Csv_file Drops the selected report (or custom report) to a defined directory on the file system, as a CSV file for integration with other applications. When creating a Csv_file task, to complete the task you require to create a custom report. Use this report as a parameter to create the CSV file. Variable in isic.properties file that defines this directory is export.data.directory. To complete the task you require to create a custom report and use it as a parameter to create the CSV file. See Updating the isic.properties file in the Version 4.1.1 - IBM Tivoli Provisioning Manager Express Administrators Guide, SC32-0172. Filescan This processes the filescan file from the FileStore table to the database.
184
Swlicences This checks all software entries for matches, and marks them as licensable if appropriate. Syncmasterdata This pulls down updated or new data from a master server configured in the properties file.
5.10.1 Adding a task

To add a task, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Select Tasks Create New Task. The create new task page opens as shown in Figure 5-80.
Figure 5-80 Adding a new task
185
When adding a new task you have to select the value of yes in the scheduled field in order to display a secondary list of fields. See Figure 5-81.
Figure 5-81 Adding a new task, extended fields
3. Fill in all the required fields and click the Submit button. The window in Figure 5-82 opens.
Figure 5-82 Adding a new task, successful message
186
5.10.2 Deleting a task

To delete a task, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Tasks All Tasks. The All Task page opens. See Figure 5-83.
Figure 5-83 Delete Task
3. Select the check box near the task you want to remove and click the Delete Selected Task(s) on the Action box or select Tasks Delete Selected Task(s) on the Administrative console menu.
187
4. The successful message displayed is shown in Figure 5-84.
Figure 5-84 Delete Task: success message
5.10.3 Update a task

To update a task, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Tasks All Tasks. The All Task pages opens showing the tasks list.
188
See Figure 5-85.
Figure 5-85 Edit Task
3. Select the check box near the task you want to remove and click the Edit Selected Task on the Action box or select Tasks Edit Selected Task on the Administrative console menu. The Edit Task Page opens as shown in Figure 5-86. Update fields as necessary and click the Submit button. Note: It is not possible to select more than one task to edit/update.
Figure 5-86 Edit task page
189
5.10.4 Running a task

There are two possibilities of running tasks. They are manual and scheduled.
Running tasks manually

To run a task manually, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Tasks. Then, select the appropriate Tasks menu option. Then, choose the appropriate task. The task runs. To see if the task has run, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Admin View Application Log and check in the log file if there is an entry for Starting task [name of your task] and the next Finished Task [name of your task].
Running tasks through the scheduler

The Task Scheduler is the engine that executes scheduled tasks. It checks the queue of scheduled tasks at a defined frequency and executes those ready to run. You can configure the Task Scheduler to start automatically when the IBM Tivoli Provisioning Manager Express for Software Distribution server starts. For further information, see Schedules properties on page 69 or started manually. Note: The Task Scheduler is initiated by default and runs all active tasks according to their schedule. For further information about how to make the scheduler not start when the server starts, refer to Schedules properties on page 69.
Manually start the Task Scheduler

To start the Task Scheduler manually, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Admin Start Task Scheduler. The Task Scheduler starts and checks all scheduled tasks to determine if they are due to be executed. The Task Scheduler continues to check for scheduled tasks according to the
190
frequency you set during the IBM Tivoli Provisioning Manager Express for Inventory installation or in the isic.properties file.
Manually stop the Task Scheduler

To stop the Task Scheduler, perform the following procedure: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Admin Stop Task Scheduler. The Task Scheduler stops.
Scheduling a task
Follow the instructions to update an existing task as described in 5.10.3, Update a task on page 188. Following this, perform the given steps: 1. Select Yes in the Active? field pull-down menu. 2. Select Yes in the Scheduled? field pull-down menu. 3. Fill in the other appropriate fields and click the Submit button. Start the scheduler, if not started, following the procedure described in Manually start the Task Scheduler on page 190.
5.11 Managing schedules

From the Schedule Management page, you can view, add, edit, and delete schedules. Schedules are a window of time for each distribution to install a software package or bundle to a set of client machines. This process enables the Software Distribution server to perform push distributions to the Software Distribution Agent. The initial Schedule Management page enables you to view a list of schedules with their associated package name, distribution list, start date, end date, and whether each schedule is enabled for distribution to the client machines. The daily start and daily stop times are based on the time on the server. The time window is specific to the server time zone and is evaluated locally on the server as each client checks for schedule availability. You must group the scheduled distributions to machines, in time zones different from the server, into a separate distribution list, to adjust the times for any server to client differences.
191
When adding a schedule, give the schedule a unique name to distinguish it from the other schedules and provide any additional information in the Description field. You can enable the schedule or leave it in an inactive state. After selecting the distribution list that determines the target list of machines, decide the daily start time and end time of the schedule. Also decide the start date and end date, before selecting the package or bundle to be distributed. When editing a schedule, you can update the description, enable the schedule, and change the distribution list. You can modify the daily start time and end time along with the start date and end date. You can also change the package or bundle, but we recommend that you create a new schedule for each application distribution. When adding or editing a schedule, perform a search for packages or bundles to include in the schedule. The search is a logical condition that enables the option for you to search on the name of the package or bundle, package type, or operating system. You can delete schedules that are no longer required from the Schedule Management page.
5.11.1 Scheduling information

Use the descriptions and options in the Add Schedule table: General tab The general tab has the following options: Schedule The name of the schedule. Description A short description of the schedule. Enable Enables the schedule for distribution of software to client machines. Distribution Name A drop-down menu that enables you to associate a distribution list to the schedule. Enable Deferral option Enables a software installation to be deferred by the end user.
192
Deferral Number Defines the number of times that the end user can defer the software installation before the software is automatically installed to the client machine. Deferral Duration Defines the duration of time between deferrals that the end user has before the dialog box is displayed again on the client side. Daily Start Time The start of the time window each day at which the scheduled distribution is available to the Software Distribution Agent. Daily End Time The end of the time window each day at which the scheduled distribution is available to the Software Distribution Agent. Start Date The start date for a range of days in which the scheduled distribution is available to the Software Distribution Agent. The format is YYYY-MM-DD. End Date The end date for a range of days after which the scheduled distribution is no longer available to the Software Distribution Agent. The format is YYYY-MM-DD. Package tab The package tab has the following options: Query Packages/Query Bundles Specifies if a package or a bundle is to be included in the distribution. Package/Bundle Name This list is the result of a search that the administrator performs. From the list, select the package or bundle to include in the schedule. Name The name of a software package or bundle to search for, to include in the schedule. The name is case-sensitive. Therefore, type the exact name or search using the wild card percent symbol (%) in the Name field.
193
Package Type Enables you to limit the search of software packages by package type. The following are the package types: Download(Open) Download(Secure) LogicalDrive(Open) LogicalDrive(Secure) DirectoryDownload(Open) DirectoryDownload(Secure)
OS Enables you to limit the search to the operating system on which you can install the software package.
5.11.2 Adding a schedule

To add a schedule, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Schedules New Schedule to display the Add Schedule table shown in Figure 5-87. 3. In the Add Schedule table, perform the following actions: Enter the name of the schedule and add any additional description information, if wanted. Select Enable to activate the schedule for distribution, or leave it cleared to allow the schedule to remain inactive until a later point. Select the distribution list from the drop-down menu to define the list of target machines to be included in the scheduled distribution. If you want the end user to have the opportunity to defer the installation to a later time, select Enable Deferral Option. Also, select the number of times the end user can defer the installation and select the duration between deferrals. Set the daily start time and daily end time and set the start date and the end date for the distribution. 4. Click Next to display the package/bundle search.
194
See Figure 5-87.
Figure 5-87 Schedule Management: Add Schedule
5. From the Package tab, select either Query Package or Query Bundle to specify what is to be distributed as shown in Figure 5-88. By default, the Package/Bundle Name drop-down list is empty. Use the search box to populate the selection list by entering the search criteria based on name, package type, and operating system. If you click Search with no preferences, then it generates a list of all packages or bundles. For more about the schedule definition fields, see 5.11.1, Scheduling information on page 192. 6. Click Add.
195
See Figure 5-88.
Figure 5-88 Schedule Management: Add Schedule package
7. The Add Schedule page, with a message that says Schedule_name has been added successfully opens as shown in Figure 5-89.
Figure 5-89 Schedule Management: Add Schedule message
196
5.11.3 Searching for a specific schedule

To search for a specific schedule, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Schedules All Schedules. The List Schedules table opens as shown in Figure 5-90.
Figure 5-90 Schedule Management: List Schedules
3. Click the Search tab. The Search table opens as shown in Figure 5-91. 4. Enter the name of the schedule or leave the Name field blank to return all created schedules. The Name field value is case-sensitive. Therefore, to return a valid search, type the exact name or perform a wild card search using the percent symbol (%) in the name field. For example, search for all schedules that start with A by typing A% in the Name field and clicking Search.
197
See Figure 5-91.
Figure 5-91 Schedule Management: Search schedule
Otherwise, use any logical conditions from the search table to search for schedules by using the following fields: In the Schedule Name field, enter the schedule name. Note: The Schedule Name field value is case-sensitive. Therefore, type the exact name or perform a wild card search using the percent symbol (%) in the Schedule Name field. In the Distribution Name field, select the distribution name to which the schedule belongs. In the Start Date field, select the schedule date designated to start a search for a schedule. In the End Date field, select the schedule date designated to end a search for a schedule. 5. In the Page Size field, type the maximum number of entries per page to display. 6. Click Search. The List Schedules table displays the results of the search with the schedule name, package name, distribution name, start date, end date, and if the schedule is enabled, as shown in Figure 5-90 on page 197.
198
5.11.4 Deleting a schedule

To delete a schedule, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Dists Schedules All Schedules. The List Schedules table opens as shown in Figure 5-90 on page 197. 3. Select the check box next to the schedule you want to delete. Click Delete. 4. Click OK to delete the schedule name as shown in Figure 5-92. The List Schedule table shown in Figure 5-90 on page 197 opens.
5.12 Managing logs and standard reports

This section provides information about using the Tivoli Provisioning Manager for Software Distribution logs.
5.12.1 Software Distribution log entry details

The logs contain the following information: TimeStamp: The date and time of the log entry UserID: The users name Client: Agent or Client HostName: The host name of the client machine Universal Unique Identifier (UUID): The UUID address of the client machine Client IP Address: The IP address of the client machine Operating System: The operating system of the client machine OS Version: The operating system version number of the client machine Java Vendor: The Java vendor name of the JRE used by the client machine Java Version: The Java version of the JRE used by the client machine Login: The user account used to log in to the operating system Package: The name of the software package
199
Install Type: The installation type of the package Schedule Name: The name of the schedule to install the package Transaction ID: The transaction ID of a client-side installation of a package Bundle ID: The bundle ID to install a set of packages on a client machine Package ID: The package ID to install a package on a client machine Status: The current status of the software package Message: The description of the status of the software package
5.12.2 Viewing a Software Distribution log

To view a distribution log, perform the following steps: 1. Select Reports Distribution Reports View Logs. The List Logs page opens as shown in Figure 5-93.
Figure 5-93 Log Management: List Logs
If available, this table displays the current days event logs.
200
2. Click the Search tab to change the Start Date to view any previous log events as shown in Figure 5-94.
Figure 5-94 Log Management: Log Search
3. Change the Start Date value and click Search. A page with the list of logs opens as shown in Figure 5-95.
Figure 5-95 Log Management: Log Search results
201
4. From Logs list, select a TimeStamp. The distribution details log displaying information about the event opens as shown in Figure 5-96. In addition, you can view the complete package log sequence from an event log.
Figure 5-96 Log Management: Log Details
5.12.3 Searching for a distribution log

To search for a specific log, perform the following steps: 1. Select Reports Distribution Reports View Logs. The List Logs page opens as shown in Figure 5-93 on page 200. The table displays the current days event logs. 2. Click the Search tab. The Search table opens as shown in Figure 5-94 on page 201.
202
3. Perform a logical condition search by using a combination of the following fields: In the Package Name field, type the package name and set the logical condition for the search. The Package Name field value is case-sensitive. Therefore, type the exact name of the package or perform a wild card search using the percent symbol (%). In the Machine Name field, type the machine name and set the logical condition for the search. The Machine Name field value is case-sensitive. Therefore, type the exact name of the machine or perform a wild card search using the percent symbol (%). In the Schedule Name field, type the schedule name and set the logical condition for the search. The Schedule Name field value is case-sensitive. Therefore, type the exact name of the schedule or perform a wild card search using the percent symbol (%). In the Track ID field, type the track ID and set the logical condition for the search. The track ID is established each time a user selects to install on a client-side pull of software. In the UserID field, type the user name and set the logical condition for the search. The UserID field value is not case-sensitive. In the Client Type field, select AGENT for all agent pushes of software to the client machines, or CLIENT for all client pulls of software to the client machine, or BOTH for agent pushes and client pulls of software to the client machine. In the Status field, enter the status and set the logical condition for the search. In the Start Date field, type the date or select it from the calendar. Select the start time for the search. In the End Date field, type the date or select it from the calendar. Select the end time for the search. 4. Click Search. The Logs tab displays the logs as shown in Figure 5-95 on page 201.
5.12.4 Deleting a distribution log

To delete a distribution log, perform the following steps: 1. Select Reports Distribution Reports View Logs. The Log Management table opens as shown in Figure 5-93 on page 200. 2. Click the Search tab.
203
3. The Search table opens as shown in Figure 5-94 on page 201. Perform a logical condition search by preference on package name, machine name, schedule name, track ID, user ID, client type, status, start date, and end date. 4. Verify that results of the search contain only the records to be deleted. 5. Return to the Search tab. Click Delete. The List Logs page opens as shown in Figure 5-93 on page 200.
5.12.5 Standard report categories

To view the standard report categories select Reports. The standard report categories page opens as shown in Figure 5-97. All Assets, Statistics, Users, Workstation Security, Information, Import Templates, My Assets, Groups, Data Maintenance, Tasks, Software, Logs, Filescan Licenses, Installed Software Licenses, and Show Table Data are the main standard report categories.
Figure 5-97 Standard report categories
204
5.12.6 Viewing package reports

To view a package report, perform the following steps: 1. Select Reports Distribution Reports Package Reports. The Package Management page opens as shown in Figure 5-98. From here, you can select one or more packages to be included in the report. 2. Select any package name or select multiple packages shown in Figure 5-98 to view the Package Summary Report that Figure 5-99 shows.
Figure 5-98 Package Management: List Packages
3. From the Package Summary Report, select Total Distributions, Success, or Failed to view detailed information for the package as Figure 5-99 shows: Total Distributions Selecting the number under this column displays a list of all machines that have installed the associated package. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine.
205
Success Selecting the number under this column displays a list of all machines that have successfully installed the associated package. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. Failed Selecting the number under this column displays a list of all machines that have failed installing the associated package. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. See Figure 5-99.
Figure 5-99 Package Summary Report
5.12.7 Searching for a package to report

To search for a package to report, perform the following steps: 1. Select Reports Distribution Reports Package Report. The Package Management page opens, where you can select one or more packages to be included in the report as shown in Figure 5-98 on page 205. 2. Click the Search tab to open the Search table.
206
See Figure 5-100.
Figure 5-100 Package Management: Distribution report search
3. Perform a logical condition search by using the following fields: In the package Name field, type the package name and set the logical condition for the search. The package Name field value is case-sensitive. Therefore, type the exact name of the package or perform a wild card search using the percent symbol (%). In the Package Type field, select AGENT for all agent pushes of software to the client machines, or CLIENT for all client pulls of software to the client machine, or BOTH for agent pushes and client pulls of software to the client machine. In the OS field, select the operating system. 4. In the Page Size field, enter the desired size of the search results to be displayed on each page or use the default of 20. 5. Click Search. 6. The Package Management page opens as shown in Figure 5-98 on page 205. Select a package name to view the report.
207
5.12.8 Viewing a machine report

To view a machine report, perform the following steps: 1. Select Reports Distribution Reports Machine Reports. The Machine Management page opens, where you can select one or more machines to be included in the report Figure 5-101 on page 208. 2. Select any machine name or select multiple machines to view the Machine Summary Report.
Figure 5-101 Machine Management: List Machines
3. From the Machine Summary Report, select Total Distributions, Success, or Failed to view the detailed information for the machines as shown in Figure 5-102: Total Distributions Selecting the number under this column displays a list of all packages that have been installed on the associated machine. Selecting the time stamp for any package displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. Success Selecting the number under this column displays a list of all packages that have been successfully installed on the associated machine. Selecting the time stamp for any package displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine.
208
Failed Selecting the number under this column displays a list of all packages that have failed installing on the associated machine. Selecting the time stamp for any package displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine.
Figure 5-102 Machine Summary Report
5.12.9 Searching for a machine to report

To search for a machine to report, perform the following steps: 1. Select Reports Distribution Reports Machine Report. The Machine Management page opens, where you can select one or more machines to be included in the report as shown in Figure 5-101 on page 208. 2. Click the Search tab. The Search table opens. 3. Perform a logical condition search by using the following fields: In the machine Name field, enter the machine name and set the logical condition for the search. The machine Name field value is case-sensitive. Therefore, type the exact name of the machine or perform a wild card search using the percent symbol (%). In the OS field, select the operating system. In the Start Date field, type the date or select it from the calendar. Select the start time for the search. In the End Date field, type the date or select it from the calendar. Select the end time for the search.
209
4. In the Page Size field, enter the desired size of the search results to be displayed for each page or use the default of 20. 5. Click Search. See Figure 5-103.
Figure 5-103 Machine Management: Machine Search
The Machine Management page opens, where you can select machines to view the reports as shown in Figure 5-101 on page 208.
5.12.10 Viewing a schedule report

To view a schedule report, perform the following steps: 1. Select Reports Distribution Reports Schedule Reports. The Schedule Summary Report page opens, where you can select one or more schedules to be included in the report as shown in Figure 5-104. 2. Select any schedule name or select multiple schedules to view the Schedule Summary Report.
210
See Figure 5-104.
Figure 5-104 Schedule Summary Report
3. From Schedule Report Details page, select Total Machines, Success, Fail, In Process, No Data, or Already Installed for the schedule as shown in Figure 5-105. The descriptions of these options are as follows: Total Machines Selecting the number under this column displays a list of all machines that were included in the distribution list for the schedule. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. Success Selecting the number under this column displays a list of all machines that were successful in completing the package installation. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. Fail Selecting the number under this column displays a list of all machines that failed while completing the package installation. The Status column includes the Software Distribution return code to be used for troubleshooting. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine.
211
In Process Selecting the number under this column displays a list of all machines that had not returned a final completion code at the time of the report. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. No Data Selecting the number under this column displays a list of all machines that were included in the distribution list for the schedule, but have not checked in or logged any events for the distribution. The last machine registration date is displayed, and these machines must have the agent service verified to be running. Already Installed Selecting the number under this column displays a list of all machines that returned a status indicating the package was already installed by another process. The stamp file was found on the machine, and no logs are present to show that the package was installed by Software Distribution. Selecting the time stamp for any machine displays the log details of the package installation. In addition, selecting the view package log sequence displays the complete log sequence of the package installation for the selected machine. See Figure 5-105.
Figure 5-105 Schedule Report Details
212
5.12.11 Viewing an assets summary report

To view an assets summary report, perform the following steps: 1. Select Reports All Assets Assets Summary. The Assets Summary Report page opens, where you can select one or more assets to be included in the report as shown in Figure 5-106. 2. Select any asset names or select multiple assets to view the Assets Summary Report.
Figure 5-106 Assets Summary Report
213
5.12.12 Searching for a schedule to report

To search for a schedule to report, perform the following steps: 1. Select Reports Distribution Reports Schedule Report. The Schedule Summary Report table opens, where you can select one or more schedules to be included in the report as shown in Figure 5-104 on page 211. 2. Select the Search tab. The Search table opens as Figure 5-107 shows. 3. Perform a logical condition search by using the following fields: In the Schedule Name field, enter the schedule name. The Schedule Name field value is case-sensitive. Therefore, type the exact name of the schedule or perform a wild card search using the percent symbol (%). In the Distribution Name field, select the distribution name for the search. In the Start Date field, enter the date or select it from the calendar for the search. In the End Date field, enter the date or select it from the calendar for the search. 4. In the Page Size field, enter the desired size of the search results to be displayed for each page or use the default of 20. 5. Click Search.
Figure 5-107 Schedule Summary Report Search
The Schedule Summary Report table opens. You can use this to select a schedule to view the report as shown in Figure 5-104 on page 211.
214
5.13 Managing custom reports (queries)

This section is for managing custom reports.
5.13.1 Adding a custom report

To add custom reports, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Reports New. 3. Click the Edit SQL button. The pop-up in Figure 5-108 opens.
Figure 5-108 Reports: Edit SQL page
4. Choose the action to perform between: Add Table: add a table to the current view Add Column: add a column to the current view Delete Column: remove a column from the current view Arrange Column: permit to exchange the position between columns Modify Conditions: adds a limit to the SQL query (host name for example) Edit SQL: permit to modify SQL query directly Edit Name: modify the name of the current report
5. The results of your query are shown in the results page.
215
6. Select Reports Save Custom Query. The page shown in Figure 5-109 opens.
Figure 5-109 Reports: Saving custom report
7. Input the Query Name, Description, and Menu Name. Correct the SQL query, if necessary. Select the groups that are going to be able to run this query. 8. Click the Submit button. The report results are shown again.
5.13.2 Adding a custom report starting from a standard report

To add custom reports, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console refer to 5.1, Accessing the Administrative console on page 98. 2. Choose a standard report as a starting point. For example, select Reports All Assets All Assets. The report page opens. See Figure 5-110.
Figure 5-110 Reports: All Assets report.
216
3. Click the Edit SQL button. The pop-up in Figure 5-108 on page 215 opens. 4. Choose the action to perform between: Add Table: add a table to the current view Add Column: add a column to the current view Delete Column: remove a column from the current view Arrange Column: permit to exchange the position between columns Modify Conditions: adds a limit to the SQL query (host name for example) Edit SQL: permit to modify SQL query directly Edit Name: modify the name of the current report
For example, to delete a column from the Asset report click the Delete Column button. The pop-up in Figure 5-111 opens.
Figure 5-111 Reports: Delete a column from a standard report
Select the column you want to remove, click Delete and then click the Submit button, the result of your query opens. 5. The results of your changes are shown in the results page. 6. Select Reports Save Custom Query. The page shown in Figure 5-109 on page 216 opens. 7. Input the Query Name, Description and Menu Name. Correct the SQL query, if necessary. Select the groups that are going to be able to run this query. 8. Click the Submit button. The report results are shown again.
217
5.13.3 Deleting a custom report

To delete a custom report, perform the following steps: 1. Log in to the Administrative console. For further information about how to log in to the console, refer to 5.1, Accessing the Administrative console on page 98. 2. Select Reports All Custom Reports. The All Custom Reports page opens. See Figure 5-112.
Figure 5-112 All Custom reports page
3. Select the check box near the task you want to remove and click the Delete Custom Report on the Action box or select Reports Delete Custom Report on the Administrative console menu. 4. The successful deletion message is displayed on screen.
5.14 Managing catalogs

The Tivoli Provisioning Manager Express for Software Distribution Catalog is a Java program used on client machines to install software applications. The client catalog enables users to select and install software packages and bundles from a custom list of applications. The catalog can be installed and run as a stand-alone application, or it can be run as a Java Web Start applet. You must install the Software Distribution Agent service to provide full functionality. The agent service allows you to install packaged applications in a restricted user environment and also allows it to be automatically installed as a part of a scheduled distribution.
218
5.14.1 Client catalog overview

The client catalog can run either from a Web browser as a Java Web Start applet, or if installed, as a stand-alone Java application. Figure 5-113 illustrates the various functions of the Software Distribution Catalog.
Figure 5-113 Software Distribution Catalog functions
The following list illustrates functions shown in Figure 5-113: Packages, A A list of all the applications available for download. Highlighting a particular application displays the size of that package in MB. The operating systems the package supports are displayed in the Selected Package Information Pane J. Selecting an application and selecting Install K, begins the installation process. Selecting multiple packages is supported, and those packages are installed sequentially. Bundles, B Displays packages that were bundled or grouped together to facilitate installation. Selecting a bundle causes a list of packages that is installed to be displayed in the next pane. Selecting a bundle and selecting Install K, begins the installation process.
219
Bundle Details, C Displays a list of packages included in a bundle. Status, D Displays whether a package is currently installed on the workstation. Search, E To narrow the list of packages displayed, you can perform a search. The search is based on the package name. To display all the packages after a search, perform a search with standard search wildcard characters, such as an asterisk (*) or a question mark (?). Install in Progress, F When a package is in the process of being installed, the Install in Progress area changes to an active state. When the installation completes, the area returns to an inactive state. Details, G Selecting Details displays package-specific information or instructions. Clear, H Clears all package selections. Refresh, I Refreshes the catalog with the latest available packages and bundles. Selected Package Information, J Displays platform and package size information for the selected package or bundle. Install, K Starts the installation process for all of the selected packages or bundles. Exit, L Closes the Tivoli Provisioning Manager Express for Software Distribution client catalog applet.
220
5.14.2 Accessing the catalog

This section describes how to access the catalog.
Starting the Software Distribution Catalog from a local system

After installing the Software Distribution Agent service, perform the following steps to access the catalog: 1. Launch the client catalog using the Start menu by selecting Start Programs IBM Tivoli Provisioning Manager Express Software Distribution Catalog. The Software Distribution Catalog Login window shown in Figure 5-114 opens.
Figure 5-114 Software Distribution Catalog Login
2. Enter the user name and password (or create a new ID) and then click Login. The Software Distribution Catalog shown in Figure 5-115 opens.
Figure 5-115 Software Distribution Catalog
221
Java Web Start applet

Use the following steps to access the client catalog using Java Web Start: 1. Open a Web browser, and in the Address bar, enter one of the following: http://server_name/tpmx/ Where server_name is the name of the Tivoli Provisioning Manager Express for Software Distribution server. http://server_IP_address/tpmx/ Where server_IP_address is the IP address of the Tivoli Provisioning Manager Express for Software Distribution server. Press Enter. 2. Tivoli Provisioning Manager Express for Software Distribution Welcome page shown in Figure 5-1 on page 98 opens. If your system already has Java 1.4, or a later version, installed and defined, the Access Catalog button is displayed in the left column. If your system does not have Java installed, an error message is displayed with a link to download and install IBM Java 1.4.2. Click Access Catalog. 3. Click Start in the Tivoli Provisioning Manager Express for Software Distribution Security Warning window shown in Figure 5-116.
Figure 5-116 Security Warning
The Software Distribution Catalog Login window opens as shown in Figure 5-114 on page 221. 4. Enter the user name and password (or create a new ID) and then click Login.
222
5. The Software Distribution Catalog opens as shown in Figure 5-115 on page 221. You might see a Tivoli Provisioning Manager Express for Software Distribution Desktop Integration window as shown in Figure 5-117: Click Yes to add a Tivoli Provisioning Manager Express for Software Distribution Catalog icon on the desktop for easier access. Click No to decline adding the icon on your desktop. Click Ask Later to defer creation of the desktop icon to a later time.
Figure 5-117 Desktop Integration
5.14.3 Creating a portable catalog, exporting and importing libraries between two servers
To create a portable catalog, perform the following steps: 1. Create an export list. For more details, refer to , Adding an export list on page 224. 2. Select Software packages or Bundles to include in the catalog. For further details, refer to Creating an XML output file for an export list to export packages and on page 227. 3. Invoke the CD Catalog Exporter. For further details, refer to Using a portable catalog on page 235. Note: Software Distribution provides the capability to create a portable catalog that you can run from a network drive, CD, or other portable media. This feature is useful for computers that are not connected to the network and computers that do not have access to the Software Distribution server.
223
Managing Export lists

Use the export option to define a set of packages and bundles to be included in an export list. You can use the export definition to replicate packages or create portable catalogs. You can create an XML output file containing all the package and bundle definition information from those specified in the export. The XML output file is used as the source to import the library definitions created on the source server into the target server. Throughout the following procedure, we use the term source server to identify the Tivoli Provisioning Manager Express for Software Distribution server that currently contains the XML source file and software packages to be exported. We use the term target server to identify the Tivoli Provisioning Manager Express for Software Distribution server to which the files are to be imported. You can also use the export definition as the source to create a portable Software Catalog, which is a library of software packages, bundles, or both, to be distributed from CD or a network drive. For further details about the import and export options, see 5.14.3, Creating a portable catalog, exporting and importing libraries between two servers on page 223 and Importing Software Distribution files from another server on page 229.
Adding an export list

To add an export list, perform the following steps: 1. Select Software Export/Import New Export. 2. In the Add Export area, enter the name in the Name field and the description in the Description field for the export as shown in Figure 5-118. Click Next.
Figure 5-118 Add Export
224
3. Select the packages to add to the export list by selecting the check box next to the package names as shown in Figure 5-119. Click Next.
Figure 5-119 Package List for Export
225
4. Select the bundles to add to the export list as shown in Figure 5-120. Click OK to save the export list.
Figure 5-120 Bundle List for Export
5. The Add Purchase Order page opens with a message that says Export_list_name has been added successfully as shown in Figure 5-121.
Figure 5-121 Successful export list addition message
Note: Click Apply to make changes permanent to the database for each page of packages/bundles.
226
Searching for an export list

To search for a specific export list name, perform the following steps: 1. Select Software Export/Import All Exports. The List Exports table opens. 2. Select the Search tab. The Search page opens. Enter the following values: In the Name field, enter the export name. The export list name is case-sensitive. Type the name exactly as the name is listed in the export list you are searching for. If you are not sure of the spelling, use the percent symbol (%) as a wild card in place of one or more characters. In the Page Search field, type the maximum number of entries that match your search criteria to display per page. 3. Click Search. The selected export list name and description opens in the List Exports table.
Deleting an export list

To delete an export list, perform the following steps: 1. Select Software Export/Import All Exports. The List Export page shown in Figure 5-122 on page 228 opens. 2. Select the check box beside the export list name you want to delete. Click Delete. 3. Click OK to delete an export list. The List Export page shown in Figure 5-122 on page 228 opens. Click Cancel for no action as shown in Figure 5-47 on page 158.
Creating an XML output file for an export list to export packages and bundles
To create an XML output file for an export list, perform the following steps: 1. Select Software Export/Import All Exports to display the export table. For further details about adding a new export list, see Adding an export list on page 224. 2. From the List Exports table, select the export name as Figure 5-122 shows.
227
See Figure 5-122.
Figure 5-122 List Exports
3. From the Edit Export table, click OutputXML as shown in Figure 5-123.
Figure 5-123 Edit Export list
228
4. Click Open to display the XML output in a browser as shown in Figure 5-124. Click Save to save the XML output.
Figure 5-124 OutputXML
Importing Software Distribution files from another server

The following procedure assumes that you already created the XML output file from the source Tivoli Provisioning Manager Express for Software Distribution server. If you have not, export the XML file now before you start this procedure. See Creating an XML output file for an export list to export packages and on page 227. Note: The two purposes of the export function in IBM Tivoli Provisioning Manager Express for Software Distribution are: They are used as an input to the CD Catalog Exporter. They are used to transfer package definitions from one server to another. Perform the following steps: 1. If the physical package files, detail files, and icon files are on a logical drive (a shared network drive outside of the source server), no further action is required. If the physical package files, details files, and icon files are stored on the source server, copy the files to the target server using one of the following methods: From the target server, map to the source server. Then, copy the appropriate package files, detail files, and icon files to the target server. At the source server, copy the appropriate package files, detail files, and icon files to portable media (such as CD or DVD). Then, bring the portable media to the target server and copy the files on the target server.
229
Note: The folder structure for the package files, detail files, and icon files must be the same on the target server as it is on the source server. Otherwise, you have to update the package information for each imported package at the target server to specify the changed paths. The affected fields are the Details field and Icon Path field on the General tab and the Remote file on the Install tab. 2. Copy the XML output file to the target server using one of the following methods: From the target server, map to the source server. Then, copy the XML output file from the source server to the target server. At the source server, copy the XML output file to a portable media. Then, bring the portable media to the target server and copy the XML source file anywhere on the target server. 3. At the target server, open the Tivoli Provisioning Manager Express for Software Distribution administration console and perform the following steps: a. Select Software Export/Import Import XML. The Select The XML File For Import page opens as shown in Figure 5-125. b. From the Select The XML File For Import area, in the File Name field, enter the XML source file name or click Browse to select the XML output file. Click OK.
Figure 5-125 Import XML
230
c. In the Import Package area, click OK to accept each package as shown in Figure 5-126. Click Skip to bypass any package you do not want to import. After all the packages and bundles contained in the output XML have been added, you are prompted to add the export definition used to create the export output XML file shown in Figure 5-118 on page 224.
Figure 5-126 Import Package
d. Click OK to finish importing the XML output file. The List Export page shown in Figure 5-122 on page 228 opens.
Exporting a portable catalog

The following procedure assumes that you already created the export list definition on the Tivoli Provisioning Manager Express for Software Distribution server. If you have not, create an export list now. Refer to Adding an export list on page 224. Perform the following steps: 1. Select Software Export/Import CD Catalog Exporter. 2. In the Security Warning dialog box, click Start as shown in Figure 5-127.
231
See Figure 5-127.
Figure 5-127 Security Warning
3. The Java-based import/export utility window shown in Figure 5-128 opens.
Figure 5-128 CD Catalog Exporter
However, at first launch, you might see the Tivoli Provisioning Manager for Software Distribution CD Catalog Exporter - Desktop Integration window, as shown in Figure 5-129. Click Yes to place an icon on desktop for easier access. Click No if an icon is already present on your desktop. Click Ask Later to defer it to a later time.
Figure 5-129 CD exporter icon
232
4. In the CD Catalog Exporter window: Select an export group from the Export Group field as shown in Figure 5-130. In the Image Location field, type the file name or click Browse to select the folder where the portable catalog files and folders are to be stored. Select Reversibly Corrupt to indicate that the individual packages must be encoded with the Reversibly Corrupt process. When this is enabled, packages in the portable catalog are only able to be installed through the Tivoli Provisioning Manager Express interface. Select Delete Image After Install to indicate that the portable catalog directory structure must be deleted after the catalog is closed at the end of one session. This is to support the Blue Button retrieval of the package catalog.
Figure 5-130 CD Catalog Exporter
5. Click Preview to display the space per package, a list of packages, the total space required, and the names of any missing files as Figure 5-131 shows.
Figure 5-131 CD export package information
233
6. Click Export to initiate the process of creating the directory structure with the specified packages from the export list. The progress is displayed at the bottom of the CD Catalog Exporter window shown in Figure 5-132.
Figure 5-132 CD Catalog Exporter progress
Note: When the export process is complete, the bottom of the CD Catalog Exporter window displays Done. 7. The required files for portable catalog are copied into the folder shown in Figure 5-133 specified in Image Location field shown in Figure 5-132.
Figure 5-133 Portable Catalog files view
234
8. If you want to put the portable catalog on CD or DVD, use the CD/DVD recording software of your choice to copy the portable catalog files and folders to the CD or DVD. If you want to put the portable catalog on a network drive or other media, copy the files to the appropriate drive or media. Note: Make sure that you maintain the directory structure and include all the files and folders.
Previewing a portable catalog

This procedure enables you to view the list of software packages contained in a portable catalog, the space required for each package, the total space required for the packages, and the names of any missing files. To preview the portable catalog: 1. Select Software Export/Import CD Catalog Exporter. The Java-based Import/Export Utility window shown in Figure 5-128 on page 232 opens. 2. In the Export Group field, select an export group name as shown in Figure 5-130 on page 233. 3. In the Image Location field, type the file name or use Browse to select the folder where the portable catalog files and folders are stored as shown in Figure 5-130 on page 233. 4. Click Preview. The space per package, a list of packages, the total space required, and the names of any missing files are displayed, as shown in Figure 5-131 on page 233. Note: Make sure that you maintain the directory structure and include all the files and folders.
Using a portable catalog

The portable catalog is an application. Therefore, the operating system must be running before you can start the portable catalog. If the portable catalog is on CD, in most cases, it starts automatically when the CD is inserted into the drive. If the portable catalog does not start automatically or if the portable catalog is on a different type of media such as network drive and USB memory key, use the following procedure: 1. Open Windows Explorer or My Computer and navigate to the folder where the portable catalog resides. 2. Double-click the SETUP.bat file.
235
Note: If a message is displayed asking you if you want to install the Build CD and Verify program, click Start. You see this message the first time you start a portable catalog on a computer. If you receive a message asking you if you want to create a desktop icon, click No. This message is typically displayed the second time you start a portable catalog. When the portable catalog opens, make your selections from the Packages and Bundles tabs, and then click Install.
Installing a package using the client catalog

The client catalog displays all software packages that a particular user has authority to access. When the user selects a software package, the client catalog displays detailed data about the package. If the package selected meets the user's requirements, the user clicks the Install button and the installation procedure starts automatically. Use the following steps to install packages from the Software Distribution Catalog: 1. Launch the Tivoli Provisioning Manager Express for Software Distribution client catalog using the steps described in 5.14.2, Accessing the catalog on page 221. 2. You can designate packages as mandatory. Mandatory packages are displayed in a separate window as shown in Figure 5-134. Select the Install Now drop-down menu to reveal if the installation can be deferred. Click OK after defining the appropriate action. The Software Distribution Catalog opens as Figure 5-115 on page 221 shows.
Figure 5-134 Mandatory Packages
236
3. Select a package or bundle to install. 4. Click the Details button to view any package-specific information or instructions prior to the installation. The Package Details page opens as shown in Figure 5-135. 5. Click Dismiss to close the Package Details window.
Figure 5-135 Package Details
6. When you are ready to install, click Install to start the installation process for the selected package. The Install In Progress area activates on the client applet as shown in Figure 5-136.
Figure 5-136 Install In Progress
As part of the installation process, you might be prompted to enter purchase order information. See Purchase orders on page 239.
237
7. A download window opens as the package is transferred to your system for installation as shown in Figure 5-137. The package installation process begins after a successful download of the package resource files.
Figure 5-137 Package file download progress
8. After the installation completes, the Install In Progress area returns to its original state, as shown in Figure 5-138, and the status changes to installed.
Figure 5-138 Install In Progress
9. Click Exit to close the Tivoli Provisioning Manager Express for Software Distribution client catalog.
238
Purchase orders
Certain packages require that a purchase order number is entered in order to allow the download. The purchase order number is used to verify that the user has the necessary approvals and licenses to install the application selected. When an application requires a purchase order number, the Purchase Order Entry window opens as shown in Figure 5-139.
Figure 5-139 Purchase Order Entry
Note the following fields and actions on the Purchase Order Entry window: Employee ID The companys assigned employee identification number for this software. This entry is case-sensitive. Purchase order The purchase order number that was received for the package. This entry is case-sensitive. This entry is verified against the information contained in the Tivoli Provisioning Manager Express for Software Distribution server to ensure the users eligibility to download. Check Inputs Click to validate the information entered. Continue Begins the installation process. Cancel Ends the purchase order entry process and displays the purchase order cancel window shown in Figure 5-140. If multiple packages were selected and a particular package did not require a purchase order, installation of that package begins now. Packages that required a purchase order number are not installed.
239
See Figure 5-140.
Figure 5-140 Cancel installation message
Click OK to return to the purchase order number window. If the purchase order number or employee ID for a package was entered incorrectly, you receive the error message shown in Figure 5-141.
Figure 5-141 Invalid information
Click OK to return to the purchase order number window.
5.15 Working with assets and user information

The IBM Tivoli Provisioning Manager Express for Software Distribution program comes with a built-in database. By default, the IBM Cloudscape database Version 5.1 provides several tables that can contain a variety of asset and user information. Understanding the information provided with this database can help you perform advanced functions such as exporting information from the database or creating a custom report. Although you primarily require to understand tables with asset and user information, internal system table information is also included. For more details refer to Version 4.1.1 - IBM Tivoli Provisioning Manager Express Administrators Guide, SC32-0172.
240
5.15.1 Assets and user information tables

The following information is provided to help understand the overall structure of the built-in database and to help understand how information is divided into each table. IBM Tivoli Provisioning Manager Express for Software Distribution keeps four scans of every agent in the database. When viewing the majority of reports, the SQL is constructed in such a manner so as to display the latest scan information. The column a.max_prozessed_revision=x.revision is, for example, to limit the information to the latest scan and contains a record of the number of scans performed on an agent. See Figure 5-142.
Figure 5-142 max_processed_revision column recording scans on agent
Note: The unique key that links Asset-related table is HWKEY and the User-related table is USERKEY.
241
5.15.2 Registering assets

There are three options available for adding an asset. Register new asset This is used to add the demographic details and scan the asset you are currently logged in to in the database. Ownership is assigned to the person currently logged in who is registering the asset. This allows for a possibility to register an agent to the database without installing an agent installer package or any of its components. Upload asset scan Uploading an asset scan allows you to either automatically scan and gather information about your computer or attach previously gathered information and send it to the database. An upload asset scan operation does not gather demographic information. Ownership of the Asset is assigned to the person currently logged in to the system, who is performing the Asset scan upload. Manually add asset Manually adding an asset requires filling out more detailed asset information and then directly submitting it to the database. When you manually add an asset to the database you can add assets other than the one on which you are working and assign ownership to specific users. You can manually register an asset.
Register new asset

To register a new asset, complete the following procedure: 1. In the IBM Tivoli Provisioning Manager Express for Software Distribution menu bar, click ASSETS. 2. Select New Register Asset. The Register Asset window opens. 3. Complete the fields by typing in the appropriate information, ensuring that all required fields (marked with a *) are complete. 4. Click Submit. A Please wait..... box opens. If you selected to inventory this machine, the message changes to sending results to server. The information is then sent to the database. 5. The My Assets screen is then displayed with the message that says that the file has been queued for processing.
242
See Figure 5-143.
Figure 5-143 Register a new asset window
Upload an asset scan

To upload an asset scan, complete the following procedure: 1. In the IBM Tivoli Provisioning Manager Express for Software Distribution menu bar, click ASSETS. 2. Select New Upload Asset Scan. The Upload Asset Scan window opens. 3. If a security warning is posted, click Yes. The security warning opens the first time you run IBM Tivoli Provisioning Manager Express for Software Distribution agent. 4. Mark one of the following options: If you want to have the existing machine inventoried, mark the Inventory this machine option button. If you want to attach an inventory file that is to be uploaded, then perform the following steps:
243
i. Mark the Attach an inventory file option button. Information is displayed asking you to Please select the inventory (.eg2) file below and then press. ii. Click Browse and locate the .EG2 file. iii. If you require to create an inventory file, click the here link in the displayed sentence that says To create an inventory file, download the Hardware scanning agent here and run it. Run the file and then attach the file. iv. Click Submit. 5. Click Submit. A Please wait.... box opens. If you selected to inventory this machine, the message changes to sending results to server. The information is then sent to the database. 6. The My Assets screen is then displayed with the message file has been queued for processing. See Figure 5-144.
Figure 5-144 Upload an asset scan window
244
Manually add an asset

To manually add an asset, complete the following procedure: 1. In the IBM Tivoli Provisioning Manager Express for Software Distribution menu bar, click ASSETS. 2. Select New Manually Add Asset. The Manually Add Asset window opens as shown in Figure 5-145. 3. Complete the fields by typing in the appropriate information, ensuring that all required fields (marked with a *) are complete. 4. Click Submit. A Please wait..... box opens. If you selected to inventory this machine, the message changes to sending results to server. The information is then sent to the database. 5. The My Assets screen is then displayed with a message that says that the file has been queued for processing.
Figure 5-145 Manually add an asset window
245
Register a remote asset uploading EG2 file

To gather information from a remote asset, complete the following procedure: 1. On the IBM Tivoli Provisioning Manager Express for Software Distribution server, using Windows Explorer(R), search for the file egather2.exe. Copy this file from the server to some form of removable media. For example, diskette or USB memory key. 2. Insert the removable media into the remote client. 3. Use Windows Explorer to browse the media and double-click egather2.exe. A DOS window opens as the system is scanned for critical hardware and software information. 4. After the scan is complete, an XXXX.EG2 file (where XXXX signifies a unique filename generated using the manufacturer, model, and serial number of the asset being scanned) is created on the removable media. Multiple assets can be scanned and the .EG2 files collected in this way. A typical .EG2 file is approximately 110KB. To load the gathered information files into the IBM Tivoli Provisioning Manager Express for Inventory system, two alternatives exist: You can upload the files via the Web interface (additional demographic information included). See Upload an asset scan on page 243. You can copy the files directly to the server and processed by executing a process files task (no demographic information included).
Uploading using the Web interface

If you upload using the Web interface, you can register the asset by providing the additional demographic information required for the asset. To upload using the Web interface, complete the following procedure: 1. On a system connected to the IBM Tivoli Provisioning Manager Express for Software Distribution network, insert the removable media containing the .EG2 files. 2. At the Login window, type your user ID and password. Click Logon. The My assets window opens. 3. In the IBM Tivoli Provisioning Manager Express for Software Distribution menu bar, click ASSETS. 4. Select New Upload Asset Scan. 5. Mark the Attach an inventory file option button. Then click the Browse button to select an .EG2 file from the removable media. 6. Click Submit. 7. Repeat steps 3 through 6 for additional .EG2 files.
246
Using the process files task

When using the task method, you can load .EG2 files from multiple assets into the IBM Tivoli Provisioning Manager Express for Software Distribution database. However, the required demographic information is not included. This process is useful for getting a large number of disconnected clients loaded into the database. To use the Process Files method, you must have Administrator authority to complete the following procedure: 1. At the IBM Tivoli Provisioning Manager Express for Software Distribution login window, type your Administrator user ID and Password. Click Submit. 2. Insert the media into the IBM Tivoli Provisioning Manager Express for Software Distribution Server. 3. Copy the gathered .EG2 file to the \gathered directory on the server. You can check for this path to the directory via the IBM Tivoli Provisioning Manager Express for Software Distribution properties file: a. In the IBM Tivoli Provisioning Manager Express for Software Distribution program menu bar select Admin. b. Select View properties file. c. In the Web Browser window, from the Edit pull-down, select Find. d. Search for the eg2.file.directory and this must have the path to the gathered directory next to it. 4. In the IBM Tivoli Provisioning Manager Express for Inventory menu bar, click Tasks and then select Process Files. 5. Click Process Files in the Configured Folder. This initiates a background process that registers the information from each of the .EG2 files found in the \gathered folder. 6. The following message is displayed on the screen: Processing task [ProcessFiles in Configured Folder] of type [GETFILES] as a background task using default criteria
247
248
Chapter 6.
Troubleshooting
This chapter discusses the information available for resolving problems with the application server, with a distribution, or with the client service. Also, you get the command line options for the eGather2 and callHome2 and there functions. This chapter includes the following topics: Server log information Server database information Client log information Enabling server debug mode Enabling agent debug mode Command line option eGather2 Command line option callHome2
249
6.1 Server log information

WebSphere Application Server - Express provides the activity logging for the IBM Tivoli Provisioning Manager Express for Software Distribution server. There are two major log files for application message logging: SystemErr.log SystemOut.log The logging information is available in the following location: C:\Program Files\IBM\Tivoli\TPMX\SERVER\ PROFILES\TPMXPROFILE\logs\TPMXSERVER Log4j.properties provides additional logging information. The levels of logging are in the order: ALL DEBUG INFO WARN ERROR FATAL OFF The major properties file where you can modify the logging is as follows: C:\Program Files\IBM\Tivoli\TPMX\SERVER\ TPMXAPP.ear\tpmx.war\WEB-INF\classes\log4j.properties The following attributes are the default settings: Default Log Level: INFO Default Location: C\:Program Files\IBM/Tivoli\TPMX\SERVER\tpmx.log
6.2 Server database information

T he IBM Cloudscape V 5.1 Database is provided with the WebSphere Application Server - Express. The database location is as follows: C:\Program Files\IBM\Tivoli\TPMX\SERVER\db\tpmxdb
250
The complete database structure and all of its sub contents is in the tpmxdb directory. You can copy it without stopping the service. The copied tpmxdb structure is useful to replicate problems from one server environment on to another. The copied tpmxdb structure is useful to synchronize IBM Tivoli Provisioning Manager Express for Software Distribution servers in a large IBM Tivoli Provisioning Manager Express for Software Distribution environment. It is good practice for you to periodically make a backup copy of the tpmxdb directory structure and also a way to restore the database if necessary. It may be used by support. The properties file to control the database logging level is in the following file: C:\Program Files\IBM\Tivoli\TPMX\SERVER\ TPMXAPP.ear\tpmx.war\cloudscape\db2j.properties Set the following property: db2j.stream.error.logSeverityLevel=0 Database access is restricted to a single user and you cannot access it while the service is running. After stopping the service or creating a copy, you can access the Cloudscape database using Cloudscape internal tools such as: IJ (command line interface to Cloudscape) CVIEW (CloudView, graphical interface to Cloudscape)
6.3 Client log information

On the client system, all startup and distribution event logs are recorded in the following directory: C:\Program Files\IBM\Tivoli\TPMX\Agent\logs The Software Distribution Agent startup, registration, and schedule distribution events are stored in sdcagent.log. There are three types of software distribution events that are stored in the sdcagent.log, which are as follows: startup registration schedule distribution
Chapter 6. Troubleshooting
251
The Software Distribution Catalog distribution events are stored in sdcclient.log. All distribution event logs are sent to the server and you can access them if you select Reports Distribution Reports View Logs. But only the distribution events from the current day are displayed.
6.4 Enabling server debug mode

WebSphere Application Server - Express provides Software Distribution server activity logging and is by default set to the INFO value. For more information about where to find the log files refer to the 6.1, Server log information on page 250. There are two ways for you to increase or decrease the server debug level. Refer to 4.1.5, The log4j.properties file on page 92 for more information regarding the log4j.properties file. 1. Modify the log4j.properties file directly: a. On the server system, using a text editor (such as Notepad) open: C:\Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\ WEB-INF\classes\log4j.properties b. Modify the following entry: log4j.logger.com.ibm=INFO Use one of the following values to modify the previously mentioned entry. They are in order of increasing debug level: OFF FATAL ERROR WARN INFO DEBUG ALL
252
2. Modify the debug level from the administrative console: a. Log in to the administrative console as shown in 5.1, Accessing the Administrative console on page 98. b. Click Admin Edit properties file. Figure 6-1 opens.
Figure 6-1 Properties files page.
253
c. Select the log4j.properties file from the pull-down menu. Figure 6-2 opens.
Figure 6-2 log4j.properties properties file
d. Modify the entry of log4j.logger.com.ibm with one of the following values. They are in order of increasing debug level: OFF FATAL ERROR WARN INFO DEBUG ALL
Restart the java application for the changes to take effect by selecting Admin Restart Application.
254
6.5 Enabling agent debug mode

To increase the amount of event logging on the IBM Tivoli Provisioning Manager Express for Software Distribution agent, you can enable the agent debug mode. Perform the following steps: 1. On the client system, using a text editor (such as Notepad) open: C:\Program Files\IBM\Tivoli\TPMX\Agent\sdc.conf 2. Add the following entry: com.ibm.sdc.agent.debug=true 3. Restart the service, IBM Tivoli Provisioning Manager Express - Software Distribution Agent.
6.6 Command line option eGather2

The eGather2 function performs the inventory scan, packs the data, and places it in a compressed file on the agent itself.
eGather2 options
The following are eGather2 options: -help Show this message. -batch Do not show the disclaimer. -silent Do not show anything during operation. -nolimit Collect the entire event log (default is last 500 entries). -step Single step through each of the probes. -debug Create a gatherer.log file in the current directory using: egather2 - debug;gatherer.log
255
-levelx Must be followed immediately by the number 1, 2, 3, 4, 5, or 6. This means that -level1 runs the fewest probes, while -level6 runs them all. To see which probes are run in each level use this parameter along with the -listprobes parameter egather2 -level4 -listprobes. -vpd Gathers only vital product data (VPD) information. This is the computer systems vendor, model, and serial number. For example, egather2 -batch -level0 -vpd. -stdout Information is displayed in the command prompt. Warning: It generates XML fragments, not a complete well-formed XML file. -filename Followed by a <filename>, it specifies the name of the eGatherer output file. -text Causes eGatherer to use a text encoding for the data rather than XML. The resultant output file uses the suffix of .GTH rather than the suffix of .EG2. -local Causes eGatherer not to compress the output file. Therefore, you can view the output file locally without the requirement to upload it to the Web site in XML format. -html Causes eGatherer to produce an uncompressed HTML file. -listprobes Lists all the available probes. -probes/ -probe Allows individual probes or a subset of the probes to be executed. Use the -listprobes parameter to obtain the list of valid probe names. -skip Allows the bypass of probes that may be superfluous or causing a problem on a particular machine. -enable Enables the execution of certain probes not enabled by default.
256
-p Used to pass additional probe specific parameters, such as -p probe_name <parameters list>. For example: -p filescan path=C:\;D:\ filter=*.exe;*.doc version=* -install/ -uninstall Installs and removes the eGatherer driver. This is provided to allow the computers administrator or a power user to install the driver, so that a user with less system privileges can run eGatherer.
Examples
The following are some examples of using egather2. Example 6-1 shows the use of eGather2 -listprobes to list all available probes.
Example 6-1 eGather2 -listprobes to list all available probes
C:\Program Files\IBM\Tivoli\TPMX\Agent>egather2 -listprobes SYSTEM_SUMMARY GATHERER_INFORMATION TIME_ZONE SCSI_DEVICES IDE_DEVICE_INFORMATION MICROSOFT_CLUSTER_SERVER SMBIOS_INFORMATION REGIONAL_SETTINGS LOGICAL_DISK_INFORMATION DISPLAY_INFORMATION WINDOWS_STARTUP_INFORMATION DEVICE_DRIVERS_AND_SERVICES LIST_OF_RUNNING_PROCESSES SERVICE_PROCESSOR_INFORMATION IBM_SSA_STORAGE MEMORY_INFORMATION PCI_DEVICES PCI_ADAPTER_INFORMATION WORKSTATION_SECURITY BROWSER_INFORMATION FILESCAN INSTALLED_SOFTWARE NETWORK SECURITY_SOFTWARE IBM_NETFINITY_FIBRE_CHANNEL_STORAGE DEVICE_MANAGER ASSETID ENVIRONMENT
257
FIRMWARE_INFORMATION LOTUS_NOTES PRINTERS SYSTEM_EVENTS_LOG IBM_TVT_USAGE IBM_LOG_FILES DEMOGRAPHICS NT_APPLICATION_EVENT_LOG NT_SYSTEM_EVENT_LOG NT_SECURITY_EVENT_LOG C:\Program Files\IBM\Tivoli\TPMX\Agent> Example 6-2 shows the use of eGather2 -level 1 running eGather2 with only the level 1 probes.
Example 6-2 eGather2 -level 1 runs eGather2 with only the level 1 probes
C:\Program Files\IBM\Tivoli\TPMX\Agent>egather2 -level1 IBM Tivoli Provisioning Manager Express - Information Gatherer Version 2.44.0282.0 Server Edition Licensed Materials - Property Of IBM 5724-N88 3787-11Z (C) Copyright IBM Corp. 2000, 2006 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Install Driver ......................... Create XML Output File ................. Create Gatherer File ................... SYSTEM SUMMARY ......................... GATHERER INFORMATION ................... SMBIOS INFORMATION ..................... WORKSTATION SECURITY ................... BROWSER INFORMATION .................... NETWORK ................................ Security Software ...................... ASSETID ................................ PRINTERS ............................... Gathering plug-in output files ......... OK OK OK OK OK OK OK OK OK OK Not found OK Directory not found
258
Close XML Output File .................. OK Close Gatherer File .................... IBM-8305K8U-KLCHM8L.EG2 Remove Driver .......................... OK Run complete, rc = 0 C:\Program Files\IBM\Tivoli\TPMX\Agent> Example 6-3 shows eGather2 -silent run eGather2 in silent mode, without output.
Example 6-3 eGather2 -silent run eGather2 in silent mode without output
C:\Program Files\IBM\Tivoli\TPMX\Agent>egather2 -silent C:\Program Files\IBM\Tivoli\TPMX\Agent>
6.7 Command line option callHome2

The callHome2 function is to call the eGather2 function and upload the scanned data to the IBM Tivoli Provisioning Manager Express for Software Distribution server. The following are callHome2 options: -debug Turns on debugging. For example, callhome2 reload debug;callhome.txt. -scanstale Forces an immediate upload. For example, callhome2 scanstale. -1minute Waits for 1 minute to run the upload. For example, callhome2 1minute. -nodebug Turns debugging back off. For example, callhome2 reload nodebug. -reload Reruns callhome2. For example, callhome2 reload. -status Checks for the status. Compares date and time of Callhome Tries and Callhomes Completed. Check scans completed date and time. For example, callhome2 status. -now Override the scheduler by forcing an immediate callhome. For example, callhome2 now.
259
-install Installs the callHome2 URL. For example, callhome2 install http://TPMXServer:80/tpmx/callHome. -uninstall Uninstalls the callHome2 URL. For example, callhome2 uninstall. Note: CallHome2 runs as a service and communicates regularly with the IBM Tivoli Provisioning Manager Express for Software Distribution server to determine if an asset scan is required. If the communication fails with the IBM Tivoli Provisioning Manager Express for Software Distribution server, the callHome2 tries again in an hour.
Examples
The following are some examples of using CallHome2. Example 6-4 shows the use of option callHome2 -1minute.
Example 6-4 callHome2 -1minute to wait one minute to run the upload
C:\Program Files\IBM\Tivoli\TPMX\Agent>callhome2 -1minute CALLHOME2.EXE - Tivoli Provisioning Manager Express - Scheduling Agent Licensed Materials - Property Of IBM 5724-N88 3787-11Z (C) Copyright IBM Corp. 2004, 2006 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Version 3.17 **** Debug is ON **** Time was set to 14:49 Time is now set to 14:50 C:\Program Files\IBM\Tivoli\TPMX\Agent>
260
Example 6-5 shows the use of option callHome2 -reload -debug. The output file is callhome.txt.
Example 6-5 callHome2 -reload -debug turns debugging on
C:\Program Files\IBM\Tivoli\TPMX\Agent>callhome2 -reload -debug CALLHOME2.EXE - Tivoli Provisioning Manager Express - Scheduling Agent Licensed Materials - Property Of IBM 5724-N88 3787-11Z (C) Copyright IBM Corp. 2004, 2006 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Version 3.17 **** Debug is ON **** C:\Program Files\IBM\Tivoli\TPMX\Agent> Example 6-6 shows the use of option callHome2 -status.
Example 6-6 callHome2 -status to see the status of the uploads
C:\Program Files\IBM\Tivoli\TPMX\Agent>callhome2 -status CALLHOME2.EXE - Tivoli Provisioning Manager Express - Scheduling Agent Licensed Materials - Property Of IBM 5724-N88 3787-11Z (C) Copyright IBM Corp. 2004, 2006 All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Version 3.17 Scheduler Service Status: Unknown Scheduler Service Path: 'Unknown' Scheduler Service Startup: Unknown Callhome Time is 14:19 Callhome URL is 'http://klchm8l:80/tpmx/callHome' Callhome Proxy is ''
261
Install Date: This Service Start: Callhome Tries: 0040 Callhomes Completed: 0005 Scans Completed: 0001
Tue Tue Last: Mon Last: Fri Last: Tue
Aug Aug Aug Aug Aug
01 01 07 04 01
15:00:04 15:00:04 14:36:06 14:18:00 15:36:23
2006 2006 2006 2006 2006
C:\Program Files\IBM\Tivoli\TPMX\Agent>
262
Chapter 7.
Maintenance
As with any software product, over time, it becomes necessary to apply maintenance to the installed server and agents. This chapter provides information about how to maintain the IBM Tivoli Provisioning Manager Express for Software Distribution environment. The following topics discuss how to apply patches to IBM Tivoli Provisioning Manager Express for Software Distribution: Identifying a requirement to apply a patch or an upgrade Retrieving patch or upgrade Applying patches or upgrades Verifying functionality
263
7.1 Identifying a requirement to apply a patch or an upgrade

In general, there are two reasons to apply patches: 1. If there are problems with the running system and a patch fixes these problems. 2. If a patch has been released that prevents problems from happening. The same reasons exist for upgrades. In addition, the reason of addition of significant functionality enhancements plays a role. The IBM Tivoli Provisioning Manager Express for Software Distribution is a bundled system which contains Java Runtime, WebSphere Express, and Cloudscape database. Any patches or upgrades must be for the entire bundled product. Do not attempt to apply patches that are intended for the individual products.
7.2 Retrieving patch or upgrade

Patches or upgrades are available from the IBM support site on the Web at: http://www.ibm.com/support Select the product name, and a list of available patches and upgrades open. If you know exactly what to look for, you may also go directly to the ftp site at: ftp://ftp.software.ibm.com From here, navigate to /software/tivoli_support/patches/patches_4.1.1.0 to find the patches that are specific to this version. Make sure to read the documentation associated with the upgrade or patch. The readme file contains information about installation, and fixes and enhancements are included. There may also be specific prerequisites.
264
7.3 Applying patches or upgrades

After the patch or upgrade has been retrieved and unpacked, you must apply it to a test system. Here, you must verify all basic system functionalities. Even if the patch has been tested thoroughly from IBM, your specific environment may have dependencies that the development team cannot take into their consideration. Therefore, always verify the patch or upgrade on a test server. After the verification is complete, the production system is next. The production system may require additional planning and information because it affects end users. Before you apply a patch, you must bring the Tivoli Provisioning Manager server into a mode where no changes can take place. Make sure no distributions are in the queue and that no administrators schedule new distributions because the administrators may be unaware that there is an upgrade taking place. It is also good to backup the IBM Tivoli Provisioning Manager Express for Software Distribution database and package repository. See Database on page 13 and 5.14.3, Creating a portable catalog, exporting and importing libraries between two servers on page 223 for further information. Run the setup program that comprises of the patch or upgrade. The setup program verifies the server installation, stops the server service, applies the update, and restarts the service. Unless specifically mentioned in the readme file or during the upgrade, there is no requirement to restart the operating system. Any connections to the server are disconnected, which means that end users and administrators require to log in again to continue their work.
7.4 Verifying functionality

After the patch or upgrade has been completed, you must verify that the basic functionalities of the server are working. This must include some of the following: Verify that the IBM Tivoli Provisioning Manager Express for Software Distribution patch is applied. Verify that the software catalog (from the server) is accessible. Log in to the catalog to verify whether the software packages are available and whether the installed packages are properly identified.
Chapter 7. Maintenance
265
Verify that the Assets console is accessible. Log in to the Manage assets console. Verify that the assets database is intact and that the database connectivity is working by viewing all assets. Select Assets from the menu, then All assets. Verify that the scheduler is working, for example, you can create a new schedule to distribute a software package to a single PC. Verify the server status. From the Admin menu, select View Current Server Status.
266
Chapter 8.
Sample Certification Test questions

This chapter provides some sample questions for the Certification Test. These are representative of the questions that you can see in the Certification Test. We recommend that you take this sample test after studying the previous chapters in this book.
267
8.1 Sample questions

The following are some sample questions with multiple choice answers from which you have to select the correct option: 1. When you log in to the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console, what is the default user name and password? a. b. c. d. Administrator; password Admin; password Admin; pswd Administrator; password
2. What is the process to download IBM Tivoli Provisioning Manager Express for Software Distribution agent through the Manage Your Assets part of the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console? a. b. c. d. Click Users Software Catalog Group Download Agent Installer. Click Software Packages Download Agent Installer. Click Asset Download Agent Installer. Click Software Download Agent Installer.
3. If you have a large customer environment of 10,000 agents. What can you do to manage these large number of agents using IBM Tivoli Provisioning Manager Express for Software Distribution? Choose any two options. a. Use multiple installations of IBM Tivoli Provisioning Manager Express for Software Distribution server. Then, use the import/export function to synchronize the metadata associated with software packages and bundles from one server to another. b. You require to use a database, other than the default Cloudscape database that is shipped with the product. We recommend DB2. c. Use multiple installations of IBM Tivoli Provisioning Manager Express for Software Distribution server. Use the server-to-server copy function to synchronize the metadata associated with software packages and bundles from one server to another. d. Use multiple IBM Tivoli Provisioning Manager Express for Software Distribution servers and a load balancer in front to provide load balancing among several Web servers. Customization is required on the server side, so that only one instance of the Software Distribution database exists. Also, you require to use a database, other than the default Cloudscape database that is shipped with the product. We recommend DB2.
268
e. Use multiple IBM Tivoli Provisioning Manager Express for Software Distribution servers and a load balancer in front to provide load balancing among several Web servers. Customization is required on the server side, so that only one instance of the Software Distribution database exists. Also, you require to use a database, other than the default Cloudscape database that is shipped with the product. We recommend an SQL Server database. 4. Which is the supported communication protocol for an IBM Tivoli Provisioning Manager Express for Software Distribution administrative console to communicate with the IBM Tivoli Provisioning Manager Express for Software Distribution server. a. b. c. d. HTTP and HTTPS JDBC HTTP UDP
5. What is the recommended system hardware platform for the load balancer for large IBM Tivoli Provisioning Manager Express for Software Distribution environments? a. b. c. d. IBM eServer xSeries 460 Dual IBM POWER5 technology-based processors IBM Bladecenter IBM eServer iSeries with IBM i5/OS on it
6. When you are installing an IBM Tivoli Provisioning Manager Express for Software Distribution server, an installation prompt opens for you to decide if the password change to a user can be operated by user/superuser/administrator. Who is allowed this operation by default? a. b. c. d. User/superuser User Admin Admin/superuser
7. Which are the three methods to install an IBM Tivoli Provisioning Manager Express for Software Distribution agent? a. CD installation, Web installation, unattended installation b. CD/Web attended installation, temporary installation, CD/Web unattended installation c. Attended installation, unattended installation d. Temporary installation, unattended installation, CD installation
Chapter 8. Sample Certification Test questions
269
8. Is it possible to install an IBM Tivoli Provisioning Manager Express for Software Distribution server while having an IBM Tivoli Provisioning Manager Express for an Inventory server already installed? a. b. c. d. Yes, it is No, it isnt Probably yes Yes, only if the installation is an upgrade installation
9. Which is the default callback interval that an IBM Tivoli Provisioning Manager Express for Software Distribution agent uses to communicate with the server? a. b. c. d. 90 min 30 min 10 min 60 min
10.What kinds of targets are supported by IBM Tivoli Provisioning Manager Express for Software Distribution package distribution? a. b. c. d. Windows all, UNIX all, Linux all Windows 2000/2003/XP/9x AIX 5.3, Linux Fedora Core 4, Windows XP Only FreeBSD Unix
11.After collecting the data from the computer, the IBM Tivoli Provisioning Manager Express for Inventory program creates a file with all the information in it. What does this file contain? Choose any two options. a. b. c. d. e. Serial number Processor type and speed Type and model Location Installed software
12.What are the three type of user accounts in the Action Authority Settings window when installing IBM Tivoli Provisioning Manager Express for Software Distribution in custom mode? a. b. c. d. All Users, Super User and Admin, Admin only All Users, Super User, Admin only Users only, Super User only, Admin only Users, Super User, Admin
270
13.Which of the following information is relevant for you to gather prior to an IBM Tivoli Provisioning Manager Express for Software Distribution server installation? Choose any two options. a. License key for IBM Tivoli Provisioning Manager Express for Software Distribution server b. Host name of the IBM Tivoli Provisioning Manager Express for Software Distribution server c. Simple Mail Transfer Protocol (SMTP) server name d. Type and model of the IBM Tivoli Provisioning Manager Express for Software Distribution server e. Serial number of the IBM Tivoli Provisioning Manager Express for Software Distribution server 14.What kind of third party packaging tools does the IBM Tivoli Provisioning Manager Express for Software Distribution support? a. Microsoft (R) Software Installer (MSI) & InstallShield b. Microsoft (R) Software Installer (MSI) & WinZip Self-Extractor c. Microsoft (R) Software Installer (MSI), InstallShield, WinZip Self-Extractor, Wise InstallManager d. Microsoft (R) Software Installer (MSI) only 15.What does the term Logical Drive stand for, when creating a new software distribution package using IBM Tivoli Provisioning Manager Express for Software Distribution administrative console? a. An unpackaged set of files and folders that are stored on the IBM Tivoli Provisioning Manager Express for Software Distribution server b. A package created by a third party packaging tool that is not stored on the IBM Tivoli Provisioning Manager Express for Software Distribution server c. A package created by a third party packaging tool that is stored on the IBM Tivoli Provisioning Manager Express for Software Distribution server d. A package created by a third party packaging tool that is not stored on the IBM Tivoli Provisioning Manager Express for Software Distribution server e. A package created by third party packaging tool that is identified by a digital signature
271
16.What is the meaning of Secure mode in the install tab of package management using the IBM Tivoli Provisioning Manager Express for Software Distribution administrative console? a. The IBM Tivoli Provisioning Manager Express for Software Distribution server distribute the package using Secure Shell (SSH) protocols. b. The communication from IBM Tivoli Provisioning Manager Express for Software Distribution server agent to server is encrypted. c. Where users run as restricted users and do not have the system authorization to perform the software installation, IBM Tivoli Provisioning Manager Express for Software Distribution has the ability to perform the installation with a system account. d. The server and the agent cannot communicate. 17.When installing an agent in unattended mode, what does the parameter SWD_USER_MGMT_ENABLED mean? a. The time, in minutes, between checks for scheduled distributions b. Enabling or disabling functions in the user interface to create users and change passwords c. For debugging only. Set to 1 to tell callHome2 to write debug info to callHome2.txt. d. The user ID management, if the proxy requires authentication 18.What is the standard server port that installs the IBM Tivoli Provisioning Manager Express for Software Distribution server? a. b. c. d. 8080 25 80 2525
19.Is there a method to deliver an sdc.conf configuration file to all of the agents from the server? a. Yes, copy a predefined sdc.conf file to the folder IBM Tivoli Provisioning Manager Express for Software Distribution home path. b. Yes, use the server to server copy menu function. c. Yes, copying a predefined sdc.conf file to the folder IBM Tivoli Provisioning Manager Express for Software Distribution home path\TPMXAPP.ear\tpmx.war\apps. d. Yes, use the server to agent copy menu function.
272
20.What are two benefits and features using IBM Tivoli Provisioning Manager Express for Software Distribution? Choose any two options. a. b. c. d. e. Its ease of integration into the enterprise environment Its ease of integration into IBM Tivoli Enterprise Console Its ease of integration into IBM Tivoli Configuration Manager 4.2.3 Its ease of installing the product Its ease of integration into Tivoli Framework
Answers
The following are the correct answer choices to the sample questions: 1. b 2. c 3. a,d 4. c 5. b 6. c 7. a 8. b 9. d 10.b 11.b,e 12.a 13.b,c 14.c 15.b 16.c 17.b 18.c 19.c 20.a,d
273
274
Appendix A.
Sample folder structure

This appendix discusses theTivoli Provisioning Manager Express for Software Distribution server folder structure and shows a sample file structure. This appendix provides three folder structures as samples that you can use as a reference to set up a folder structure on your Tivoli Provisioning Manager Express for Software Distribution server. All software packages, detail files, and icon files stored on the Tivoli Provisioning Manager Express for Software Distribution server must be stored under the document root, which by default is as follows: C:\ProgramFiles\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war The document root on your server may be different, depending on the options you chose during installation. All sample folder structures in this appendix show the default document root. The folder structure you implement is entirely up to you, as long as it resides under the document root. You can organize your files by operating system, type of application, or any other characteristic that meets the requirements of your organization.
275
Figure A-1 is a sample that shows the use of separate folders for software packages, detail files, and icon files.
Figure A-1 Separate folders for software packages
276
Figure A-2 is a sample that shows a folder for each software package, each containing the package file, the details file, and the icon file.
Figure A-2 Single folder for software packages
Appendix A. Sample folder structure
277
Figure A-3 shows separate folders for each operating system, under which are folders for each software package that you can use for that operating system. The COMMON folder shown, contains folders for software packages that you can install on either Microsoft Windows XP or Windows 2000.
Figure A-3 Separate folders for each operating system
278
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this IBM Redbook.
IBM Redbooks
For further information about ordering these publications, refer to How to get IBM Redbooks on page 280. Note that some of the documents referenced here may be available in softcopy only. Some IBM publications that you can refer to are as follows: Deployment Guide Series: IBM Tivoli Provisioning Manager Express V4.1 for Software Distribution, SG24-7236
Other publications
These publications are also relevant as further information sources: IBM Tivoli Provisioning Manager Express Administrators Guide, SC32-0172 IBM Tivoli Provisioning Manager Express for Software Distribution Client Catalog User's Guide, SC32-0173 IBM Tivoli Provisioning Manager Express for Inventory Users Guide, SC32-0174 IBM Tivoli Provisioning Manager Express Installation Guide, SC32-0175
Online resources
These Web sites and URLs are also relevant as further information sources: Online publications link to Tivoli Provisioning Manager Express for Software Distribution V4.1 manuals: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc =/com.ibm.itpmesd.doc/toc.xml The IBM Professional Certification Program Web site: http://www.ibm.com/certify/index.shtml
279
IBM support and download site: http://www.ibm.com/support The Apache project Web site: http://logging.apache.org/log4j/docs
How to get IBM Redbooks

You can search for, view, or download IBM Redbooks, Redpapers, Hints and Tips, draft publications, and additional materials, as well as, order hardcopy IBM Redbooks or CD-ROMs, at this Web site: ibm.com/redbooks
Help from IBM

IBM Support and downloads ibm.com/support IBM Global Services ibm.com/services
280
Certification Guide Series: IBM Tivoli Provisioning Manager Express for Software Distribution
Index
Symbols
.gif 120 .jpg 120 .msi executable 118 Asset Demographics Form 32 asset information tables 241 asset scan 32 asset.keep.baseline 69 asset.revisions 69 assettag 66 authentication.LDAP 54, 83 authentication.LDAP.config 54, 83 authority roles 28 auto-update 95
A
accessing the administrative console 98 Action Authority Settings 28 adding the software package 124 administrative console 34 administrator e-mail address 26 agent installation advanced setup 38 command line properties 44 CALLHOME_DEBUG 44 CALLHOME_WINDOW_END 44 CALLHOME_WINDOW_START 44 PROXY_AUTH_B64 44 PROXY_HOSTNAME 44 PROXY_PASSWORD 44 PROXY_PORT 44 PROXY_USER_ID 44 SERVER_CONTEXT 44 SERVER_HOSTNAME 44 SERVER_PORT 44 SWD_REFRESH_INTERVAL 44 SWD_USER_MGMT_ENABLED 44 Destination Folder window 38 Proxy Settings window 39 Scheduler Settings window 40 Server Address window 38 typical 37 unattended command line 43 verifying 40 alternate http server 96 Apache project 93, 280 app.antivirus.name.x 77 app.antivirus.ver.x 77 app.firewall.name.x 77 app.firewall.ver.x 77 applet 14, 218, 222 application log file 36 applying patches 264
B
background process 183 bundle ID 200
C
callhome.file.directory 80 callHome2 function 16, 259 catalog accessing 221 creating 223 exporting 231 installing a package using the catalog 236 overview 219 previewing 235 certification benefits 3 certificate 7 checklist 5 IBM Professional Certification Program 2 process 7 Tivoli Certification 4 client catalog 219 Cloudscape 240, 250 code 15T890 8 collect inventory data 36 com.ibm.sdc.agent.clientHost 96 com.ibm.sdc.agent.debug 94 com.ibm.sdc.agent.offset 94 com.ibm.sdc.client.bundlesEnabled 95 com.ibm.sdc.client.downloadURL 96 com.ibm.sdc.client.logfile 94 com.ibm.sdc.client.login 96
281
com.ibm.sdc.client.password 96 com.ibm.sdc.client.userMgmtEnabled 95 com.ibm.sdc.server.host 94 com.ibm.sdc.server.port 94 com.ibm.sdc.server.protocol 94 common.properties file 54 communication protocols 17 courses 9 creating the source files 118 details file 118 icon file 118 source software package file 118 CurrentControlSet 120 custom report 216 customization considerations 19
D
dbcleaner.frequency 71 dbcleaner.launch.on.startup 71 dbleaner.interval.period 72 default server port 37 detail files 276 details file 120 device drivers 15 digital certificate 146 DirectoryDownload 194 DirectoryDownload package type 119 DirectoryDownload(Open) 194 DirectoryDownload(Secure) 194 dirFTP.threshold 83 distribution lists 161 adding 163 deleting 166 information 162 modifying 169 searching 167 searching for a machine 169 DNS suffix-list 59 document root 275 Download(Open) 194 Download(Secure) 194
eGather2 options 255 e-mail settings 26 email.admin 61 email.delete.other.email 79 email.delete.processed.email 79 email.enabled 59 email.file.send.receipt 79 email.from 61 email.receive.enabled 78 email.spam.filter 79 Enable Network Speed Detection 145 Enable Process Tracking 141 encrypt password 30 encrypted password utility 87 evaluation.lastRun.offset 85 evaluations 174 adding 174 deleting 179 searching 180 updating 182 everyoneincludesanonymous 122 expire.new.password 73 export.data.directory 65
F
file shares 96 file.email.encoding 60 file.email.mime.type 60 file.email.name 60 file.email.type 60 file.export.encoding 65 file.export.type 65 file.upload.directory 66 file.upload.password 66 filescan data 63 fileshare 96 FileStore table 184 firewall 16 folder structure 118, 275 Form Settings window 32 fully qualified domain name 25
E
eg.demographics.fields 68 eg.fields 68 eg2.file.delete 65 eg2.file.directory 65 eGather2 function 16
G
gatherer.log 255 groups adding 107 changing the description 111 deleting 109
282
updating user information 112
H
hdd.password.required 76
I
IBM AIX 5L V5.1 21 IBM Certification Agreement 6 IBM Cloudscape database 240 IBM POWER5 technology 21 IBM Professional Certification mark 7 IBM Tivoli Provisioning Manager Express for Software Distribution administration 97 apply a patch 264 applying patches 264 common.properties 54 components agent 14 database 13 inventory 15 server 12 configuration 51 configuring the agents 93 courses 9 customization considerations 19 deployment considerations 16 hardware and software specifications 20 large environments 19 non-IBM systems 15 small and medium environments 18 installation 23 agent installation 36 server installation 24 isic.properties 58 ldap.properties 85 Linux support 21 log4j.properties 92 maintenance 263 publication 9 recommended resources for study 8 Redbooks 10 retrieve patch 264 sample folder structure 275 sdc.properties 81 troubleshooting 249 verify functionality 265 IBM WebSphere Application Server 12
IBM WebSphere Edge Server 19 icon file 120, 276 installed software 15 installing agent 36 server 25 verifying the WebSphere service 35, 46, 49 installing agent destination folder 38 proxy settings 38 scheduler settings 38 server address 38 InstallShield 118 inventory component admin 183 callHome2 259 eGather2 255 eGather2 options 255 troubleshooting 255 working with assets 240 inventory functions 28 inventory scan 255 isic properties database cleanup properties 71 isic.properties 58 asset registration properties 74 e-mail engine properties 77 password properties 72 schedules 69 security policy properties 75 system maintenance properties 80 isic.properties file 183 isic.properties, authority parameters 67
J
Java Database Connectivity (JDBC) 18 Java J2SE SDK/Runtime 20 Java Vendor 199 Java Version 199 Java Web Start applet 218219 Java WebStart application 14
L
lanmanserver 120 LDAP (Lightweight Directory Access Protocol) 17 LDAP search filter 89 ldap.alternateURL 87 ldap.connectionName 86
Index
283
ldap.connectionPassword 86 ldap.connectionPasswordEncrypted 87 ldap.connectionURL 87 ldap.debug 87 ldap.digest 90 ldap.groupBase 88 ldap.groupDescription 88 ldap.groupName 88 ldap.groupNameTrim 88 ldap.groupSearch 89 ldap.groupSubtree 89 ldap.principalPattern 90 ldap.properties basic LDAP configuration 86 group data 88 user authentication 89 ldap.properties file 85 ldap.userBase 91 ldap.userEmail 90 ldap.userGroupName 90 ldap.userPassword 90 ldap.userPattern 91 ldap.userRealm 90 ldap.userRoleBase 90 ldap.userRoleName 90 ldap.userRoleSearch 90 ldap.userRoleSubtree 90 ldap.userSearch 91 ldap.userSubtree 91 Linux support 21 load balancer 21 localhost 59 log4j.properties file 92 logical disk information 15 LogicalDrive package type 138 LogicalDrive(Secure) 194 LogicalDrive(Secure) packages 120 logon.newuser 72 logs 12, 93, 199
distribution lists 161 evaluations 174 logs 199 machines 171 packages 117 purchase orders 156 schedules 191 software bundles 147 tasks 183 user groups 107 user ID 100 mandatory packages 236 master.server.address 80 match.on.assettag 66 match.on.computername.if.valid.serial.or.uuid.stored 66 max.keys 67 memory size 15 message digest algorithm 90 metadata 19 Microsoft Active Directory 17 Microsoft Software Installer (MSI) 118 msiexec 118119 multipackage installation 145
N
network bandwidth 14 network interface cards (NICs) 20 network speed allowed 145
O
online catalog 14 operating system information 15 OutputXML 228
P
package ID 200 package types DirectoryDownload(Open) 194 DirectoryDownload(Secure) 194 Download(Open) 194 Download(Secure) 194 LogicalDrive(Open) 194 LogicalDrive(Secure) 194 packages 117 adding 124125 creating 117
M
machines 171 deleting 171 searching 172 maintenance 263 managing catalogs 218 database 240
284
deleting 131 searching 133 packaging tools 118 Part Number 144 password 25, 2728, 30, 100 Password Control Settings 30 Password Creation Rules 31 Password Settings window 30 password.check 73 password.encrypt 73 password.max.length 74 password.max.matching.sequential.chars 74 password.max.previous.chars 74 password.min.length 74 password.must.have.non.alphanumeric 74 password.must.have.non.numeric 73 password.must.have.numeric 73 password.period 73 password.reuse 73 password.timeout 73 password.timeout.period 73 Pearson Virtual University Enterprises 6 planning 11 pop3 accounts 78 pop3.inbox.x 78 pop3.password.x 78 pop3.server.x 78 pop3.userid.x 78 portable catalog 223 creating 223 using 235 post-install program 145 post-requisite conditions 145 power.on.password.required 76 preinstall program 145 prerequired program 145 printstamp.jar 143 probe properties 68 Process Files in Configured Folder 65 properties.backup.archive 54 proxy server 16 publications 9 purchase order management 82 purchase orders 156 adding 156 deleting 158 searching 158 updating 160 purchase.autoupdate 82
purchase.autoupdate.offset 82 purchase.autoupdate.path 82 purchase.autoupdate.seperator 82
Q
query.max.results 67
R
recertification 7 Redbooks Web site 280 Contact us xx regedit 141 regional settings 15 Registry Editor window 141 RegKey 141 remote file shares 14 Remove Directory After Install 141 restrictanonymous 121 retrieve patch 264 return on investment (ROI) 5 rpm 139
S
sample/assessment test 6 save.file.use.gzip.compression 64 schedule name 200 scheduled.demographics.check.interval 70 scheduled.interval 70 scheduled.interval.period 70 scheduled.launch.on.startup 70 scheduled.task.period 70 scheduled.update.demographics 70 scheduled.upload 69 scheduled.upload.interval 70 scheduled.upload.queue.lookup.threshold 70 scheduled.upload.queue.threshold 70 scheduler.use.queue 70 schedules 191 adding 194 deleting 199 searching 197 Scheduling window 29 sdc.conf 93, 95 sdc.properties directory download 83 machine identification key 84 purchase order management 82
Index
285
sdc.properties file 81, 157 sdcagent.log 251 sdcclient.jsp 94 sdcclient.log 252 SDClocal.conf 93, 95 search.limit.results 67 secure package 146 Security Settings window 33 serialised.queue.object 80 Server (Web) URL 26 server context 38 server installation 24 custom 25 e-mail settings window 26 tasks 24 typical 25 uninstalling 45 verification 34 Web site settings window 25 server name 25 server port 25 server properties files 52 server.log.max.age 72 servlet 80 SHA (Secure Hash Algorithm) 73 show command 141 Simple Mail Transfer Protocol (SMTP) 27 SMTP password 27 smtp server 59 smtp.authentication 59 smtp.password 59 smtp.server 59 smtp.userid 59 software bundle adding 147 creating 147 definition information 154 deleting 131, 151 searching 133, 152 updating the information 154 Software Distribution agent 14 catalog 14, 107 database 19 library 124 log 200 software package 276 adding 124 definition information 136
deleting 131, 151 searching 133, 152 updating the information 135 source files 118, 123 source software package file 118 spam filter 79 SplashMessage 85 SQL-compliant database 20 stamp file 212 Stamp File Date 143 Stamp File Mode 143 Stamp Mode 143 standard report 216 storing the source files 123 subnet 20 swl.sigenabled 80 syslog file 63 SystemErr.log 250 SystemOut.log 250
T
Task Scheduler 190 task types Checkprocessed 184 Checksecurity 184 Checksoftwarelicence 184 Csv_file 184 e-mail 183 Filescan 184 Getemail 183 Getfiles 183 Logreports 183 Proceslatest 184 Processal 184 Processlog 183 Rechecksecurity 184 Reprocessall 184 Swlicences 185 Syncmasterdata 185 task.log.max.age 72 task.process.files.max.queue.length 71 task.process.filescan.max.queue.length 71 task.process.software.security.length 71 task.process.xml.max.queue.length 71 task.use.other.threads.queue.limit 63 tasks 183 adding 185 deleting 187
286
managing 183 running 190 scheduling 191 Task Scheduler 191 updating 188 Thomson Prometric 6 Tivoli environment 5 software education 9 Software Professional Certification 4 Tivoli Certification benefits 5 how to get? 4 Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification 8 tpmxsd_setup.exe 48 transaction ID 200 tx.log.max.age 72
upload.save.userxml 63 upload.save.xmlfile 63 upload.send.receipt 64 upload.store.user.history 63 upload_history table 63 uploading asset scans 26 url 61 USB memory stick 22 user demographics compliance 55 User Demographics Form 32 user information tables 241 user.access.max.age 72 USERKEY 241 users adding 101 modifying group membership 105 searching 104 updating user information 106 UUID 199
U
uninstalling agent 47 tpmxsd_setup.exe 48 using the Add/Remove program using the maintenance program verifying 49 server 45 using the Add/Remove program using the maintenance program verifying 46 update.client.files 69, 80 update.server.files 80 upload.autoqueue.process.filescan.task upload.autoqueue.process.xml.task 63 upload.delete.after.forward 79 upload.delete.after.receipt 79 upload.email.forward 64 upload.email.forward.address 79 upload.process.filescan 63 upload.process.filescan.max.queue 63 upload.process.xml 62 upload.process.xml.max.queue 62 upload.save.applog 63 upload.save.attachments 63 upload.save.eg2file 63 upload.save.filescan 63 upload.save.seclog 63 upload.save.syslog 63
V
vbs 139 48 47
W
Web-based courses 8 WebSphere service 35 win.file.sharing 76 win.gina.dll 76 win.gina.version 76 win.max.pw.age 76 win.min.pw.length 76 win.password 76 win.screensaver 76 Windows RegKey 141 Windows RegKey field 142 WinZip Self-Extractor 118 Wise InstallManager 118
46 45
63
X
XML data 62, 184
Index
287
288
(0.5 spine) 0.475<->0.875 250 <-> 459 pages
Back cover
Certification Guide Series

IBM Tivoli Provisioning Manager Express for Software Distribution V4.1
Helps you become a certified Tivoli Provisioning Manager Express Explains the certification path and prerequisites you require Includes best practices for Software Distribution
This IBM Redbook is a study guide for Tivoli Provisioning Manager Express for Software Distribution V4.1 and is aimed at the people who want to get an IBM Professional Certification for this product. The Tivoli Provisioning Manager Express for Software Distribution V4.1 Certification, offered through the Professional Certification Program from IBM, is designed to validate the skills required of technical professionals who work in the implementation of the Tivoli Provisioning Manager Express for Software Distribution V4.1 product. This book provides a combination of theory and practical experience needed for a general understanding of the subject matter. It also provides sample questions that help in the evaluation of personal progress and provide familiarity with the types of questions that you encounter in the exam. For your convenience, we structure the chapters based on the sections of the Tivoli Provisioning Manager Express for Software Distribution V4.1 Implementation Certification test, such as Planning, Installation, and so on, so studying each chapter helps you prepare for one section of the exam.
INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.
For more information: ibm.com/redbooks

SG24-7247-00 ISBN 0738496782

Certification Guide Series IBM Tivoli Provisioning Manager Express For Software Distribution V4.1 Sg247247

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Certification Guide Series IBM Tivoli Provisioning Manager Express For Software Distribution V4.1 Sg247247

Enviado por

Direitos autorais:

Formatos disponíveis

Front cover

Certification Guide Series

Copyright IBM Corp. 2006. All rights reserved.

Copyright IBM Corp. 2006. All rights reserved.

Copyright IBM Corp. 2006. All rights reserved.

6-3 6-4 6-5 6-6

Copyright IBM Corp. 2006. All rights reserved.

Copyright IBM Corp. 2006. All rights reserved.

The team that wrote this IBM Redbook

Become a published author

Copyright IBM Corp. 2006. All rights reserved.

1.1 IBM Professional Certification Program

1.1.1 Benefits of certification

Chapter 1. Certification overview

1.1.2 Tivoli Software Professional Certification

Benefits of being Tivoli certified

Chapter 1. Certification overview

Chapter 1. Certification overview

1.2.1 Test 879 objectives

1.2.2 To get 15% discount on the Certification

1.3 Recommended resources for study

Chapter 1. Certification overview

Copyright IBM Corp. 2006. All rights reserved.

Remote file shares

2.1.2 Inventory components

2.2 Infrastructure deployment considerations

2.2.1 Communication protocols

Figure 2-1 Communication protocols

2.2.2 Small and medium environments

2.2.3 Large environments

2.3 Customization considerations

2.4 Hardware and software specifications and recommendations

2.4.2 Administrative console requirements

2.4.3 Load Balancer

Copyright IBM Corp. 2006. All rights reserved.

3.1 Server installation tasks

3.1.1 Server installation: typical

3.1.2 Server installation: custom setup

Web site Settings window

Figure 3-1 Web site Settings window

E-mail Settings window

Figure 3-2 E-mail Settings window

Action Authority Settings window

Figure 3-3 Action Authority Settings window

See Figure 3-4.

Figure 3-4 Scheduling window

Password Settings window

Figure 3-5 Password Settings window

Form Settings window

Figure 3-6 Form Settings window

Security Settings window

See Figure 3-7.

Figure 3-7 Security Settings window

3.1.3 Server installation verification

Accessing the administrative console

Verifying the WebSphere service

Checking the server log file

Viewing the application log file in the administrative console

3.2 Installing the agent

3.2.1 Installing the agent: typical

3.2.2 Installing the agent: advanced setup

Destination Folder window