Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Changing network-based software deploy options

Using the BLPackage editor, you can modify options for network-based deployments of software packages.

This procedure lets you modify the URL used to identify the location of a network-based software package. It also lets you specify how a network-based software package should be deployed to a target server.

The options described in this procedure are only available when a BLPackage includes software that was packaged using source files from a network location (rather than source files copied to the file server). In addition, the BLPackage cannot specify that the source files are soft-linked.

To change network-based software deploy options

  1. In the hierarchy view, select a software package included in the BLPackage. The right pane shows the attributes associated with that object.
  2. In the right pane, do any of the following:
    • Select Location and modify the path to the installable source files. A source file path can include parameters. Enter a parameter manually or click Select Property g_V95_SelectPropertyIcon.gif, which appears when you click in the Value column. (For more information about this tool, see Inserting-a-parameter.) If the package has a network-based location, the URL you enter must comply with the BMC Server Automation standard for network data transmission (see URL-syntax-for-network-data-transmission).
    • Select Staging and then click in the Value column. A drop-down list appears. Select one of the following:
      • Copy to Agent at stage — The Application Server mounts/maps the device specified in the URL and copies all source files from this network location to the staging directory on the agent during the staging phase of a Deploy Job.

      • Agent mounts source for direct use — The agent on the target server mounts/maps the device specified in the URL and deploys the software package directly to the target server. The software package is not copied to a staging area on the server. The agent uses the protocol specified in the URL to access the specified source files. This option does not create a local copy of the source files on the target server.
        To use this option, the object being deployed must provide a URL that complies with BMC Server Automation requirements for network data transmission, including a data transmission protocol: either NFS or SMB. See URL-syntax-for-network-data-transmission for detailed information about the required syntax. 

        Warning

        Note

        If you deploy this package using a large network-based deployment, first consider the capabilities of your network and the server being mounted or mapped. When you deploy to a large number of target servers, the agents on those servers all need to mount or map the host where source files are located.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Server Automation 8.3