Important

   

This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

Adding software to the Depot

You can add a software package to the Depot, which you can then deploy to servers. A software package consists of all the files necessary to perform an unattended installation of a software executable.

When you add software to the Depot, the system provides built-in support for packaging many types of software. If you are adding one of these types, the system automatically generates the appropriate install and uninstall commands. If necessary, the standard commands include references to support files. For example, installation of some types of software requires a response file. When you add software to the Depot, you must provide the location of any support files.

You can also add custom software to the Depot by packaging any kind of software that provides a command line-based, unattended installation. For custom software packages, you must determine the necessary command line options for silently installing and uninstalling the software. The install and uninstall commands should reference required support files.

Adding Windows hotfixes to the Depot requires a similar procedure. See Adding a hotfix to the Depot.

After adding a software package to the Depot, you can deploy it using a Deploy Job. For a description of this procedure, see Creating a Deploy Job. You can also modify the definition of an existing software package or modify the contents of a software package).

To add software to the Depot

  1. Perform one of the following actions to open the Add Depot Software wizard:
    • Using the Depot folder, right-click the folder where you want to add a software package. Select New > Software, and then select the type of software package to create. 

      Note

      If you are trying to add an AIX patch with extension epkg.Z in DEPOT as AIX Patch, and the Invalid AIX Header Magic Number error message appears, import the AIX Patch as Custom Software Package, as described in the knowledge base article, BMC BladeLogic Server Automation support of “EPKG” files as part of AIX Patch Analysis.

    • Using the Servers folder, right-click a server and select Browse, which displays the Live node in a tab in the content editor. Using the File System object type, select one or more files or directories and right-click. Or, using a software server object type, such as a Solaris patch or an HP-UX bundle, select one or more server objects, right-click, and select Add To Depot As. Then select the type of software package to create.

      Notes

      Selecting Add To Depot > Hotfix initiates a related procedure, described in Adding a hotfix to the Depot.

      Unix file system permissions are not preserved when adding depot software. When the payload is deployed to the target(s), it is granted read, write, and execute (0700) permissions for the local user running the deployment. Any required permission changes must be performed in the installation routine.

    • Using the results of a Snapshot Job, select software packages to add to the Depot, as described in Adding software to the Depot from snapshot results.
    • Using the Select Matching Software window, you can add software packages to the Depot, as described in Matching software with depot items. The Select Matching Software window appears in many contexts throughout the TrueSight Server Automation Console.
  2. In the Select Installable Sources dialog box, select the installable file.

    The Select Installable Source dialog box provides options for accessing the installable file. Use the hierarchical tree to browse to the location where the installable file is saved and select the file.

    You can browse and select the source file from the following locations:

    • Servers
    • Local Computer
    • Web Repositories NEW

    Alternatively, you can manually enter the path to the installable file by using the Source Location field. The file paths can include parameters. You can enter parameters manually or click Select Property, see Inserting a parameter for more information.

    Depending on how you want to access the installable file, select either of the following option buttons:

    FieldDescriptions
    Upload source to File ServerSelect this option if you want to copy the installable file to the file server. When you select this option, you cannot edit the contents of the Source Location field.
    Refer to source at its current locationSelect this option if you want the installable file to reside at network location until deployment. When you select this option, you cannot use the hierarchical tree to select the source files. Under Refer to source at its current location, select one of the following options:
    • Copy to Agent at staging — The Application Server copies the installable file to a staging directory on the agent during the staging phase of a Deploy Job.
      To use this option, the Source Location field must provide a URL that complies with TrueSight Server Automation requirements for network data transmission, including a data transmission protocol of RSCD, NFS, or SMB. For details about the required syntax, see URL syntax for network data transmission.
    • Agent mounts source for direct use at deployment (no local copy) — The Deploy Job instructs an agent to mount or map the device specified in the URL and deploy the software package directly to the agent. When you select this option, the agent uses the data transmission protocol specified in the URL to access the specified source files. The installable file is not copied to a staging area on the agent, so no local copy of the source file is created.
      To use this option, the Source Location field must provide a URL that complies with TrueSight Server Automation requirements for network data transmission, including a data transmission protocol: either NFS or SMB. For details information about the required syntax, see URL syntax for network data transmission.

      Note

      (Only for Windows 2012 targets) Before you enable the Agent mounts source for direct use at deployment (no local copy) option, you need to add the mounted device in the security zone of the target. This can be done by making the following changes to the registry of the target.

      1.  Under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscRanges\, create a key with the name Range1. If key Range1 already exists, create a key with the next available number (for example Range2, Range3, Range4 and so on).
      2. Create the following values under the Range1 key:

        Value Name

        Value Data

        :Range<mountedDeviceIPAddress>
        file1 hexadecimal

  3. Provide information for the wizard, as described in the following sections:
  4. After completing the last step of the wizard, click Finish.
    A background process saves the software package to the Depot. Depending on how you have specified behavior for background processes, either a dialog box opens or the Show background operations icon appears in the lower right corner of the console. Both indicate an operation is running in the background.
Was this page helpful? Yes No Submitting... Thank you

Comments