Editing deployable packages

You can edit any part of an existing deployable package except the operating system and platform.

Note

You can delete predefined packages but cannot edit them. To save a predefined package with a different name, edit the predefined package, provide a different package name, and select Save As.

  1. Log on to the TrueSight console. In the navigation pane, expand Administration, select Repository, and select the Deployable Packages tab.
  2. In the list of deployable packages, select the action menu for the deployable package to edit, and select Edit.
    The Edit Deployable Package wizard starts.
  3. From the Solutions list, select the components that you want to include in the package.

  4. From the Version list, select the version of each component that you include in the package.
    By default, the latest version available in the Presentation Server is selected. Select latest to automatically update the package with latest versions of components when they are imported to the Presentation Server.

    Note

    To automatically update the components in deployable packages, do not include PATROL Agents or PATROL Agent patches in the deployable packages.

  5. Perform one of the following actions, depending on your requirements:
    • Add or edit the installation details of existing or new components.
Click here to view the instructions.

For monitoring solutions that contain sub-components, select the sub-components to be included in the deployable package.

Tip

 To reduce the deployable package file size, choose only the sub-components that you will use.

Package_Subcomponents.png

Provide PATROL Agent related information:

Note

The following fields depend upon the components that are included in the deployable package. Not all fields may be displayed while creating a deployable package.  

  1. Specify the installation directory.
    Perform one of the following actions:
    • Proceed with the installation in the default directory.
    • Enter a different directory for installation.
    • Leave the field blank and proceed with the installation.
      You can leave the field blank if you do not know the location where the KM or PATROL Agent is installed. When you leave the field blank, the correct directory is automatically selected through the BMC_BASE variable.
  2. Specify the PATROL 3.x product directory.
  3. Follow the instructions in the Important Information section of the wizard.
  4. For UNIX operating system, provide the System Root account details.
    Note: You can continue the package process without the Root details but you will need to complete the root configuration at a later time for the selected component to run correctly.

  5. Provide the PATROL default account credentials.
    You must create this account manually before continuing with the installation. If you plan to use a domain account, type the following otherwise type the local account details:

    1. (Windows) DOMAIN_NAME\account name
    2. (Linux) DOMAIN_NAME\\account name
      Double slash before the account name ensures that the account name is parsed correctly. While editing the package, if the double slash is deleted, type it again.

    Note

    To allow the PATROL Agent to use the Local System account as the default account, leave the username and password fields blank.

  6. Select the security level.
    The default security level is appropriate for most environments.
  7. Specify the PATROL Agent port number.
    The port number is used by the PATROL Agent to communicate with the console. If you are installing a new version of the PATROL Agent over an existing one, ensure that you specify the same port number used by the earlier Agent.
  8. Provide the Infrastructure Management integration configuration:

    1. INTEGRATIONSERVICES variable: this variable is used for automatic registration of the PATROL Agent with Infrastructure Management.Enter one or more existing Integration Service(s) to connect to. Separate each entry by a comma and use the format Protocol:IntegrationServiceHostname:PortNumber. For example tcp:Integration Service Hostname:3183, where 3183 is the port on which the Integration Service host listens for an incoming PATROL Agent auto-registration connection.

      Note

      You can connect to the local integration service installed on the Infrastructure Management Server, or Downloading and installing a new instance of the Integration Service

    2. Central Monitoring Administration Tag(s):

      Provide comma separated tags that the PATROL Agent will use to get configuration from Central Monitoring Administration. Each tag follows the format TagName:Description. If there is a space in the description, enclose it with quotes. For example, WinOS:"Windows OS Monitoring".

    3. By default, Central Monitoring Administration manages the PATROL Agent(s) configuration. If you select No, you can enable policy management from Central Monitoring Administration later. For more information, see Managing-Infrastructure-Management-devices-from-the-TrueSight-console.

  9. (Optional) Provide the cell configuration details.
    Enter the Infrastructure Management encryption key and the cell details in the format Host/Port.

    You can choose to route events via an Integration Service.

    Note

    To route events via an Integration Service, the /EventSetup/Configuration/ForwardEventsToIS PATROL Agent pconfig variable must be set to Yes. 

    During the upgrade of earlier versions of the BMC PATROL Agent, ensure to provide the correct Cell name in the Infrastructure Management - Primary Cell and Infrastructure Management - Secondary Cell fields in the Infrastructure Management Performance Management Cell Configurations installation screen.

    Proceeding with the default value resets the Event Destination of the BMC PATROL Agent to localhost/1828.

    If /EventSetup/Configuration/ForwardEventsToIS is set to Yes and Infrastructure Management - Primary Cell is set to localhost/1828, then the PATROL Agent sends events to the local Cell of the Integration Service.

  10. (Optional) Provide the RTSERVERS variable details.
    BMC PATROL 7 products communicate with each other through one or more RTservers. For previously installed PATROL Agents (version 3.5 or later), you must set the RTSERVERS variable and restart the PATROL Agent. Provide comma separated RTSERVERS variables in the format protocol:hostname:port. For example, tcp:localhost:2059.
  11. Configure the firewall.
    You can choose to automatically add the components to the firewall exception list.

    • Click Finish to skip to the Installation Package Details window.

      Note

      If you add or remove a component from the deployable package, the Finish button does not appear and you must complete the configuration process.

  2. Review the deployable package details.If you added a monitoring solution that contains sub-components, click the plus sign to view the included sub-components.
  3. In the Installation Package Details window, modify the following information as needed:
    • To save the same package: Do not change the package name. Select Save to overwrite the package with the modified information.
      To create a new package: Provide a different package name. Select Save As to create a new package. No changes are made to the original package.
      Package name can contain only A-Z, a-z, 0-9, and underscore (_).
    • (Optional) Description: Enter a description of the package.
      The description is displayed in the list of deployable packages.
    • Format: The default file format for the operating system is automatically selected. Select a different format if required.
  4. A template of the package is saved to the <Presentation Server installation directory>\truesightpserver\data\pproxy\installer_templates folder and is listed in the Deployable Packages tab. 

 

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