Professional Documents
Culture Documents
Table of Contents
INSTALLING THE BPPM SERVER AND INTEGRATION SERVERS ............................................................... 3
OVERVIEW ...................................................................................................................................................................................... 3
DOWNLOAD AND EXTRACT THE FILES ....................................................................................................................................... 4
PREPARING YOUR BPPM ENVIRONMENT:................................................................................................................................ 4
INSTALLING THE BPPM SERVER ON WINDOWS ..................................................................................................................... 5
Validate that the BPPM server is up and running ..................................................................................................8
Apply the license files .........................................................................................................................................................9
INSTALL THE BPPM INTEGRATION SERVICES ....................................................................................................................... 11
CONNECTING THE IS NODES TO THE BPPM SERVER ........................................................................................................... 17
CONFIGURING THE CELLS .......................................................................................................................................................... 19
CREATING AND INSTALLING PATROL AGENT AND KM PACKAGES ...................................................... 22
ADDING THE EXTENDED REPOSITORY PACKAGE TO CMA. .................................................................................................. 22
Option 1: using the pw commands ............................................................................................................................. 22
Option 2: using CMA ........................................................................................................................................................ 23
CREATING AN INSTALL PACKAGE OF PATROL FOR WINDOWS: ........................................................................................ 26
INSTALL THE WINDOWS AGENT PACKAGE TO YOUR WINDOWS IS SERVER ..................................................................... 33
GENERAL OVERVIEW OF ADMINISTRATION ................................................................................................ 34
PRIVILEGE MANAGEMENT ......................................................................................................................................................... 35
CREATE A ROLE ........................................................................................................................................................................... 35
CREATE A USER GROUP AND ASSOCIATE THE CREATED ROLE ............................................................................................. 36
CREATE A USER AND ASSOCIATE TO THE USER GROUP ...................................................................................................... 37
VISUALIZING COMPONENT STATUS AND HEALTH. .................................................................................... 38
OVERVIEW: .................................................................................................................................................................................. 38
INTEGRATION SERVICE .............................................................................................................................................................. 39
PATROL AGENTS ......................................................................................................................................................................... 40
MARKED FOR DELETION (MFD) ............................................................................................................................................. 40
POLICY STATUS ........................................................................................................................................................................... 42
OPERATING SYSTEM VERSION .................................................................................................................................................. 42
UTILITIES...................................................................................................................................................................................... 43
AGENT QUERY TOOL .................................................................................................................................................................. 43
CREATING A TIMEFRAME IN CMA. .................................................................................................................... 44
ADD A TIMEFRAME TO BPPM SERVER USING THE CMA ..................................................................................................... 45
ADD A ONCE OCCURRING TIMEFRAME .................................................................................................................................... 45
ADD A WEEKLY OCCURRING TIMEFRAME ............................................................................................................................... 46
CREATING/EDITING GLOBAL THRESHOLDS IN CMA. ................................................................................ 47
UNDERSTANDING EVENT THRESHOLDS .................................................................................................................................. 48
DECIDE ON THE TYPE OF THRESHOLD ..................................................................................................................................... 48
BPPM IS FAILOVER CLUSTERING ...................................................................................................................... 51
INSTALL BPPM IS ON DIFFERENT SYSTEMS .......................................................................................................................... 51
ADD THE NEW INTEGRATION SERVICE TO BPPM SERVER USING CMA ........................................................................... 55
CREATE THE IS CLUSTER USING CMA .................................................................................................................................... 56
BASIC POLICY MANAGEMENT: ........................................................................................................................... 59
LEVERAGING PRECEDENCE IN POLICY MANAGEMENT ......................................................................................................... 59
WALK THROUGH EXERCISE: ..................................................................................................................................................... 60
This section covers the install of BPPM 9.5 including the BPPM server and two
Integration Service Nodes. One Integration Server will be installed on Windows
and the other on RedHat 6.2. After completion of this section these major
infrastructure components will be installed and configured so that the Integration
Service nodes are connected to the BPPM server and communicating with
performance matrix being populated in the database for analytical purposes.
Download and extract the files
http://webapps.bmc.com/epd
Log in using your Customer Support credentials
Navigate to:
BMC ProactiveNet Performance Management Suite
BMC ProactiveNet Performance Management Suite 9.5.00
BMC ProactiveNet Performance Management Suite (Monitoring, Analytics, Diagnostics, Event
and Impact) 9.5.00
BMC ProactiveNet 9.5.00
Check for available product patches under the Product Patches tab and
download if any exist:
Instructions to apply the patch will be included in the documentation associated
with that patch.
https://docs.bmc.com/docs/display/public/proactivenet95/Preparing+host+comput
ers+for+installation
Perform all OS applicable pre-installation tasks listed in the following link:
https://docs.bmc.com/docs/display/public/proactivenet95/Preinstallation+tasks
Progress through the install screens accepting the license agreement and
selecting defaults until you get to the screen that allows you to select the Single
Server or Multiple Server options. For the purposes of this guide, select the
Single Server option and click Next.
Select the ZIP file for the Base Repository from the
~/<RepositoryExtractLocation\9.5_base-<build#>.zip directory similar to the
example below. The Extended Repository is loaded later in this document.
The installation completion screen will display an installation log including any
errors. Verify that there are no installation errors from the installation completion
screen. Click the Done button when you are finished verifying that there are no
installation errors.
If Email is configured, verify that you received an email from the BPPM server
that you just installed.
Windows: Right Mouse Button (RMB) on the BPPM icon in the system tray
and select System Status. The following command window should be
displayed automatically.
Open new telnet/cmd window and run the license update command as shown
below:
Run the install package you just downloaded by right-clicking on it and choosing
Run as Administrator.
Select the defaults for all prompts and make sure you choose to install the
Integration Service and the Remote Cell.
For Linux platforms, the BPPM component installs require specific 32 bit
compatible library files that are not already installed on most RedHat servers.
This applies to the BPPM server, Integration Services, and PATROL agents.
The packages containing the necessary libraries are:
libXtst.i686
glibc.i686
libstdc++.i686
libstdc++.x86_64
compat-libstdc++-296.i686
compat-libstdc++-33.i686
compat-libstdc++-33.x86_64
pam.i686
You can install using either yum or rpm. The preferred method is yum as it will
automatically apply any dependencies.
NOTE:
You might get an error that references a missing library named libstdc++-libc6.11.so.2 during the installation of the BPPM server or Integration Services on
RHEL. This might not be resolved using yum in other environments. If this
happens on RHEL 6.2 try the following:
Download the following RPM packages from a RPM source (for example
http://rpm.pbone.net/ )
libstdc++-4.4.7-3.el6.i686
libstdc++-devel-4.4.7-3.el6.i686
compat-libstdc++-33-3.2.3-69.el6.i686
Install the RPM packages in the order listed above using the following command:
rpm -ivh <RPM file>
Use the following command to uninstall an RPM package:
rpm -e <RPM file>
If you get a compatibility error when installing compat-libstdc++-33-3.2.369.el6.i686 uninstall the RPM that the compatibility error indicates is already
installed, and then install compat-libstdc++-33-3.2.3-69.el6.i686.
You will install the Integration Server on the RedHat node in this step. Be certain
that you have completed installing the required libraries before attempting to
continue.
Log into your BPPM server (In this case it is a Windows system)
Launch a cmd window using Run as Administrator
Change directories to <BPPMExtractLocation>\BPPMAgent\Linux.
FTP the following two files using the put command to transfer the two files from
your BPPM server to your RedHat node.
bmc_pnet_is_install.options
BPPMAgent9.5_b241177692.bin
The instructions above are shown executed in the screen shot below.
-P installLocation=/opt/bmc/BPPMAgent
-A IM
-A IEA
-A IELA
##### Component Selection settings
#Set IS_INSTALL_INTEGRATION_SERVICE=true if you want to install all
the components Integration Service
-J IS_INSTALL_INTEGRATION_SERVICE=true
#Set IS_INSTALL_REMOTE_CELL=true if you want to install Remote
Cell.
-J IS_INSTALL_REMOTE_CELL=true
##### Agent port
**NOTE** Make sure to remove any # sign from the second
highlighted line if it exists
(e.g. J IN_INSTALL_REMOTE_CELL=true)
Save the file and quit vi.
Change permissions on the install binary to 744 and initiate the install of the
Integration Services using the commands as shown below.
After the install completes, check the install log for errors. You will find the install
log in the following location.
/tmp/bppm_agent_install_log.txt
Use the following command to search for errors.
#cat /tmp/bppm_agent_install_log.txt | grep ERROR
The install process starts the Integration Service processes after the install is
complete. Verify that the Integration Service and cell are running.
#ps ef | grep BPPM
The ps command should return a list of processes running under the BPPMAgent
directory. These will include java processes, mcell, and other BPPM IS
processes.
Click the Add button (green circle with a +) to add a remote Integration Server.
Fill in the fields for your Integration Service running on Windows as shown in the
example below. Enter the values for your Integration Service node.
You can specify a descriptive value for the Integration Service Name as noted by
the red arrow. You must enter the appropriate DNS hostname or IP address for
the Integration Service node.
Notice you can designate where the cell on the Integration Service node will send
events at this point in the install. You can also define or select a cluster for the
Integration Service. Additionally, you can flag the integration services as a
Staging node.
After entering the appropriate values click the Add button.
The Integration Service should appear in the server list as shown below.
Add your Integration Service node running on RedHat in CMA following the steps
outlined above.
$MCELL_HOME/etc
%MCELL_HOME%/etc
Add an entry for the BPPM server embedded cell as shown by the format below
and save the mcell.dir file.
Note: Use UPPERCASE for the first word in the line (e.g. CELL)
Format:
<BPPM Server>:1828
Example:
CELL pncell_clm-hou-006927
mc
clm-hou-006927:1828
Edit the mcell.dir file on the BPPM server. You will find the mcell.dir files under
the following location:
Linux:
$MCELL_HOME/etc
Add entries for both of the cells on your IS nodes as shown by the format below
and save the mcell.dir file.
Format:
cell
mc
<IS node>:1828
Example:
cell
cell
clm-hou-006977
clm-hou-006937
mc
mc
clm-hou-006977:1828
clm-hou-006937:1828
Add the cells on your Integration Service nodes to the administration cell on the
BPPM server. Use the command below to add the cells. The entire command is
entered on a single line. You will need to run the command for each of the cells
you are adding.
Format:
iadmin ac
name=<Cell_Name>:key=mc:primaryHost=<IS_node>:primaryPort=1828:
environment=Production:usergroups=*
Example:
iadmin ac name=clm-hou-006937:key=mc:primaryHost=clm-hou006937:primaryPort=1828:environment=Production:usergroups=*
Add the cells in the BPPM Ops Console. Click on the Navigation Pane Options
button. Select the admin cell and your remote cells under the Other Cells list
from the Navigation pane as shown below. Click the Ok button to save the
settings.
Overview:
This section demonstrates the ways of adding the Extended Repository.
There are two ways of adding the extended repository.
Adding
extended
repository
using the pw
commands
using the
CMA
functionality
5) In the import screen, select the Full Repository and click on import
6) In the next screen navigate to the 9.5 Extended Repository zip file in
the BPPM Server and click on Extract
By default the PATROL Agent is already selected for you. Select any additional KMs
by putting a check in the box next to the line item and click the Right Arrow.
Click Next
In the following screens, provide the required information and click Next
Click Next.
Leave the Yes radio button selected for Route events via Integration Service and
Click Next
If you are using Patrol Central and want this PATROL Agent to connect to an RTServer,
enter the appropriate information or blank out the default entry and click Next.
For Windows Servers, you will be prompted whether or not you want the installation
program to automatically update Windows Firewall settings. We suggest you select
Yes and click Next.
In the final screen, give this Deployment Package a name, short description of its
contents. Select the file type of .zip and click the Save Installation Package button
Download the saved file either to your desktop and ftp/transfer the package to the
desired target system(s) or connect to the CMA via a web browser from the system
you intend to install the PATROL Agent to and Download the saved Installation
Package directly on that system.
Click the Close button to exit.
If you have not already done so, create a default patrol user account. Ensure the
account is a member of the Local Administrators group
Navigate to the Windows server location where the PATROL Installation package
is saved as the patrol default account user.
Extract the installation package.
Open a cmd window and execute the RunSilentInstall.exe from the command
line.
Privilege Management
Overview:
This section demonstrates the configuration and usage of privilege management.
Create a role
Create a User
Group and
associcate the
created role
Create a USER
and associate
to the User
Group.
Create a Role
1. Login to the ADMIN UI of the BPPM Server.
2. Right click on Role and choose Add Role
Select the user group Example_Ug_2 from the Available User Groups and
move it to the Selected User Groups using the >> button. Click Add.
Login to the BPPM console as the Example_User_2 user and observe the
privileges.
Integration Service
Sl ICON
#
Meaning
Comment
Patrol Agents
Sl # ICON
1
The status of
the
Integration
Server.
Meaning
The status of the
Patrol Agent.
Meaning
The Green
plug indicates
that the IS node
is connected to
the BPPM server
On
disconnection the
plug will turn to
Red
Click on the
triangle next to
the IS.
Click on the
triangle before
the IS to list all
patrol agents
connected to the
selected IS node.
Comment
The Green plug
indicates that the
PATROL agent is
connected to the IS
node.
On disconnection
the plug will turn to
Red.
Comment
The
icon
represents MFD
In 9.5 we support
MFD for
Instances and
Devices only.
MFD is not
supported for IS
nodes.
Note: The following is
the general criteria to
set the MFD flag:
1. The IS node is
dis-connected (or
is down)
2. PATROL agent is
not connected to
the IS node.
3. The deviceassociated
instance is
deleted at the
PATROL agent.
4. The instance is
deleted at the
PATROL agent.
5. When the source
PATROL agent is
marked for
deletion.
Policy Status
Sl ICON
#
1
Meaning
Comment
Moving
your
mouse
over the
icon will
give you
more
information
about the
PATROL
agent.
GREEN good
RED one or more
policies was not
applied
successfully
Utilities
Sl ICON
#
1
Meaning
Comment
Execute. The buttons to the right of the Execute button are agent control buttons
that allow you to reinitialize, stop, reload and purge the agent.
Click on the
Add Icon
a. Enter Example_TimeFrame_1 in the name field
b. In the start field, enter the present time.
c. The end time should be 4 hours from now.
Click on the
Add Icon
a. Enter Example_TimeFrame_2 in the name field
b. In the start field, enter the 11:55 pm.
c. Duration end time should be after 3.5 hours
d. Select the alternate days starting from Monday.
Steps:
Decide on
the type of
Threshold
configure the
threshold
using CMA
Enable the
configured
threhsold.
Note: the attributes with a blue tick mark are enabled and the
ones with a KEY are KPIs.
2. Navigate to the Percentage Bandwidth Utilization of Host Network section.
a. Click on All Unix and Linux HP UX and Linux 9.12.00
Network
Steps:
Install BPPM IS on
different systems
Congigure the IS
Cluster by using the
Cluster configuration
feature of CMA.
c. Click on the
Add Icon and add the IS.
d. Enter your information using the example as shown below.
e. Make sure that the IS nodes are listed in the registered list.
c. Click on the
Add Icon and enter the details. From the available
integration server list search for your IS nodes and move them to
the selected list.
d. Note that you have to make 1 of them the primary and the rest
secondary.
Notice that you can sort on the Precedence Column letting you view all Policies
by precedence number. When you have a question about a policy and which
other policies may be effecting your desired result, sorting by precedence will
help show you possible policies to investigate for conflicts.
Configuration Selection
The first wizard screen allows you to identify all areas of configuration for this
policy. A future configuration step will be presented for each area check marked
on this screen. We will visit all of them as we proceed through this section. In
practical use, you would only select those areas for which you have configuration
information relative to the policy being created.
** Word of Caution ** Once an area is Checked configuration information MUST
be entered to proceed further in the Wizard. Previous entries for username and
password are not retained.
General Configuration.
Agent Selection
This is the most important screen in the Policy Wizard. This information will
determine which Agents (if any) will adopt the policy being created. Insure that
your entry defines ONLY Those Agents you want, and EXCLUDES those that
you do not want. An incorrect policy with a global reach will create global issues.
Use the below example to see how compound criteria can be used.
NOTE: notice the (+) and (-) signs to the right of the entry fields. These are used
to add and remove additional criteria.
If you provide criteria that the system deems a potential problem it will present a
dialog box validating your decisions. You should not rely on the Wizard to catch
all potential problems.
Monitoring Configuration
Monitoring Configuration is the first screen in the Wizard that presents a 2 page
model of data entry. The pages are:
1.) A Summary of current configuration
2.) A Detailed Entry screen for adding to the presented summary
Click the green circled plus sign (+) Icon on the left of the summary page. To
open the Detailed Entry Screen
Select a Solution (for our purposes select the Windows Server solution)
You can then select a Monitoring Profile. For this walk though select Windows
OS Basic Health Monitoring (similar to NT_BASE).
The Example used does not require further information from the User to activate.
There are Monitoring Profiles which require additional information.
Lets look at one example
Click the green circled plus sign (+) Icon on the left of the summary page. To
open the Detailed Entry Screen
Select a solution (for our purposes select the Windows Server solution)
You can then select a Monitoring Profile. For this example well select Windows
Event Log Monitoring
This Profile has 3 tiers of information required including the Hostname, the log,
and any filters you may want to apply.
** Configuration requires a hostname entry. This is due to a common use of the
Profile across local agent monitoring of logs and remote monitoring of logs.
Enter the Hostname and select Application as the Log Name.
Scroll down using the intra scroll bar and you will notice that each tier of the
Configuration has an Add to List button toward the bottom of each section.
Click the Add to List for the server entry, then complete the log and filter
information.
Now Click the Add to List for the Filter
Now Click the Add to List for the Log
Finally you can click the Add button at the bottom (the example shows Update).
Click the Close button to get to the back to of Monitoring Summary Screen.
Filtering Configuration is another Multi Page model in the Wizard that presents
a 2 page model of data entry. The pages are:
1.) A Summary of Filters configured
2.) A Detailed Entry screen for adding to the presented summary
You have the Option of Filtering everything in the Agent to one option or you can
be more granular and perform filtering for the Monitoring Type or even at the
Attribute level.
You are presented with the Details page. It should look familiar to you now. You
can select the Solution and Monitor Type of interest.
Select the Windows Servers solution and the BlueScreen Status Monitoring
type.
The Last Step is to define what Filtering you would like to apply.
Use the Pick List under the Specify the Filter Label.
You will have 4 Options to choose from:
NO FILTER (Send everything)
Filter OUT only the Data, Send the Events
Filter OUT only the Events, Send the Data
Filter OUT All the Data, All the Events
After picking a filter you can click the Add button at the bottom, followed by
Close button to get to back to the Filtering Summary Screen.
Click Next to move on to the Agent Threshold Configuration
Agent Threshold Configuration
Agent Threshold Configuration is another Multi Page model in the Wizard that
presents a 2 page model of data entry. The pages are:
1.) A Summary of Thresholds configured
2.) A Detailed Entry screen for adding to the presented summary
Click the green circled plus sign (+) Icon on the left of the summary page. To
open the Detailed Entry Screen
Select the Windows Solution and Pick the Paging File Monitor type
Select the Paging File Usage Attribute
In the Threshold Section enable the Alarm 1, set for WARN between 90 100
After configuring the Threshold click the Add button at the bottom, followed by
Close button to get to back to the Agent Threshold Summary Screen.
Click Next to move on to the Server Threshold Configuration
BPPM Server Threshold Configuration
Click the green circled plus sign (+) Icon on the left of the summary page. To
open the Detailed Entry Screen
Pick any Monitor Type that suits your fancy, configure at least one threshold
After configuring the Threshold click the Add button at the bottom, followed by
Close button to get to back to the Server Threshold Summary Screen.
Agent Configuration
Alter the Value for the Events Format Container (Event Profile to the Agent)
Enter BiiP3. This is the format used in 9.0 and most rules are written to today.
Click Next to move on to the Server Configuration Section
Server Configuration
Click the green circled plus sign (+) Icon on the left of the summary page to
open the Detailed Entry Screen.
Enter values similar to the example below. This will instruct an agent using this
policy to Disable the KM entered in the Value field. Click the Add button to save
your entry and return to the Summary Screen.
You have now visited all the different sections of Policy Creation. Not all Policies
require information for each Section. You should be familiar with what you want
to accomplish through a policy prior to creating it, then build the policy to that
plan.
Click the Finish Button
** Note when you click the Finish button the Policy is validated and a warning
will appear when it finds another Policy in the Environment assigned the same
precedence number. Not to worry here, this is our first Policy and it should not be
used for any agent.
Now you should see your first Policy in the Summary Screen
This section will demonstrate PATROL Agent data continuity when switching ISs
and the catch up capability of data and events in BPPM after a data path
interruption.
Pre-Requisites: BPPM Server, PATROL Agent with monitoring policy, an IS
installed on a Linux server, an IS installed on a Windows server
Verify the PATROL Agent is sending data to BPPM server
Verify the PATROL Agent is sending data to BPPM server via the IS installed on
the Linux server. In the example below the PATROL Agent running on clm-hou006936 server is sending data through the IS installed on clm-hou-006936.
When the agent query window appears enter a PSL command in the window and
select the Execute button. Also, notice the other functions available to
manipulate the agent.
print(get("/hostname"));
Blackouts
Overview:
This lab will demonstrate the new blackout capabilities in CMA. In this lab you will
create a blackout for the Linux Agent so that no alerts are received during a
specific time period.
Pre-req: BPPM Server, Linux PATROL Agent with basic OS monitoring policy.
Hands-on Exercise:
Create a blackout for an entire Linux agent. (Emergency Blackout)
Log into CMA as admin and select the General drawer in the navigation pane.
Select Timeframes and select the green plus
in the upper right hand corner
to create a new timeframe.
Set the blackout period to Always Active and Start Immediately. Notice the
different recurrence patterns available. Give the blackout a name and save it.
NOTE: The Timeframe cannot cross the midnight hour. For example: If your
timeframe for a blackout is between March 31st at 22:00 and April 1st at 01:00,
you will have to create two timeframes. One for March 31st from 22:00 to 23:59
and one for April 1st from 00:00 to 01:00.
In CMA, select the Policies drawer in the navigation pane. Now open the
Blackout heading and select All. Create a new blackout policy by selecting
the green plus sign
in the upper right.
Give the policy a name and select the timeframe created earlier. Notice you
could also create a new timeframe here by selecting the New button. When
finished select Next.
Select the type of output to be blacked out such as data collection or events and
then the scope of the blackout by selecting an entire agent or selecting specific
application classes and instances. For our purposes, select Data for the
blackout and select Complete Agent for the scope. Select Finish when done.
NOTE: To blackout specific monitors or instances you change the scope to
Monitor types and Instances and select the green plus sign to add the
appropriate monitor(s) and instance(s) to be blacked out.
Verify the agent has been blacked out by looking at the events in the BPPM
Operations Console as seen below and / or by drilling into the Agent that was
selected for blackout. After drilling into the agent, verify that no more data is
being collected for any of the parameters.
"/ConfigData/EventSetup/Configuration/EventCells" = { REPLACE =
"<cellname>/1828" }
b.) You Remove the Agent configuration variable:
"/EventSetup/Configuration/EventCells" = { REPLACE = "<cell>/1828" },
c.) You alter the value Directly in the Agent configuration with a variable
change like:
"/EventSetup/Configuration/EventCells" = { REPLACE = "<cell>/1828" },
NOTE: The Policy entries (e.g. /ConfigData/..) will ALWAYS win
over the Local Variables.
2.) Event integration properties for an IS can be provided when adding the IS
to the BPPM Server via the CMA. Setting the Value here dictates that any
PATROL Agent sending events to the IS node (or configured to use
Integration Server Settings in a Policy) will follow the settings specified.
Options are:
a.) Route to the BPPM Server
b.) Use the integration Server Setting (e.g. use the cell associated to the
IS node you are adding)
c.) Dictate the Cell you want to use (You MUST identify the <host>/<port)
Monitoring Policies
Example:
Login to the BPPM Central Monitoring Administration (CMA) Console
Edit your basic windows Monitoring Policy under All to implement specific
management configuration that will ONLY apply to your Windows PATROL
Agent.
To Edit the policy Highlight your Windows policy and click the pencil icon.
Select/Check the Agent Threshold and Agent Configuration options (if not
already included) as the areas you would like to configure/edit.
Click on the link for the Agent Threshold screen
Create a Threshold for:
Solution = Windows Server
Monitor Type = Memory
Attribute = Memory Used (MB)
Create a Monitoring Policy for All to implement Base Agent configuration that
should/can be applied to all Servers as a Standard.
To Add the policy click on the green circled plus sign (+) Icon on the right of
your screen
The first wizard screen allows you to identify all areas of configuration for this
policy. We will visit just the Configuration Variables Section.
Agent Selection
This is the most important screen in the Policy Wizard. This information will
determine which Agents (if any) will adopt the policy being created. Insure that
your entry defines ONLY Those Agents you want, and EXCLUDES those that
you do not want. An incorrect policy with a global reach will create global issues.
Create a Condition that Agent Port equals 3181 (This will cause the policy to be
applied to all of your Agents running on port 3181)
Click Next to move on to the last section The Configuration Variables Section
We want to enter a number of Variables that will be a standard for most if not All
Agents in the environment.
There are two Options for entry:
1. Individually Type them in by clicking the green circled plus sign (+) Icon
on the left of the summary page. Then open the Detailed Entry Screen for
each entry.
** Note when you click the Finish button the Policy is validated and a warning
will appear if it finds another Policy in the Environment using the same
precedence. No other Policy should have your Precedence Setting.
This section demonstrates the CMAs new functionality of a Staging IS. It will
cover the installation and identification of a staging IS and the use case for
staging PATROL agents to BPPM.
In large environments it becomes a difficult challenge for the end users to
maintain multiple Images of patrol agents to match different IS nodes. This
functionality allows the end user to maintain minimal images and then do a
proper load balancing once the agent is connected to CMA through the IS.
In large environments, it is highly recommended to have a dedicated IS on a
different system for this purpose.
Steps:
Enable an IS to be a
Staging IS
Cross Check the availability of the New Patrol Agent under the staging IS.
c. Click on the Staging IS and the new Patrol Agent should be registered
underneath.
a. Using the example below, please enter the appropriate information and
click Next.
b. In the next window, enter the TAG (if any) and change the IS to the single
Integration Service and click Finish.
d. Wait a few minutes then verify that the New Patrol Agent switched from
the staging IS to the dedicated IS.