PSL External Commands

%DUMP — List Specific Information

Return a list of specific information
Format
%DUMP option
Description
The %DUMP command returns a list of information that is specified
by the parameter option.
Field Definition
option One of the following:
• ALLReturn info about PATROL® Agent data structures
• APP_INSTSReturn info about each application
instance
• APPSReturn a list of applications
• CHANNELSReturn a list of open PSL global file and
process channels
• CONSOLESReturn a list of connected consoles
• ERRORSReturn a list of PSL errors that have
occurred
• GLOBALSReturn a list of global channels
• KM_LISTReturn a list of loaded KMs
• LIBRARIESReturn a list of loaded libraries
• PARAMSReturn a list of PATROL Agent parameters
• RTLISTReturn info about processes in the Agent
run-time queue
• RUNQReturn a list of items scheduled in the run
queue
• TASKSReturn a list of current tasks


%DUMP CHANNELS — List PSL Global Channels


List open PSL global process and file channels
Format
%DUMP CHANNELS
Description
The %DUMP CHANNELS command returns a list of global file and process
channels opened using either the fopen() or popen() functions. The
output from the %DUMP CHANNELS command contains the same
information as that provided by the get_chan_info() function within
a PSL program. The PSL interpreter returns the list of global channel
information to the console window from which the %DUMP CHANNELS
command was executed.
Note
The %DUMP CHANNELS command is one of a series of dump commands
available from the command line. Use the %DUMP command


%DUMP LIBRARIES — List Loaded PSL Libraries


Format
%DUMP LIBRARIES


Description
Each line of output from the %DUMP LIBRARIES command is a string
with the format:
- ,
Example
When typed into the computer window, the command
OS>%DUMP LIBRARIES outputs the following:
================ Currently Loaded Libraries =========================
response_def_lib.lib - unmodified, Wed Nov 6 15:34:42 1996
unix_misc_lib.lib - unmodified, Wed Dec 11 13:11:16 1996
set_share_lib.lib - unmodified, Tue Nov 26 16:56:38 1996
=====================================================================


%PSL — Execute a PSL Statement


Execute a one-line PSL statement
Format
%PSL statement
Parameter
Description
The %PSL command submits statement to the PSL interpreter for
immediate interpretation.


%PSLPS — List Current PSL Processes

List all scheduled or active PSL processes on the computer system
Format
%PSLPS
Description
The %PSLPS command returns a list of currently scheduled or active PSL
processes on the computer system to the console window. The
information displayed by the %PSLPS command includes the process
identifier (PID) and the name of the PSL process or command.


psl — PSL Compiler Command

Call the PSL interpreter and compiler for the specified PSL source file
Format
psl inputfile -o outfile -n -r -w -l -P -O -q -b -R -e functionname -s
librarynames -S


Parameters
Parameter Definition
inputfile Name of the PSL source file
-o outfile Write the compiled binary output as the file outfile. This
option implicitly includes the -n option; that is, the -o
option does not schedule outfile for execution after
compilation.
The PSL compiler may add a .lib or .bin extension
to outfile if you selected the -l or -b option
respectively.
-n Do not schedule outfile for execution after compilation.
-r Suppress runtime error messages. This option is
equivalent to including the statement PslDebug = 0;
in the PSL script.
-w Suppress compilation warning messages produced by
the PSL compiler.
-l Write the compiled output in library mode as the file
outfile.lib. This option implicitly includes the -n
option; that is, the -l option does not schedule
outfile.lib for execution after compilation.
-b Write the compiled output in binary mode as the file
outfile.bin.This option implicitly includes the -n option;
that is, the -b option does not execute the binary after
compilation.
-P Activate the PSL Profiler


Parameter Definition
-O Specify the optimizer level. (For more information about
optimizer levels, see “Optimization Levels” on page
C-11.)
-q Print the PSL bytecode to the screen
-R Inform the PSL compiler that statically or dynamically
loaded libraries are required for the compilation
Default if not specified: No statically or dynamically
loaded libraries required for the compilation
-e functionname Specify the user-defined function functionname within
the PSL source file as the execution entry point for the
compiled program
Default if not specified: Execution begins with the first
statement within inputfile that is not part of a
user-defined function definition.
-s Instruct the PSL compiler to statically load all user
libraries required for compilation.
Default if not specified: Load library names with the
.lib extension statically and all other library names
dynamically
librarynames List of user library names that should be statically
loaded for compilation. Library names should have the
format library_name.lib. The PSL compiler loads any
library name without the .lib extension dynamically
unless the -l flag is specified.
Default if not specified: No user libraries are included.
-S Display the PSL symbol table


Description
The psl command creates an executable binary file from inputfile and
specified librarynames. The stand-alone interpreter will immediately
execute the compiled binary if options -o outfile, -l, and -b are omitted.
Use this command to create PSL libraries and PSL binaries that can be
used in the PATROL Agent. Doing so allows for a significant
performance gain.
-O Specify the optimizer level. (For more information about
optimizer levels, see “Optimization Levels” on page
C-11.)
-q Print the PSL bytecode to the screen
-R Inform the PSL compiler that statically or dynamically
loaded libraries are required for the compilation
Default if not specified: No statically or dynamically
loaded libraries required for the compilation
-e functionname Specify the user-defined function functionname within
the PSL source file as the execution entry point for the
compiled program
Default if not specified: Execution begins with the first
statement within inputfile that is not part of a
user-defined function definition.
-s Instruct the PSL compiler to statically load all user
libraries required for compilation.
Default if not specified: Load library names with the
.lib extension statically and all other library names
dynamically
librarynames List of user library names that should be statically
loaded for compilation. Library names should have the
format library_name.lib. The PSL compiler loads any
library name without the .lib extension dynamically
unless the -l flag is specified.
Default if not specified: No user libraries are included.
-S Display the PSL symbol table
Parameter Definition
BMC Software, Inc., Confidential and Proprietary Information
5-10 PATROL Script Language Reference Manual
The following PSL features cannot be fully simulated with the PSL
interpreter:
• complex built-in functions such as create() and destroy() that
rely on the full object hierarchy of the agent
• multiple PSL process issues such as timeouts or waiting for a lock
• security issues with functions such as fopen() and cat(), which rely
on the user name operating the agent’s command

Locking Functions for Concurrency Control

PSL includes two built-in functions for enforcing concurrency control:
lock() and unlock(). These functions are typically used to linearize
accesses by different PSL parameters, commands, and processes to
shared data structures. These shared data structures include the object
hierarchy accessed by the PSL set() and get() functions and external
resources such as files.
All PSL processes attempting to linearize accesses to a resource must
cooperate by requesting locks of a given lock name. All resource
accesses, including the set() and get() functions, are denied shared
resource access without a lock. It is the responsibility of each PSL
process to access a resource only when it holds the required lock.

PSL Built-in Functions

PSL includes a number of built-in functions that provide
PATROL-specific actions such as creating and manipulating PATROL
objects and general-purpose functions such as mathematical, logical, and
I/O functions. Following is a summary of the PSL built-in functions. The
functions are individually described in Chapter 4, “PSL Built-in
Functions.”

Diagnostics

If any compilation errors are encountered when a PSL script is compiled,
error messages tell you the line number of the error and briefly describe
the cause of the error. See Chapter 6, “Diagnosing PSL Program Errors,”
for further information.

Optimization

Like C, PSL does a certain amount of expression evaluation at compile
time, whenever it determines that all of the arguments to an operator are
static and have no side effects.
In particular, string concatenation is done at compile time between string
literals. Backslash interpretation is also done at compile time. You can
say
“Now is the time for all” .“\n” .
“good men to come to.”
and this expression is reduced to one string internally.
PSL is also highly efficient. The language is not immediately interpreted,
but instead is compiled into an internal form, which is then executed by a
high-speed interpreter.

Compiled PSL Binary Files

PSL includes a standalone compiler to compile PSL scripts and create
executable PSL binaries outside the PATROL Agent. There is also an
external interpreter that simulates all aspects of PSL execution except
those areas specific to the PATROL Agent.

Interpreted PSL Scripts

Upon receiving a script, PSL compiles the whole script into an internal
form. If the script is syntactically correct, the internal form is then
interpreted. Upon reexecution, the script is not recompiled.

What Is PSL

PSL is both an interpreted and a compiled language for writing complex
application discovery procedures, parameters, and commands within the
PATROL environment. It is also a good language for writing arbitrary
commands and tasks.
PSL has been designed to provide functions needed to efficiently develop
Knowledge Modules for the PATROL environment. To accomplish this,
PSL sacrifices some of the completeness of languages such as C, csh,
Perl, or awk while implementing some of the statements and functions
that make those languages so powerful and popular. Users familiar with
one of those languages should have little difficulty adapting to PSL.

Blackout Knowledge Module for PATROL

The blackout of a PATROL KM is used to temporarily disable the monitoring of certain software during special operations such as backups, updates, etc. Its purpose is to make sure no false alerts are triggered wile performing such operations. For example, if an application is stopped to upgrade to the latest version, it is not necessary to receive an alert in the PATROL Console because the application’s processes are down.
Blackout KM for PATROL can disable a whole Knowledge Module (KM) down to a single PATROL instance. Several modes can be used to automatically trigger the blackout:
• At a given date and time
• Upon the presence or absence of a file
• Upon the presence or absence of a process
• Upon the presence or absence of a NT Service
The same modes can be used to stop the Blackout or a timeout can be set.
download the PDF

What information is required when raising cases?

Issue: Installation Logs%USERPROFILE%\Application Data\BMCINSTALL\ _.log$HOME/BMCINSTALL/_.log

Issue: PATROL Console Server %PATROL_ROOT%\log\cserver\cserver-.log$PATROL_ROOT/log/cserver/cserver-.log

Issue: Rtserver%RTHOME%\log\rtserver.log$RTHOME/log/rtserver.log

PATROL Central Operator Web Edition%BMC_ROOT%\WebCentral\jakarta-tomcat\logs$BMC_ROOT/WebCentral/jakarta-tomcat/logs

Patrol Agent Debug

UNIX:
./PatrolAgent -debug 0 > /tmp/PAdebug.txt 2>&1

Windows: A. Stop the PatrolAgent service. B. Change the startup to manual C. On services dialog enter the following in the Startup parameters box:-debug all,file=c:\temp\debug.txt D. Start the service If you need to put a size limit then execute the following...-debug ALL,file=C:\\patrol_agent_debug_output.txt,count=1000

PatrolDiags.psl
This is a Diagnostic utility that obtains information in the following order:
%DUMP KM_LIST%PSLPS%DUMP CONSOLES%DUMP CHANNELS%SETOS environment variablesInstalled KM versionsAll Agent error logs located in %PATROL_HOME%\BMC Software\Patrol3\logAgent configuration variablesPlease see .readme for execution instructions.

UNIXIf running 9.0.00 or higher version of PKM for Unix the following diagnostics would be a good start for any Unix Agent/KM related problem.Capture Unix Diagnostics (UNIX OS => KM Commands => Debug and Diagnostics => Capture Unix Diagnostics) - Select all log files. This file contains a multitude of information that will be used to help resolve the issue.

PM Version informationWindows:\Patrolagent –version. UNIX: /opt/bmc/Patrol3/PatrolAgent -vWindows:\Rtserver –version . UNIX:/opt/bmc/Patrol7/?Windows:\Cserver –version. UNIX: /opt/bmc/Patrol7/?To Determine the PATROL KM Version1. From the PATROL console, access the top-level KM application.2. Right-click the application and select the menu command InfoBox.The PATROL KM version is displayed next to KM Version.

OS Information
What Platform/OS? UNIX – e.g. Solaris, oslevel, uname –a, cat etc/redhat-release.
Windows SP.

Patrol Central Operator - Web Edition Geting Started 20899

PATROL Central - Web Edition is composed of a core console and a set of console modules
that add end-user functionality and business logic to the core. The core console provides
the basic services that are used by all components. These include common page
templates, online Help interface and a database repository.
The PATROL Central - Web Edition architecture is shown in the diagram below.


The presentation layer includes the PATROL Central - Web Edition core infrastructure and
is composed of libraries, styles, templates and applets that maintain a common look-andfeel
throughout the application. The console module components are implemented on top
Page 7
of the core infrastructure. Console modules share a common look and feel, user interaction
model, and are interoperable with other PATROL components. Console modules are usually
displayed as top-level. They can also operate with other console modules to display
functionality in other areas of the interface.
The business logic layer provides servlets, JAVA beans, and tag libraries that console module
developers can leverage when creating their own product. This layer accesses the console
server interface, which provides all the features and benefits of COS. This interface
maintains connection-related information with the console server and presents the console
server object model to the PATROL Central - Web Edition components. It serves as an
interface to the data to manage PATROL objects (managed systems, Knowledge Modules,
parameters) rather than interfacing directly with COS.
User profile information and Web site metadata are stored in a small database repository
which is shipped with the product.

Patrol Central Web Edition

Download the PDF here

BMC ships consoles to wrap up Patrol upgrade

BMC Software Inc. this week announced that it has completed the rollout of its Patrol Version 7 enterprise management software, and clothing retailer The Men's Wearhouse Inc. said it's ready to put BMC's new network management consoles into production after a three-month test. Men's Wearhouse, which operates more than 600 stores nationwide, uses Patrol to manage a network of 200 servers at its Houston headquarters. The Windows and Web-based management consoles now available for Patrol 7 will help the retailer become more proactive in managing network growth, said Katie Scully, manager of enterprise management services. "It's the difference between fighting fires and being proactive," she said. "Before Patrol came along, we'd react to problems, sometimes something as simple as running out of disk space." Men's Wearhouse has used earlier versions of Patrol for three years. With Patrol 7, the retailer expects to need fewer people to run its network. The new consoles provide network managers with the ability to assign rights and privileges to end users and centrally control security and authentication, according to Houston-based BMC. Scully said the Patrol upgrade also gives network managers a view of monitoring agents installed on switches, routers and other network nodes, making it easier to remotely install additional agents. "It actually reduces the time the network managers need to be here," she said. The Web and Windows management consoles each sell for $3,500, said BMC, which also released software to manage the deployment of its products for Windows and Unix systems. Rich Ptak, an analyst at Ptak & Associates in Amherst, N.H., said BMC's new consoles don't leapfrog the ones offered by rivals. But he called BMC's pricing competitive.

To know more please visit here

Integration Pack for BMC PATROL

Optimize Service Levels and Reduce Overall System Downtime
Opalis Integration Server connects data center components to automate processes in a way that's simple, fast and effective. The Opalis Integration Pack for BMC PATROL enables you to automate problem management routines and maintenance procedures to optimize service levels and reduce overall system downtime.
Automate Problem and Incident Management Routines Faster
Problem and incident triage often involves ad hoc phone calls, manual analysis and data re-entry. With Opalis, you can automate diagnostics routines and corrective actions, and pass data to other systems like a help desk - and finally realize the benefits of a self-healing data center.
Automate BMC PATROL Event Suppression during Maintenance Windows and Troubleshooting
During times of server maintenance or troubleshooting, administrators need to be able to automatically shut off event generation on selected managed servers. Opalis provides the ability to toggle PATROL event suppression during automated maintenance procedures or corrective actions, and the ability to automatically detect and prevent event storms.
Coordinate and Consolidate Events between Help Desk and Monitoring Applications
The Opalis Integration Pack for BMC PATROL provides a simple, yet powerful graphical user interface for filtering PATROL events and auto-generating pre-populated trouble tickets in service management tools like BMC Remedy. Conditional logic and data look-ups can easily be implemented for auto-assigning these tickets to the appropriate help desk personnel or department, or escalating critical requests by email or pager. Similarly, PATROL event data can be shared and synchronized with other system monitors such as HP OpenView Operations, IBM Tivoli or Microsoft MOM.
Instant integration with Help Desks and System Monitors
2-Way Integration with other system monitoring tools
Create custom BMC PATROL Events within standardized IT processes
An Automation Policy
2-Way Integration with other system monitoring tools

To know more please visit here

BMC Strengthens its Market Position with the Introduction of BMC Atrium CMDB 2.0

On May 15, BMC introduced its new generation Configuration Management Database (CMDB,) BMC Atrium CMDB 2.0, as a follow on to BMC Atrium CMDB 1.0 in January, 2005. This is significant on several counts. BMC, more than any other vendor, has succeeded in articulating the importance of CMDBs as both a foundation for IT Infrastructure Library (ITIL) best practices, and as a design point to accommodate more effective integration and automation across a versatile, multi-brand management portfolio. While CMDBs remain obscure to many in the media and confusing to many buyers, the "CMDB Revolution" is real—transforming the IT management marketplace into a more collaborative and logically defined set of architectural and functional parameters.
In addition to BMC’s Atrium CMDB 2.0, BMC announced expanded BSM (Business Service Management) foundation technologies, which together offer significant enhancements across a broad range of capabilities. These include: process workflows, discovery, visualization, configuration management, analytics, and CMDB data integration and maintenance. Enterprise Management Associates (EMA) believes that through the introduction of Atrium CMDB 2.0, BMC has strengthened its market position as a leading provider of CMDB solutions. Moreover, with its introduction of process workflows and analytics, BMC is building creatively and aggressively on its CMDB base.

Configuration Management
BMC has enhanced its capabilities for managing changing configurations in the infrastructure via Atrium. This includes stronger enforcement for compliance controls, more granular diagnostics, and more automated capabilities for contrasting changes made in time and across the infrastructure.

download the PDF


To know more about please visit here

Implementing BMC Performance Assurance in a VMware Environment

With BMC Performance Assurance Suite for Virtual Servers, one can manage the performance of VMware ESX servers. A person can analyze performance information for the virtualized systems (Windows and Linux) and obtain a system-level view of the VMware ESX server for server sizing, modeling, performance management, and daily reporting. BMC Performance Assurance Suite for Virtual Servers provides the ability to collect VMware ESX server configuration and system-wide statistics, analyze this data with the BMC Performance Analyzer, report on the data, and model the VMware server with BMC Performance Predictor. One can also view VMware reports using BMC Performance Perceiver, a dynamic Web server that provides easy access, viewing, and export of BMC Performance Assurance data for non-console users.

Download the pdf here BMC Performance -VMWare



for more please visit here

BMC Performance Manager Express for Hardware version 2.3.00 by Sentry Software

Before you install BMC Performance Manager Express for Hardware ensure that following prerequisites are fulfilled before installation.
BMC Portal version 2.3 should be installed on one computer.
Remote Service Monitor program (RSM) must be installed on at least one computer. This could be the same computer as Portal in small environments.
More info about installing BMC Portal and BMC Performance Manager Portal can be found at BMC Software Web site at http://www.bmc.com/
Warning
BPM Express for Hardware 2.3.00 is not compatible with any version of the Portal prior to 2.3
Prerequisites for managed systemsOperating system must be one the following:
IBM AIX 4.3, 5.1, 5.2 or 5.3
Microsoft Windows NT 4.0 Service Pack 5 or greater , with the latest [Windows Management Instrumentation (WMI)], [WBEM], [Windows Scripting Host (WSH)] and [VBScript] components installed.
Microsof t Windows 2000 Service Pack 2 or greater
Microsof t Windows XP (any Service Pack)
Microsof t Windows Server 2003 (any Service Pack)
RedHat Enterpr ise Linux 2.1 or greater
SUSE/Novel l Linux 8 or greater
A complete list of managed systems supported can be found at BMC Software Web site at http://www.bmc.com/
BMC Performance Manager Express for Hardware requires a specific hardware agent to collect information from the managed node. Depending on the platform different components are required.
IBM [xSeries], [Netfinity servers] requires that the IBM Director Agent installed for BMC Performance Manager Express for Hardware to function properly.
The IBM Director agent can be downloaded for free on the IBM Web site at the following address:http://www-03.ibm.com/systems/management/director/downloads.html
IBM [RS/6000], [pSeries] and [eServer p5] don't require any agents.
More info can be found at BMC Software Web site at http://www.bmc.com/
Warning
It is required that you install the full IBM Director Agent (Level 2) for BMC Performance Manager Express for Hardware to work properly.BMC Performance Manager Express for Hardware does not and will not support IBM Director Agent version 5.10 and 5.10 Update 1.Currently supported versions of the Director Agent are 3.11, 4.2x and 5.10 Update 3.

Sun Servers Integration 2.0 for BMC PATROL Enterprise Manager

The Sun Servers Integration 2.0 for BMC PATROL Enterprise Manager provides the tools and utilities needed to completely integrate Sun servers into a BMC PEM environment.

Supported Servers:

Sun Fire X4100 Server
Sun Fire X4100 M2 Server
Sun Fire X4200 Server
Sun Fire X4200 M2 Server
Sun Fire X4500 Server
Sun Fire X4600 Server
Sun Fire X4600 M2 Server
Sun SPARC Enterprise T1000 Server
Sun SPARC Enterprise T2000 Server
Sun SPARC Enterprise T5120 Server
Sun SPARC Enterprise T5140 Server
Sun SPARC Enterprise T5220 Server
Sun SPARC Enterprise T5240 Server
Sun Blade X6220 Server Module
Sun Blade T6300 Server Module
Sun Blade T6320 Server Module
Sun Blade X8400 Server Module
Sun Blade X8420 Server Module
Sun Blade X8440 Server Module


for more info please visit/click here

Network Management - BMC Software PATROL® Perform/Predict

PRODUCT DESCRIPTION

BMC Software PATROL® Perform/Predict, Version 6.5.30 is a Security Pack for users of PATROL® for Microsoft Windows Servers Performance and PATROL® for Unix Performance. The security pack ensures that unauthorized users cannot start a collection process. The Security Pack update to Perform Agent requires Perform Agent 6.5.20 to be present on the machine. A version of Perform Agent prior to 6.5.20 is NOT supported with the Security Pack.
A managed (agent) node updated to Version 6.5.30 has all network communication disabled to and from the managing node (console) - data collection must be initiated locally on secure managed nodes, and the data must be manually transferred to the managing computer (console). PATROL® Perform/Predict, Version 6.5.30 provides this security feature through the UDR Provider component's use of an access control list/authorization file to validate a user's authority to start a data collection process.

SECURITY EVALUATION SUMMARY

The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) processes and procedures. The evaluation demonstrated that the Authorization function of the Perform/Predict product meets the security requirements contained in the Security Target. The criteria against which the BMC Software PATROL® Perform/Predict, Version 6.5.30 was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.1. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 1.0. Computer Sciences Corporation determined that the evaluation assurance level (EAL) for the product is EAL 2. The product, configured as installed by the BMC Software technician, satisfies all of the security functional requirements stated in the Security Target. A validator, on behalf of the CCEVS Validation Body, monitored the evaluation carried out by Computer Sciences Corporation. The evaluation was completed in March 2002. Results of the evaluation can be found in the Validation Report BMC Software PATROL® Perform/Predict, Version 6.5.30 prepared by the National Information Assurance Partnership (NIAP) CCEVS.

ENVIRONMENTAL STRENGTHS

The UDRProvider component of Perform/Predict, Version 6.5.30 uses an access control list/authorization file to validate a user's authority to start a data collection process. The default configuration grants all users that are members of the patrol group full authorization, however, this file can be edited on a per-user basis by assigning one of two possible access permissions, or no access based on omission. If the authorization file is not on the node, or if the user is not authorized on the local node, UDRProvider will not process a collection request and will exit.

Adding Value to BMC Performance Manager With BMC ProactiveNet Analytics

As a BMC customer, one has come to rely on BMC Performance Manager (formerly BMC PATROL) to help ensure the optimal performance and availability of the critical business services. Now, one can get even more value from the BMC Performance Manager implementation through the integration of BMC ProactiveNet Analytics. BMC ProactiveNet Analytics filters, correlates, analyzes, and enriches the data and alarms provided by BMC Performance Manager to accelerate problem diagnosis and resolution, while also reducing the load on one's IT operations staff. What's more, by analyzing BMC Performance Manager data, BMC ProactiveNet Analytics automatically learns to distinguish between "Normal" and "Abnormal" behavior in one's distributed system, and sets thresholds accordingly.






To know more about please visit/click here.

BMC Software Uses PATROL Performance Assurance Solutions to Free Up Administrator Time

BMC Software provides enterprise management solutions that empower companies to manage their IT infrastructure from a business perspective. The challenge was to provide information to application owners and administrators in a quick, concise and high-level format, thus freeing resources for critical performance assurance tasks. BMC Software developed a Web server product that provides easy access, viewing and export of PATROL Performance Assurance data: PATROL Perceive. Perceive allows systems programmers to quickly provide performance data to customers, without a console.








To know more please visit/click here

BMC PATROL Enterprise Manager (PEM) with multi-listener, version 4.4 or higher

GroundWork Monitor Connector to BMC PATROL Enterprise Manager
The GroundWork Monitor Connector to BMC PEM enables events in BMC PEM to be automatically created from alarms or individual monitoring events within GroundWork Monitor. Events in BMC PEM are populated with GroundWork Monitor data, including device and last message information.
Benefits
Integrating GroundWork Monitor with BMC PEM enhances your monitoring capability while allowing you to maintain your current console solution. This assures that the investment made in your current console is not lost, that workflows are retained, and that you avoid the cost of retraining call center personnel.
You can also define business rules in BMC PEM that combine BMC-managed metadata with information contained in GroundWork Monitor generated events.
How It Works
The GroundWork Monitor Connector passes alarms and individual monitoring events to BMC PEM when they are generated on the GroundWork system.
The Connector communicates with BMC PEM using a TCP socket connection to the PEM multi-listener. Business rules are applied using BMC PEM message processor definitions when each event is processed by the connector.
Requirement
Connectivity between GroundWork Monitor server and BMC PEM server using a fixed TCP port.

for more info please visit/click here.

BMC PATROL for Windows

BMC Software is a major player in the crowded IT software management arena. It has a long history of products for monitoring and managing enterprise-level server configurations. BMC PATROL for Microsoft Windows Servers works with a variety of server types: file, print, mail, and application servers, and takes an approach targeted for full-scale enterprise configurations, for example, it works with Microsoft Cluster Servers and servers using Microsoft Active Directory.
BMC sells PATROL for Microsoft Windows Servers as three products: Perceive, Perform, and Predict. A combined package, called PATROL Performance Assurance for Microsoft Windows Servers, provides all of the services.

PATROL for Microsoft Windows Servers is a suite of many components that monitor various aspects of a large-scale server infrastructure. The most active component is PATROL Agent, which does the actual monitoring. It uses the many Knowledge Modules (KMs) that specify what to monitor and how to interpret it. The function of these KM components is fairly self-explanatory, based on their names: PATROL KM for Microsoft Windows Operating SystemPATROL KM for Microsoft Windows Active DirectoryPATROL KM for Microsoft Windows Domain ServicesPATROL KM for Microsoft Cluster ServerPATROL KM for Microsoft COM+PATROL KM for Microsoft Message QueuePATROL KM for Event ManagementPATROL KM for Log ManagementPATROL KM for History Loader (loads PATROL data into a relational database)
The key to PATROL's approach is the relative autonomy of the PATROL Agent, which, when loaded with instructions from the PATROL Knowledge Modules, can start, monitor, alert, record, and manage the server without a connection to a PATROL Console (the central management tool).

Although the Windows modules have many features in common with other BMC PATROL products for Linux and Unix operating systems, this list illustrates how the product has been tailored for the features and terminology specific to Microsoft Windows (e.g., specific support for Microsoft Active Directory).
Installation of the PATROL system uses a PATROL Agent on each server to be monitored, and various KMs guide the agent. A server with a PATROL Console, the management component, must also have all of the KMs used in the servers being monitored. Configuration is on a per-module, per-server basis and can be very detailed. The PATROL Configuration Manager supports centralized deployment of server configurations through the PATROL Agent. BMC provides a large number of 'Rulesets' to provide default configuration for the Knowledge Modules. The PATROL Cluster Configuration Wizard is an invaluable tool to manage the complexities of cluster setup.

monitoring functionality is through the PATROL Console using a dual-pane window with an expandable tree-list on the left, and the information/options on the right (i.e., Windows Explorer-like). This approach has become so ubiquitous that it is easily a de facto standard. Explanations and online help are provided for all options and monitoring values, although referencing the printed manuals will most likely be necessary.
As should be expected, PATROL for Microsoft Windows Servers must run an elaborate dance between its views of the system, the view(s) provided by Microsoft (e.g., through WMI — Windows Monitoring Instrumentation), and the large amount of systems' data available either through Microsoft software, other software, or the hardware. The PATROL Wizard for Microsoft Performance Monitor and WMI is the primary tool for using this interface because it can incorporate user-defined monitoring points based on the data and events provided by MPM or WMI.

One PATROL capability of note is how it manages system event logs (most operating systems have several). When system logs become large or reach capacity limits they can (dramatically) affect server performance. PATROL KM for Log Management supports four types of files: Text, Command scripts, Named Pipes, and Binary files.
Alerts rely on scripting (Perl and VB Script) and usually a notification server (both a primary and backup). Use of phone, SMS, or network message alerts is not directly supported. Recovery actions are built into the Knowledge Modules and usually provide an option to run automatically. Actions include: terminate a runaway process, clear temp directory, clear logs, restart processes and services, increase DFS, share connections, and restart a PATROL agent. Logs, events, and other data are loaded by the PATROL History Loader KM into a database (typically a MS SQL Server). The PATROL Console provides access to a number of analytical and reporting options. The PATROL Adapter for Microsoft Office enables access to the same data through MS Office applications, typically Microsoft Excel.



To know more about please Visit/Click here

BMC PATROL CONSOLE INTEGRATION

The SAS® Intelligence Platform and SAS Business Solutions provide intelligence that drives many business activities. To keep business data flowing smoothly throughout the enterprise, it is critical that Business and IT administrators are able to actively monitor the underlying systems, detect and respond to anomalies in a timely manner.
Using BMC PATROL Console for Windows® 3.5.62 and BMC PATROL UNIX Knowledge Modules® (KM) executing on Sun Solaris 10®, we have implemented a monitoring and management framework for the SAS 9.1.3 SP4 BI Server environment. The BMC PATROL UNIX KM format, allows SAS customers to implement monitoring and management for the SAS BI servers in all supported UNIX environments.
Refer to the BMC PATROL documentation for a more exhaustive description on the features and capabilities of Patrol.
To view a snapshot for monitoring the SAS 9 Metadata server under BMC PATROL, click here.
Download the SAS 9.1.3 and BMC PATROL Integration document
If you are a SAS customer and would like to download a copy of the SAS 9.1.3 and BMC PATROL Integration document, click here.
SAS 9.2 Enterprise Business Intelligence Support for BMC Patrol
The EMI team is scheduling an updated BMC Patrol package to support SAS 9.2. Customers interested in using BMC Patrol with SAS 9.2 should contact the EMI team. We want to understand your requirements and schedule development resources accordingly.

To know more about SAS please Visit /Click here

BMC PATROL

BMC PATROL

An application management suite from BMC that uses agents to report on software activities on all the servers within the enterprise. Using the information in "knowledge modules" (KMs) about each system component, agents detect events, collect information and notify system and network administrators to take corrective action.

The most active component is PATROL Agent, which does the actual monitoring. It uses the many Knowledge Modules (KMs) that specify what to monitor and how to interpret it. The function of these KM components is fairly self-explanatory, based on their names:

PATROL KM for Microsoft Windows Operating SystemPATROL KM for Microsoft Windows Active DirectoryPATROL KM for Microsoft Windows Domain ServicesPATROL KM for Microsoft Cluster ServerPATROL KM for Microsoft COM+PATROL KM for Microsoft Message QueuePATROL KM for Event ManagementPATROL KM for Log ManagementPATROL KM for History Loader (loads PATROL data into a relational database)

The key to PATROL's approach is the relative autonomy of the PATROL Agent, which, when loaded with instructions from the PATROL Knowledge Modules, can start, monitor, alert, record, and manage the server without a connection to a PATROL Console (the central management tool).
Installation of the PATROL system uses a PATROL Agent on each server to be monitored, and various KMs guide the agent. A server with a PATROL Console, the management component, must also have all of the KMs used in the servers being monitored. Configuration is on a per-module, per-server basis and can be very detailed. The PATROL Configuration Manager supports centralized deployment of server configurations through the PATROL Agent. BMC provides a large number of 'Rulesets' to provide default configuration for the Knowledge Modules. The PATROL Cluster Configuration Wizard is an invaluable tool to manage the complexities of cluster setup.
Alerts rely on scripting (Perl and VB Script) and usually a notification server (both a primary and backup). Use of phone, SMS, or network message alerts is not directly supported. Recovery actions are built into the Knowledge Modules and usually provide an option to run automatically.

Actions include: terminate a runaway process, clear temp directory, clear logs, restart processes and services, increase DFS, share connections, and restart a PATROL agent.

Logs, events, and other data are loaded by the PATROL History Loader KM into a database (typically a MS SQL Server). The PATROL Console provides access to a number of analytical and reporting options. The PATROL Adapter for Microsoft Office enables access to the same data through MS Office applications, typically Microsoft Excel.

PATROL is a systems, applications, and event management tool.
It provides an environment where you can monitor the status of every vital resource in the distributed environment you are managing.

1. PATROL AGEGNTS & PATROL KNOWLEDGE MODULES ->2

2.MONITORING OPERATING SYSTEMS AND APPLICATIONS THAT ARE RUNNING ->3


3.THEN COMMUNICATING TO PATROL CONSOLE -> 4


4.CONSOLE WHICH KEEPS ACT AS LIBRARY AND UPDATING STATUS OF AGENTS->5


5.WHICH THEN IS SHARED INFORMATION WITH USER (MONITORING TEAM) UPON REQUEST.


PATROL is now BMC Performance Manager.BMC Performance Manager products allow you to proactively manage the availability, performance, and business impact of your distributed systems environment, including your network and a broad range of applications, databases, and operating systems. A common presentation interface enables you to view the status and business impact of both IT components and business services.

Related Products

BMC ProactiveNet Performance Management
BMC Performance Manager Express
BMC Performance Manager Express for Hardware by Sentry Software
BMC Performance Manager for High Availability Management by OTL Software
BMC Performance Manager Integration for HP OpenView IT/Operations
BMC Performance Manager for Microsoft Exchange Servers
BMC Performance Manager for Web Application Servers
BMC Performance Manager for Tivoli Workload Scheduler by OTL Software
BMC Performance Manager for WebSphere Business Integration
BMC Performance Manager for Hardware by Sentry Software
BMC Performance Manager for Citrix Presentation Server - BMC
BMC Performance Manager Monitoring Studio by Sentry Software
BMC Performance Manager for Backup Management by OTL Software
BMC Performance Manager Integration for Tivoli
BMC Performance Manager for Internet Servers
BMC Performance Manager for HP Insight Manager
BMC Performance Manager for Business Applications
BMC Performance Manager for Virtual Servers
BMC Performance Manager for BEA Tuxedo
BMC Performance Manager for iSeries
BMC Performance Manager for Informix
BMC Performance Manager for OpenVMS
BMC Performance Manager for Servers
BMC Performance Manager for Databases
BMC Performance Manager for iSeries - Perform
BMC Performance Manager Integration for HP OpenView Network Node Manager
BMC Performance Manager Portal
BMC Performance Manager Reporting

BMC PATROL

PATROL is now BMC Performance Manager.
BMC Performance Manager products allow you to proactively manage the availability, performance, and business impact of your distributed systems environment, including your network and a broad range of applications, databases, and operating systems. A common presentation interface enables you to view the status and business impact of both IT components and business services.