Creating a deployable package

As an administrator, you can select monitor installation components, such as the PATROL Agent and monitoring solutions to create a deployable package. The components can then be installed together using the deployable package. You can reuse the deployable packages, or deploy the packages to multiple computers.

Before you begin

• Ensure that you have downloaded and imported the KM.
• Ensure that you have reviewed the Deployable packages best practices .

To create a deployable package

1. In the navigation pane, expand Administration, select Repository, and select the Deployable Packages tab.

2. ClickCreate Deployable Package.
   The Create Deployable Package wizard starts.

3. On the Installation Package Solution Selection page, select the operating system for which you want to create a package, and then select a platform on which you want to install the package.
   The list of components in the repository that are supported on the specified operating system and platform is displayed.

4. Select the components that you want to include in the package. Ensure that you select the JRE solution according to your operating system.

5. From the Version list, select the version of the component that you want to 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.

   Important

   Deployment from the console is not supported if the deployable package contains the following components:

   • PATROL Configuration Manager
   • PATROL Classic console
   • Oracle JRE only

   If any of these components are present in the deployable package, the package is not seen in the Deploy and Install Packages screen.

   
   

6.  For monitoring solutions that contain sub-components, select the sub-components to be included in the deployable package. (This screen is not available in ProactiveNet and Central Monitoring Administration console.) 

7. 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.
      Note that the PATROL products are installed one level below the BMC products installation directory.

      Note

      The default installation directory is C:\Program Files\BMC Software and not C:\Program Files (x86)\BMC Software. If you have installed a previous version of the product, use the path specified for that installation.

   2. Specify the PATROL 3.x product directory.
      Follow the instructions in the Important Information section of the wizard.
   3. 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.
   4. 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, enter DOMAIN_NAME\account name; otherwise, enter the local account. To allow the PATROL Agent to use the Local System account as the default account, leave the username and password fields blank.
   5. Select the security level.
      The default security level is appropriate for most environments.
   6. 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.
   7. 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.

      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.

   8. (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 PATROL Agent to version 10.0, 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 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.

   9. (Optional) Provide the RTSERVERS variable details.
      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.
   10. Configure the firewall.
       You can choose to automatically add the components to the firewall exception list.

8. 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.

9. In the Installation Package Details window, enter the following information:

   • Name: The name of the deployable package. 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.

10. Perform one of the following steps:

    • To save the package for future installation on the current host or other hosts, click Save.

    • To save the package and download it immediately, click Save and Download.

      Tips

      • To deploy packages to PATROL Agents earlier than version 10.0, use the Save and Download option. For more information, see Deploying packages to earlier versions of PATROL Agents.
      • Pop-up blockers might prevent downloading the deployable package when you select Save and Download. Turn off pop-up blockers or click the pop-up blocked icon in the browser navigation bar to start downloading the deployable package.

    A template of the package is saved to the installationDirectory\truesightpserver\data\pproxy\installer_templates folder and is listed in the Deployable Packages tab. 

Where to go from here

After creating deployable packages, deploy them to PATROL Agents.