You can edit any part of an existing deployable package except the operating system and platform.
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.
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.
To automatically update the components in deployable packages, do not include PATROL Agents or PATROL Agent patches in the deployable packages.
Perform one of the following actions, depending on your requirements:
Add or edit the installation details of existing or new components.
For monitoring solutions that contain sub-components, select the sub-components to be included in the deployable package.
To reduce the deployable package file size, choose only the sub-components that you will use.
Provide PATROL Agent related information:
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.
Specify the installation directory.
Perform one of the following actions:
Specify the PATROL 3.x product directory.
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.
You can connect to the local integration service installed on the Infrastructure Management Server, or download and install a new instance of Integration Service.
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".
(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.
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 to version 10.7, 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.
Click Finish to skip to the Installation Package Details window.
If you add or remove a component from the deployable package, the Finish button does not appear and you must complete the configuration process.
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.