Autoinstall.sh utility script redp4296

461 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
461
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Autoinstall.sh utility script redp4296

  1. 1. Redpaper Pete Soto Vasfi GucerAutoinstall.sh Utility Script This IBM® Redpaper explains the functions of the autoinstall.sh utility script, its requirements, operation, implementation, and procedures, to facilitate UNIX® FTA fixpack installations that are initiated from the Tivoli® Workload Scheduler master workstation. We provide two scenarios along with discussions about the various menus and options. Initial first time execution Subsequent executions Utility menusUtility overview The autoinstall.sh utility script is designed to run from the Tivoli Workload Scheduler Version 8.2.0, or greater, master workstation to install fixpacks on UNIX FTA (fault-tolerant agent) workstations with the following UNIX operating systems: AIX® HPUX Linux_i386 Solaris™ The autoinstall.sh utility script, in conjunction with Tivoli Workload Scheduler (UNIX 8.2.0 or greater), reduces the amount of operations and hours required to© Copyright IBM Corp. 2007. All rights reserved. ibm.com/redbooks 1
  2. 2. maintain FTA workstations that are current on maintenance fixpacks. This is accomplished by automating and monitoring UNIX FTA fixpack installations from a central location. Note: Lowercase should be used for all inputs, except for passwords, because they are case sensitive. The script uses existing UNIX tools, “ssh” and “scp”, to perform tasks between UNIX master and UNIX FTA workstations. The ssh protocol is used to provide a secure protocol between the master and FTA. SSH certificates may be created to eliminate the need to provide a password when connecting to a remote system. Refer to “Configuring OPENSSH” on page 77 for more details. Some operating systems may require that these tools be configured or installed, if they were not part of the initial operating system installation. Please consult with your UNIX administrator for configuration or installation assistance. The script is designed to work on AIX, HPUX, Linux_i386 and Solaris platforms. It must reside on the UNIX master and may only patch UNIX FTA workstations. The script must be run as “root” user, because the Tivoli Workload Scheduler fixpack installations require that “root” user execute the patch installation. Although written for Tivoli Workload Scheduler fixpack installation, the script may be customized to schedule and install or patch any application that has a UNIX command line installation option. Note: Any customizing is the responsibility of the user and will not be supported by Tivoli Level 2 support. The script may be placed in any directory. It will create temporary files in the /tmp directory. Any created temporary files will have an extension .#####, where ##### is the process ID for the script when executed. The temporary files will be removed when exiting the script normally.Features The following are the features of autoinstall.sh utility: The script runs on the server, and: – Gathers and stores client installation information for patch installations or new product installations. – Transfers installation scripts from the server to the client. – Can be customized by the user to patch or install any product with a command line interface.2 Autoinstall.sh Utility Script
  3. 3. Uses Tivoli Workload Scheduler to: – Schedule, launch and monitor the Tivoli Workload Scheduler patch installation or a new installation of any product with a command line interface from a central location.Requirements Here are the requirements of the solution.System requirements The autoinstall.sh utility script is designed to run from the Tivoli Workload Scheduler Version 8.2, or greater, master workstation on the following UNIX platforms and may only install fixpacks on UNIX FTA workstations. AIX HPUX Linux_i386 Solaris The .profile for the twsuser must have the TWSHome and TWSHome/bin directory in PATH variable for the master and FTA. You should be able to invoke Tivoli Workload Scheduler commands without having to specify the path. The FTA must be able to issue ssh and scp commands. The ssh protocol is used to provide a secure protocol between the master and FTA. Some operating systems may require that these tools be configured or installed, if they were not part of the initial operating system install. Please consult with your UNIX administrator for ssh and ssl configuration or installation assistance.Autoinstall.sh script information and requirements The autoinstall.sh script must run on a AIX, HPUX, Linux_i386 or Solaris master to patch AIX, HPUX, Linux_i386 or Solaris FTA workstations. The script may be run by multiple users to create or update files. Temporary files will be generated in the /tmp directory each time the script is run and will be removed when exiting normally from the script. Autoinstall.sh Utility Script 3
  4. 4. Attention: There is a known issue with the autoinstall.sh when it is run on Liniux_i386. The carriage return, which is not visible in AIX, HPUX and Solaris, appear as “/c” on Linux_i386 when running the autoinstall.sh script. The script functionality is not affected. A master domain manager (MDM) definition directory will be created when the script is executed using information from the Tivoli Workload Scheduler master user. This directory will be used to store information for applying fixpacks on FTA workstations that it manages. The /etc/TWS/APPL.tws directory, which will be the repository for utility scripts, will be created on the master the first time the script is run. The utility scripts for the FTA workstations will exist locally on the FTA in the /etc/TWS directory. The utility script can be used to copy (via scp) the utility scripts from the master to the FTA. The Tivoli Workload Scheduler utility scripts, patch_install.sh, and patch must be placed in the /etc/TWS/APPL.tws directory for the master workstation. The Tivoli Workload Scheduler fixpack installation scripts, patch_install.sh and patch_lau.sh, must be copied from the repository on the master (/etc/TWS/APPS.tws directory) to the /etc/TWS directory on FTA and should be executable by the Tivoli Workload Scheduler user, specified during the initial FTA Tivoli Workload Scheduler installation. If the master and FTA workstation exist on same node then the utility scripts must exist in both directories. Other applications directories, /etc/TWS/APPL.xxxx, may be created with the autoinstall.sh script to serve as a utility repository for other application scripts but the autoinstall.sh script must be customized by the user. The directory for these must be APPL.name where name is the name of the application in lowercase. Customizing will be the user’s responsibility and will not be supported by Tivoli Workload Scheduler level 2 support. Contact IBM Services for assistance with customizing. The autoinstall.sh script requires basic FTA information that is stored for future fixpack installations. The script extracts the node/ip, Tivoli Workload Scheduler version and operating system for FTA, provided FTA exists, in the current Symphony file and is linked. The user will need to provide the Tivoli Workload Scheduler user, specified at FTA installation and base path directory for fixpack repository. The FTA specific base path should include the Tivoli Workload Scheduler version and operating system in the path to facilitate user fixpack maintenance. Ideally the fixpack path should be an NFS mounted file system which is mounted on all FTA workstations using the following naming convention. The fixpack directory should have a common base path followed by TWSversion/OS (/patchesbasepath/twsversion/os). Refer to Example 1.4 Autoinstall.sh Utility Script
  5. 5. Example 1 Fixpack base naming conventionExample: Base path directory for AIX FTA currently on TWS 8.3 /images/patches/8.3.0/aixWhere:patchesbasepath = /images/patchestwsverison = is 8.3.0 (use 3 digit format)os = aix (aix, hpux,linux_i386 or solaris)The FTA workstation information will be written to FTA.ftaname file, where FTAtext is in uppercase and ftaname is the FTA workstation name in lowercase, asshown in Example 2.Example 2 FTA.workstation fileExample: Information on FTA Borg will exist in a file called:FTA.borgThe FTA file will exist in a sub-directory of its workstation master. The name ofthe directory is /etc/TWS/MDM.masteruser.mastername, where text MDM is inuppercase, masteruser is the Tivoli Workload Scheduler user for the master andthe mastername is the workstation name of the master (lowercase). Refer toExample 3.Example 3 MDM.masteruser.mastername definition directoryExample: TWS user m821 for master workstation Data will have thefollowingdirectory for FTA’s that it manages:MDM.m821.dataThe autoinstall.sh script will request specific patch information when patching anFTA. The patches must be in a sub directory named fp##. Refer to Example 4.Example 4 Fixpack directory conventionThe patches must be in a sub directory named fp##, where fp is inlowercase and ## is the two digit patch number for fixpack (fp01, fp02,fp10, fp11 etc...).Example: The following path must exist for patching a TWS 8.3 AIX FTAwith fixpack FP01./images/patches/8.3.0/aix/fp01The autoinstall.sh script will verify that untarred fixpack files exist in the fp## subdirectory. If only the fixpack tar file exists, it will suggest that it be untarred prior to Autoinstall.sh Utility Script 5
  6. 6. running the autoinstall script. It will also verify that the Tivoli Workload Scheduler version and patch level, specified in the menu, match the Tivoli Workload Scheduler version and patch level of the fixpack files. Patching will only be permitted if the specified fixpack is the same level or greater than the current fixpack level on the FTA workstation. After the information has been gathered and verified, a job definition will be created and added to the patch_job_def file in the /etc/TWS/MDM.masteruser.mastername directory. The job created will be unique to the FTA, because it will be for a specific fixpack. Note: Because each fixpack includes all fixes for previous fixpacks, entering multiple fixpacks for the same FTA workstation is not required. Concurrent autoinstall.sh scripts can be executed to add to the patch_job_def file. Duplicate job definitions in the patch_job_def file will be ignored when the job stream is created. The autoinstall.sh script will create the patch_lau_sch_def and patch_succ_sch_def files in the /etc/TWS/MDM.masteruser.mastername directory. These files will contain the definitions for the TWSPATCH_LAUNCH and TWSPATCH_SUCC job streams. These definitions will run on the master once added to the Tivoli Workload Scheduler database. Unique job definitions created by the autoinstall.sh that exist in patch_job_def file in the /etc/TWS/MDM.masteruser.mastername directory will be added to the TWSPATCH_LAUNCH job stream. Multiple job definitions with the exact same name that exist in the patch_job_def file will exist only once in the TWSPATCH_LAUNCH job stream. The creation of the job stream operation may be run several times, because it will overwrite the previous job stream files. The autoinstall.sh script will be used to add the completed job and job stream definition files to the Tivoli Workload Scheduler database. Caution: Adding the job stream definitions to the Tivoli Workload Scheduler database will replace the existing job stream definition for TWSPATCH_LAUNCH and TWSPATCH_SUCC. After adding the job and job stream definitions files to Tivoli Workload Scheduler database, remove the patch_job_def file in the /etc/TWS/MDM.masteruser.mastername directory. This file may be removed using the autoinstall.sh script.6 Autoinstall.sh Utility Script
  7. 7. Attention: The fixpack job definitions should be removed from the Tivoli Workload Scheduler jobs database after the fixpack job has installed the fixpack. This is suggested to limit the number of jobs that will no longer be used, because the fixpack jobs are unique to the FTA and fixpack.The TWSPATCH_SUCC job stream will not have defined jobs, but will containad-hoc submitted jobs from FTA workstations when FTA fixpack jobs havecompleted successfully. The ad-hoc job will be submitted from the FTA when thefixpack installation completes successfully. Example 5 shows the namingconvention for the job name of a successful fixpack installation.Example 5 TWSPACTH_SUCC jobsftaname_twsver_FP_xx_jobnum_SUCCwhere:ftaname is the FTA workstation patchedtwsver is the TWS versionxx is fixpack number (2 digit format)jobnum is the job number of FTA fixpack install jobExample: Fixpack install job for TWS version 8.2 Fixpack 10, job number5767 installed on FTA M82A successfully will have the this jobname inthe TWSPATCH_SUCC job stream on master workstation:M82A_820_FP_10_5767_SUCCThe provided scripts use variables for specific information. The debug option isthe only customizable option in the autoinstall.sh script. DO NOT edit or modifyany variables.Changes to the variables will cause script and installation problems and will notbe supported by Tivoli Workload Scheduler Level 2 support. The patch_install.shscript executes the patch_lau.sh script after verifying that the informationprovided by the job is valid. The patch_lau.sh will inherit the values for variablesthat were defined in the patch_install.sh script.The patch_install.sh script executes patch_lau.sh, which initiates the fixpackinstall. This script, which requires four options: -uname, -patchdir, -version and–patch, makes up the job definition created by the autoinstall.sh script. Werecommend that autoinstall.sh script is used to create and add the job and jobstream definitions.The patch_lau.sh script will create the ftaname_fp_fp##_jobnum.stdlog file in the/tmp directory. This will log procedures prior to executing the twspatch install.Once the twspatch installation launches, the fixpack installation will write to thelog specified the fixpack readme file. Autoinstall.sh Utility Script 7
  8. 8. Tivoli Workload Scheduler requirements The autoinstall.sh script must be run from Tivoli Workload Scheduler 8.2.0, or greater, UNIX master. The script may be placed in any directory. It will create temporary files in the /tmp directory. Any created temporary files will have a extension .#####, where ##### is the process ID for script when executed. The temporary files will be removed when exiting the script normally. The TWSRegistry.dat file must be correct and up to date, because the script extracts Tivoli Workload Scheduler FTA instance information, including fixpacks currently installed, from the file. Root user on the master must have access to Tivoli Workload Scheduler files and databases and must exist in the Tivoli Workload Scheduler Security file, because fixpack installations must be run as root. The root user on FTA must be able to submit ad-hoc jobs that logon as the root user on the master. The master must have a current Symphony file and be linked to FTA workstations that will be patched, because information will be extracted when the script is executed. The script uses the cpuinfo command to validate master and FTA workstations. The “thiscpu=” field in TWSHome/localopts and the “master=” field in TWSHome/mozart/globalopts file must be valid and correct on both master and FTA workstations, or Tivoli Workload Scheduler user validation issues may occur when the script is run. The autoinstall.sh script is used to add the job and job stream definitions to the Tivoli Workload Scheduler database. The definitions should be reviewed prior to adding them to the database. Duplicate job definitions will not be included in the job stream but will be added to the jobs database. If duplicate job definitions exist, the last one added to the jobs database will be used. Multiple fixpack installation jobs that install different fixpacks on the same FTA workstation should be avoided, because installing the latest fixpack includes all previous fixes. The script does not prevent this action.Patching procedures The autoinstall.sh script may be used to provide information for a fixpack install or create FTA.workstation definitions files for future fixpack installs.8 Autoinstall.sh Utility Script
  9. 9. Creating FTA.workstation definition files for future fixpack installations will speed up the process when applying a fixpack to an FTA. This option is useful if the master manages a large number of FTA workstations and is part of the utilities menu options. To perform either of these options requires the creation of specific files or directories which is accomplished by the initial execution of the autoinstall.sh script. This section discusses the first time execution and subsequent patching procedures using the patch option of the autoinstall.sh script.Patching procedures - First time execution The initial execution of the autoinstall.sh script will create files and directories with FTA specific information that will be used in future executions of the autoinstall.sh script. Certain tasks must be performed before executing the script. 1. Create patch repository for each FTA (refer to Autoinstall.sh Script Information and Requirements section). This is necessary, because this information will be requested when creating a FTA.workstation definition file (discussed later). 2. Verify that the localopts and globalopts on FTA and Master are correct. Incorrect information will cause problems in extracting or validating information. 3. Verify that the .profile for FTA TWSuser includes the TWSHome and TWSHome/bin directory in the PATH variable. The script issues remote Tivoli Workload Scheduler commands from the master to the FTA workstation, and errors might occur if the TWSuser .profile does not include the Tivoli Workload Scheduler path in the PATH variable. 4. Verify that all FTA workstations that will be patched are linked, active and have current Symphony file. FTA information is gathered from the Symphony file, this requires that the master be linked to the FTA workstation. The script may not be able to extract or validate information if they are not linked and have a current Symphony file. 5. Logon to the master workstation as root user. This is required, because gathering information and applying the fixpack must be executed as the root user. 6. Execute the autoinstall.sh script as the root user. The script will display message about location of temporary files and their extension, information about the master workstation, current master instance(s) that exist and ask that a master user name be provided to create the MDM definition directory for FTA workstations that it will manage. Refer to Figure 1. Autoinstall.sh Utility Script 9
  10. 10. Current system OS is HPUX The current process id is 18671, Temporary created files will be created in the /tmp directory and have a .18671 extension. No existing MDM definition file exists You will need to create a mdm definition file. This is a list of defined MDM users in the TWSRegistry.dat file for this workstation. m821a m83rtm Enter TWS User for master cpu or press enter to obtain a list of MDM users listed in the TWSRegistry.dat file -> Figure 1 MDM definition directory 7. Provide the Tivoli Workload Scheduler user for the MDM that will be used to manage FTA workstations that will be patched. The script will determine if the provided user is valid and display information about the provided user.10 Autoinstall.sh Utility Script
  11. 11. Enter TWS User for master cpu or press enter to obtain a list of MDM users listed in the TWSRegistry.dat file -> m821a Agent type for user m821a is MDM. m821a is a valid TWS user for a master cpu. TWSPATH for m821a user is: /tws/m821a TWS Master workstation m821a for TWS master user m821a on this workstation will be used to schedule installs. Will create MDM definition file for TWS user -> m821a on TWS master workstation -> m821a. /etc/TWS/MDM.m821a.m821a No existing APPL definition file exists Will need to create a APPL definition file. Will create the tws APPL definition directory /etc/TWS/APPL.tws Application tws will be used. The current process id is 18671, Temporary created files will be created in the /tmp directory and have a .18671 extension. Main Menu To patch a workstation enter (p). To access FTA or job and job stream utilities enter (u). To exit utility enter (e). Enter p, u or e ->Figure 2 Create TWS MDM and application definition directories The application will create the directory MDM.masteruser.mastername which will serve as the repository for FTA.workstationname files that contain specific FTA information. It will also create the APPL.tws directory, if it does not exist. The APPL.tws directory will serve as the repository for utility scripts that will be sent to FTA workstations. Autoinstall.sh Utility Script 11
  12. 12. 8. Reply to the prompt that asks the type of task to perform. Enter p to proceed to patch installation tasks. Refer to Figure 3. The following prompt, as shown in Figure 3, will appear asking you to provide a valid FTA to patch. Pressing <Enter> will list all workstations that exist in the Symphony file. Only UNIX FTA workstations may be patched. Enter p, u or e -> p Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> Figure 3 FTA patch installation prompt Pressing <Enter> will display all workstations that exist on the current master. Refer to Figure 4. Note: Only UNIX FTA workstations may be patched. Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> <enter> Below is a list of valid FTA’s for m821a master user: M821A M821A AF T 38211 taos HORBLM82 HORBLM82 A AT 31822 testmaster M82A M82A AFAT 31822 taos XA-FUEGO M82A A AT 31822 fuego.tivlab.austin.ibm.com Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> Figure 4 FTA Listing 9. Provide an FTA to patch. The script will determine if workstation is a UNIX FTA, and then gather some basic FTA workstation information from the Symphony file and display as shown in Figure 5.12 Autoinstall.sh Utility Script
  13. 13. Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> m82a Input value is M82A TWS workstation M82A on node/ip taos is a UNIX FT-AGENT ie.. an FTA. TWS workstation M82A on node taos is valid, will patch. Will determine if basic information for FTA m82a on master m821a exists. Will need to create information file for m82a: /etc/TWS/MDM.m821a.m821a/FTA.m82a since the above file does not exist. Additional information is required for TWS workstation m82a. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. ->Figure 5 Extracted FTA workstation information10.Provide the TWSuser specified when the FTA was installed. The application will attempt to verify the specified user. If an SSH certificate file does not exist between the master and FTA, the user will be prompted for root password for the FTA workstation. Refer to Figure 6. Will try to validate TWS user m82a and that it manages TWS workstation m82a. You may need to provide root password for node/ip taos more than once. Password:Figure 6 Validate TWS FTA user If <Enter> is depressed, it will ask if you want to extract list of users on node/ip for FTA. Replying “y” will then prompt for root password for the node/ip of FTA. Refer to Figure 7. Autoinstall.sh Utility Script 13
  14. 14. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> <enter> Do you want to extract list of TWS users on node/ip taos? (Enter y or n) -> Figure 7 Prompt to extract Tivoli Workload Scheduler users for FTA workstation Replying “y” to “extract list of TWS users” will then prompt for the password for the FTA workstation. A list of Tivoli Workload Scheduler users for instances on FTA will be displayed. Refer to Figure 8. Do you want to extract list of TWS users on node/ip taos? (Enter y or n) -> y Will attempt to connect to node/ip taos and extract list of TWS users. You may need to provide root password for node/ip taos. Password: fta2nd83 fta83rtm m82a m82b mae001 The above is a list of TWS users for FTA workstations listed in the TWSRegistry.dat file on node/ip taos. You will need to specify the correct TWS user for TWS workstation m82a. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> Figure 8 Extracted list of TWS users for FTA workstation Provide TWSuser specified when the FTA was installed. The application will attempt to verify the specified user. If a SSH certificate file does not exist14 Autoinstall.sh Utility Script
  15. 15. between the master and FTA, the user will be prompted for root password for the FTA workstation. Refer to Figure 6. If the script is unable to validate the user, it will ask if you want to still use the specified user. Refer to Figure 9. This warning could be caused by: – An invalid user – FTA workstation “this cpu” field in the localopts file is incorrect – Master workstation is unable to connect to FTA workstation Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> pete /localopts: No such file or directory The extracted value in the "thiscpu" field of localopts for user pete is: <empty> or localopts file does not exist. Warning: Unable to validate user. Enter y to use user pete or n to specify another user ->Figure 9 Unable to validate TWS FTA user Once the TWSuser for FTA has been validated, information about the FTA will be extracted. Extracted FTA workstation information is obtained from the master Symphony file, FTA localopts, and TWSregistryt.dat files. The extracted information will be displayed and will prompt for the local base path for fixpack files. Refer to Figure 10. Autoinstall.sh Utility Script 15
  16. 16. The extracted value in the "thiscpu" field of localopts for user m82a is: m82a Logon user m82a exists. The TWS user m82a will be used for TWS workstation m82a. Will try to determine OS and current TWS version for FTA m82a. FTA m82a should be linked, this may take a few seconds. Extracted TWS version for m82a is 8.2 Will use TWS version 8.2.0. Extracted OS for m82a is HP-UX. OS HPUX will be used for m82a. Provide base path for patches for FTA m82a on taos on current TWS version. Path should start with slash / -> Figure 10 Validate user and prompt for fixpack base path 11.Provide the fixpack base path for FTA (see base path requirements shown in Example 6). Note: The base path provided must be valid, because it will be used to determine the fixpack directory path. Example 6 Suggested naming convention. The fixpack directory should have a common base path followed by TWSversion/OS (/patchesbasepath/twsversion/os). Example: Base path directory for AIX FTA currently on TWS 8.3 /images/patches/8.3.0/aix Where: patchesbasepath = /images/patches twsverison = is 8.3.0 (use 3 digit format) os = aix (aix, hpux,linux_i386 or solaris16 Autoinstall.sh Utility Script
  17. 17. /images/patches/8.2.0/hpux You may need to provide the root password for taos. Password:Figure 11 Password prompt12.Provide the root password for FTA; it may prompt for root password if an SSH certificate does not exist. Refer to Figure 11. Once the path has been validated it will ask if you want to use specified path. Refer to Figure 12. Path /images/patches/8.2.0/hpux exists Enter y, to use this path or enter n to specify another path. ->Figure 12 Fixpack path validation and prompt Once the base path has been confirmed, the FTA definition file will be created for the FTA. Refer to Figure 13. Enter y, to use this path or enter n to specify another path. -> y Base patch path /images/patches/8.2.0/hpux will be used for m82a User m82a, TWS current version 8.2.0, OS HPUX and base patch path /images/patches/8.2.0/hpux for FTA workstation m82a on node/IP taos basic information will be used for TWS FTA and will be added to: /etc/TWS/MDM.m821a.m821a/FTA.m82a Provide TWS 8.2.0 patch level to install, in ## format ie.. 01, 02, 03 … Enter TWS patch level->Figure 13 FTA.ftaworkstation file creation and fixpack prompt13.You must then provide the fixpack number to install. The fixpack must be a two digit number. The fixpack number will be verified that it exists locally on the FTA, and that it is the same or greater than what is currently installed on the FTA before proceeding. Refer to Figure 14. Autoinstall.sh Utility Script 17
  18. 18. Note: When fixpack path for fixpacks is created in the base patch path, it must be fp##, where “fp” text is in lowercase and “##” is fixpack number in two digit format. Provide the two digit fixpack number when replying to fixpack prompt. Because each fixpack includes all fixes for previous fixpacks, entering multiple fixpacks for the same FTA workstation is not required. Provide TWS 8.2.0 patch level to install, in ## format ie.. 01, 02, 03 … Enter TWS patch level of patch -> 10 Level entered is 10 10 TWS patch level 10 will be verified. Base patch path is /images/patches/8.2.0/hpux. Will verify that patch files exist in /images/patches/8.2.0/hpux/fp10 directory. You may need to provide root password for node/ip taos Password: Figure 14 Fixpack verification 14.Provide the root password for FTA if an SSH certificate does not exist. Once the fixpack number has been entered it will determine if fixpack may be applied. The script will install fixpacks that are at same level or higher than current or the last fixpack applied to FTA workstation, or if FTA workstation has no previous fixpacks. It will ask if you want to use a specified fixpack if it meets the requirement. Refer to Figure 15.18 Autoinstall.sh Utility Script
  19. 19. You may need to provide root password for node/ip taos Password: Lasted installed version is 8.2.0, Lasted installed fixpack level is 10 Untarred patch files exist for patch 8.2.0-TIV-TWS-FP0010.TAR WARNING: Specified patch level to install is same level as currently installed on workstation. Do you want to use the specified information? (Enter y or n) ->Figure 15 Fixpack installation confirmation15.Reply to prompt asking if the specified fixpack number should be used. If the reply is “n”, you will need to provide another fixpack number. If it is “y”, a job definition will be created in the patch_job_def file in the /etc/TWS/MDM.masteruser.mastername directory. This file will contain the information required to install the specified fixpack on the FTA workstation. Refer to Figure 16. Do you want to use the specified information? (Enter y or n) -> y WARNING: Current specified patch file will be used Patch install job definition file patch_job_def will be created in the /etc/TWS/MDM.m821a.m821a directory. FTA Patch Menu Do you want to enter another FTA to patch? To patch another FTA enter (p) To go back to Main Menu enter (b) To exit utility enter (e) Enter p, b or e) ->Figure 16 Apply fixpack to another FTA prompt Autoinstall.sh Utility Script 19
  20. 20. 16.Reply to above prompt to provide information to apply the fixpack to another FTA workstation, go back to Main Menu, or exit the autoinstall.sh script. Refer to Figure 17. Temporary files generated by the script will be removed when exiting normally from the script. Enter p, b or e) -> e Will exit patch FTA mode. The current process id is 28525, removing all temporary files with .28525 extension in the /tmp directory. Exiting ./autoinstall.sh script. Figure 17 Exit autoinstall.sh utilityPatching procedures- Subsequent executions Executing the autoinstall.sh script later will bypass some of the initial operations and screens. If an MDM already exists it will display information for MDM and will ask if you want to use the existing MDM definition. Refer to Figure 18. Note: Using a different MDM definition is only possible if the current workstation has multiple master instances. Current system OS is HPUX The current process id is 20511, Temporary created files will be created in the /tmp directory and have a .20511 extension. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> Figure 18 Use existing MDM definition 1. Reply to the prompt with “y” to use the existing MDM definition. Replying “n” will prompt the user to provide information for the new MDM and will use the new MDM definition. Refer to Figure 19.20 Autoinstall.sh Utility Script
  21. 21. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> n You will need to create a mdm definition file. This is a list of defined MDM users in the TWSRegistry.dat file for this workstation. m821a m83rtm Enter TWS User for master cpu or press enter to obtain a list of MDM users listed in the TWSRegistry.dat file ->Figure 19 Prompt for new MDM definition Replying “y” will display a message stating that the existing MDM definition for the TWS user on the master workstation will be used. The script will ask the user if they want to use the APPL.tws application definition. Refer to Figure 20. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> y Existing TWS user m821a for master cpu m821a on this workstation will be used. This is a list of defined MDM users in the TWSRegistry.dat file for this workstation. m821a m83rtm drwxrwxr-x 2 root sys 96 Feb 20 16:15 /etc/TWS/APPL.tws Found the tws application definition on this workstation, ok to use? (Enter y or n) ->Figure 20 Use APPL.tws definition prompt2. Reply to the prompt asking to use the existing APPL.tws application. Autoinstall.sh Utility Script 21
  22. 22. Reply “n” to use or provide another APPL.xxxx definition. This requires that the autoinstall.sh utility script be modified to include user defined functions for the new application. You will need to provide the name for the application directory. The script will precede the name with APPL., when creating the definition directory. Refer to “Create a new APPL.xxxx definition” on page 33 for more details. Refer to Figure 21. Found the tws application definition on this workstation, ok to use? (Enter y or n) -> n You will need to create a APPL definition. Enter name for application -> Figure 21 Create new APPL.xxxx definition prompt After replying “y” to use the APPL.tws definition, the master workstation definition will be used for managing information of FTA workstations. 3. Reply “p” to proceed, providing information about the FTA workstation to patch. Refer to Figure 22. The utilities option is discussed later. Temporary files generated by the script will be removed when exiting normally from the script.22 Autoinstall.sh Utility Script
  23. 23. Found the tws application definition on this workstation, ok to use? (Enter y or n) -> y Application tws definition for master cpu m821a on this workstation will be used to schedule install. Application tws will be used. logout The current process id is 20511, Temporary created files will be created in the /tmp directory and have a .20511 extension. Main Menu To patch a workstation enter (p). To access FTA or job and job stream utilities enter (u). To exit utility enter (e). Enter p, u or e ->Figure 22 Prompt for patch or utilities operations The following prompt as shown in Figure 23 will appear, asking that you provide a valid FTA to patch. Depressing “Enter” will list all of the workstations that exist in the Symphony file. Only UNIX FTA workstations may be patched. Caution: Pressing <Enter> will display all defined workstations. The displayed list will scroll on the screen as they are displayed. Enter p, u or e -> p Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. ->Figure 23 FTA patch installation prompt Pressing <Enter> will display all of the workstations that exist on the current master. Refer to Figure 24. Autoinstall.sh Utility Script 23
  24. 24. Note: Only UNIX FTA workstations may be patched. Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> <enter> Below is a list of valid FTA’s for m821a master user: M821A M821A AF T 38211 taos HORBLM82 HORBLM82 A AT 31822 testmaster M82A M82A AFAT 31822 taos XA-FUEGO M82A A AT 31822 fuego.tivlab.austin.ibm.com Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> Figure 24 FTA Listing 4. Provide an FTA to patch. The script will determine if the workstation is a UNIX FTA then gather some basic FTA workstation information from the Symphony file and display. Refer to Figure 25.24 Autoinstall.sh Utility Script
  25. 25. Enter a valid FTA workstation name to patch. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> m82a Input value is M82A TWS workstation M82A on node/ip taos is a UNIX FT-AGENT ie.. an FTA. TWS workstation M82A on node taos is valid, will patch. Will determine if basic information for FTA m82a on master m821a exists. Will need to create information file for m82a: /etc/TWS/MDM.m821a.m821a/FTA.m82a since the above file does not exist. Additional information is required for TWS workstation m82a. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. ->Figure 25 Extracted FTA workstation information5. Provide the TWSuser specified when the FTA was installed, or press <Enter> to extract a list of users for TWS instances on FTA. The application will attempt to verify the specified user. If a SSH certificate file does not exist between the master and FTA user will be prompted for root password for FTA workstation. Refer to Figure 26. Autoinstall.sh Utility Script 25
  26. 26. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> m82a Will try to validate TWS user m82a and that it manages TWS workstation m82a. You may need to provide root password for node/ip taos more than once. Password: Figure 26 Validate TWS FTA user If <Enter> is depressed it will prompt whether you want to extract list of users on node/ip for FTA. Replying “y” will then prompt of root password for node/ip of FTA. Refer to Figure 27. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> enter Do you want to extract list of TWS users on node/ip taos? (Enter y or n) -> Figure 27 Prompt to extract TWS users for FTA workstation Replying “y” to “extract list of TWS users” will then prompt for password for the FTA workstation. A list of TWS users for instances on FTA will be displayed. Refer to Figure 28.26 Autoinstall.sh Utility Script
  27. 27. Do you want to extract list of TWS users on node/ip taos? (Enter y or n) -> y Will attempt to connect to node/ip taos and extract list of TWS users. You may need to provide root password for node/ip taos. Password: fta2nd83 fta83rtm m82a m82b mae001 The above is a list of TWS users for FTA workstations listed in the TWSRegistry.dat file on node/ip taos. You will need to specify the correct TWS user for TWS workstation m82a. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. ->Figure 28 Extracted list of TWS users for FTA workstation Provide TWSuser specified when the FTA was installed. The application will attempt to verify the specified user. If a SSH certificate file does not exist between the master and FTA, the user will be prompted for root password for the FTA workstation. Refer to Figure 26.If the script is unable to validate the user, it will ask if you want to still use thespecified user. Refer to Figure 29. This warning could be caused by: An invalid user FTA workstation “this cpu” field in the localopts file is incorrect Master workstation is unable to connect to FTA workstation Autoinstall.sh Utility Script 27
  28. 28. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> test Warning: Unable to validate user. Enter y to use user test or n to specify another user -> Figure 29 Unable to validate TWS FTA user Once the TWSuser for FTA has been validated, information about the FTA will be extracted. Extracted FTA workstation information is obtained from the master Symphony file, from the FTA localopts and TWSregistryt.dat files. The extracted information will be displayed and will prompt for the local base path for fixpack files. Refer to Figure 30. The extracted value in the "thiscpu" field of localopts for user m82a is: m82a Logon user m82a exists. The TWS user m82a will be used for TWS workstation m82a. Will try to determine OS and current TWS version for FTA m82a. FTA m82a should be linked, this may take a few seconds. Extracted TWS version for m82a is 8.2 Will use TWS version 8.2.0. Extracted OS for m82a is HP-UX. OS HPUX will be used for m82a. Provide base path for patches for FTA m82a on taos on current TWS version. Path should start with slash / -> Figure 30 Validate user and prompt for fixpack base path Example 7 Fixpack base path requirements The following naming convention. The fixpack directory should have a common base path followed by TWSversion/OS (/patchesbasepath/twsversion/os). Example: Base path directory for AIX FTA currently on TWS 8.328 Autoinstall.sh Utility Script
  29. 29. /images/patches/8.3.0/aixWhere:patchesbasepath = /images/patchestwsverison = is 8.3.0 (use 3 digit format)os = aix (aix, hpux,linux_i386 or solaris)6. Provide the fixpack base path for FTA (see base path requirements in Example 7). Provide base path for patches for FTA m82a on taos on current TWS version. Path should start with slash / -> /images/patches/8.2.0/hpux You may need to provide the root password for taos. Password:Figure 31 Password prompt7. Provide the root password for FTA; it may prompt for root password if an SSH certificate does not exist. Refer to Figure 31. Once the path has been validated it will ask if you want to use the specified path. Refer to Figure 32. You may need to provide the root password for taos. Password: Path /images/patches/8.2.0/hpux exists Enter y, to use this path or enter n to specify another path. ->Figure 32 Fixpack path validation and prompt Once the base path has been confirmed, the FTA definition file will be created for the FTA. Refer to Figure 33. Autoinstall.sh Utility Script 29
  30. 30. Enter y, to use this path or enter n to specify another path. -> y Base patch path /images/patches/8.2.0/hpux will be used for m82a User m82a, TWS current version 8.2.0, OS HPUX and base patch path /images/patches/8.2.0/hpux for FTA workstation m82a on node/IP taos basic information will be used for TWS FTA and will be added to: /etc/TWS/MDM.m821a.m821a/FTA.m82a Provide TWS 8.2.0 patch level to install, in ## format ie.. 01, 02, 03 … Enter TWS patch level -> Figure 33 FTA.ftaworkstation file creation and fixpack prompt 8. You must then provide the fixpack number to install. The fixpack must be in a two digit number. The fixpack number will be verified that it exists locally on the FTA, and that it is the same or greater than what is currently installed on the FTA before proceeding. Refer to Figure 34. Note: When the fixpack path for fixpacks is created in the base patch path, it must be fp##, where “fp” text is in lowercase and “##” is fixpack number in two digit format. Provide the two digit fixpack number when replying to the fixpack prompt. Because each fixpack includes all fixes for previous fixpacks, entering multiple fixpacks for the same FTA workstation is not required.30 Autoinstall.sh Utility Script
  31. 31. Provide TWS 8.2.0 patch level to install, in ## format ie.. 01, 02, 03 … Enter TWS patch level -> 10 Level entered is 10 10 TWS patch level 10 will be verified. Base patch path is /images/patches/8.2.0/hpux. Will verify that patch files exist in /images/patches/8.2.0/hpux/fp10 directory. You may need to provide root password for node/ip taos Password:Figure 34 Fixpack to apply and password prompt9. Provide the root password for FTA if an SSH certificate does not exist. Once the fixpack number has been entered it will determine if the fixpack may be applied. The script will install fixpacks that are at same level or higher than current or last fixpack applied to FTA workstation or if FTA workstation has no previous fixpacks. It will ask if you want to use specified fixpack if it meets the requirement. Refer to Figure 35. Base patch path is /images/patches/8.2.0/hpux. Will verify that patch files exist in /images/patches/8.2.0/hpux/fp10 directory. You may need to provide root password for node/ip taos Password: Lasted installed version is 8.2.0, Lasted installed fixpack level is 10 Untarred patch files exist for patch 8.2.0-TIV-TWS-FP0010.TAR WARNING: Specified patch level to install is same level as currently installed on workstation. Do you want to use the specified information? (Enter y or n) ->Figure 35 Fixpack installation confirmation Autoinstall.sh Utility Script 31
  32. 32. 10.Reply to the prompt asking if the specified fixpack number should be used. If the reply is “n” you will need to provide another fixpack number. If the reply is “y” a job definition will be created in the patch_job_def file in the /etc/TWS/MDM.masteruser.mastername directory. This file will contain the information required to install the specified fixpack on the FTA workstation. Refer to Figure 36. Do you want to use the specified information? (Enter y or n) -> y WARNING: Current specified patch file will be used Patch install job definition file patch_job_def will be created in the /etc/TWS/MDM.m821a.m821a directory. FTA Patch Menu Do you want to enter another FTA to patch? To patch another FTA enter (p) To go back to Main Menu enter (b) To exit utility enter (e) Enter p, b or e) -> Figure 36 Apply fixpack to another FTA prompt 11.Reply to the prompt to provide information to apply the fixpack to another FTA workstation or to exit the autoinstall.sh script. Temporary files generated by the script will be removed when exiting normally from the script. Refer to Figure 37. Enter p, b or e) -> e Will exit patch FTA mode. The current process id is 28525, removing all temporary files with .28525 extension in the /tmp directory. Exiting ./autoinstall.sh script. Figure 37 Exit autoinstall.sh script32 Autoinstall.sh Utility Script
  33. 33. Create a new APPL.xxxx definition The autoinstall.sh utility script may be used to patch or install any application that uses a UNIX command line installation. The script will require that additional functions/modules be added to support this functionality. It will be the user’s responsibility to edit and support the new functions. TWS level 2 support will not support these changes. Contact IBM Services to provide this service. The APPL.xxxx definition is part of a MDM definition, because the master for the MDM is used to schedule the patch or installation of the APPL.xxx application. To define a new APPL.xxxx definition execute the autoinstall.sh utility script. A prompt will ask you if you want to use an existing MDM definition. 1. Reply “y” to the prompt asking to use the existing MDM definition. Refer to Figure 38. Current system OS is HPUX The current process id is 18671, Temporary created files will be created in the /tmp directory and have a .18671 extension. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> Figure 38 Use existing MDM definition 2. Reply “n” to the prompt asking to use the APPL.tws application definition. Refer to Figure 39. Autoinstall.sh Utility Script 33
  34. 34. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> y Existing TWS user m821a for master cpu m821a on this workstation will be used. This is a list of defined MDM users in the TWSRegistry.dat file for this workstation. m821a m83rtm drwxrwxr-x 2 root sys 96 Feb 20 16:15 /etc/TWS/APPL.tws Found the tws application definition on this workstation, ok to use? (Enter y or n) -> Figure 39 Use APPL.tws definition prompt 3. Provide the name for the new APPL.xxxx definition directory. The script will precede the name with APPL. prefix when creating the definition directory. Refer to Figure 40. Found the tws application definition on this workstation, ok to use? (Enter y or n) -> n You will need to create a APPL definition. Enter name for application -> Figure 40 New APPL.xxxx definition directory prompt After entering the name for the new APPL.xxxx definition you will be asked if you want to use the provided name. 4. Reply “y” to use this name or “n” to re-enter a new name. Refer to Figure 41.34 Autoinstall.sh Utility Script
  35. 35. Enter name for application -> test You specified test definition is this correct. (y or n) -> Figure 41 Confirm new APPL.xxxx definition directory 5. Reply “y” to the prompt to use the new APPL.xxxx definition; the script will attempt to access the new functions or modules that should have been added to the autoinstall.sh script. If the script has not be edited for this, then it will exit after creating the new APPL.xxxx definition and displaying current the APPL.xxxx definition directories. Refer to Figure 42. You specified test definition is this correct. (y or n) -> y APPL.test directory will be created on this workstation and will be available for future installs Will create APPL definition directory test on m821a /etc/TWS/APPL.test /etc/TWS/APPL.tws Application test will be used. Application install is not TWS. The current process id is 12365, removing all temporary files with .12365 extension in the /tmp directory. Exiting ./autoinstall.sh script. Figure 42 Creation of new APPL.xxxx definitionUtilities Operations The utilities operations consist of FTA, or job and jobs stream, utility tasks. The FTA utilities are for FTA maintenance operations used to add, update, or delete an FTA.workstation file or to export fixpack installation utility scripts from the master to the FTA workstation. Autoinstall.sh Utility Script 35
  36. 36. The job and job stream utilities include a task that creates the job streams for fixpack installation jobs, a task to add job and job stream definitions to the TWS jobs and job stream database, or a task to rename the patch_job_def job definition file. The renamed patch_job_def file will have an extension of _mmddyy_hhmmss, where mmddyy is the month, day, and year, and hhmmss is hour, minute, and second.Utilities - FTA Utilities FTA maintenance will be performed from the FTA Utilities Menu. You will need to proceed past some of the general menus or prompts to get to the FTA Utilities Menu. If an MDM already exists it will display information for MDM and ask if you want to use the existing MDM definition. Refer to Figure 43. Note: Using a different MDM definition is only possible if the current workstation has multiple master instances. Current system OS is HPUX The current process id is 20511, Temporary created files will be created in the /tmp directory and have a .20511 extension. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> Figure 43 Use existing MDM definition 1. Reply to prompt with “y” to use existing MDM definition. Replying “y” will display a message stating that existing MDM definition for TWS user on the master workstation will be used. The script will ask the user if they want to use the APPL.tws application definition. Refer to Figure 44.36 Autoinstall.sh Utility Script
  37. 37. Found an existing MDM definition for m821a user on master cpu m821a on this workstation, ok to use? (Enter y or n) -> y Existing TWS user m821a for master cpu m821a on this workstation will be used. This is a list of defined MDM users in the TWSRegistry.dat file for this workstation. m821a m83rtm drwxrwxr-x 2 root sys 96 Feb 20 16:15 /etc/TWS/APPL.tws Found the tws application definition on this workstation, ok to use? (Enter y or n) ->Figure 44 Use APPL.tws definition prompt2. Reply “y” to the prompt asking to use the existing APPL.tws application. Refer to Figure 45. After replying “y” to use the APPL.tws definition, the master workstation definition will be used for managing information of FTA workstations. Autoinstall.sh Utility Script 37
  38. 38. Found the tws application definition on this workstation, ok to use? (Enter y or n) -> y Application tws definition for master cpu m821a on this workstation will be used to schedule install. Application tws will be used. logout The current process id is 20511, Temporary created files will be created in the /tmp directory and have a .20511 extension. Main Menu To patch a workstation enter (p). To access FTA or job and job stream utilities enter (u). To exit utility enter (e). Enter p, u or e -> Figure 45 Prompt for patch or utilities operations 3. Reply “u” to proceed to the Main Utilities Menu. Refer to Figure 46. Enter p, u or e -> u Main Utilities Menu To access FTA utilities enter (f). To access job and job stream utilities enter (j). To go back to Main Menu enter (b). To exit utility enter (e). Enter f, j, b or e -> Figure 46 FTA utilities menus 4. For FTA maintenance tasks, reply f to perform FTA maintenance tasks.38 Autoinstall.sh Utility Script
  39. 39. Enter f, j, b or e -> f FTA Utilities Menu To add or update an FTA file enter (a). To delete an FTA file enter (d). To export the utility scripts to an FTA enter (x). To go back to Main Utilities Menu enter (b). To exit utility enter (e). Enter a, d, x, b or e ->Figure 47 FTA utilities menu Proceed to one of these sections: – “Add or Update an FTA File” on page 39 – “Delete an FTA file” on page 51 – “Export Utility Scripts to FTA” on page 53 Refer to Figure 47.Add or Update an FTA File i. At the FTA Utilities Menu screen, reply a to add or update an FTA definition file. Refer to Figure 48. Enter a, d, x, b or e -> a FTA to be added or updated must be exist in current Symphony file and linked before executing utility. Press enter l to get a list of FTA files that may be updated or any other key to bypass list. ->Figure 48 List FTA definition prompt Entering l will display a list of current FTA definitions that already exist in the MDM.mastername.mastername definition directory. This option should be selected it you want to see existing FTA.workstation definition files. Autoinstall.sh Utility Script 39
  40. 40. Pressing any other key will bypass this operation. ii. Press either “l” or any key to continue. Refer to Figure 49. Press enter l to get a list of FTA files that may be updated or any other key to bypass list. -> l Below is a list of current FTA files managed by Master cpu m821a. MDM.m821a.m821a/FTA.m82a This is the FTA add or update module. Enter a valid FTA workstation name to add or update. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> Figure 49 Existing FTA.workstation list and FTA name to add or update prompt The script will then prompt for FTA name to add or update; pressing <Enter> will display a list of workstations that exist in the current master Symphony file. Refer to Figure 50. Caution: Pressing <Enter> will display all defined Workstations. The displayed list will scroll on the screen as they are displayed. Enter a valid FTA workstation name to add or update. Press enter to display a list of valid workstations in current Symphony file on master cpu.-> <enter> Below is a list of valid FTAs for m821a master user. M821A M821A AF T 38211 taos HORBLM82 HORBLM82 A AT 31822 testmaster M82A M82A AFAT 31822 taos XA-FUEGO M82A A AT 31822 fuego.tivlab.austin.ibm.com Enter a valid FTA workstation name to add or update. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> Figure 50 Workstation list from the master Symphony file40 Autoinstall.sh Utility Script
  41. 41. iii. Reply to prompt with FTA name. If FTA name exists as an FTA.workstation definition file it will update the existing file. If the file FTA.workstation definition file does not exist it will prompt for FTA specific information to add a new FTA definition. Proceed to one of these sections: “Add New FTA Definition” on page 41, or “Update an Existing FTA.workstation File” on page 46.Add New FTA Definition Press <Enter> to display a current list of workstations in the master Symphony file. Note: The FTA must exist in the Symphony file to be linked to the master, to extract the required information for the FTA.workstation file. iv. Enter the name of the UNIX FTA workstation that exists in the master’s Symphony file. The script will extract specific information to generate the FTA.workstation file if FTA exists in the master’s Symphony file and is a UNIX FTA. It will display the following and ask for the TWS user that was specified when FTA was installed. Refer to Figure 51. Autoinstall.sh Utility Script 41
  42. 42. Input value is HORBLM82. TWS workstation HORBLM82 on node/ip testmaster is a UNIX FT-AGENT ie.. an FTA. TWS workstation HORBLM82 on node testmaster is valid, will add or update. Will determine if basic information for FTA horblm82 on master m821a exists. Will need to create information file for horblm82: /etc/TWS/MDM.m821a.m821a/FTA.horblm82 since the above file does not exist. Additional information is required for TWS workstation horblm82. Enter the TWS user for workstation horblm82 (node/ip testmaster) or press enter to obtain list of TWS users on node/ip testmaster. -> Figure 51 FTA verification and TWS user prompt v. You may provide the TWSuser for the FTA specified or press <Enter> to obtain a list of Tivoli Workload Scheduler instance users that exist on the FTA workstation. The list of Tivoli Workload Scheduler instance users is extracted from the TWSRegistry.dat file. Pressing <Enter> to produce a list of users for Tivoli Workload Scheduler instances that exist on the FTA workstation may require the root password if an SSH certificate does not exist on FTA. Refer to Figure 52. Note: The user list displayed, will consist of users for all Tivoli Workload Scheduler instances that exist, if multiple Tivoli Workload Scheduler instances exist on the FTA node. You must use the Tivoli Workload Scheduler user for the FTA that was specified in the previous step.42 Autoinstall.sh Utility Script
  43. 43. Enter the TWS user for workstation horblm82 (node/ip testmaster) or press enter to obtain list of TWS users on node/ip testmaster. -> <enter> Do you want to extract list of TWS users on node/ip testmaster? (Enter y or n) -> y Will attempt to connect to node/ip testmaster and extract list of TWS users. You may need to provide root password for node/ip testmaster. Password: e82pdm f821 The above is a list of TWS users for FTA workstations listed in the TWSRegistry.dat file on node/ip testmaster. You will need to specify the correct TWS user for TWS workstation horblm82. Enter the TWS user for workstation horblm82 (node/ip testmaster) or press enter to obtain list of TWS users on node/ip testmaster. ->Figure 52 List of FTA node TWS instance users Provide the Tivoli Workload Scheduler user for the specified FTA; you may be prompted for the root password for the FTA node. Refer to Figure 53. Enter the TWS user for workstation horblm82 (node/ip testmaster) or press enter to obtain list of TWS users on node/ip testmaster. -> e82pdm Will try to validate TWS user e82pdm and that it manages TWS workstation horblm82. You may need to provide root password for node/ip testmaster more than once. Password:Figure 53 FTA TWS user prompt and root password prompt Autoinstall.sh Utility Script 43
  44. 44. vi. Enter root password of the FTA node. Once the TWSuser for FTA has been validated, information about the FTA will be extracted. Extracted FTA workstation information is obtained from the master Symphony file, from the FTA localopts, and TWSregistryt.dat files. The extracted information will be displayed and will prompt for the local base path for fixpack files. Refer to Figure 54. Logon user e82pdm exists. The TWS user e82pdm will be used for TWS workstation horblm82. Will try to determine OS and current TWS version for FTA horblm82. FTA horblm82 should be linked, this may take a few seconds. Extracted TWS version for horblm82 is 8.2 Will use TWS version 8.2.0. Extracted OS for horblm82 is HP-UX. OS HPUX will be used for horblm82. Provide base path for patches for FTA horblm82 on testmaster on current TWS version. Path should start with slash / -> Figure 54 Validate user and prompt for fixpack base path Example 8 Fixpack base path requirements The following naming convention. The fixpack directory should have a common base path followed by TWSversion/OS (/patchesbasepath/twsversion/os). Example: Base path directory for AIX FTA currently on TWS 8.3 /images/patches/8.3.0/aix Where: patchesbasepath = /images/patches twsverison = is 8.3.0 (use 3 digit format) os = aix (aix, hpux,linux_i386 or solaris) vii. Provide the fixpack base path for FTA (see base path requirements in Example 8).44 Autoinstall.sh Utility Script
  45. 45. Provide base path for patches for FTA horblm82 on testmaster on current TWS version. Path should start with slash / -> /images/patches/8.2.0/hpux You may need to provide the root password for taos. Password:Figure 55 Password prompt Note: When the fixpack path for fixpacks is created in the base patch path, it must be fp##, where “fp” text is in lowercase and “##” is fixpack number in two digit format. Provide the two digit fixpack number when replying to the fixpack prompt. Because each fixpack includes all fixes for previous fixpacks, entering multiple fixpacks for the same FTA workstation is not required. viii.Provide the root password for FTA; it may prompt for root password if an SSH certificate does not exist. Once the path has been validated it will ask if you want to use the specified path. Refer to Figure 56. You may need to provide the root password for taos. Password: Path /images/patches/8.2.0/hpux exists Enter y, to use this path or enter n to specify another path. ->Figure 56 Fixpack path validation and prompt ix. Reply “y” to use the specified path. Once the base path has been confirmed, the FTA definition file will be created for the FTA. The script will ask to add or update another FTA or to exit the utility. Refer to Figure 57. Autoinstall.sh Utility Script 45
  46. 46. Enter y, to use this path or enter n to specify another path. -> y The extracted value in the "thiscpu" field of localopts for user e82pdm is: horblm82 User e82pdm, TWS current version 8.2.0, OS HPUX and base patch path /images/patches/8.2.0/hpux for FTA workstation horblm82 on node/IP testmaster basic information will be used for TWS FTA and will be added to: /etc/TWS/MDM.m821a.m821a/FTA.horblm82 Do you want to add or update another FTA? To add or update another FTA enter (a) To go back to FTA Utilities Menu enter (b) To exit utility enter (e) Enter a, b or e to exit -> Figure 57 Create FTA.workstation file x. Reply to prompt; a will prompt FTA to add or update, “b” will return to the FTA Utilities Menu, and e will exit the utility script. Temporary files generated by the script will be removed when exiting the script. Refer to Figure 58. Enter a, b or e to exit -> e The current process id is 28800, removing all temporary files with .28800 extension in the /tmp directory. Exiting ./autoinstall.sh script. Figure 58 Exit script Update an Existing FTA.workstation File Press <Enter> to display a current list of workstations in the master Symphony file.46 Autoinstall.sh Utility Script
  47. 47. Note: The FTA must exist in the Symphony file to be linked to the master, to extract and update the required information for the FTA.workstation file. i. Enter the name of the UNIX FTA workstation, to update. The FTA must exist in the master’s Symphony file. The script will extract specific information to update the FTA.workstation file. It will display existing information and ask if you want to use this information. Refer to Figure 59. Enter a valid FTA workstation name to add or update. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> m82a Input value is M82A. TWS workstation M82A on node/ip taos is a UNIX FT-AGENT ie.. an FTA. TWS workstation M82A on node taos is valid, will add or update. Will determine if basic information for FTA m82a on master m821a exists. Information for m82a exists in file /etc/TWS/MDM.m821a.m821a/FTA.m82a Basic information for FTA m82a: CPUNAME=m82a NODENAME_IP=taos TWSUSER=m82a VERSION=8.2.0 OS=HPUX BASEPATCHPATH=/images/patches/8.2.0/hpux Do you want to use above information? (Enter y or n) ->Figure 59 Display existing FTA.workstation definition file information ii. Reply “n” to proceed. You will be prompted to provide the Tivoli Workload Scheduler user for the FTA workstation. Refer to Figure 60. Autoinstall.sh Utility Script 47
  48. 48. Do you want to use above information? (Enter y or n) -> n You will need to create an updated information file for TWS workstation m82a. Additional information is required for TWS workstation m82a. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> Figure 60 Provide Tivoli Workload Scheduler user for FTA.workstation prompt iii. Provide the Tivoli Workload Scheduler user for the FTA workstation. Once the TWSuser for FTA has been validated, information about the FTA will be extracted. Extracted FTA workstation information is obtained from the master Symphony file, from the FTA localopts, and TWSregistryt.dat files. The extracted information will be displayed and will prompt for the local base path for fixpack files. Refer to Figure 61.48 Autoinstall.sh Utility Script
  49. 49. Enter the TWS user for workstation m82a (node/ip taos) or press enter to obtain list of TWS users on node/ip taos. -> m82a Will try to validate TWS user m82a and that it manages TWS workstation m82a. You may need to provide root password for node/ip taos more than once. Password: The extracted value in the "thiscpu" field of localopts for user m82a is: m82a Logon user m82a exists. The TWS user m82a will be used for TWS workstation m82a. Will try to determine OS and current TWS version for FTA m82a. FTA m82a should be linked, this may take a few seconds. Extracted TWS version for m82a is 8.2 Will use TWS version 8.2.0. Extracted OS for m82a is HP-UX. OS HPUX will be used for m82a. Provide base path for patches for FTA m82a on taos on current TWS version. Path should start with slash / ->Figure 61 Validate user and prompt for fixpack base path iv. Provide the fixpack base path for FTA (see base path requirements in Example 9).Example 9 Fixpack base path requirementsThe following naming convention.The fixpack directory should have a common base path followed byTWSversion/OS (/patchesbasepath/twsversion/os).Example: Base path directory for AIX FTA currently on TWS 8.3 /images/patches/8.3.0/aix Autoinstall.sh Utility Script 49
  50. 50. Where: patchesbasepath = /images/patches twsverison = is 8.3.0 (use 3 digit format) os = aix (aix, hpux,linux_i386 or solaris) Provide base path for patches for FTA m82a on taos on current TWS version. Path should start with slash / -> /images/patches/8.2.0/hpux You may need to provide the root password for taos. Password: Figure 62 Password prompt Note: When the fixpack path for fixpacks is created in the base patch path, it must be fp##, where “fp” text is in lowercase and “##” is fixpack number in two digit format. Provide the two digit fixpack number when replying to the fixpack prompt. v. Provide the root password for FTA, it may prompt for root password if an SSH certificate does not exist. Refer to Figure 62. Once the path has been validated it will ask if you want to use specified path. Refer to Figure 63. Path /images/patches/8.2.0/hpux exists Enter y, to use this path or enter n to specify another path. -> Figure 63 Fixpack path validation and prompt Once the base path has been confirmed, the FTA definition file for the FTA will be updated. The script will ask to add or update another FTA, go back to FTA Utilities Menu, or to exit the utility. Refer to Figure 64.50 Autoinstall.sh Utility Script
  51. 51. Enter y, to use this path or enter n to specify another path. -> y Base patch path /images/patches/8.2.0/hpux will be used for m82a User m82a, TWS current version 8.2.0, OS HPUX and base patch path /images/patches/8.2.0/hpux for FTA workstation m82a on node/IP taos basic information will be used for TWS FTA and will be added to: /etc/TWS/MDM.m821a.m821a/FTA.m82a Do you want to add or update another FTA? To add or update another FTA enter (a) To go back to FTA Utilities Menu enter (b) To exit utility enter (e) Enter a, b or e to exit ->Figure 64 Update FTA.workstation file vi. Reply to the prompt; “y” will prompt FTA to add or update, “b” will return to FTA Utilities Menu, and “e” will exit the utility script. Temporary files generated by the script will be removed when exiting the script. Refer to Figure 65. Enter a, b or e to exit -> e The current process id is 28800, removing all temporary files with .28800 extension in the /tmp directory. Exiting ./autoinstall.sh script.Figure 65 Exit scriptDelete an FTA file i. At the FTA Utilities Menu screen, enter d to delete an FTA.workstation file. Refer to Figure 66. Autoinstall.sh Utility Script 51
  52. 52. FTA Utilities Menu To add or update an FTA file enter (a). To delete an FTA file enter (d). To export the utility scripts to an FTA enter (x). To go back to Main Utilities Menu enter (b). To exit utility enter (e). Enter a, d, x, b or e -> d Enter name of FTA file (do not use *) to delete, press enter to get a list of FTA files or e to exit utility. -> Figure 66 FTA Utilities menu ii. Press <Enter> to get a list of the defined FTA.workstation files. Refer to Figure 67. Enter name of FTA file to delete, press enter to get a list of FTA files or e to exit utility. -> <enter> /etc/TWS/MDM.m821a.m821a/FTA.horblm82 /etc/TWS/MDM.m821a.m821a/FTA.m82a Enter name of FTA file to delete, press enter to get a list of FTA files or e to exit utility. -> Figure 67 List of defined FTA.workstation definition files. iii. Enter the name of the FTA to delete; there is no need to precede ftaname with “FTA.” text. Refer to Figure 68. Enter name of FTA file (do not use *) to delete, press enter to get a list of FTA files or e to exit utility. -> horblm82 Do you want to delete the FTA file? (Enter y, n or e to exit) -> Figure 68 FTA name to delete52 Autoinstall.sh Utility Script
  53. 53. Note: Do not use “*” asterisk in the FTA name. iv. Reply “y” to delete the file; the script will remove FTA.workstation file. Next the prompt will ask to delete another FTA, return to the FTA Utilities Menu, or exit the utility. Refer to Figure 69. Do you want to delete the FTA file? (Enter y, n or e to exit) -> y File /etc/TWS/MDM.m821a.m821a/FTA.horblm82 exists and will be removed. Do you want to delete another FTA? To delete another FTA enter (d) To go back to FTA Utilities Menu enter (b) To exit utility enter (e) (Enter d, b or e to exit) ->Figure 69 FTA delete confirmation v. Reply to the prompt.Export Utility Scripts to FTA i. At the FTA Utilities Menu screen, enter x to export the utility scripts to FTA. Refer to Figure 70. Autoinstall.sh Utility Script 53
  54. 54. FTA Utilities Menu To add or update an FTA file enter (a). To delete an FTA file enter (d). To export the utility scripts to an FTA enter (x). To go back to Main Utilities Menu enter (b). To exit utility enter (e). Enter a, d, x or e -> x This is the FTA export util scripts module. Enter a valid FTA workstation name to receive utility scripts. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> Figure 70 Export utilities FTA workstation prompt ii. Enter the name of the FTA to receive the utility scripts (do not enter the node/ip), or press <Enter> to view a list of FTA workstations. Refer to Figure 70. Note: Use the FTA workstation name not the node/ip for workstation. Utility scripts may be sent to an FTA prior to creating the FTA.workstation file. The export uses UNIX scp, providing the root password for the FTA workstation, which may be required if an SSH certificate does not exist. Pressing <Enter> will display list of all workstations that exist on the current master’s Symphony file. Refer to Figure 71.54 Autoinstall.sh Utility Script
  55. 55. Enter a valid FTA workstation name to receive utility scripts. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> <enter> Below is a list of workstations for m821a master user. M821A M821A AF T 38211 taos HORBLM82 HORBLM82 A AT 31822 testmaster M82A M82A AFAT 31822 taos XA-FUEGO M82A A AT 31822 fuego.tivlab.austin.ibm.com Enter a valid FTA workstation name to receive utility scripts. Press enter to display a list of valid workstations in current Symphony file on master cpu. ->Figure 71 List of workstations on the current master Symphony file The script will verify that the provided name is an FTA workstation. Refer to Figure 72. Enter a valid FTA workstation name to receive utility scripts. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> xa-fuego Input value is XA-FUEGO. TWS workstation XA-FUEGO on node/ip fuego.tivlab.austin.ibm.com is an UNIX X-AGENT, NOT a UNIX FTA. This utility may only patch UNIX FTAs. Enter a valid FTA workstation name to receive utility scripts. Press enter to display a list of valid workstations in current Symphony file on master cpu. ->Figure 72 Invalid agent type for workstation specified iii. Provide the name for a UNIX FTA workstation. After confirming that the provided name is for a UNIX FTA, the script will prompt for root password for FTA node/ip, if an SSH certificate does not exist. Refer to Figure 73. Autoinstall.sh Utility Script 55
  56. 56. Enter a valid FTA workstation name to receive utility scripts. Press enter to display a list of valid workstations in current Symphony file on master cpu. -> m82a Input value is M82A. TWS workstation M82A on node/ip taos is a UNIX FT-AGENT ie.. an FTA. TWS workstation M82A on node taos is valid, will receive utility scripts. You may need to provide root password for node/ip taos more that once. Will attempt to transfer files to FTA m82a on node/ip taos. Password: Figure 73 Confirmed FTA workstation, prompt for root password iv. Provide root password for the FTA node/ip. You may need to provide the password twice. Review the transfer messages to verify that they completed successfully. Refer to Figure 74.56 Autoinstall.sh Utility Script
  57. 57. Will attempt to transfer files to FTA m82a on node/ip taos. Password: patch_lau.sh 100% 6243 0.0KB/s 00:00 Password: patch_install.sh 100% 19KB 0.0KB/s 00:00 Review the above scp messages and verify that secure copies were successful before proceeding. Do you want to export utility scripts to another FTA? To export utility scripts to another FTA enter (x) To go back to FTA Utilities Menu enter (b) To exit utility enter (e) Enter x, b or e to exit -> Figure 74 Utility script transfer confirmation v. Reply to the prompt to continue or to exit.Job Stream Utilities Specific steps are required after creating the job definitions for the fixpacks and must be performed in a specific order. You must create the job stream definitions files, add the job and job stream definitions and finally rename the patch_job_def file. The renamed patch_job_def file will have an extension of _mmddyy_hhmmss, where mmddyy is the month, day, and year, and hhmmss is hour, minute, and second. These maintenance operations may be performed from the Job Stream Utilities Menu. You will need proceed past some of the general menus or prompts to get to the Job Stream Utilities Menu. If an MDM already exists it will display information for MDM and ask if you want to use the existing MDM definition. 1. Reply to the prompt with “y” to use the existing MDM definition. Refer to Figure 75. Autoinstall.sh Utility Script 57

×