Entuity Integ BPPM

USER GUIDE
Entuity 12.5
Entuity Integration Module for BMC ProactiveNet Performance Management
The Entuity integration module for BMC ProactiveNet Performance Management forwards events from Entuity to the designated BMC ProactiveNet Performance Management server. A sample integration allows for easy configuration of both the Entuity and BMC ProactiveNet Performance Management servers.
North America Headquarters

4 Mount Royal Avenue Suite 340 Marlborough, MA 01752 Tel: +1 508 357 6344 Fax: +1 508 357 6358
EMEA Headquarters
9a Devonshire Square London, EC2M 4YN Tel: +44 (0)20 7444 4800 Fax: +44 (0)20 7444 4808
www.entuity.com
0000-0125-PD054 entuity_integ_bppm.rev1.fm
Copyright 2000 - 2012 Entuity. All rights reserved.
Entuity The Entuity product and its related documentation are protected by copyright and distributed under licenses restricting use, copying, distribution, and decompilation. Unless you have negotiated with Entuity specific terms and conditions for using its product and associated documentation, such use shall be governed by Entuity's standard licence terms, a copy of which is distributed with the product. Entuity may make improvements and/or changes to the product(s) and/or program(s) described in this publication at any time. These changes will be incorporated into new editions of the relevant publication.
Entuity , Eye of the Storm , InSight Center , Green IT Perspective, Network Delivery Perspective and Service Delivery Perspective are registered trademarks of Entuity. All other trademarks are the property of their respective owners.
License terms and conditions of use for Entuity and included third party software can be found on the Entuity server at entuity_home/licenseTerms/. A listing of these third party trademarks, references and software included with Entuity is available through its web UI.
Entuity
Contents
1 Integrating BMC ProactiveNet Performance Management
BMC ProactiveNet Performance Management .....................................................1-1 Entuity integration module for BMC ProactiveNet Performance Management ....1-1 Module Availability.............................................................................................1-1 Module Security.................................................................................................1-2 Overview of Forwarding Events ........................................................................1-2 Mapping Severity Levels ........................................................................................1-3
2 Configuring the Integration

Configure BMC ProactiveNet Performance Management Server .........................2-1 Configuring the Entuity Classes, Rules and Collectors ....................................2-1 Integration Configuration Files ..............................................................................2-2 Configuration Overview .........................................................................................2-3 Configuring the Integration ....................................................................................2-5 Amending the Default Configuration .....................................................................2-7 Amending the Default View and User Account.................................................2-7 Stopping and Starting Event Forwarding..........................................................2-8
3 Managing Event Forwarding

Automatic Event Forwarding is View Based ..........................................................3-1 Controlling Which Events the Integration Forwards ..............................................3-1 Using Entuity Views with Event Forwarding......................................................3-1 Event Severity and Descriptions .......................................................................3-2 Configuring Advanced Action Filters ................................................................3-2 Troubleshooting Event Forwarding .......................................................................3-2 BEMForkEvent.log.............................................................................................3-3 BEMForkEventFailedSend.log ..........................................................................3-3
4 Viewing Entuity Events in BMC ProactiveNet Performance Management

Entuity Events in BMC ProactiveNet Performance Management .........................4-1 Event Summary Information..............................................................................4-1 Event Object Information...................................................................................4-2 Event Log and Note Information .......................................................................4-3 Event Source Information..................................................................................4-4 Event Other Details............................................................................................4-5
Entuity Integration Module for BMC ProactiveNet Performance Management Guide
iii
Entuity
Launching Entuity From BMC ProactiveNet Performance Management .............4-6
A Integration Installation Files

Name and Location of Integration Files ............................................................... A-1 Renaming Configuration Files .............................................................................. A-1 Renaming Sample Configuration Files ............................................................ A-2 Configuration Files ................................................................................................ A-2 BMC ProactiveNet Performance Management Entuity Event Class .................... A-4
B Configuring Event Forwarding

Configuring forkevent ........................................................................................... B-1 Pipe Process..................................................................................................... B-1 Integration forkevent Configuration.................................................................. B-2 Configuring forkevent Connection ........................................................................ B-7
C Configuring Context Cross Launch

Configuring the Entuity Context Cross Launch ............................................... C-1
Glossary Index
iv
Entuity
Figures
Figure 1-1 Figure 2-1 Figure 2-2 Figure 2-3 Figure 4-1 Figure 4-2 Figure 4-3 Figure 4-4 Figure 4-5 Figure 4-6 Figure 4-7 BMC ProactiveNet Performance Management Architecture ......................1-3 Integration Configuration Process Overview ..............................................2-4 Configuring Event Forwarding ....................................................................2-5 Configure the Integration ............................................................................2-6 Entuity Forwarded Events ...........................................................................4-1 Entuity Event Summary ..............................................................................4-2 Entuity Event Object Details .......................................................................4-3 Entuity Event Logs and Notes ....................................................................4-4 Entuity Event Source Details ......................................................................4-5 Entuity Event Other Details .........................................................................4-5 Launching Entuity in Context ......................................................................4-6
1 Integrating BMC ProactiveNet Performance Management

Entuity Integration Module for BMC ProactiveNet Performance Management allows forwarding of events, in real-time, from Entuity to BMC ProactiveNet Performance Management server. Using Entuity views you can control which events are forwarded. A sample integration maps Entuity event severity levels to BMC ProactiveNet Performance Management event severity levels. It also maps Entuity event fields to BMC ProactiveNet Performance Management event slots, with a BAROC file defining the Entuity event class so BMC ProactiveNet Performance Management can handle Entuity specific event fields. From BMC ProactiveNet Performance Management Operations Console you can drill-back to the event source, viewing the details in Component Viewer. This integration uses the BMC II Web Services Server API.
BMC ProactiveNet Performance Management

BMC ProactiveNet Performance Managements primary purpose is to accept real-time events from one or more sources, process these events using various techniques and forward resulting events to other products including the BMC Remedy Action Request system. BMC ProactiveNet Performance Management allows you to detect IT problems and concentrate on the fastest resolution before there is an impact on critical IT services. Built upon highly scalable architecture, this product receives events from IT components and translate them into information to solve the problem faster by filtering, prioritizing, enriching, correlating and automatically handling events according to business and operations priorities. It also automates corrective actions, integrates diverse technologies (frameworks), and interoperates with other management applications like your help desk.
Entuity integration module for BMC ProactiveNet Performance Management

Entuity integration module for BMC ProactiveNet Performance Management requires a valid license and inclusion of configuration files to Entuity. The default installation allows automatic forwarding of events from the Regional view using the admin user account, to the BMC ProactiveNet Performance Management.
Module Availability
Entuity integration module for BMC ProactiveNet Performance Management is available with Entuity (for details on Entuitys technical specification see the Entuity Getting Started Guide). It is approved for use with:
BMC ProactiveNet Performance Management 8.0.10/BEIM 2.0 using the web services
API of the BMC Impact Integration Developers Kit 7.3.02.
BMC ProactiveNet Performance Management 8.5 using IIWS 7.4.

You can amend the integration configuration to allow it to work with BMC ProactiveNet Performance Management 8.0 or BMC Event Manager 7.X by amending in entuity.cfg bem.version. (See Appendix B - Configuring Event Forwarding.)
Entuity Integration Module for BMC ProactiveNet Performance Management Guide 1-1
Entuity
h
Entuity integration module for BMC ProactiveNet Performance Management
The screen captures, terminology and instructions used for this guide are taken from BMC ProactiveNet Performance Management 8.0.10.
Module Security
Entuity access permissions are granted based on that view membership according to the standard Entuity security model. With automatic event forwarding the user account defined in the bem section of entuity.cfg must have access to the Entuity view used with the integration.
Overview of Forwarding Events

The default Entuity integration module for BMC ProactiveNet Performance Management configuration automatically forwards from Entuity all of the events raised in the Regional view to the BMC ProactiveNet Performance Management server and cell specified during configure. When Entuity raises an event in the Regional view:
1) proffer forwards the event to forkevent (when forkevent starts it registers itself as a client
of proffer, using the details in the connect section of its configuration file).
2) forkevent structures the information and by default passes event information to the
EventActionApplication, BEMForkEvent.
3) BEMForkEvent converts the Entuity information to the format required by the target BMC
ProactiveNet Performance Management server.
4) BEMForkEvent forwards events to the BMC ProactiveNet Performance Management IIWS

which forwards events to the BMC ProactiveNet Performance Management server.
5) BMC ProactiveNet Performance Management server is configured for Entuity events

through the Entuity supplied BEM server configuration files.
1-2
Entuity
Mapping Severity Levels
Advanced Action Configuration

sw_bem_menu_def.cfg
Entuity Server
proffer raising events
Event Action Configuration

bemforkevent.cfg
forkevent
Pipe
EventActionApplication (BEMForkEvent)
Fork
BMC ProactiveNet Performance Management Configuration

BEMEventTypes.properties BEMSeverityMapping.properties
bemForkEvent
BMC Server Impact Manager
BMC ProactiveNet Performance Management Server
Server Configuration
Entuity supplied console, collector class and rule files
Figure 1-1 BMC ProactiveNet Performance Management Architecture

When forwarding events from Entuity to BMC ProactiveNet Performance Management server, the events are forwarded with BMC ProactiveNet Performance Management severity levels. The integration maps Entuity event severity levels to BMC ProactiveNet Performance Management severity levels through BEMSeverityMapping.properties. When Entuity cannot make a mapping events are forwarded with severity marked as UNKNOWN. Entuity Severity Description
Critical Severe Major Minor Info -
BMC ProactiveNet Performance Management Severity Color

Red Amber Yellow Green -
Internal Value
10 8 6 4 2 -
Description
Critical Minor Warning Info OK Unknown
Value
CRITICAL MAJOR MINOR WARNING INFO OK UNKNOWN Red
Color
Orange Amber Yellow Blue Green Grey
Orange Major
Table 1-1 Mapping Entuity and BMC ProactiveNet Performance Management Event Severity Levels
h
The event severity values visible from Event Viewer run from 1 to 5, the internal values which you should use for mapping run from 2 to 10.
1-3
Entuity
Entuity recommend that you create a view for use by the integration. For the BMC ProactiveNet Performance Management view set appropriate event and object filters, as by default every event raised in this view triggers the automatic forwarding of event details. You can set an additional event filter, through sw_bem_menu_def.cfg, to allow only certain events in a view to automatically trigger BMC ProactiveNet Performance Management generation.
1-4
2 Configuring the Integration

Entuity integration module for BMC ProactiveNet Performance Management is supplied with a sample configuration. This configuration forwards all events in the Regional view to the BMC ProactiveNet Performance Management server specified during Entuity configure. You can amend the default integration to use:
a different Entuity user account a different Entuity view multiple Entuity views, which requires configuration of multiple forkevents multiple Entuity servers to forward events to one or more BMC ProactiveNet Performance Management servers.
Entuity recommend you configure the Entuity integration module for BMC ProactiveNet Performance Management in this sequence:
1) BMC ProactiveNet Performance Management server, creating the required cell for the
Entuity event data
2) activating the Entuity integration module for BMC ProactiveNet Performance

Management
3) amending, if required, the sample Entuity integration module for BMC ProactiveNet
Performance Management.
Configure BMC ProactiveNet Performance Management Server

BMC ProactiveNet Performance Management server configuration is required to allow for Entuity to Entuity integration module for BMC ProactiveNet Performance Management integration specific slots. This server side configuration also adds Entuity collectors, cancellation and de-duplication rules and context cross launch.
h
Entuity recommend you always consult the BMC ProactiveNet Performance Management documentation when configuring BMC ProactiveNet Performance Management.
Configuring the Entuity Classes, Rules and Collectors

You must configure the BMC ProactiveNet Performance Management to allow for Entuity integration module for BMC ProactiveNet Performance Management specific slots. Slots are columns in the BMC IX.
1) Copy the class, rules and collector files: entuity_home/integ/BEM/server/etc/CELL/kb/classes/eye_event.baroc to

MCELL_HOME/etc/<CELL_NAME>/kb/classes.
entuity_home/integ/BEM/server/etc/CELL/kb/rules/ eye_integration.mrl to
MCELL_HOME/etc/<CELL_NAME>/kb/rules.
Entuity
Integration Configuration Files
entuity_home/integ/BEM/server/etc/CELL/kb/collectors/eye_collector.mrl to
MCELL_HOME/etc/<CELL_NAME>/kb/collectors. where:
MCELL_HOME is the root of the BMC Server Impact Manager <CELL_NAME> is the name of the cell that you are forwarding events to. 2) Amend MCELL_HOME/etc/<CELL_NAME>/kb/classes/.load to include:
#Integration for EYE EYE_EVENT
3) Update the file MCELL_HOME/etc/<CELL_NAME>/kb/rules/.load to include:

#Integration for EYE eye_integration
4) Update the file MCELL_HOME/etc/<CELL_NAME>/kb/collectors/.load to include:

#Integration for EYE eye_collector
5) From MCELL_HOME/etc/<CELL_NAME>/kb/ run:

mccomp manifest.kb
6) Restart <CELL_NAME>. 7) Add the new slots to your cell view in BMC IX.
h
mccomp manifest.kb only has to be run once after all the files have been copied to their correct locations and the appropriate .load files have been updated. Once compilation is complete, the cell can be restarted.
Integration Configuration Files

Configuration of the Entuity integration module for BMC ProactiveNet Performance Management integration is through application of configuration files and the subsequent running of configure. You can also edit the configuration files to customise the sample integration. Filename
bem.cfg BEMEventTypes.properties
Description
configure automatically generates the file. It holds BMC ProactiveNet Performance Management details. Defines BEM slot and BEM types.
Table 2-1 Entuity integration module for BMC ProactiveNet Performance Management Integration Files
2-2
Entuity
Configuration Overview
Filename
Description
BEMSeverityMapping.properties Maps Entuity event severity levels to BMC ProactiveNet Performance Management severity levels. eye_event.baroc bemforkevent.cfg Event class definition file. This file must be added to the target BMC ProactiveNet Performance Management server. Event Action Configuration, specifies automatic forwarding of events through the forkevent process and EventActionApplication. Default name of the BMC ProactiveNet Performance Management forkevent log file. Sets the parameters for the BMC ProactiveNet Performance Management forkevent log file, including name, maximum number of backups, maximum file size, warning level. The bem section details parameters required to connect to the BMC ProactiveNet Performance Management server. A standard Entuity file that defines Entuity processes that should run when the Entuity server is running, The site specific startup file for Entuity. For automatic event forwardingn copy the bemclient section from startup_O/S.cfg and set the state to normal. Advanced Actions Configuration, details the type of information gathered for automatic event forwarding. This is applied to the Entuity server.
bemForkEvent.log BEMForkEventLoggerConf.xml
entuity.cfg startup_O/S.cfg startup_O/S_site_specific.cfg
sw_bem_menu_def.cfg
Table 2-1 Entuity integration module for BMC ProactiveNet Performance Management Integration Files
h
When you edit the configuration files you may want to consider backing them up, or renaming them, to preserve the changes during any subsequent Entuity re-install or upgrade (see Appendix A - Integration Installation Files).
Activation of Entuity integration module for BMC ProactiveNet Performance Management requires an appropriate license, inclusion of its configuration and the running of Entuity configure.
2-3
Entuity
Configure Automatic Event Forwarding
Start Entuity
Create Entuity view for the integration
Amend bemforkevent.cfg
Amend
startup_o/s_site_specific.cfg
Rename Configuration Files and References to those Files
Stop and Restart Entuity
Figure 2-1 Integration Configuration Process Overview
The Entuity integration module for BMC ProactiveNet Performance Management is supplied with a default implementation. Before activating Entuity integration module for BMC ProactiveNet Performance Management you should:
add to the Entuity server a license that includes Entuity integration module for BMC
ProactiveNet Performance Management. By default license.dat is installed to entuity_home\etc.
consider renaming, or backing up, configuration files when you have amended the
default settings (see Appendix A - Integration Installation Files)
decide which managed object - event type combinations you want to allow Entuity
integration module for BMC ProactiveNet Performance Management to forward. Create a view that meets these requirements, using the object and event view filters.
create a user account that allows access to the new view.

Entuity
Configuring the Integration
login to the BMC ProactiveNet Performance Management server for an extended period
to monitor the type of events raised, and judge whether the configuration meets your requirements.
h
By default Entuity integration module for BMC ProactiveNet Performance Management uses the Regional view and the admin user account. You could use this combination, if you still have an account called admin, however it will forward all Entuity events to the BMC ProactiveNet Performance Management.

Entuity recommend configuring Entuity integration module for BMC ProactiveNet Performance Management through configure. When you want to amend the default installation, you can then manually edit the configuration files.
Copy to the Entuity server a valid license
Is Entuity Running ?
No
Run Configure
Yes
Select BCM ProactiveNet Performance Management from Module screen Stop Entuity
Complete Integration Module Details
Complete Configure
Create EYE view for Remedy

Start Entuity
Entuity forwards events from the Regional view to the BMC ProactiveNet Performance Management server.
Figure 2-2 Configuring Event Forwarding
To activate the integration:

Entuity
1) Acquire a valid license from your Entuity representative. The new license file should be
added to entuity_home/etc.
2) Stop the Entuity server. 3) Run Entuity configure, and when it is run: as a wizard, from the Module Select page check the BMC ProactiveNet Performance
Management integration
from the command line, when prompted enter yes to modify the activated modules
and again when prompted to activate the appropriate version of BMC ProactiveNet Performance Management integration.
4) configure prompts for you to make a connection and forward events to BMC
ProactiveNet Performance Management:
BMC Cell Name, the BMC ProactiveNet Performance Management instance to which
Entuity forwards events.
Web Server Host Name, hostname of the server where the BMC II Web Services
Server is located.
Web Server Port Number, the port number used by the BMC II Web Services Server,
by default 9080.
Web Service Name, the name of the web service, by default ImpactManager.
Figure 2-3 Configure the Integration
5) Complete configure. 6) Restart the Entuity server.

Entuity
Amending the Default Configuration

By default the Entuity integration for Entuity integration module for BMC ProactiveNet Performance Management forwards all events that Entuity raises in the specified view, Regional. The Entuity user account, by default admin, must have access to this view. This combination forwards all Entuity events to the BMC ProactiveNet Performance Management defined during configure. After using configure to install the default integration you can amend the integration through its configuration files. You should stop the integration from forwarding events when amending its configuration. (See Stopping and Starting Event Forwarding.) Editing of the configuration files allows you to:
change the default view and user account create configuration that allows forwarding of events from multiple Entuity views. Each
view requires its own forkevent. Before amending the default configuration backup the Entuity integration module for BMC ProactiveNet Performance Management configuration files. After amending the default configuration take a second backup of these files. If you are amending the content of the default files, but not renaming them, the next time you upgrade Entuity their content is overwritten. You can use the second backup to restore your customisations.
Amending the Default View and User Account

Through Component Viewer you can create a view, and define a user account, for use when connecting to BEMForkEvent. Through this view you can restrict which events are forwarded, by event type and/or by managed object. To change the Entuity view and user account used to forward events:
1) Open an Entuity client and create the view, e.g. coreRouters, for use with the integration.
Take care to include to the view only those object - event type combinations against which you want to forward events. By default all events that are raised in this view are forwarded to the BMC ProactiveNet Performance Management. You can open this view in Event Manager, the events raised here are the events Entuity would forward to the BMC ProactiveNet Performance Management.
2) From the view use Access Control to associate the user groups allowed to access the
view. This user group should include the user account, e.g. JJones, you are going to use with BEMForkEvent.
3) Amend entuity_home/etc/entuity.cfg to permit access to that view on your Entuity server,

for example:
[bem] username=JJones view=coreRouters
2-7
Entuity
This example forwarded all events in the coreRouters view, with access being permitted to forkevent through the defined Entuity user account, JJones.
h
By default Entuity integration module for BMC ProactiveNet Performance Management forwards all events in the defined view. You can apply an additional filter, through sw_bem_menu_def.cfg, which would only forward explicitly detailed events.
Stopping and Starting Event Forwarding

By default bemforkevent starts when Entuity starts, this is configured through the [bemclient] section in entuity_home/etc/startup_o/s_site_specific.cfg. You can copy the sample configuration from entuity_home/etc/startup_o/s.cfg.
[bemclient] state=none
To control event forwarding:
1) Stop the Entuity server. 2) From the [bemclient] section set the state to: normal, for the Entuity integration fpr Entuity integration module for BMC
ProactiveNet Performance Management to run
none, to suspend the forwarding of events. 3) Stop and restart Entuity.

Entuity integration module for BMC ProactiveNet Performance Management logging information is listed in EventActionApplication.log file. For more detail set the log level to info in entuity_home/etc/BemForkEventLoggerConf.xml. You can view the current state of the forkevent process, through the Process Health page of the web interface.
2-8
3 Managing Event Forwarding

You can configure Entuity to automatically generate events for BMC ProactiveNet Performance Management servers. The trigger for the forwarding of an event is the raising of an event which has an associated advanced action configured through the Entuity integration module for BMC ProactiveNet Performance Management integration.
Automatic Event Forwarding is View Based

When Entuity (proffer) raises an event it checks against the forwarding filter as to whether the event details should be forwarded to the BMC ProactiveNet Performance Management, specifically is the raised event:
in the specified view, e.g. Regional does the specified user account allow access to the view, e.g. admin of the specified type, e.g. in the sample configuration all events are passed.
Only when all conditions are met is event information passed to the BMC ProactiveNet Performance Management.
h
In the sample configuration the Regional view and all event types are specified, which would result in all events received by the Entuity server being forwarded to BMC ProactiveNet Performance Management server. Entuity recommend changing the view to a more restricted view, through bemforkevent.cfg.
Controlling Which Events the Integration Forwards

Through a combination of Entuity view and advanced action configuration Entuity integration module for BMC ProactiveNet Performance Management determines when an event raised in Entuity results in the automatic forwarding of an event. Entuity views allow you to control the combination of managed objects and event types that can appear in a view. Through:
bemforkevent.cfg you define the connection to this view; the connection used by
forkevent to forward event information to the BMC ProactiveNet Performance Management.
sw_bem_menu_def.cfg you can configure an additional event filter, so not all events
raised in the view are forwarded.
Using Entuity Views with Event Forwarding

Entuity views allow you to control both the objects displayed, and the events displayed through two filters:
an object filter that only permits those objects against which you would want to forward
events.
Entuity
Troubleshooting Event Forwarding
a view filter, through which you select which type of events are displayed against the
managed objects in the view. When you have setup a view you must still configure forkevent to use that view, through the connection section of bemforkevent.cfg. Entuity recommend you tightly control the number of managed object - event combinations that can Entuity integration module for BMC ProactiveNet Performance Management forwards. For details on view creation and management see the Entuity System Administrator Guide.
Event Severity and Descriptions

Entuity event severity and event description are configurable from the Entuity client, through the Preferences dialog. When you amend these settings from the client on the Entuity server the forwarded events include these changes.
Configuring Advanced Action Filters

The event filter is defined as part of the Advanced Action in sw_bem_menu_def.cfg. By default this event filter uses wildcards (asterisks) for event group and event identifiers, allowing events of all types through to the BMC ProactiveNet Performance Management:
[MenuItem Event_Menu_BEM_ForkEvent] . supportedEventTypes=*:* .
You can adjust the event filter to only forward explicitly specified events, for example:
supportedEventTypes=8:7
uniquely identifies AvailMonitor Node Down as 8 is its event group identifier and 7 is its event identifier. (See the Entuity Event Guide for details on Entuity event groups and identifiers.) You can identify more than one event type, using commas to separate each event:
supportedEventTypes=1024:800,1024:802
respectively identifies AP Host Count High and AP Host count Low events.
h
Entuity recommend you consult your Entuity Support representative before amending Advanced Action configuration files.

Entuity integration for Entuity integration module for BMC ProactiveNet Performance Management includes two log files in entuity_home\log:
BEMForkEvent.log BEMForkEventFailedSend.log.
Entuity
BEMForkEvent.log
This log file records the reasons for event forwarding failure:
when the target BEM cell does not exist on the target BMC ProactiveNet Performance
Management, the log file includes this message:
Check BMC II Web Server is running on [serverName] and that cell[eye_integration] exists Error -110 connecting to cell eye_integrations.File eye_integrations, Line impl.cpp.
when the forwarding of an event fails, the log file includes this message:
Check BMC II Web Server is running on [serverName] and that cell[eye_integration] exists
when a connection to the BMC Web Services Server fails

Check BMC II Web Server is running on [serverName] java.net.ConnectException: Connection refused: connect
BEMForkEventFailedSend.log
This log file records the events Entuity fails to forward.
3-3
4 Viewing Entuity Events in BMC ProactiveNet Performance

Management
Entuity forwards appropriately configured events to BMC ProactiveNet Performance Management, which through the addition of an Entuity event class can handle these events. From BMC ProactiveNet Performance Management you have available a full history of the event including severity levels, event type, event source. You can also drill-back from BMC ProactiveNet Performance Management to the event source in Entuity.
Entuity Events in BMC ProactiveNet Performance Management

This section indicates the type of Entuity event data displayed within BMC ProactiveNet Performance Management.
Figure 4-1 Entuity Forwarded Events
Event Summary Information

The Event Information section details:
Entuity
Status, indicates current status of the event, e.g. Open. Severity, BMC ProactiveNet Performance Management event severity. Message, Entuity event name and source Entuity server. Detailed Message, Entuity event name, source Entuity server and event details. Class, Entuity event class, EYE_EVENT. Repeated, number of times the event is repeated. Metric, Entuity event name.
Figure 4-2 Entuity Event Summary
Event Object Information

The Event Monitored section details:
Object, identifier of the managed object, e.g. the interface on the device. Object Class, type of Entuity object, e.g. StormWorks, Device, Application. Object URI, opens the event in Entuity. Host, identifier of the managed device. Parameter, name of the Entuity event. Location, physical location of the managed object.
4-2
Entuity
Figure 4-3 Entuity Event Object Details
Event Log and Note Information

Time Stamps section provides the events history:
Occurred, time the event was raised in Entuity. Origin Time, time the event was raised in Entuity. Arrived, time the event arrived at the BMC ProactiveNet Performance Management. Received, time the event received at the BMC ProactiveNet Performance Management. Modified, time the event was last modified, indicating the event has been repeatedly raised.
Repeated, number of times Entuity raised the event.
4-3
Entuity
Figure 4-4 Entuity Event Logs and Notes
Event Source Information

Event Source section details:
Tool, name of the event provider software, i.e. Entuity. Tool ID, Entuity server name. Client Address, Entuity client address. Tool Class, environment Entuity is installed to. Tool Severity, Entuity severity level. Tool Address, Entuity server IP address.
4-4
Entuity
Figure 4-5 Entuity Event Source Details
Event Other Details

Event Other section details:
eye_comp_id, internal Entuity component identifier. eye_event_group Entuity event group identifier. eye_event_id, Entuity event identifier which is unique within the event group. eye_impact_descr, indicates the impact of the network event on performance. eye_stormworks_id, internal Entuity unique object identifier. eye_userID, Entuity user account name used for forwarding events.
Figure 4-6 Entuity Event Other Details
4-5
Entuity
Launching Entuity From BMC ProactiveNet Performance Management
Launching Entuity From BMC ProactiveNet Performance Management

You can launch Entuity from BMC ProactiveNet Performance Management. This launch the uses the Object URI available from the events object panel, displaying the events object details in Entuity.
Figure 4-7 Launching Entuity in Context
4-6
Appendix A
Integration Installation Files
Name and Location of Integration Files

Entuity integration module for BMC ProactiveNet Performance Management is supplied with your standard Entuity installation. The installed integration includes:
sample configuration files in entuity_home/etc/: bem.cfg bemforkevent.cfg BEMForkEventLoggerConf.xml. sw_bem_menu_def.cfg startup_O/S.cfg startup_O/S_site_specific.cfg file generated after configure in entuity_home/install/template/etc: bem.cfg files in entuity_home/integ/BEM/etc: BEMEventTypes.properties BEMSeverityMapping.properties files in entuity_home/integ/BEM/server/etc/CELL/kb/: classes/eye_event.baroc collectors/eye_collector.mrl rules/eye_integration.mrl files in entuity_home/integ/BEM/console/etc/event_op/: eye_actions.xml eye_cross_launch eye_cross_launch.cmd LocalActions.xml files in entuity_home/integ/BEM/lib/: BMCEventManager.jar iiws-client-stub.jar sendEvents.jar
Renaming Configuration Files

The sample configuration files are overwritten with each new Entuity installation. When you want to use the sample configuration in a live installation you can either take a backup of your files and reinstall them after each upgrade, or consider the supplied files as templates that you should rename after amending them. When renaming files remember to edit the content, so any references to these files are also amended.
A-1
Entuity
Configuration Files
Renaming Sample Configuration Files

Rename the sample files and settle on a standard naming format, for example:
sw_bem_menu_def_NEWNAME.cfg. bemforkevent_NEWNAME.cfg.
You must also rename any references to these files within the configuration files. For example, in:
sw_menu_def_site_specific.cfg, include sw_bem_menu_def_NEWNAME.cfg. bemforkevent._NEWNAME.cfg, rename the references to BEMForkEventLoggerConf.xml

to BEMForkEventLoggerConf_NEWNAME.xml.
startup_O/S_site_specific (bemclient section copied from startup_O/S.cfg), rename the

reference to bemforkevent.cfg to bemforkevent_NEWNAME.cfg.
Configuration Files
Entuity integration module for BMC ProactiveNet Performance Management configuration files:
identify the connection between Entuity and the BMC ProactiveNet Performance
Management server(bem.cfg)
define the event information to forward from Entuity (BEMEventTypes.properties,

bem_forkevent.cfg)
map the event severity levels of the two pieces of software

(BEMSeverityMapping.properties)
map Entuity event fields to BMC ProactiveNet Performance Management slots, using
existing slots or ones created for Entuity (sw_bem_menu_def.cfg)
define the Entuity event class (eye_event.baroc).

h
Entuity provide a sample integration for forwarding event information.
bem.cfg
bem.cfg is automatically generated by configure. It defines the connection between Entuity and the BMC ProactiveNet Performance Management cell.
[connection] cellname=entuity webServerHostName=decade webServerPortNumber=9080 webServiceName=ImpactManager refreshCache=3600
where:
A-2
Entuity
Configuration Files
Cellname, the BMC ProactiveNet Performance Management instance to which Entuity

forwards events.
webServerHostName, hostname of the server where the BMC II Web Services Server is
located.
webServerPortNumber, the port number used by the BMC II Web Services Server, by
default 9080.
webServiceName, the name of the web service, by default ImpactManager. refreshCache is the time in seconds that the integration slots are maintained in memory
by Entuity, after which Entuity automatically initiates a refresh of the list. The default value is 3600.
BEMEventTypes.properties
BEMEventTypes.properties defines BMC ProactiveNet Performance Management slots and their types. These are the slots and their formats supplied in the sample integration:
mc_ueid=STRING msg=STRING mc_long_msg=STRING severity=STRING mc_tool_sev=STRING mc_tool=STRING mc_tool_id=STRING mc_tool_address=STRING mc_tool_class=STRING mc_parameter=STRING mc_parameter_value=STRING mc_parameter_unit=STRING mc_incident_time=STRING mc_object=STRING mc_object_class=STRING mc_tool_key=STRING mc_tool_uri=STRING eye_userId=STRING eye_impact_descr=STRING eye_stormworks_id=STRING eye_comp_id=STRING eye_event_group=STRING eye_event_id=STRING
A-3
Entuity
Configuration Files
BEMSeverityMapping.properties
BEMSeverityMapping.properties maps Entuity event severity levels to BMC ProactiveNet Performance Management event severity levels:
EYE_SEVERITY_CRITICAL=BEM_SEVERITY_CRITICAL EYE_SEVERITY_SEVERE=BEM_SEVERITY_MAJOR EYE_SEVERITY_MAJOR=BEM_SEVERITY_MINOR EYE_SEVERITY_MINOR=BEM_SEVERITY_WARNING EYE_SEVERITY_INFO=BEM_SEVERITY_OK
Advanced Action Definition

sw_bem_menu_def.cfg defines the Advanced Action that initiates forwarding of Entuity events.
BMC ProactiveNet Performance Management Entuity Event Class

eye_event.baroc defines the Entuity event class for use in the BMC ProactiveNet Performance Management server. Each element within the definition is a slot. This example creates the additional fields required to manage Entuity event information in the sample integration:
MC_EV_CLASS : EYE_EVENT ISA EVENT DEFINES { mc_object: dup_detect=yes; mc_tool_id: dup_detect=yes; eye_userId: STRING; eye_impact_descr: STRING; eye_stormworks_id: STRING; eye_comp_id: STRING; eye_event_group: STRING, dup_detect=yes; eye_event_id: STRING, dup_detect=yes; }; END
A-4
Appendix B
Configuring Event Forwarding
For automatic event forwarding you must configure and run forkevent. The default instance of forkevent is called BEMForkEvent. forkevent is configured through its own event action configuration file (bemforkevent.cfg), to forward event information to the EventActionApplication. Specifically forkevent uses details in the [pipe_bem7_4] section when calling EventActionApplication. forkevent structures the event details, and sends the data to EventActionApplication using the stdin of the pipe process.
h
You can also run more than one forkevent process at one time, although they must use different configuration files. For details contact your Entuity Support representative. EventActionApplication uses the default configuration, specifically:
1) EventActionApplication uses the appropriate menu in sw_bem_menu_def_menu.cfg to

build a complete parameter list from forkevents direct data and StormWorks event object details and Entuity host/user information.
2) EventActionApplication builds a string that contains the returned parameters and then
passes it to the BMC ProactiveNet Performance Management. forkevent connection uses details in the [bem] section of entuity.cfg to register with proffer. forkevent becomes a client of proffer, proffer only forwards to forkevent those events in the registered view.
Configuring forkevent
Pipe Process
forkevent communicates with the database using Pipe, each time forkevent recognizes an event it sends the event data to the stdin of the Pipe process. The format and structure of the event data is taken from the [data] section in the configuration file. The Pipe continues to run until it is explicitly stopped or the Entuity server is stopped. Each time a new event occurs the same forkevent process is used. In Pipe mode forkevent sends event data in the format:
VariableLabel VariableValue <CR> BlankLine <CR>
Where:
VariableLabel is the label assigned to the event data in the [data] section, e.g. Descr in
Descr=${event.PAPIDescr}.
VariableValue is the event data value, extracted from the [data] section, e.g.
${event.PAPIDescr} in Descr=${event.PAPIDescr}.
B-1
Entuity
<CR> is the end of line marker. Each value is passed on its own line. BlankLine is automatically sent at the end of the event data to signal the end of that event. Integration forkevent Configuration
The Entuity integration module for BMC ProactiveNet Performance Management configuration file, e.g. bemforkevent.cfg, contains details used to determine the format and order event data is passed to the BMC ProactiveNet Performance Management server. There are a number of sections, each starts with its section name, enclosed within square brackets, e.g. [connection] and [data]. All variable definitions are held within sections. These sections can be divided into three types:
Connection section contains details required to access the Entuity database (see
Connection Section).
Process section determines which parameters are passed. You can specify one or more
process sections, which one is used is passed as an argument when running forkevent (see Process Sections).
Data section details the event data passed to the Pipe process (see the Data Section).
h
Entuity supply a sample file, bemforkevent.cfg. You should read this section and then take a backup of the file before attempting to amend it. Connection Section In bemforkevent.cfg configure the connection, for example:
[connection] username=${bem.connection_username} view=${bem.connection_view} extendedEvents=${bem.connection_extendedEvents}
Process Sections The process sections define the pipe process and its arguments. A configuration file can have more than one process definition, although only one is used at any one time. This is passed as an argument when forkevent is run. This is the sample process section:
[pipe_bem7_4] start=${install.JAVA} -Dlog4j.configuration=file:${ENTUITY_HOME} ${FPS}etc${FPS}BEMForkEventLoggerConf.xml =-Dhostname="" =-Djava.library.path=${ENTUITY_HOME}${FPS}lib =-Dbem.properties=${ENTUITY_HOME}${FPS}etc${FPS}bem.cfg =-Dseverity.mapping=${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}etc${FPS} BEMSeverityMapping.properties
B-2
Entuity
=-Dbem.eventTypes=${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}etc${FPS} BEMEventTypes.properties =-cp ${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}common${FPS}classes$ {EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}webapps${FPS}webUI${FPS}WEB -INF${FPS}lib${FPS}EYEAuthModel.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}webapps${FPS}webUI${FPS}WEB -INF${FPS}lib${FPS}EyeAuthClientWS.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}webapps${FPS}webUI${FPS}WEB -INF${FPS}lib${FPS}XMLStream.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}common${FPS}lib${FPS}activa tion.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}common${FPS}lib${FPS}jaxbapi.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}common${FPS}lib${FPS}jaxbimpl.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}common${FPS}lib${FPS}jsr173 _1.0_api.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}common${FPS}lib${FPS}webrpc .jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}TomCat${FPS}webapps${FPS}webUI${FPS}WEB -INF${FPS}lib${FPS}mysql-connector-java-3.1.13-bin.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}ImpactManager-testclient.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}BMCEventManager.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}axis2-kernel1.5.1.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}axis2-adb1.5.1.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}axiom-api1.2.8.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}axiom-impl1.2.8.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}XmlSchema1.4.3.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}neethi2.0.4.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}axis2-transportlocal-1.5.1.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}axis2-transporthttp-1.5.1.jar${EPS}
B-3
Entuity
=${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}commons-httpclient3.1.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}mail-1.4.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}httpcore4.0.jar${EPS} =${ENTUITY_HOME}${FPS}integ${FPS}BEM${FPS}lib${FPS}commons-codec1.3.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}map${FPS}axis.jar${ EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}map${FPS}jaxrpc.jar ${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}map${FPS}commonsdiscovery-0.2.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}map${FPS}commonslogging-1.0.4.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}map${FPS}saaj.jar${ EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}map${FPS}wsdl4j1.5.1.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}EOSServer.jar${EPS} =${ENTUITY_HOME}${FPS}lib${FPS}httpd${FPS}EOS${FPS}log4j.jar =com.entuity.eos.menu.EventActionApplication =period=0 appname=BEMForkEvent userid=${bem.connection_username} webport=${webportnum} args= type=pipe directory=${LOGDIR}
Where the following arguments may be passed to the menu application:
[pipe_bem7_4] is the section name. This is passed as a parameter with the forkevent
command.
start runs the specified application with the set arguments: maxactions, the maximum number of concurrently executing menu actions, by default
15. Once exceeded Entuity queues remaining actions. It is optional, but when set must be 1 or greater.
timeout, the time after which an executing action can be removed from the pool and
queued actions run. A timeout action can be terminated, or left for execution based on the value of terminate. 0 indicates no timeout, the default is 900000 ms, 15 minutes, and the minimum value is 100 ms.
terminate, when set to true, the default, terminates a timed-out action, false allows the
action to complete.
period, specifies the minimum amount of time in milliseconds that must elapse
Entuity Integration Module for BMC ProactiveNet Performance Management Guide B-4
Entuity
between action executions, and is used to control throughput of action executions and system load. The default is 1000.
dshost, IP address or hostname of the Entuity StormWorks server, by default

localhost.
dsport, Entuity StormWorks port, the default is 5467. dstimeout, timeout for the Entuity StormWorks database connection. The default is 60
seconds.
appname, name of the application forkevent runs to gather the BMC ProactiveNet
Performance Management data.
userid, the account name used to access Entuity events. When customising the
installation you could change this user account.
clienthost, application's IP address, by default localhost. eyeserver, IP address or hostname, and port of the Entuity web server, by default
localhost:80. This attribute is used in place of webport but can also make use of it, for example where keli is the Entuity server hostname:
eyeserver=keli:${webportnum}
webport, the port on which the Entuity web server is accessible, by default 80. args allow you to pass commandline arguments with the Pipe and Fork processes. They
are not used with the Entuity integration module for BMC ProactiveNet Performance Management.
When type is pipe, start runs as soon as forkevent runs, creating the Pipe process. EmptyVariable is used to enter a value in an event variable passed from Entuity that does
not contain any data, i.e. to make it easier to identify in the integrated package. By default EMPTY_VARIABLE is entered, using EmptyVariable you can replace that with one of your choice, e.g. MISSING_VALUE.
directory is the directory from which the process is run and log files are written to. loglevel is the level of logging information recorded, i.e. errors, warning, info, debug
and all. Data Section This section holds the associations between labels and Entuity event variables. These labels can be used by the Pipe process to identify and manipulate event data. There must only be one data section in an Event Forward configuration file.
h
The data section is only used with the Pipe process. The Pipe process runs continually and it is only through the data section that arguments can be passed for each event. The Fork process is started for each event, and so arguments are passed each time an event occurs. This is an example section:
[data] event.PAPIId=${event.PAPIId} event.PAPIEventGroup=${event.PAPIEventGroup}
B-5
Entuity
event.PAPIEventId=${event.PAPIEventId} event.PAPIEventStr=${event.PAPIEventStr} event.PAPItimeStamp=${event.PAPItimeStamp} event.PAPIObjectID_1=${event.PAPIObjectID_1} event.PAPIObjectID_2=${event.PAPIObjectID_2} event.PAPIObjectID_3=${event.PAPIObjectID_3} event.PAPIObjectID_4=${event.PAPIObjectID_4} event.PAPIpriority=${event.PAPIpriority} event.PAPIAttr=${event.PAPIAttr} event.PAPIDescr=${event.PAPIDescr} event.PAPIImpact=${event.PAPIImpact} event.PAPIImpactDescr=${event.PAPIImpactDescr} event.PAPIDetails=${event.PAPIDetails}
Where:
[data] is the mandatory name of the data section. ${event.PAPIID} is a numeric value specifying the current instance of the event. ${event.PAPIEventGroup} is a numeric value specifying the event's group. ${event.PAPIEventID} is the event identifier within the context of the event group.
The combination of event group and event ID uniquely identify all Entuity event types (see the Entuity Event Guide).
${event.PAPIEventStr} is the description of the event associated with the event identifier. ${event.PAPItimestamp} is the time the event occurred, represented as UTC
(Coordinated Universal Time, i.e. the number of seconds since 1970-01-01 00:00:00 GMT).
${event.PAPIObjectID_1}, ${event.PAPIObjectID_2} and ${event.PAPIObjectID_3} and

${event.PAPIObjectID_4} are internal values that indicate the origin of the event.
${event.PAPIpriority} is an obsolete attribute retained for Entuity backward compatibility. ${event.PAPIAttr} is an internal numeric attribute, not used for the integration. ${event.PAPIImpactDescr} lists entities likely to be affected by the event, e.g. hosts,
VLANs and monitored applications.
${event.PAPIDescr} is a textual description of the managed object on which the event

occurred, e.g. VLAN, device, module or port.
${event.PAPIDetails} is supplemental information on the particular event, e.g. actual

values of network statistics which caused a threshold event.
B-6
Entuity
Configuring forkevent Connection

The bem section in entuity.cfg uses the connection information in bemforkevent.cfg, to provide the information required to access Entuity to collect event data. This is an example section:
[bem] connection_username=admin connection_view=Regional connection_extendedEvents=0 version=7_4
Where:
[bem] is the name of the section that contains the details required to access Entuity event
data.
connection_view is the Entuity view from which events are collected, by default Regional.
Only when an event occurs on a managed object within the defined view is it forwarded by forkevent. Regional includes all managed objects, Entuity advise changing view to a more restricted view to only include events from required objects.
connection_extendedEvents sets the maximum number of characters that forkevent

forwards for the event description. Event descriptions greater than this setting are truncated. When set to:
0, forwards event descriptions to a maximum of 127 characters 1, forwards event descriptions to a maximum of 4095 characters.
h
You should create the view and user account to use with Entuity integration module for BMC ProactiveNet Performance Management before configuring the integration. After configuring the integration and restarting Entuity, Entuity immediately starts forwarding events using these connection details. If the view and user account combination do not exist the integration fails.
version, sets the version of IIWS used with the integration to 7.4. This is the default setting
and supports the recommended BMC products:
BMC ProactiveNet Performance Management 8.0.10/BEIM 2.0 using the web

services API of the BMC Impact Integration Developers Kit 7.3.02.
BMC ProactiveNet Performance Management 8.5 using IIWS 7.4.

To use this integration with an earlier version of IIWS and allow it to work with BMC ProactiveNet Performance Management 8.0 or BMC Event Manager 7.X, remove the version number, i.e.:
version=
B-7
Appendix C
Configuring Context Cross Launch
Configuring cross context launch of Entuity is only required for versions of BMC ProactiveNet Performance Management earlier than 8.0.
Configuring the Entuity Context Cross Launch

The context cross launch is implemented as a Local Action of the BMC ProactiveNet Performance Management Server.
1) Copy to IMPACT_SOLUTIONS_HOME/console/etc/event_op these files:

entuity_home/integ/BEM/console/etc/event_op/eye_actions.xml entuity_home/integ/BEM/console/etc/event_op/eye_cross_launch entuity_home/integ/BEM/console/etc/event_op/eye_cross_launch.cmd
2) Edit IMPACT_SOLUTIONS_HOME/console/etc/event_op/LocalActions.xml to include the

Entuity action group:
<ActionGroup name="EYE Tools" tip="Eye of The Storm Actions"> <Action location="eye_actions.xml" id="eye_cross_launch"/> <EventClass>EYE_EVENT</EventClass> </ActionGroup>
3) Restart the <CELL_NAME> you are sending to.
C-1
Glossary
BMC Cell
BMC Impact Manager instance. A cell receives events from Entuity and displays them in the BMC IX.
BMC II Web Services Server

BMC Impact Integration Web Services Server. You can connect to the BMC II Web Services at the end point as defined by the URL format, http://webServerHostName: webServerPortNumber/webServiceName, e.g. http://decade:6080/impactManager.
BMC IIDK
BMC Impact Integration Developer's Kit, used with the Entuity BEM System.
BMC IX
BMC IX (BMC Impact Explorer) displays events received from Entuity.
BMC ProactiveNet Performance Management

BMC ProactiveNet Performance Management which receives events from Entuity.
Data Management Kernel (DMK)

The DMK supports Entuity's intelligent discovery function. It includes out of the box data models for a wide range of managed devices including hundreds of Ethernet switches and routers. These customizable data models define the attributes of each managed element, its possible dependencies in relation to other elements of the network, and the specific details to retrieve for each element. The DMK manages these data models and automatically applies updates and changes to the Entuity database schema.
Drop Box
Drop box acts as a temporary repository for objects, for example gauges, charts, links, device metrics, that you want to include to new reports, dashboards.
Entuity
Entuity is both the name of the network management software and the company producing it. Entuity software is designed for networks of any size and complexity, from the smallest, simplest corporate infrastructure to the largest multinational. Every customer can access the full functionality of our cornerstone solution, incorporating fault, performance and inventory management.
Entuity Integration Module for BMC ProactiveNet Performance Management Guide Glossary-1
Entuity
Essential Reports
Entuity provide a number of Essential Report templates that determine the basic report type, e.g. PVC Data Loss report. An Entuity administrator can use these templates to create new Essential Report definitions, setting when the report runs, which view it reports on, the page layout and the reports Prime Time. Entuity users that have access to the associated views, can then access the generated reports through Reports in the web UI or Component Viewer. These reports are currently available as pdf documents.
Eye of the Storm (EYE)

Until Entuity 12.5 the software was known as Eye of the Storm (EYE).
Polling Engine
The Polling Engine (or Core Management Engine) is the set of processes within an Entuityserver responsible for all general network management tasks excluding flow collection (e.g.network discovery, inventory, monitoring, event management). Administrators can enable/disable an Entuity servers Polling Engine through configure, a decision which should be made according to the role the administrator wants the server to perform in the management of the network.
Reachability
Availability Monitor sends an ICMP ping to the management IP address of managed devices, by default every two minutes. Devices that respond are considered reachable, those that do not respond, after the set number of retries, are considered unreachable. When Availability Monitor is not running, then the reachability of the device is Unknown for that period, although Entuity maintains the last known state of the device. Entuity maintains a record of device reachability, which is available through Entuity reports, e.g. Routing Summary, Switching Summary, Device Uptime and Reachability reports.
Reboot
Entuity uses the device sysuptime to calculate when the device was last rebooted, or more accurately when the device last came up after being rebooted.
Uptime
By default Entuity polls devices every five minutes, retrieving device sysuptime. Entuity checks as to whether the device has been continually up since the last poll, and modifies the devices uptime value accordingly. When sysuptime indicates the device has been down during the polling interval but is now up, from sysuptime alone Entuity cannot identify for how long the device was down. Entuity
Glossary-2
Entuity
takes this unknown time, and adds fifty percent of it to the known uptime value, with the remaining fifty percent considered UNKNOWN. For example where sysuptime has a value of two minutes. Entuity cannot determine the state of the device over the first three minutes of the polling interval. Entuity adds ninety seconds to the sysuptime value, giving an uptime value of two hundred and ten seconds and records the device state as UNKNOWN for ninety seconds. Device uptime is visible through Component Viewer, and is used in many reports, e.g. Routing Summary, Switching Summary, KPI Device Availability / Uptime.
Glossary-3
Entuity
Index
A
Advanced Actions configuration 2-3 event filters 3-2 Event Forwarding event attributes B-5 EventActionApplication 1-2 configuration 2-3 EventActionApplication.log 2-8
B
baroc file Entuity event class 2-1 bem.cfg A-2 BEMEventTypes.properties A-3 BEMForkEvent B-1 bemforkevent.cfg 2-7, 2-8 bemForkEventLoggerConf.xml 2-8 BEMSeverityMapping.properties A-4 BMC Event Manager 7.X B-7 BMC ProactiveNet Performance Management versions 1-1, B-7 amending B-7 BMC ProactiveNet Performance Management 8.0 B-7
Events filtering 3-2 groups B-6 identifiers B-6 restricting B-7 Extensible Menus 1-4, 2-3 eye_collector.mrl A-1 eye_event.baroc 2-1, A-4 location A-1 eye_integration.mrl A-1
F
forkevent application name B-5 automatic startup 2-8 connection B-7 data B-5 process B-2 workflow B-1
C
cacheRefresh A-3 cacheUser A-3 Configuration Files Entuity upgrades A-2 renaming A-1
L
Log Files 2-8 troubleshooting 3-2
D
DMK Glossary-1
P
Pipe mode B-1 Process Health forkevent 2-8 proffer raising events 3-1
E
Entuity integration module for BMC ProactiveNet Performance Management files A-1 installing A-1 entuity.cfg bem section 2-3, B-7
R
Renaming Configuration Files A-1
Index-1
Entuity
S
Security 1-2 startup_O/S_site_specific.cfg A-1 backups A-2 definition 2-3 startup_O/S.cfg A-1 definition 2-3 sw_bem_menu_def.cfg 1-4, 2-3, A-4 backups A-2
U
User Account bemforkevent.cfg 2-7, B-5
V
Views restricting events B-7
Index-2

Entuity Integ BPPM

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Entuity Integ BPPM

Hochgeladen von

Copyright:

Verfügbare Formate

USER GUIDE

North America Headquarters

Copyright 2000 - 2012 Entuity. All rights reserved.

2 Configuring the Integration

3 Managing Event Forwarding

4 Viewing Entuity Events in BMC ProactiveNet Performance Management

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

Launching Entuity From BMC ProactiveNet Performance Management .............4-6

A Integration Installation Files

B Configuring Event Forwarding

C Configuring Context Cross Launch

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

1 Integrating BMC ProactiveNet Performance Management

BMC ProactiveNet Performance Management

Entuity integration module for BMC ProactiveNet Performance Management

BMC ProactiveNet Performance Management 8.5 using IIWS 7.4.

Entuity integration module for BMC ProactiveNet Performance Management

Overview of Forwarding Events

4) BEMForkEvent forwards events to the BMC ProactiveNet Performance Management IIWS

5) BMC ProactiveNet Performance Management server is configured for Entuity events

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

Mapping Severity Levels

Advanced Action Configuration

Event Action Configuration

BMC ProactiveNet Performance Management Configuration

BMC Server Impact Manager

BMC ProactiveNet Performance Management Server

Entuity supplied console, collector class and rule files

Figure 1-1 BMC ProactiveNet Performance Management Architecture

Mapping Severity Levels

BMC ProactiveNet Performance Management Severity Color

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

Mapping Severity Levels

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

2 Configuring the Integration

2) activating the Entuity integration module for BMC ProactiveNet Performance

Configure BMC ProactiveNet Performance Management Server

Configuring the Entuity Classes, Rules and Collectors

1) Copy the class, rules and collector files: entuity_home/integ/BEM/server/etc/CELL/kb/classes/eye_event.baroc to

Integration Configuration Files

3) Update the file MCELL_HOME/etc/<CELL_NAME>/kb/rules/.load to include:

4) Update the file MCELL_HOME/etc/<CELL_NAME>/kb/collectors/.load to include:

5) From MCELL_HOME/etc/<CELL_NAME>/kb/ run:

Integration Configuration Files

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

entuity.cfg startup_O/S.cfg startup_O/S_site_specific.cfg

Entuity Integration Module for BMC ProactiveNet Performance Management Guide

Configure Automatic Event Forwarding

Create Entuity view for the integration

Rename Configuration Files and References to those Files

Stop and Restart Entuity

Figure 2-1 Integration Configuration Process Overview

create a user account that allows access to the new view.

Configuring the Integration

Configuring the Integration

Copy to the Entuity server a valid license

Complete Integration Module Details

Create EYE view for Remedy

Figure 2-2 Configuring Event Forwarding

To activate the integration:

Configuring the Integration

Figure 2-3 Configure the Integration