- Alerts - Overview
- Are there any prerequisites before I create and forward Alerts?
- How can I forward Alerts to Enterprise Manager Tools?
- What are my options for adding and customizing Alerts?
- How can I check the status of my Alerts?
- How can I Activate and Deactivate Alerts?
- Do I have an option of viewing Alerts that were generated i.e. Alert Logs?
- How can I take an automated action when the Alert conditions are breached?
- Can I copy Alerts from one NonStop server to another?
- How can I suppress alerts for duplicate EMS messages?
- How can I escalate Alerts?
- How can I check Alert Detail for a specific metric?
- Overview - Delivery
- What delivery options do I have?
- How can I configure/update SMTP information?
- How can I configure Alert Delivery via SMS Text?
- What are the supported SNMP Versions?
- How can I configure SNMP protocol?
- How can I configure SYSLOG protocol?
- How to set up Alert Delivery to Enterprise Manager via JSON data?
- Overview - Create and Manage Users and Response Teams
- Are there multiple authentication methods?
- Can I restrict user permissions to specific sections of the Product?
- Can staff members create their own Alerts?
- Can Manager add Alerts and make them public to other Staff users?
- Add a Group instead of individual aliases
Onboard Your Own Apps
Configurations and Considerations
< All Topics
How can I define Events generated by my in-house applications?
0 out of 5 stars
- Business Application Manual (BAM) is where you can Cause, Effect, and Recovery information on EMS Events. You may enter these for NonStop Subsystem Events, as well as any of your inhouse applications.
Note: BAM is the primary source of detailed descriptive information consulted by HPE Web ViewPoint Enterprise’s Event subsystem. BAM uses a file similar to, but totally independent of Eventtx, which is consulted first by Web ViewPoint Enterprise. Messages need not be updated with new releases of Eventtx. Since this file is independent from Eventtx, any new release of Eventtx will leave BAM unaffected. Furthermore, you may enter information into BAM about a NonStop Event, which is already present in Eventtx. This enables the company to enforce its own set of instructions for any subsystem messages, to overwrite those present in Eventtx.
- Three columns of Owners, Subsystem, and Events list the current settings.
- Each column has a “+” Icon on its heading. Click on it to add.
- Adding an Event gives you the option to enter Cause, Effect, and Recover information.
- An additional field named Detail is also available to enter additional comments.
- Together, these give you the ability to tailor the information to your company. They guide your Operation Staff on how to respond to each Event, whether the Event is generated by a NonStop Subsystem, or one of your own (or vendor installed) Applications.
- Progressively click from left to right to select an Event. Its Cause, Effect and Recovery will be displayed on the far-right panel.
- Click on the Edit button placed below that panel to Edit the fields. BAM allows you to add and/or delete Owners, Subsystems, and Events. Go to Admin -> EMS -> Exceptions for doing this.
Was this article helpful?
0 out of 5 stars
Table of Contents