At its core, Web ViewPoint Enterprise was designed to be a browser based (Edge, IE 11, Firefox, and Chrome are supported) tool to monitor and query posted Events from HPE NonStop’s EMS (Event Management Subsystem).  This later expanded to offer:

• System Performance monitoring
• Alert & notification subsystem
• Failure recover logic
• Storage management & interface
• Spooler interface

This version also offers connection to a Cloud subsystem (if user chooses to activate) which can maintain a lifelong history of system performance data.  This can be used for a variety of purposes such as:

• Behavior analyses
• Problem avoidance
• Quick problem resolutions if/when they occur
• Capacity planning
• Application monitoring & chargeback
• System trend and availability reports
• Deep analyses

In a simplified format, these topics and usage of Web ViewPoint Enterprise is described in the following sections.

Web ViewPoint Enterprise is manufactured by Idelji Corporation www.idelji.com and marketed & supported by HPE.  For support contact HPE’s GNSC.  For more information, write webviewpoint@hpe.com 

The following is a summary of new features included in this release (H01AAE-L01AAF):

• • • Enhanced performance dashboard by providing customization of layout, design, and preferences on a per-user basis giving the flexibility users want.
    • New user authorization features are introduced into WVP E. Objective is to allow for a larger user community, while managing functions each user has access to. This also allows for each user to create her/is own environment and settings customized to suit.
    • Enhanced Threshold screen to make it more user friendly
    • Active CLIM sockets & openers are now displayed on the screen Subsystems/TCP/IP/Process Status.
    • Ability to ACK large number of events at once
    • Added a new section ‘Analyzer’ under Admin to manage EA/SA admin capabilities.
    • Ability to add email/text for users who do not have nonstop id’s; a new leaf ‘Response Team’ is added under Admin section to serve this purpose.
    • Other minor bug fixes and enhancements.

The following is a summary of new features included in this release (HO1AAC-LO1AAD):

• Added new entities to the alert monitoring feature, increasing the total monitorable resources from 48 to 60. Newly added alerts are listed below.
  • CPU:
    • PCB High Pin
    • PCB Low Pin
    • TLE

• • Pathway Server Class:

• • • Max Process Count
    • Min Process Count

• • • Expand:
      • Line Quality
      • Response Time
    • Netbatch:
      • State
    • Spooler:
      • State
  • Inclusion of Pathway
  • Enhanced the alerting module by:
    • Allowing wildcard in selection of Disks
    • Discarding duplicate EMS messages within a specific time frame
    • Suppressing specific events using a filter file
    • Providing ability to activate/deactivate alerts by entity type and/or group name
    • Providing ability to deactivate alerts for a specific time period.
  • Improved overall product usability by making minor enhancements
  • Playback of 1-hour worth of performance data on your browser
  • Enhanced online monitor piece
    • Added CPU/IPU Memory and Process Memory to the Summary graphs

• Improved the Admin-Threshold screen by introducing sliders to configure values.

A Neighborhood is a collection of NonStop Servers (Cluster), each of which has a running copy of Web ViewPoint Enterprise.  Each Server in this model is called a Resident.  Each Resident holds information (e.g. ip address / name) about all other Residents in its Neighborhood.  
Web ViewPoint Enterprise connects to each Resident directly (Expand is not used), and in doing so learns about all other Residents/neighbors. It is therefore able to retrieve information from all Residents and display content on one or more Browser Windows as its user requires.

By hierarchy, we refer to how access to information is organized, as it appears on the left panel of the browser. Web ViewPoint Enterprise

is designed for HPE NonStop Servers, and that is where the hierarchy starts.

A globe icon is displayed on the highest level.Click on this icon to see a the current Performance statistics of all the neighborhood Servers in a summary format.

Below the globe icon, each NonStop Server is identified by its name (e.g. MYNSTOP). Click on the Server name, to expose and access all available features, described below:

• • Performance – Has 2 sections under this category
    • Monitor – See current / live performance statistics of the Server in a more detail format, and if so licensed, access Remote Analyst for deep analyses, discoveries, and historical trends.
    • Events– See live and historical EMS (Event Management System) Events.
  • Operations– Comprises of the below sections
    • Event Analyzer – Event Analyzer captures daily snapshots of all EMS Events of one or more Collectors, which are then analyzed and stored in a historical indexed database.
    • Storage Analyzer – Storage Analyzer captures daily snapshots of all Disks and files, which are then analyzed and stored in a historical indexed database.
    • Storage – View and interact with the storage (Disks/sub-volumes/file) subsystem
    • OSS – View and interact with the storage subsystem from an OSS point of view.
    • Spooler – View and interact with the Spooler subsystem
    • Pathways – View Pathway User functions which include all day to day monitoring and management tasks for all supported Pathways
  • Admin– Perform the following administration tasks
    • Alerts – Setup EMS Events you want notifications to be sent out when they happen, and what automated action to take.
    • Delivery – Configure the following settings:
      • SNMP – Define SNMP information required to forward Events to Enterprise Management software (e.g. Tivoli).
      • JSON to Enterprise – Define the IP/DNS name, port number to which the JSON information must be sent
      • SMTP Server – Define SMTP information needed to email out Alerts
    • EMS
      • BAM – Business Application Manual (BAM) is really an imaginative/quirky (you be the judge) name given to the ability to add detail (description, cause, effect, recovery) information about Events generated by your in-house applications. Here is when you define them.
      • Exceptions– Description of category of Events you absolutely do not want to be bothered with.
      • Skins – Choose font type & size, and color characteristics of how Events should be displayed; give it a name, and use it. Your colleagues can create more, or use yours.
      • Template – A Template sets what you want to see on your Events screen, and how they should be displayed. Here is where you define them.
    • Pathways-Administration functions are used to initialize & maintain the central host databases used by Web ViewPoint Pathway. The following information is maintained per Pathway:
      • Lists number of TERM, TCP, and SERVER entities that are running
      • Maintenance of Group definitions
      • Syncing, Starting, Stopping and deleting pathways
      • Cold, Cool and Shutdown Obey file names
      • Start & Shutdown of Pathways
    • License – See when your license to use Web ViewPoint Enterprise on each Server expires. You may also (assuming internet connection to the outside world) receive updated licenses, or otherwise enter one given to you by HPE.
    • Users – Setup who (by guardian users) should have access to what features of Web ViewPoint Enterprise, and on what Servers. You can also enter their contact info for notification purposes.
    • Response Team – Add who (any non-guardian users) should be able to receive email and text alerts, and on what servers by configuring their contact information.
    • Thresholds – Thresholds can be defined on how the alerts can be viewed. Entering a numeric value for Warning and Critical section will determine the trigger for these thresholds.
    • Analyzer – Configure Event Analyzer & Storage Analyzer related settings.

Web ViewPoint Enterprise collects and displays performance data from HPE NonStop Servers every 5 seconds. This information is kept for 20 minutes in your browser’s memory.  Older data is cycled out, as new data comes in.  However, if your NonStop Server is licensed for Remote Analyst, then Remote Analyst modules on your NonStop can send all its performance data out to the cloud (internal to your cloud: Local Analyst, or on AWS: Remote Analyst), every 15 minutes.

Remote Analyst Password: If the user has a valid Remote Analyst license they can access their performance statistics directly from Web ViewPoint Enterprise. Clicking on the blue cloud icon available on the summary screen will prompt the users to enter a password associated with their Remote Analyst account. Once the password is entered, users will be able to see activities of their system in full detail.  You then have access to all historical data RA maintains, and may use all its features (if an active license is in place.)

This means that the information you may be missing on your browser memory (anything older than 20 minutes), is already in the cloud.  All you need to do, is to click on the cloud icon on the toolbar for any NonStop Server to access all historical data spanning years.  
If your Remote Analyst password is previously entered, then you will securely and automatically be logged into Remote Analyst, and see activities of your system in full detail.  You then have access to all historical data RA maintains, and may use all its features.

Click on the Clock icon to view the historical performance metrics. This icon is present on the left side of the title bar for each node, and is also available for each graph.

It stores up to 60 minutes worth of information. Based on the values set in Admin-Threshold section, values will be highlighted with the highest alert condition (yellow: warning alert, or red: Major alert.). features (if an active license is in place.)

Click on the Globe icon on the left panel, to see live Performance metrics on all your NonStop Servers in a summary format. Note that the title bar for each NonStop uses color to point out alert conditions. Color may be white: all is ok, yellow: warning alert, or red: Major alert.

Starting from (H01AAE-L01AAF), Ticker will not be available. WVP E ships with 6 Metrics/Frame options to choose from: CPU, Process, Disk, TMF, Network, & CLIM.

Dash Settings are saved on NonStop, per Guardian logon ID. Logon ID of 0,0 is the default everyone gets on initial logon. This is shipped by Idelji. Any user can make adjustments, and have their own individual settings when they save.

Display

The Performance Summary display can be customized by clicking the = icon.

Starting from H01AAE-L01AAF versions, by default, the dashboard layout is a 2-row, 6 entity setting with a display of both Live & Trend graphs. Within the settings screen, users can perform the following operations.

• Add upto 4 rows and 4 widgets per each row.
• Drag and drop widgets using pointer
• Remove widgets from the Dashboard
• Modify widget settings

Adding Rows and Widgets:

User can control the number of rows to be displayed by clicking on the dropdown list for Rows and can select upto 4 rows.

Click on the plus icon on the left to add a Widget to a row. Widget setting is displayed for the user to choose from available metrics and what should be displayed.

Click on the Plus again to add a second widget. Up to 4 widgets per row are allowed. At 4, Plus icon will be disabled.

 

Reset discards all the changes made before saving them. Once the settings are changes and saved to your desired settings, Reset will not switch it to the default.

The drag and drop function:

Move the widgets anywhere you want by simply dragging them with your pointer on icon.

Remove Widgets:

You can remove a widget by clicking on the icon at the top right corner of each widget frame.

Modify Widget settings:

On the main live Dash, a new setting icon will also be displayed for each frame. A click on that icon displays the above window enabling the user to make any necessary changes.

Below 2 sections are applicable for H01AAA-L01AAB & H01AAC-L01AAD versions.

• Monitor – graph widgets showing performance metrics
  • Select the zero or more Entities to display. Each entity corresponds to a graph widget
  • Specify whether the widgets will be displayed in one or two rows. The widgets are evenly distributed if 2 rows are selected.
• Ticker – select the type of information to show on the ticker
  • What:
    • CPU and/or Process
    • Show only those CPU/Processes that are above Minor or Major thresholds

Ticker (Applicable for versions H01AAA-L01AAB & H01AAC-L01AAD).

In addition to bell icon indicators, you can monitor the warning and critical threshold breaches using the ticker. The ticker can show Processes and/or CPUs that have breached warning or critical thresholds.

The ticker at every each interval

• • If all is OK then check mark is shown next to the interval timestamp (hh:mm:ss)
  • Otherwise If at least one Process or CPU (depending on the selection) has breached the threshold, then the interval time display is followed by one section per CPU. Each Section:

• • Has a CPU # indicator which is in yellow or red background..
  • Per CPU, Process name is displayed (PIN: nnnn if process name is unknown), followed with % busy value
  • If above threshold, follow with up or down arrow is displayed, in color matching threshold.

Dash View/Summary

Starting from versions H01AAC-L01AAD: Each panel can be collapsed or expanded. When expanded, you see six graphs (or upto 16 graphs). Each graph has its own panel. The heading of each panel is color coded (white, yellow, or red) to represent alert conditions currently in place for the information it represents. Bell icons (red/yellow) also show the number of alerts for each panel. Click on a bell icon to see details.

By default, there are six panels. Each panel is further divided into Live & Trend views:

• • CPU:Upper part of the widget (Trend): Per CPU, shows trend of % CPU Busy, CPU Queue Length or CPU Memory over time. Click on a CPU data point at a point in time to see either the list busiest Processes or Processes with the highest Receive queue at that time. Use the slide bar area below the graph to move back and forth in time and expand or contract your view. Click on the S icon on the heading to toggle the scale setting.

Lower part of the widget(Live): Per CPU, shows % CPU Busy (Y1), and Queue Length (Y2) of the most recent interval. % Busy is shown with a 100% cap. Click on any Y1 data point to see a list of top 5 busiest processes on the selected CPU, or on any Y2 data point to see a list of top 5 processes with the highest Receive Queue. On the new Window, click on any Process to see its trend over time. Also from the CPU graph, you may click on the trend icon (upper right) to either see a trend of % CPU Busy, or CPU Queue Length over time. On the new Trend Window, click on a CPU data point at a point in time to see either the list busiest Processes or Processes with the highest Receive queue at that time.

Counter	Formula
% Busy	(CPU-BUSY-TIME CPU / DELTA-TIME CPU) * 100
Queue Length	(CPU-QTIME CPU / DELTA-TIME CPU)
% Memory	(CURRENTLOCKEDMEMORY / MAXIMUMLOCKEDMEMORY) * 100

• • IPU (Applicable ONLY from Web ViewPoint H01ABQ-L01ABR & Web ViewPoint Plus H01AAI-L01AAJ) – Per CPU,shows a stacked bar of % IPU Busy of IPUs of that CPU (Y1), and Queue Lengths of IPUs of that CPU (Y2) of the most recent interval. % Busy is shown as a multiple of 100% since the IPUs are stacked. Click on the S icon on the heading to toggle the scale setting. Click on any Y1 data point to see a list of top 5 busiest processes on the selected CPU, or on any Y2 data point to see a list of top 5 processes with the highest Receive Queue. On the new Window, click on any Process to see its trend over time. Also from the IPU graph, you may click on the trend icon (upper right) to either see a trend of % CPU Busy, or CPU Queue Length over time. On the new Trend Window, click on a CPU data point at a point in time to see either the list busiest Processes or Processes with the highest Receive queue at that time.

 

 

Counter	Formula
Queue Length	(IPU-QTIMEn CPU / DELTA-TIME CPU)
% Busy	(IPU-BUSY-TIMEn CPU / DELTA-TIME CPU) * 100

• • Process – Per CPU, shows the % CPU Busy of the busiest Process (Y1), and Receive Queue of the Process with the highest Receive Queue (Y2). % Busy is shown in scaled format. Click on the S icon on the heading to toggle the scale setting. Click on any data point to open a new Trend window for either metrics. You may also click on the trend icon to see the same options. On the new Trend Window, click on a CPU data point at a point in time to see either the list busiest Processes or Processes with the highest Receive queue at that time. Use the slide bar area below the graph to move back and forth in time and expand or contract your view.
    

 

 

Counter	Formula
% Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
Receive Queue	(RECV-QTIME PROCESS / DELTA-TIME PROCESS)
Memory Used	(PRESPAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PagesToBytes

• • Disk – Per interval, for the recent intervals, shows the % CPU Busy of the Disk with the highest DP2 Busy (Y1), as well as queue length of the Disk with the highest Queue length. % Busy is shown in scaled format. Click on the S icon on the heading to toggle the scale setting. Click on either data points to see a list of top Disks in each category. You may also click on the trend icon to see the same options. On the new Window, click on any Disk to see its trend over time. Use the slide bar area below the graph to move back and forth in time and expand or contract your view.
    

 

 

Counter	Formula
% DP2 Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
Queue Length	(REQUEST-QTIME DISC / DELTA-TIME DISC)

• • TMF – Per interval, shows a stacked bar chart representing % of aborted transaction compared to total. Click on the a graph data point to see a list of top processes with the highest TMF activity. Click on the trend icon to see the trend of overall transaction activity (all processes – system wide). On the trend window, click on any data point to see a list of processes with the highest TMF activity at that point in time. Use the slide bar area below the graph to move back and forth in time and expand or contract your view.
    

 

 

Counter	Formula
% Abort	(ABORT-TRANS PROCESS / BEGIN-TRANS PROCESS) * 100
TPS	(ZTRANSACTION-RATE FROM TMF STATUS COMMAND) / 100

• • Network– Per interval, shows a trend for ‘Total Sent Messages’, and ‘Total Received Messages’ of the most recent interval. Click on any data points to see the Network Processes with highest Total Received messages/Total Sent messages. On the new Window, click on any Process to see its trend over time. Also from the Network graph, you may click on the trend icon (upper right) to either see a trend of Total Received messages, or Total Sent messages over time. On the new Trend Window, click on a data point at a point in time to see Processes with highest Total Sent/Received trend at that time. Use the slide bar area below the graph to move back and forth in time and expand or contract your view.
    

By default the alert values are already defined. Users can also modify the warning and critical level thresholds for performance statistics within the Admin Thresholds section.

When the threshold criteria is met, the Globe icon on the left panel, to see live Performance metrics on all your NonStop Servers will be highlighted with the highest alert condition (yellow: warning alert, or red: Major alert.).  The title bar for each NonStop uses color to point out alert conditions as well.  Color may be white: all is ok, yellow: warning alert, or red: Major alert.

On the right panel, each panel can be collapsed or expanded. The heading of each panel is color coded (white, yellow, or red) to represent alert conditions currently in place for the information it represents. It also shows the number of alerts for each pane. No color is displayed if there are no alerts.  

Bell icons (red/yellow) also show the number of alerts for each panel.  Click on a bell icon to see details.

Web ViewPoint Enterprise watches for alert conditions. It maintains a log corresponding to activity for each alert profile. You can review the activity by clicking on the Alert Log icon for any of the nodes. You are prompted for the following information:

Filter Options

• When: Select a review period from time and optionally to time to specify the time period of the activity that you are interested in.
• What
  • You can cast your net wide or zoom in on a specific instance. Select Any or specific entity / metric / instance combination
  • Severity: Look for any or specific type of alert conditions. At least one needs to be selected.
• Whom (optional)
  • If selected and users specified will filter only those alarms that were sent via email or text to the selected users or group of users (Example: super.*)

Alert Summary View

This shows the filtered list of alarms that were generated in response to the alert profiles. The filter is based on the criteria selected/specified above.

• Severity: Each row is color coded to represent the severity of the alert. Red – Major, Yellow – Minor.
• Time: When the alarm was generated.
• Entity:  The name of the entity for which the alarm was generated.
• Metric: The metric whose value was breached.
• Object: Name of the object that breached the threshold condition.
• Expected: Specifies the threshold value (above or below) which the actual value should have been.
• Actual: Specifies the value of the metric for the corresponding instance when the threshold was breached.

Click on any column heading to sort the list for that column. Click on the alarm entry to get more details associated with the subscription for this alert.

In addition, a heat map is displayed at the top of the Alert Summary View. This provides an immediate visual summary of the major and/or minor alerts for the criteria selected above.

Alert Detail View

This lists the activity log for the corresponding profile. Click on any column heading to sort the list for that column.

The level of detail is controlled by the Log every breach attribute of the profile. As described in the Log every breach section, the following information is logged

• Alarm generation
• Details regarding the first notification
• Details regarding the recovery notification
• Escalation
• Automated operation

If detailed logging is specified, then in addition to the above, the following is logged

• Instances when thresholds are breached
• Instances when alarm is not  generated because the thresholds are within tolerance.

Each Server is identified by its name on the left panel, and below the Globe icon.  Click open the Server name to see the following features:

• Monitor – Displays current (every 5 seconds) performance metrics, in detail format for following:
  • • CPU  – A graph shows % CPU Busy (Y1 – Line) per CPU, and highest Queue length experienced by any CPU (Y2 – Bar), over the most recent  one minute period (12 data points at 5-second intervals).  Click on a CPU line to open a new Window, and see a list of busiest Processes on that CPU at that point in time.  On the new window, switch between CPUs, or click on a Process to see the trend of that Process activities over time.  Click on a bar to see a list of Processes with the highest Receive Queue.

   

  Counter	Formula
  % Busy	(CPU-BUSY-TIME CPU / DELTA-TIME CPU) * 100
  Queue Length	(CPU-QTIME CPU / DELTA-TIME CPU)
  % Memory	(CURRENTLOCKEDMEMORY / MAXIMUMLOCKEDMEMORY) * 100

  • • Process, Busiest – Shows top 5 busiest Processes on the Server.  Click on a Process name to open a new Window and see its trend over time. Following information is displayed per Process, for the latest interval:
      • Process name
      • CPU:IPU where the Process is running
      • Program name (pass the mouse over to see the full name)
      • Guardian Group.User ID of the Process owner
      • Receive Queue
      • In MB, memory used by the process
      • % CPU Busy (IPU) used by this process

   

  Counter	Formula
  % Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
  Receive Queue	(RECV-QTIME PROCESS / DELTA-TIME PROCESS)
  Memory Used	(PRESPAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PagesToBytes

  • • Disk, Highest Queue– Shows top 5 disks with the highest queue length.  Click on a Disk to open a new Window and see its trend over time. Following information is displayed per Disk, for the latest interval:
      • • Disk name
        • Queue length
        • % Cache Hit rate
        • % Device Read Busy
        • % Device Write Busy
        • % Device CPU Busy

   

  Counter	Formula
  % DP2 Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
  Queue Length	(REQUEST-QTIME DISC / DELTA-TIME DISC)
  % Device Busy	(DEVICE-QBUSY-TIME PROCESS / DELTA-TIME DISC) * 100
  % Read Busy	(READ-QBUSY-TIME PROCESS / DELTA-TIME DISC) * 100
  % Write Busy	(WRITE-QBUSY-TIME PROCESS / DELTA-TIME DISC) * 100

  • • TMF, Highest Abort Rate – Shows top 5 Processes with the highest percent TMF Abort rate.  Click on a Process name to open a new Window and see its trend over time. Following information is displayed per Process, for the latest interval:
      • • Process name
        • Percentage of transactions aborted
        • Begin transactions per second
        • Abort transactions per second
        • CPU and IPU where this process is running
        • Program name (pass the mouse over to see the full name)
        • Receive Queue
        • In MB, memory used by the process
        • % CPU Busy (IPU) used by this process

  Counter	Formula
  % Abort	(ABORT-TRANS PROCESS / BEGIN-TRANS PROCESS) * 100
  TPS	(ztransaction-rate from TMF STATUS command) / 100
  Begin Transactions per second	( BEGIN-TRANS PROCESS / DELTA-TIME PROCESS ) * 10^6
  Abort Transactions per second	(ABORT-TRANS PROCESS / DELTA-TIME PROCESS) * 10^6
  Receive Queue	(RECV-QTIME PROCESS / DELTA-TIME PROCESS)
  Memory used by the process	(PRESPAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PageSizeBytes
  % CPU Busy (IPU) used by this process	(CPU-BUSYTIME PROCESS / DELTA-TIME PROCESS) * 100

• • • • Network, Total Sent – Shows top network processes displaying ‘Total Sent Messages’, and ‘Total Received Messages’ at that point in time. Click on a Process name to open a new Window and see its trend over time. Following information is displayed per Process, for the latest interval:
        • • • Process name
            • Total Sent

    Counter	Formula
    % Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
    Receive Queue	(RECV-QTIME PROCESS / DELTA-TIME PROCESS)
    Memory Used	(PRESPAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PagesToBytes

  • • • •  CLIM, Busiest – Per CLIM, for the recent intervals, shows the % CLIM Busy (Y1) with the highest memory used (Y2). % Busy is shown in scaled format. Click on the S icon on the heading to toggle the scale setting. Also from the CLIM graph, you may click on the trend icon (upper right) to either see a trend of % CPU Busy, or Memory used over time.
      • • • CLIM Name
          • % Busy
          • % Memory

  • • Counter	Formula
      % Busy	As reported by vmstat on the CLIM
      Memory Used	As reported by vmstat on the CLIM

Placeholder

This feature opens a Window where you can view VHS (Virtual Home terminal System) messages sent to the VHS primary log file. You can control the type and scope of the messages that get displayed based on a set of criteria you define in the Settings Panel (Upper section). Following is a description of the available options on the Setting Panel.

Node: Select from the list of available nodes. Multiple nodes are listed when neighborhood is configured.

VHS Environment: Select from the list of available VHS environments in the log file. This list is determined from the previously learnt environments and the server startup file used by Web ViewPoint Enterprise.

Learn VHS: Existing VHS environments on the node on which Web ViewPoint Enterprise is running can be learnt. Web ViewPoint Enterprise looks for processes of the VHS program file. The environment names learnt are the names of the corresponding VHS processes. Please note that the learning operation takes a few minutes. Learnt environments are remembered.

Refresh Rate: Select a refresh rate from every 1, 5 or 10 minutes. This specifies how often the browser screen will communicate to the server to retrieve and display the latest information.

Number of Entries per page: Select from 25, 50, and 100, the maximum number of recent entries to be displayed at one-time on the Browser Window. New information is appended at the end as they arrive, and older entries are removed as the selected limit is reached.

There are three search options which give you more control over what gets displayed on the screen. These are placed on a toolbar on the upper part of the window. They are:

1. After: Specify a date and/or time to set as the starting point for the displayed messages. Only VHS messages after that date/time will be generated. Date format is 10/31/2017. Time format is hh:mm:ss. You may select the desired date from the calendar.
2. Process: Enter the process name or id of a process generating VHS message(s). Only messages generated by this process will be displayed.
3. Search Text: Enter a string of characters to be matched against the selected set of VHS messages. Only those for which there is a match between any part of their text, and the text entered here will be displayed. The match is case sensitive and does not support wild-card or other special search characters (e.g. “?”). All characters are treated as normal ASCII characters. On large files you will see a search status indicator.

You may enter none, one or more Search options. Please note this criteria is applied to incoming live messages. If needed, you may click on the Reset button to reset all selections to your last selected settings.

Click on the Scan button once your selections are made. The lower panel, VHS-Log Browser Live Window will be displayed based on your defined settings.

Displays a set of most recent VHS messages (from the current log file) & is refreshed regularly based on your settings in Log Browser Settings Panel. To stop the refresh, click on the icon  on the toolbar. The icon changes to . You may click on this icon to resume the automatic refresh operation.

This feature opens a Window where you can display VHS (Virtual Home terminal System) outstanding prompt messages sent to the VHS primary log file. You can control the type and scope of the messages that get displayed based on a set of criteria you define in the Settings panel. Following is a description of the available options on the Setting Panel.

1. VHS Environment: Select from the list of available VHS environments in the log file. This list is determined from the previously learnt environments and the server startup file used by Web ViewPoint.
2. Learn VHS: Existing VHS environments on the node on which Web ViewPoint is running can be learnt. Web ViewPoint Enterprise looks for processes of the VHS program file. The environment names learnt are the names of the corresponding VHS processes. Please note that the learning operation takes a few minutes. Learnt environments are remembered.
3. Refresh Rate: Select a refresh rate from every 1, 5 or 10 minutes. This specifies how often the browser screen will communicate to the server to retrieve and display the latest information. 
4. Number of Entries per page: Select from 25, 50, and 100, the maximum number of recent entries to be displayed at one-time on the Browser Window. New information is appended at the end as they arrive, and older entries are removed as the selected limit is reached.

If needed, you may click on the Reset button to reset all selections to your last selected settings.

Click on the Scan button once your selections are made. The lower panel will be displayed based on your defined settings. The lower panel displays a set of most recent VHS Prompt messages & is refreshed regularly based on your settings. To stop the refresh, click on the icon  .The icon changes to:   . You may click on this icon to resume the automatic refresh operation.

Four pieces of information are displayed per VHS Message. They are:

• Date: Date & time when the prompt was generated
• Process ID: Process id of the process that generated the message
• Program File Name: Name of the Object file currently being executed by the process.
• Prompt Text: Text of the prompt message generated by the process

The Prompt Text is a link to a menu. Click on any Prompt Text to expose two available options:

1. Detail: Displays a Window where more information can be obtained about this message.
2. Reply: Opens a Window where you can type in text to be used to reply to the message. This text will be sent via the VHS process back to the process that originally generated the prompt. It will also be reflected in the log file and may be viewed via Log Browser Window. The Prompt message will be removed from the Prompt screen once you submit your reply.

The Events feature allows the user to view EMS messages both in live and historical view of a single node or multiple resident(s).

User controls the type and scope of the messages that are displayed based on a set of criteria the user define in the Events window. The Settings window is the first screen that is displayed when user accesses the Events menu.

Toggle navigation accordion menu by clicking on the titles to expose available features, described below:

• Profile – By default, no profiles are populated. On selecting an available profile, the Events screen is populated with the values specified in the profiles.
  • Profiles – Clicking on the Profiles button will expose Save, Save as Profile and Other Profiles.
    • Save – The Events Settings on the current screen are stored on to the NonStop using the supplied user name.
    • Save as Profile – Added/updated by specifying the profile name in the “Save Profile as:” textbox and clicking on the “Save” button.
    • Other Profiles – Select the profile to delete and press the “Delete” button.
• Source / Time – The user can specify one or more collector(s) by default $0 is selected. The user can move collector from available to selected by Double clicking on a collector to move them in the the selected collector box.
  • Collectors (s) – You may specify one or more Collector processes (maximum of 10) to retrieve messages from. These Collectors can be on one or more NonStop Servers of an Expand network. A list of Collectors on the current node (the NonStop Server to which Web ViewPoint Enterprise directly communicates with) is displayed to the left side of this area. To select a Collector from this list, simply double click on its name. This will add your selection to those already in the input box.
  • File – Select an EMS log file for Web ViewPoint Enterprise to read Events from. Only one log file may be entered. Select volume, sub-volume and the name of the file. The file drop down exposes a list of log files (predetermined based on file code: 843), if any.

                    Note: Starting from H01ABO-L01ABP onwards, users can only read from log files for nodes which have valid Web ViewPoint license.
                    Example: User has Web ViewPoint licensed for NODE1 and no Web ViewPoint license for NODE2. If the user copies over the EMS log files from NODE2 to NODE1 and tries to read the logs it won’t display any events. This is because NODE2 has no valid WVP license.

        Applicable for Web ViewPoint Enterprise users ONLY: If there are multiple nodes configured in a neighborhood, user can select a logfile from each node.  Multiple logfiles from the same node cannot be selected at once.

• From – Toggle button (Now/Then)
  • Now – Event will start from current time onward.
  • Start From: Select from the list of 4 options available (30 mins, 1 hour, 2 hours & 3 hours). Based on which option is chosen, events will be displayed from that time onwards.
  • Then – Select a from and to time to get events going forward or backward in time.

• Filter – In this section you can set conditions for the type of messages to be displayed.
  • File – Select the name of the EMS Filter files.
    Applicable for Web ViewPoint Enterprise users ONLY: If there are multiple nodes configured in a neighborhood, user can select a filter file from each node.  Multiple filter files from the same node cannot be selected at once.
  • Pass– Toggle button (Yes/No). A Yes displays only the Events that meet/pass the criteria. A No displays only those that fail to meet the criteria.
  • Event – Select Node, Owner and one or more Subsystems (click on their name on the list).
  • Only -Select CPU #, type Goup.User / Alias, (e.g. super.super), pin and event #
  • String – This is where you may enter a string of characters which Web ViewPoint Enterprise should match in the text of each message.
    Note: The following characters are not allowed in the search string ‘: / ?& =’
  • Case Sensitive – Toggle button (Yes/No). User can also elect whether the match logic should be case sensitive.
  • Exclude – Toggle button (Yes/No). User can Exclude Event, Only and String fields
  • Type – Select one or all from the selection, Critical, Action or Others.
  • Acked By (Applicable for WebViewPoint Enterprise only): Filters the events Acked by a specific Group.User.
• Display – Here the user can customize the display of EMS events.
  • Skin – Select from available Skins. Note: User must 1st create a Skin, view Skins section for more details.
  • Template – Select from available templates. Note: User must 1st create a template, view Template section for more details.
  • Show Date – Toggle button (Yes/No). This will remove the DATE segment from the time stamp, additional text truncation may also be necessary to prevent line wrapping
  • Show Collector – Toggle button (Yes/No). On selecting this option, the collector of the EMS message will be displayed on Yes. The collector name will contain the resident name too.
  • Truncate Text – Toggle button (Yes/No). This option will just truncate text to prevent line wrapping.

This Window maintains an on-line live connection with a dedicated EMSLINK on the NonStop Server. This process checks EMS messages as they are generated to determine if they meet your selection criteria. You may stop this flow of messages at any time by clicking on the icon on the upper right side of the screen. This changes the icon to .You may click on this icon to restart the live stream of messages. A Live Window can hold up to 1000 EMS messages in the Events Monitor Window.
Information for each message occupies one row. Each row is organized as follows:

Token Dump icon :
The information icon here is a link to a Window which displays more detailed information about this Event. This includes help text (description, cause, effect, & recovery methods), as well as a token dump. Clicking on the icon for a corresponding event opens a pop up window and display the detailed information about the event. Users can use the ‘Forward’ and ‘Backward’ button to view the events details for all the events.

Acknowledgment :
This is a quick method to acknowledge a single Event. Clicking on this icon causes the corresponding event to get acknowledged. The display is updated to change the event color to green. Event acknowledgements are managed centrally and displays of other users will get updated automatically. By specifying the PARAM HIDEACKS YES in UGATCONF file, the display update can be changed to hide the acknowledged event. Consequently the event will also get hidden / not appear in the displays of other users. The user is also provided the option to specify up to a maximum of 255 characters worth of acknowledgement comments and information when acking the corresponding event. All types of events can be acknowledged.

Acknowledged icon :
Clicking on this icon will cause a popup window to appear that contains information on who acknowledged the event, the date/time of acknowledgement and any comments if present.

Selection checkbox :
Clicking this check box alternatively selects or deselects critical, action & other events.

Once a selection is made, you may click on the acknowledgement icon & on the upper left toolbar to acknowledge & view the Event details for all selected messages.

Users can now ACK upto 200 events. You can control the maximum number of events to be displayed on the browser by configuring PARAM EVENTS-PAGE-SIZE 200 in the UGATCONF file. This restricts the number of events displayed in the screen to 200 and allows users to utilize the ‘Select All’ feature to ACK all 200 events at a time.

Generation Time: 2017-03-09 17:50:00
It is the date and time the message was generated on the NonStop Server. This calculation is done on the NonStop Server where the message was generated.

Process ID: NSDEMO.$X9AT
It is the name/id of the process which generated the message.

Subsystem ID: TANDEM.257.0
It is the owner/subsystem for which the message is generated. It may be an internal hp NonStop subsystem or an in-house application, or third party vendor’s product.

Event #:000525
The Event number for this message associated with this subsystem.

Text: Meascol: Entity Type 7,
The text for this message associated with this subsystem.
The displayed information for all events may be sorted in either direction based on the value of any column. To do so, click on the column heading of a selected column. Sort direction (ascending or descending) switches when you click on the same column twice.

A summary bar at the top of the Window shows the total count of messages currently displayed for each of the three message type categories (Critical, Action, Others). These are all color coded and on clicking any of the category it will open a pop up window which displays events of only that particular category.

Export to Excel : This opens an instance of Microsoft Excel and populates a spread sheet of a new ‘book’ with the results of the current Events Settings.

Export to PDF : A PDF file will be downloaded with the results of the current Events Settings.

BAM : Opens a new window with BAM information in Read-only.

Displaying EMS Event help & Token Dump:

You may retrieve and display help text (where available) for a selected Event, along with a dump of all tokens included with the Event message. The help text is retrieved from one of two databases on the host. This contains information such as summary and detail description of the reported message. Also included, is information on Cause of the Event, its Effect on the system or applications, and Recovery methods.
To display this information, simply click on the sequence number of the Event message. Web ViewPoint Enterprise first searches its BAM (Business Application Manual) database for any available help text.
Next, HP’s Operator Messages Manual (file EVENTTX) is consulted, if there are no entries in the BAM database for the selected Event. Any information found is displayed, in absence of BAM content. Note that if BAM data is displayed, a link will also be present to give you access to the relevant content in the Operator Messages Manual as a secondary source of information.

Note that you can always display and access the Operator Message manual in its entirety by clicking on the icon on the upper right side of the screen.

Search Feature:

Users can also search individuals columns. To search a single column, enter the search text in the desired column search field and it retrieves a list of matching records. To search multiple columns, Enter the search text in each of the desired column search fields and it retrieves a list of matching records.

Storage offers a File Explorer-like interface to NonStop disks & files, with various features and commands.  The Storage Icon within the left pane represents the Storage subsystem. Clicking on this icon displays a list of Disks in the panel to the right, along with their % used value.

You may sort the list of disks for either column (name or % used) by clicking on the icon above its column heading. Clicking on the same icon a second time, reverses the sort order.

Clicking on a sub-volume name  displays a list of files in that sub-volume, along with their summary information (similar to a FUP INFO * for that sub-volume). You may sort this information for any column by clicking on its column heading. Clicking on the same heading a second time, reverses the sort order.

Note: There is an instant results file searching tool which can be used to find and display a list of files matching criteria you specify by typing in the available fields under the header.

You may issue one of several commands on a selected file (command execution requires proper user-id & authority). Clicking on the file name brings up a popup menu displaying the available file commands, listed below:

• Properties: Opens a new Window and displays detail file information.
• Obey: This option is valid for files with file code 101 (text files).  Obeys the selected file, and displays the results in a new Window. Start and stop time stamp will also be displayed to determine the time it takes to complete the operation.
• Run: This option is valid for TACL Macro files with file code 101 (text files). The pop-up that displays gives you the option to run the macro in a nowait format, and specify an output location.
• Rename: Prompts you to change the file name (volume & sub-volume names remain the same).
• Alter: Prompts you with the option to alter file code, owner, file security, and maximum extents. You may alter multiple attributes at once.
• Delete: Upon your confirmation, purges the file.
• Duplicate: Prompts you with a dialog box where you can enter the full file name (volume.subvolume.filename) where you want this file to be duplicated to. Its alternate key files or other partitions, if any, are not affected. Current volume and subvolume where the file is located are used as default.

• Opened By:This option is available only when a file is open. It displays a list of processes which have this file opened.

• Move: Prompts you with a dialog box where  you can enter the full file name (volume.subvolume.filename) where you want this file to be moved to. This deletes the file from its current location and moves it to the target location. Its alternate key files or other partitions, if any, are not affected. Current volume and subvolume where the file is located are used as default.

The OSS subsystem offers a File Explorer-like interface to the OSS file system. This feature is available and is visible only on NonStop systems that have OSS installed. The OSS icon represents the OSS subsystem. Clicking on this icon displays the Fileset Report icon as well as the OSS file system Root folder icon. Clicking on the Fileset Report icon displays a report of filesets configured on the NonStop system, on the right hand side of the screen. The Root folder icon provides means to traverse the OSS file system in a File Explorer-like fashion. The left side of the screen displays the directory tree and the right side displays the directory contents.

• Using the directory contents view – The right hand side of the screen displays the list and basic details of files and directories present in the selected directory. The top status bar indicates the currently selected directory and the count of files/directories present. The list can be sorted in ascending or descending order by clicking on the corresponding column heading. Clicking on a directory name will cause the respective directory to be opened and the existing directory content display will get replaced. Clicking on the file name and selecting Properties opens a new Window and displays detail file information.
  • File Commands:
    • Properties: Opens a new Window and displays detail file information.
    • Open: Opens the file for editing. This command is not available for directories.
  • Toolbar Functions: Toolbar provides operations that can be performed on the directory. Click on the file create icon and directory create icon to create new files or directories in the currently selected directory.

The Spooler feature allows you to access jobs on various Spoolers running on the NonStop Server you are directly connected to.

Clicking on the Spooler icon in the left pane displays a list of available spoolers. You may sort the list of spoolers by clicking on the icon above its column heading. Clicking on the same icon a second time, reverses the sort order

You may click on available spooler to display its content in the right panel.

Sorting is available by clicking on the icon above its column heading. Clicking on the same icon a second time, reverses the sort order.

Note: There is an instant results job searching tool which can be used to find and display a list of jobs matching criteria you specify by typing in the available fields under the header.

Clicking on a job name will display a pop-up menu of commands:

• Open – Downloads the job’s content to a browser based read-only editor. There you can view the content and use the search feature.
• Delete – Upon your confirmation, deletes the job off the spooler
• Alter – Prompts you with an option to alter the following job properties:
  • Copies
  • Form
  • Hold option
  • Hold After option
  • Link option
  • Location
  • Priority
• Toolbar Functions: The following icons on the toolbar are used for export operations.
  • Export to PDF: This opens an instance of PDF and populates with the information table currently being viewed.
  • Export to Excel: This opens an instance of Microsoft Excel and populates a spreadsheet of a new ‘book’ with the information table currently being viewed.

Event Analyzer captures daily snapshots of all EMS Events of one or more Collectors, which are then analyzed and stored in a historical indexed database.  This information is retained for any period of time determined by the system administrator.

Event analyzer has a control bar on top, along with three graphs which display Event counts in a drill-down fashion, in two categories of Critical (red) and Non Critical / others (green).  When you first access Event Analyzer, it displays information for the most recent day of the current month (or most recent month, if today is the first day of the month).

Control Bar – Select from the options below, and click on Submit.

• Year – Default is the current year, but you may select any prior year for which data is retained.
• All  or selection – By default counts of all Events are displayed.  You may however choose a specific Owner, or Owner & Subsystem, or Owner & Subsystem & Event number.
• D/H or  W/H – Default is Days & Hours (D/H) which displays information for each day of a selected month.  You may also choose Weekdays and Hours (W/H), which sums up counts of Events and displays them for the weekdays (Sunday – Saturday) of each month.

Top Graph – Shows Total Event counts (critical and others) per month.  Click on a bar to select:

• Event Detail – Non Critical:  Opens a new Window and displays the actual list of Non critical (others) Events posted for the selected month.
• Event Detail – Critical:  Opens a new Window and displays the actual list of critical Events posted for the selected month.
• Trend Daily:  Shows Event counts (critical and others) per day of the month in the middle Graph, and also displays the hourly counts for the last day of the selected month in the bottom Graph.

Middle Graph – Shows Total Event counts (critical and others) per day of the selected month (from the Top Graph).  Click on a bar to select:

• Event Detail: Non Critical – Opens a new Window and displays the actual list of Non critical (others) Events posted for the selected day.
• Event Detail:  Critical – Opens a new Window and displays the actual list of critical Events posted for the selected day.
• Trend Hourly- Shows Event counts (critical and others) per hour of the selected day, in the bottom Graph.

Bottom Graph – Shows Total Event counts (critical and others) per hour of the selected day (from the Middle Graph).  Click on a bar to select:

• Event Detail – Non Critical – Opens a new Window and displays the actual list of Non critical (others) Events posted for the selected hour.
• Event Detail – Critical – Opens a new Window and displays the actual list of critical Events posted for the selected hour.

Storage Analyzer captures daily snapshots of all Disks and files, which are then analyzed and stored in a historical indexed database.  This information is retained for any period of time determined by the system administrator.

Main screen displays the analyses in one simplified view for the most recent date.  A date control on top allows the user to do the same for any date.  This date control is available on all screens, except for list of files which reverts back to current time, showing current actual files on NonStop.

Below describes the content and the drill down options available:

On top, total available storage is shown in Terabyte, and a stacked bar shows used vs. available in both TB and percentage.

The graph below breaks the storage used, by Guardian Group ID, and displays it in the order of Groups with most used space.  Y1 shows storage used in Megabyte, and Y2 shows number of files “owned” by each Group.  

• Click on a graph point to display a new window showing the breakdown per User of that Group.
  • Click on a user on that window, to open a ne window and see a list of Volumes where this used has files, and relevant statistics, such as total count, files near capacity, corrupted files, etc.
    • Click on a Volume to open a new window and see the breakdown per subvolume.
      • Click on a subvolume on that window, to open a new window and see a list of current files.
        • Click on a filename on that window, to carry out simple file commands.

Files section in the middle displays statistics per Volume (logical).  It shows tallies of files as follows:

• Count – Total number of files
• > 90% – Number of files at above 90% of configured capacity.
• Full – Number of files at full capacity
• Corrupt – Number of corrupted files
• Licensed – Number of files with License flag set
• PROGID – Number of files with ProgID flag set
• Audited – Number of TMF audited files
• New – Number of files created on the displayed date.
• New Licensed – Number of files which were licensed on the displayed date.
• New PID – Number of files which had their ProgID set on the displayed date.
• Old – Number of files which have not been opened for a set number of days (set by system manager and used for all files).
• Unused – Number of files which have never been opened.

Content may be sorted for any column, and you may click on any non-zero number to see the list of files for that category.

By default information displayed is for All files.  There are two other options displayed on the Tab displayed above the grid:

1. Only mine – Limit the display to only your (based on the user ID you used to logon to Web ViewPoint) files.
2. Only for – Displays a field where you can type in and submit a Guardian user id (Group.User).  The list is then displayed to the files belonging to the user you specified.

• You may click on a Volume name displayed on the table, to open a new window which displays the breakdown of all files on that disk, per subvolume.

• Click on a subvolume on that window, to open a new window and see a list of current files in that subvolume.
  • Click on a filename on that window to select and carry out simple file commands.

Disks section at the bottom displays the following information per Disk drive (Physical), as of the selected date:  

• Size GB – Size in Gigabytge
• % Used – Percent used  
• Delta MB – Variation in MB used spaced when compared to the prior date.
• New MB – In Megabyte total size of the files newly created on that date.
• Days to 90% – Based on past 30-day history, number of days before this Disk reaches 90% of its capacity.
• Days to 100% – Based on past 30-day history, number of days before this Disk reaches its full capacity.

You may click on a Volume name displayed on the table, to open a new window which displays the breakdown of all files on that disk, per subvolume.

• Click on a subvolume on that window, to open a new window and see a list of current files in that subvolume.
  • Click on a filename on that window to select and carry out simple file commands.

This feature provides access to the Administrative functions of Web ViewPoint Enterprise. Through the menu items of the Admin tab, the Administrator can setup user accounts and set various administrative controls.

Admin – Perform the following administration tasks:

• • • Alerts – Setup EMS Events you want notifications to be sent out when they happen, and what automated action to take.
    • Delivery – Configure the following settings:
      • SNMP – Define SNMP information required to forward Events to Enterprise Management software (e.g. Tivoli).
      • JSON to Enterprise – Define the IP/DNS name, port number to which the JSON information must be sent.
      • SMTP Server – Define SNMP information needed to email out Alerts.
    • EMS
      • Template – A Template sets what you want to see on your Events screen, and how they should be displayed. Here is where you define them.
    • • BAM – Business Application Manual (BAM) is really an imaginative/quirky (you be the judge) name given to the ability to add detail (description, cause, effect, recovery) information about Events generated by your in-house applications. Here is when you define them.
      • Exceptions– Description of category of Events you absolutely do not want to be bothered with.
      • Skins – Choose font type & size, and color characteristics of how Events should be displayed; give it a name, and use it. Your colleagues can create more, or use yours.
    • Pathways – Administration functions are used to initialize & maintain the central host databases used by Web ViewPoint Pathway. The following information is maintained per Pathway:
    • • Lists number of TERM, TCP, and SERVER entities that are running
      • Maintenance of Group definitions
      • Syncing, Starting, Stopping and deleting pathways
      • Cold, Cool and Shutdown Obey file names
      • Start & Shutdown of Pathways
    • Phone Carriers – Lists the phone carriers that have been already configured. The email address corresponds to the SMS mailbox address of the Phone carrier to which Web ViewPoint Enterprise will send SMS notifications
    • Users – Setup who (by guardian users) should have access to what features of Web ViewPoint, and on what Servers. You can also enter their contact info for notification purposes.
    • License – See when your license to use Web ViewPoint Enterprise on each Server expires. You may also (assuming internet connection to the outside world) receive updated licenses, or otherwise enter one given to you by HPE.
    • Threshold – Thresholds can be defined on how the alerts can be viewed. Entering a numeric value for Warning and Critical section will determine the trigger for these thresholds.

This is where you set conditions that you want Web ViewPoint Enterprise to watch for, issue alerts, and take action when they occur.  You may set as many alert conditions as needed. Web ViewPoint Enterprise can watch the following set of entities and metrics.

Entities	Metric	Description
EMS		Alert when an event matching the specified filter criteria is met.
CPU	Down	Alert when any CPU goes down.
CPU	% Busy	% of the interval time that the processes spent of the ready list. Alert when the actual value if of CPU is above the threshold. (CPU-QTIME CPU / DELTA-TIME CPU)
CPU	Queue Length	% of the interval time that the processes spent of the ready list. Alert when the actual value if of CPU is above the threshold. (CPU-QTIME CPU / DELTA-TIME CPU)
CPU	GB Memory Left	Memory remaining in GB on the CPU. Alert when the actual value of any CPU is below the threshold. (ENDING-FREE-MEM CPU * PAGE-SIZE-BYTES CPU) / (1024^3)
CPU	% Memory Left	% of Memory remaining on the CPU. Alert when the actual value of any CPU is below the threshold. (ENDING-FREE-MEM CPU / MEM-FRAMES CPU) * 100
CPU	High PIN PCB %	% of High PIN PCBs used in a processor. Alert when the value actual value of High PIN PCBs is above the threshold specified. (current number in use / (number free+current number in use)) * 100
CPU	Low PIN PCB %	% of Low PIN PCBs used in a processor. Alert when the value actual value of Low PIN PCBs is above the threshold specified. (current number in use / (number free+current number in use)) * 100
CPU	TLE %	% of TLEs used in a processor. Alert when the value actual value of TLEs is above the threshold specified. (TLE Used / TLE Configured) * 100
IPU	% Busy	% of the interval time that the IPU was busy. Alert when the actual value of any IPU is above the threshold. (IPU-BUSY-TIMEn CPU / DELTA-TIME CPU) * 100
IPU	Queue Length	% of the interval time that the processes spent of the ready list. Alert when the actual value of any CPU is above the threshold. (IPU-QTIMEn CPU / DELTA-TIME CPU)
Process	Down	Alert when the specified process is not running.
Process	Looping	Alert when any process is currently running at a reduced priority due to heavy processor use.
Process	% Busy	% of the interval time that the CPU spent executing this process. Alert when the actual value if of any or specified process is above the threshold. (CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
Process	Receive Queue	Number of messages waiting on the process message input queue/$RECEIVE. Alert when the actual value if of any or specified process is above the threshold. (RECV-QTIME PROCESS / DELTA-TIME PROCESS)
Process	MB Memory	Memory used in MB on the CPU. Alert when the actual value if of any or specified process is above the threshold. (PRES-PAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PAGE-SIZE-BYTES CPU) / (1024^2)
Program	MinImum Process Count	Number of instances of the specified program. Alert when the actual value if of specified program is below the threshold.
Program	Maximum Process Count	Number of instances of the specified program. Alert when the actual value if of specified program is above the threshold.
Disk	Down	Alert when any, specified or group of disks are down.
Disk	% DP2 Busy	% of the interval time that the CPU spent executing the DP2 process. Alert when the actual value if of any or specified DP2 process is above the threshold. (CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
Disk	% Device Busy	% of the interval time of which requests of any number or type were queued to this disk in this processor. Alert when the actual value if of any or specified disk is above the threshold. (DEVICE-QBUSY-TIME DISC / DELTA-TIME DISC) * 100
Disk	Queue Length	Number of requests on the disk process internal queue. Alert when the actual value if of any or specified disk is above the threshold. (REQUEST-QTIME DISC / DELTA-TIME DISC)
Disk	Cache Hit Rate	% of requests served from cache. Alert when the actual value if of any or specified disk is below the threshold. (C.HITS DISC / (C.HITS DISC + C.MISSES DISC)) * 100
Disk	% Full	% of disk space capacity used. Alert when the actual value if of any or group of disks or specified disk is above the threshold.
File	% Full	Alert when the actual value of the specified file is above the threshold.
File	Missing	Alert when any the specified file is missing.
File	Security	Alert when the security of specified file does not match the threshold value.
File	Owner	Alert when the owner of specified file does not match the threshold value.
File	Modified	Alert if the specified file is modified.
File	Index	Alert when the actual value of the specified file is above the threshold.
CLIM	Link Status	Alert when any of the CLIMs is not in the STARTED state
CLIM	Link Status	Alert when any of the PROVs not in the STARTED state
TMF	Abort Rate	% of the transactions that were aborted. Alert when the actual value of any process is above the threshold.
TMF	Audit Trail % Full	% of Audit trail capacity. Alert when the actual value of the audit trail files is above the threshold.
TMF	Hung Xns	Alert when any of the TMF transactions are in the HUNG state.
TMF	Long Xns	Alert when any transaction runs longer than the threshold.
TMF	Begin Xns State	Alert when BeginTrans status is not ENABLED.
TMF	Audit Dump	Alert when the status of any Audit Dump  is not Active or its state is not ENABLED.
TMF	Data Volume	Alert when the status of any Audit Trail data volume is not ONLINE.
RDF	State	Alert when the RDF State is not NORMAL
RDF	Volume	Alert when any of the RDF volumes are in error condition.
RDF	Process	Alert when any of the RDF processes are in error condition.
RDF	RTD Time	Alert when the RTD time of the extractor process exceeds the threshold.
RDF	Rel. Byte Address	Alert when the Relative Byte Address of the extractor process does not change.
NetBatch	Start By	Time in hh:mm by which the specified NetBatch job must start. Alert when the job does not start by the specified time or if the start time of the job is after the specified time.
NetBatch	Stop By	Time in hh:mm by which the specified NetBatch job must stop. Alert when the job does not stop by the specified time or if the stop time of the job is after the specified time.
NetBatch	State	Alert when the Netbatch is in SUSPENDED State or in any one of the Special Conditions State.
NetBatch	Too Short	Time in seconds taken by the NetBatch job to execute.  Alert when actual value of any job is above the threshold.
Expand	State	Alert when the state of the Expand Line or Path is not STARTED.
Expand	Line Quality	Alert when the Line Quality drops below the value specified
Expand	Response Time	Alert when the Response Time goes above the specified value
Spooler	Job Count	Number of jobs in the spooler. Alert when actual value is above the threshold.
Spooler	Max Job Number	Highest Job Id of the jobs in the spooler. Alert when actual value is above the threshold.
Spooler	State	Alert when the Spooler State is NOT ACTIVE..
Spooler	% Full	% of allocated file space of the spooler’s data file used.Alert when the actual value if specified file is above the threshold.
P.Server C.	Min Process	Number of Pathway Server Classes. Alert when the actual value of the Pathway Server is above the threshold.
P.Server C.	Max Process	Number of Pathway Server Classes. Alert when the actual value of the Pathway Server is above the threshold.

Note: While the action taken in response to occurrence of a certain event is similar to that of other entities, the triggering condition is different.

Following icons are used for miscellaneous operations. These icons appear on the Admin-Alerts toolbar.

Deactivate Alerts : This requires you to select one or more alerts which need to be deactivated. Once the selection is made, it displays a new window with 2 options as shown below.

• • Deactivate until activated again – This will deactivate the selected alerts until you activate them again.
  • Deactivate From/To – This gives you an option to select the From and To time between which you want the alerts to be deactivated. You can schedule to deactivate alerts in advance.

Activate Alerts: This requires you to select one or more alerts which you want to Activate. Clicking on this icon activates the alerts.

Check Status: This displays the status of all the alerts added. The new window with the alert status displays the Alert Name, Status & Current Status of each alert defined.

• Status: Tells you if the alert is active or inactive at the global level.
• Current Status: Tells you if the alert is active or inactive at that point in time. Example: Assume today is Tuesday, you configured the alert to monitor & send out messages on all days except Tuesdays. So, when you click on ‘Check Status’ icon on Tuesday, you would see ‘Status – Active’ and ‘Current Status – Inactive’. This is because the alert is Active on all days except for Tuesdays.

Summary list displays a list of previously defined Alerts.  Click on any column heading to sort the list for that column. Click on Edit or Delete button, next to each Alert to edit its profile, or delete its definition.

Click on the Add button on the top right to add a new Alert profile. Following are the parameters to select:

• Alert Name: You can now specify a name for every alert. It’s an optional field.
• Group Name: Allows you to create a Group. You can assign one or more alerts to this Group. This helps when you want to deactivate or activate alerts based on Groups.
• Watch for: Select the Entity and Metric. Both are required. The applicable metrics for the selected entity are shown.
• Threshold: Identify what constitutes a Major and Minor alert condition. You must specify at least one type.
  • Specify the threshold value and the duration for which it must persist for an alert condition to be considered as breached.
  • Note: State metrics such as CPU Down, Process Looping etc. Don’t have tolerance conditions. These are considered as Major and an alarm would be generated as soon as the condition occurs.
• Monitor: Specify how frequently Web ViewPoint Enterprise should watch for this profile and select weekdays and hours which this profile applies to.  Default is 24*7.
• Forward:
  • Two choices:
    • Enterprise Manager
      • via SNMP – directs alarms generated by above conditions to an Enterprise Manager tool (e.g. Tivoli) via SNMP traps.  Information on where to send the SNMP trap must be specified via the Delivery section.
      • via JSON – directs alarms generated by above conditions to an Enterprise Manager tool (e.g. Moog) via JSON data.  Information on where to send the JSON must be specified via PARAM (PARAM JSON-ENTERPRISE NN.NN.NN.NN) in the STRTWVPE file within Web ViewPoint Enterprise subvolume.
    • Any one or more users via Email or text message to their cell phone.  A list of users previously defined via the Users section will be displayed to select from.  Choose from Email or text.  Note that these options appear, only if all selected users have their email and phone # recorded in their profile.
  • Notifications can be sent either once when the alarm is generated or at a specified frequency until the conditions resolves.
  • Users can also set to receive notifications when the condition resolves.
  • You could specify the same or different forwarding actions for Minor and Major conditions. The Sync option copies the Minor forward settings to Major.
  • Escalate: Notify any one or more users via Email or text message to their cell phone when the condition does not resolve after the specified period of time.
• AutOp: Here you can ask Web ViewPoint Enterprise to also take an action when this condition is noticed.  You may ask it to Obey an Obey file, or Run a TACL macro. If so, select the option, and then select orderly from the volume to subvolume to file list to select the Obey or TACL macro file. You can also specify the outfile where the results of the operation would be logged.
• Status: Activate or deactivate a profile. Web ViewPoint will not monitor conditions for inactive profiles.
• Log every breach: Controls the level of information related to this profile’s activity is recorded.
  • By default, it is set to No and the following information is logged
    • Alarm generation
    • Details regarding the first notification
    • Details regarding the recovery notification
    • Escalation
    • Automated operation
  • If detailed logging is specified, then in addition to the above, the following is logged
    • Instances when thresholds are breached
    • Instances when alarm is not  generated because the thresholds are within tolerance

Reset puts all fields back to their default value.  Click on Submit to add the new Alert profile.

Note: Click here for more information on how to setup and configure alerts.

Delivery configure the following settings:

SNMP – Define SNMP information required to forward Events to Enterprise Management software (e.g. Tivoli).

• A Trap Receiver component for UNIX or Windows must be installed, configured, and running. For example Trap Receiver or HPE Open View can be configured as a Receiver that has a specific port.
  Enter the username, IP address, port of the SNMP receiver then click Submit. Clicking on the Reset will revert all the fields back to previous Submitted entry. Clicking on Delete will remove the entry.

JSON to Enterprise– Define the IP/DNS name, port number to which the JSON information must be sent.

SMTP – Define SMTP information needed to email out Alerts.

• The option to Use NonStop Email/SMS is recommended and must be configured with a a valid SMTP IP address, Email address and Email password then click Submit. Clicking on the Reset will revert all the fields back to previous Submitted entry. Clicking on Delete will remove the entry.

In order to map the Web ViewPoint Enterprise’s Subsystem ID to its Subsystem Name for generated EMS messages by Web ViewPoint Enterprise, the Web ViewPoint Enterprise EMS template file needs to be installed.

Click on EMS, to expose and access all available features, described below:

• • • Template – A Template sets what you want to see on your Events screen, and how they should be displayed.  Here is where you define them.
    • BAM – Business Application Manual (BAM) is really an imaginative/quirky (you be the judge) name given to the ability to add detail (description, cause, effect, recovery) information about Events generated by your in-house applications. Here is when you define them.
    • Exceptions– Description of category of Events you absolutely do not want to be bothered with.
    • Skins – Choose font type & size, and color characteristics of how Events should be displayed; give it a name, and use it.  Your colleagues can create more, or use yours.

A Template sets what you want to see on your Events screen, and how they should be displayed.  Here is where you define them.

Click on Add Template button, to expose and access all available features, described below:.

• Template Name – Enter desired template name
• Select Template – Click to get drop down of pre-configured templates.
• Hide Acknowledgement – Click to toggle On and Off.
• Available tokens – Double click on a token to move them in the Show tokens in this order box
• Column width – Click on the button to adjust column width
• Preview – Click on the button to view current setup
• Save – Clicking on Save will save the Template and add them in the Template list.

Business Application Manual (BAM) is a repository of customizable information about EMS messages on HPE NonStop Servers. 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.
BAM allows you to add and/or delete Owners, Subsystems, and Events. Information on how to do this is below.

• Owners -Click on the plus (+) icon next to the Owner column header, this opens a pop-up with a text box to enter the name that you would like to give to the new owner. Click Save to complete or Save & New to add additional owner.
• Subsystem – Click the plus (+) icon next to the Subsystem column header. This will open a pop-up with the current owner’s name and a textbox to enter the name that you would like to give to the new subsystem. Click Save to complete or Save & New to add additional owner.
• Events –  Click the plus (+) icon, next to the Event column header, this will open a pop-up with a list of existing Owners and another list of their Subsystems. It will also have text boxes for Event Number, Cause, Effect, Recovery, and Detail. By default, the Increment Event # checkbox is enable, which means that the Event # field will be read-only and pre-populated with the next Event number in the selected Owner’s, selected Subsystem.

Using the BAMCOPY tool: BAMCOPY is a console utility to import BAM information from Version 4 SPR AAC and Version 4 AAD BAM database files (BAMO, BAMS, BAME) to the new BAM database (BAM and BAMD). To run this utility, set the following params and issue RUN BAMCOPY

PARAM SOURCE-SUBVOL <$volume.subvolme>
PARAM DESTINATION-SUBVOL <$volume.subvolme>

The utility reports the result of the import operation at the end.

Using the EVTCXIM tool:

EVTCXIM is a console utility to import EVENTCX information to BAM. To run this utility, set the following params and issue RUN EVTCXIM PARAM EVENTCX-LOCATION <$volume.subvolme > PARAM BAM-LOCATION <$volume.subvolme >

This screen lists all added Owner-Subsystem. You may sort the list of Owner-Subsystem by clicking on the column heading. Clicking on the same column heading, reverses the sort order. You can delete an Owner-Subsystem by clicking on the delete button.

Click on the Add button on the top right to add a new Owner-Subsystem.

Owner-Subsystem.
The application owner-subsystem created through this option will be available in the Selection – Events -> Filter.
Enter the owner name (max length is 8) and
the subsystem name (max length is 8 and must be between -32767 and 32767). On clicking ‘Save’ the entry gets
stored in a key-sequenced file which is stored in the same subvolume as Web ViewPoint Enterprise of the logged-in resident.

Here users can adjust the font-family, font size and color of the events section to their preference. Users may sort the list of skins by clicking on the column heading. Clicking on the same column heading, reverses the sort order. You can delete or edit current skins by clicking on the delete or edit button.

Click on the Add button on the top right to add a new Skin. Following are the parameters to select then click Save when done:

• Skin name: Max length for skin name is 18 characters long
• Select Font-Family: Clicking on the drop down, will provide different font family to choice from.
• Color : The color palette can be used to quickly choose a color or manually enter the HTML color code, (e.g. #3865a8).  
• Font-size: Using the arrows up and down you can select the desired font size or type in the font size in pixels (px) value, (e.g. 12)

Starting from H01AAE-L01AAF, new user authorization features are introduced into WVP Enterprise. Objective is to allow for a larger user community, while managing functions each user has access to. This also allows for each user to create her/his own environment and settings customized to suit.

A No setting of “Enforce-Security” parameter will overwrite these new features.

User Classes

WVP E users are divided into two classes:

Manager– This class of users are responsible for managing the overall WVP E configuration environment, as well as user maintenance and authorization. A Manager may add/update/delete users of either Manager or Staff class. A Manager can also change a Staff user into a Manager.

First Manager user is set at initial installation. User is asked to identify the guardian user id (Group.User) of a Manager.

Manager Setting Options They can set their own settings, as well as availability/default for others. And will be given access to all sections within Web ViewPoint Enterprise.

Staff Authority Control – Grant user ALL or ONLY specific permissions from the three available categories:

• Performance
• Operations
• Admin

Available access described below:
Performance: Monitor, Events with ACK: Yes/No
Operation: Storage, Spooler, OSS, Event Analyzer, Storage Analyzer & Pathway
Admin: Alerts with Forward: Yes/No, AutoOp: Yes/No

NOTE: By default Staff users will have access to
Admin – >Thresholds
Admin -> EMS -> Skins
Admin -> EMS ->Templates.

Staff Setting Options: Staff can only set their own settings are private to that user. The Staff users cannot add or maintain other users. Their access to various features of WVP E is set and managed by Manager users.

For the below sections, if the Manager updates the settings as public, it will be visible to all the other Managers & Staff members. Other Managers can modify/delete these settings, whereas the Staff user can only view the settings(public) but cannot modify/delete them.

Feature/Section	Manager		Staff
	Public (Visible to everyone)	Private (Visible to user only)	Private (Visible to user only)
Performance – Events- Profiles	System based Managers – RW Staff – R	User based	User based
Admin – Thresholds	N/A	User based	User based
Admin – EMS – Skins	System based Managers – RW Staff – R	User based	User based
Admin – EMS – Templates	System based Managers – RW Staff – R	User based	User based
Admin – Users	System based Managers – RW	N/A	N/A
Admin – License	System based Managers – RW	N/A	N/A
Admin – Phone Carriers	System based Managers – RW	N/A	N/A
Admin – Alerts	N/A Can view/edit alerts added by any user	User based	User based

User list specify what features users can access and receive sms or email alerts, (more details on alerts available in the Alerts section).

You may sort the list of skins by clicking on the column heading. Clicking on the same column heading, reverses the sort order.
When you create users, you assign access level to a profile to each one.

User list specify what features Nonstop user account can access and receive sms or email alerts, (more details on alerts available in the Alerts section).

Click on the Add button on the top right to add a new User. Following are the parameters to select then click Add when done:

• Guardian User ID/Alias: Enter your NonStop username or Alias or group.user*, (e.g. super.super, superalias or super.*).
• Email:Enter desired email, here the user will receive email alerts (Note: This is optional if you do not want to configure email alerts to this user. It is required if you want this user to receive email alerts)
• Mobile #:Enter desired mobile #, here you will receive sms alerts (Note: This is optional if you do not want to configure SMS alerts to this user. It is required if you want this user to receive SMS alerts)
• Phone Carrier: Click on the drop down and select from the available mobile carrier (Note: if desired carrier is not in the list you can add it via Admin – Phone Carriers section).
• Status: Click to toggle user from Active to Inactive.
• Type: Manager/Staff
  • Manager– This class of users are responsible for managing the overall WVP configuration environment, as well as user maintenance and authorization. A Manager may add/update/delete users of either Manager or Staff class. A Manager can also change a Staff user into a Manager.They can set their own settings, as well as availability/default for others.NOTE: First Manager user is set at initial installation. That user can logon and set other users.
  • Staff – Grant user ALL or ONLY specific permissions from the three available categories; Performance, Operations and Admin. Check 1 or multiple boxes to all give access to the user. Available access described below:Performance: Monitor, Events & ACK: Yes/NoOperation: Storage, Spooler, OSS, Event Analyzer, Storage Analyzer & PathwayAdmin: Alerts, Forward: Yes/No, AutoOp: Yes/NoThe Staff users cannot add or maintain other users.
• Permission (Applicable for versions until H01AAC-L01AAD) : Grant user ALL or ONLY specific permissions from the three available categories; Admin, Performance and Operations. Check 1 or multiple boxes to all access to the user. Available access described below:
  • Toggle button (All/Only)

Selecting ALL gives user access to all the features within that category.
Selecting ONLY allows you to select specific sections within that category.
Available categories and their respective sections described below:
Admin: Alerts, Delivery, EMS, Carriers, License, Thresholds, Users & Pathways
Performance: Summary, Monitor and Events section
Operation: Storage, Spooler, OSS, Event Analyzer, Storage Analyzer & Pathways

• For: Add or remove NonStop Server access

This feature provides display and management of all licenses of Web ViewPoint Enterprise defined within the License configurations. If the PC used to manage Web ViewPoint Enterprise has connected to the Internet then Web ViewPoint Enterprise retrieves the licenses for the product automatically.

Also periodically, depending on the time to expiry date, Web ViewPoint Enterprise will attempt to refresh the license. This feature also allows a manual refresh whereby the Administrator can proactively update the license. A refresh of the license key will only be required on a major software version change (e.g. H01 to H02).

Manual Licensing – If Web ViewPoint Enterprise does not have access to the internet you can enter a License Key provided by Licensing Manager license.manager@hpe.com . To enter the License Key click on the Add button, paste the license key provided by Licensing Manager and click Submit.

Thresholds can be defined on how the alerts can be viewed. You can set the numeric value for Warning and Critical sections by using the sliders(dragging it) provided for each metric. These values will determine the trigger for these thresholds.

Starting with H01AAA-L01AAB onwards, users have the ability to activate or deactivate thresholds for specific or all objects. Upon deactivation or setting the object(s) to No/Inactive, no warning or critical alerts will be displayed on the screen even if the thresholds are breached. If activated or set to Yes/Active, based on the threshold conditions appropriate warning and critical alerts will be displayed on screen (bell icons, colors and numbers next to nodename)

Starting from H01AAE-L01AAF version, threshold screen has been updated to the below.

Below is the Threshold screenshot starting for versions H01AAA-L01AAB to H01AAC-L01AAD.

Following Object and Counters are available.

• CPU
  • % Busy
  • Queue Length
  • Memory
• IPU
  • % Busy
  • Queue Length
• Disk
  • % Busy
  • Queue Length
• Process
  • % Busy
  • Receive Queue
  • Memory

• CLIM
  • % Busy
  • % Mem
• Network
  • Total Sent
  • Total Received
• TMF
  • % Abort
  • TPS

This screen lists the phone carriers that have been already configured. The email address corresponds to the SMS mailbox address of the Phone carrier to which Web ViewPoint Enterprise will send SMS notifications. The user’s cell phone number along with the SMS mailbox address makes up the email address to which the notification will be sent to. The phone carrier will then deliver this message as a SMS to the user’s phone device.

The following functions can be performed:

Add Phone Carrier: Click on the ‘Add Carrier’ button. Populate the Carrier and Email Address fields and click on the ‘Add’ button. Please note that Email address is of the form ‘@mailserver.com’.

Note: If the user would like to add a Phone carrier in the Web ViewPoint Enterprise database, check the ‘Add to master list’ text box and click on the submit button. An email with the Phone carriers details will be opened, please email it to webviewpoint@hpe.com and we will update the Phone carrier database within Web ViewPoint Enterprise.

Edit Phone Carrier: Click on the ‘Edit’ Phone Carrier to update. Update the email address and click on the ‘Update’ button.

Delete Phone Carrier: Click on the Delete button corresponding to the Phone Carrier in order to delete it.

Synchronize: This function can be performed if the Non-Stop host has connection to the Internet. The www.idelji.com site will be queried for the phone carrier information and added to the local NonStop database.

Starting from H01AAE-L01AAF, the SA/EA Runtime Admin settings can be changed by accessing the Admin -> Analyzer screen as shown below:

Note: By default, above values are populated based on the parameters set at the time of the installation.

There are six parameters whose values are set on this screen:

Store Volume: “$DSMSCM”, or any desired volume. This is the volume where the log files storing action event information are stored. One file is created daily, named EAACT, and is stored in a subvolume named ‘EAyymmdd’, where ‘yymmdd’ represents the day on which the action events were generated.

Collectors: ‘’0’’, or/and any other collectors. This drop down lists the collectors whose log files are scanned daily by EACOLL. Multiple collectors can be added and once added, EACOLL scans all specified collectors for analyzing the events. By default, $0 is added as a collector during the installation.

Run at (hh:mm): “2359” or any other hhmm. This specifies the time at which the collection should run for. It is advisable to select an hour during which there is minimal activity on the NonStop server.

Retain Collection data (days): 90” or any number between 1 to 180. This specifies the maximum number of days to retain data collection. Valid range is 1-180. The default value is 90 days.

Note: If the retention period is set to “x” then data will be retained for a period of “Today – x days” to “Today”. This would result in the deletion of all pre-retention data stored in <$SVol>.<SAyymmdd>. The retention also triggers updating various files on the install subvol where archived information is stored.

Old files criteria (days): “365” days or any number between 1 to 1000, only the files that have not been opened for the specified number of days (or more) will be collected.. Valid range is 1-1000. The default value is set to 365 days.

The value for this field is used to determine what files will be included in the old file count (i.e. those files that do not have a used date within the number of days specified).

Reload criteria (days): “3” days or any number between 1 to 255, only the files whose index levels are greater than or equal to the specified value will be selected for collection. Valid range is 1-255. The default value is set to 3. The value for this field is used to calculate the number of reloadable files for disks.

NOTE: The changed settings do not come into effect until after the next run of the collector. In other words, the WVP E’s SA/EA modules reads the configuration file after it has finished collecting for that day and it only runs once every day. So, if the user changes the run time the following are possible scenarios:

Collector run scenarios
Original Run time	New Run time	Has run today?	Effect on Collection
1:00 pm	8:00 pm (later than the original schedule)	No (i.e. current time is prior to 1pm)	Collector will run at 1:00 pm today and will run at 8:00 pm from the next day onward.
1:00 pm	8:00 pm (later than the original schedule)	Yes	Collector will run at 1:00 pm the next day ,read the new settings and run at 8:00 pm from the next day onward. Note that it will not run again today.
1:00 pm	10:00 am (before the original schedule)	No	Collector will run at 1:00 pm today and will run at 10:00 am from the next day onward.
1:00 pm	10:00 am( before the original schedule)	Yes	Collector will run at 1:00 pm today, read the new settings and run at 10:00 am from the next day onward.

Response Team list comprises of individuals (users who do not have NonStop user ids) who will receive emails or SMS messages in the event of an Alert being triggered. You can configure users without having to associate them with Nonstop user ids.

Configuring a User

To add a new user, navigate to the Admin – Response Team page and click on the Add button.

Following are the parameters to select then click Add when done:

• Name: Enter the Name (e.g. John).
• Email: Enter desired email, here the user will receive email alerts
• Mobile #: Enter desired mobile #, here you will receive sms alerts
• Phone Carrier: Click on the drop down and select from the available mobile carrier (Note: if desired carrier is not in the list you can add it via Admin – Phone Carriers section).
• Status: Click to toggle user from Active to Inactive.
• For: Add or remove NonStop Server access

This chapter provides requirements you should consider before installing the software along with the instructions to perform the installation.

Required Hardware:
HPE NonStop Server
Non-dedicated Windows based PC(s) for browser based User Interface (recommended PC configuration defined below)

Minimum OS Release:
NonStop Kernel release;
H06.03 onward
J06.02 onward
L15.08 onward

Recommended PC hardware configuration for UI functions:

8 GB RAM minimum or higher
CPU Speed 2.40GHz or faster
Microsoft Windows 10 (32bit and 64bit) is the primary OS platform used for most of the WVP E testing.
Windows Server 2016 can also be used.

Required Software:

Measure

Supported Browsers:

Google Chrome 58 or higher (Recommended Browser)
Mozilla Firefox 34 or higher
Microsoft Edge 38 or higher
Microsoft Internet Explorer Ver. 11

 

Web ViewPoint Enterprise Installation steps:

Manual or DSM/SCM Installation Overview

Web ViewPoint Enterprise can be installed using the DSM/SCM tool or can be installed manually.

For DSM/SCM, use the IPSETUP.exe program to upload the files from the CD / PC to the NonStop server. Follow the screens on the Wizard and provide the necessary information as prompted. It is strongly recommended that the user have SUPER.SUPER credentials. Once the IPSETUP program completes ensure that the files listed below have been transferred in the correct format and the file codes are correct.

NOTE: After running the IPSETUP program, please make sure to copy the UMPPAK and SETUPWVP files to a new Install subvolume. If there are additional files (i.e. apart from UMPPAK and SETUPWVP), the RUN SETUPWVP command will fail to extract the files from the UMPPAK file.

For Manual Installation, use the files within WS_SW/WVPE Installation folder and follow the below instructions.

1. Note: Make sure your <installation-subvol> subvolume is empty before starting the transferring.

** Make sure that the wvp.tar file which is distributed along with the installation package is downloaded to your PC. This file should not be present within the <installation-subvol>

2. Upload the SETUPWVP and UMPPAK (H, J or L series) to your <installation-subvol> in binary mode.
3. Run the below set the parameters for Web ViewPoint Enterprise Installation.

> RUN SETUPWVP

Starting from H01AAE-L01AAF, below prompt is added

Input the guardian user id of a user who you want to be the Manager of Web ViewPoint i.e. with all Administrative privileges

Input “F” for fresh install or “I” for import over from an older version of Web ViewPoint or Web Viewpoint Plus.

NOTE: An older version of Web ViewPoint or Web ViewPoint Plus need NOT be stopped before continuing with import over.

It prompts user to specify the parameters they want to use for Web ViewPoint Enterprise.

• If the default parameters will not be changed input “S” and enter to Submit. To change the default parameters, follow the examples below.

Examples changing the default parameters:
1. Input number 1 and enter, input desired TCP Process name and enter.
2. Input number 2 and enter, input desired Listening Port # and enter
3. Input number 3 and enter, input desired Store Volume and enter

Event Analyzer:

4.Input number 4 and enter, input desired Collector and enter.
If multiple collectors are needed use comma separate values, (e.g. $0,$ZLOG,$UMP).

Note: If invalid collector is entered the following message will appear “Invalid collector:”and default collector will not change.

Storage Analyzer:

5.Input number 5 and enter, input time (hhmm) and enter.

Note: This is when the collector will run.

6.Input number 6 and enter, input 1 to 180 (days) and enter

Note: This specifies the maximum number of days to retain data collection.

All data past the retention date will be deleted from the store volume entered in section 3 (e.g. $DSMSCM.SA170228 <$VOL>.).

7. Input number 7 and enter, input 1 to 1000 (days) and enter

Note: Only files that have not been opened for the specified number of days (or more) will be collected.

Recommendation: Keep this value at a reasonable amount, setting this value at a low number may result in SA running slower than normal.

8. Input number 8 and enter, input 1 to 255 (days) and enter.

Note: Only files whose index levels are greater than or equal to the specified value will be selected for collection.

Input “Y” if you want to import EA and SA files (without having to stop old version from where you want to import the data) from older WVP Plus instance to Web ViewPoint Enterprise.

Input “N” if you dont want to import EA and SA data.

NOTE: If you want to retain same process names and store volume as the older version in new WVPE, you can first test the new WVPE instance by bringing it up in shadow mode and using STRTPRXY and STOPPRXY to make sure all is ok. Users will need to edit the process names within these proxy files to test if everything looks good before stopping the old istance. Proxy files will help you to temporarily bring up the new WVPE instance with different process names (until you run OBEY STOPPRXY). When ready, you can stop the old instance and restart WVPE with the default process names by running OBEY STOPPRXY (stopping the different process names which you brought up for testing) and then run OBEY STRTWVPE which allows to start with the default process names.

• Input “N” to edit the parameters within the configuration files and start the collector later.

Starting from H01AAE-L01AAF, below prompt is added

Input Y if you want to enable the user permissions and access control feature

Input N if you do NOT want to enable the user permissions and access control feature

If necessary, follow the steps below to change the process names and port number within the configuration files.

4. Edit the “STRTWVPE” configuration file, change the process names to unique process names.

stop $WVPMN
stop $WVLST
stop $WVCL8
stop $WVDRN
stop $WVSKY
stop $WVCMN
stop $WVCIP
stop $WVCLM
stop $WVECL
stop $WSAMR
stop $WSAHR
push #param
clear all

ASSIGN PROGCONF1, UGATCONF
PARAM LISTENER-PROCESS $WVLST
PARAM TCP-PROCESS $ZTC0

RUN PROCMAN/NAME $WVPMN,PRI 160, NOWAIT/

RUN UMPCOL8 /NAME $WVCL8, NOWAIT, TERM $ZHOME/

#DELAY10
RUN UMPDRNE /NAME $WVDRN, NOWAIT, TERM $ZHOME/
#DELAY10
RUN UMPSKYI/NAME $WVSKY, NOWAIT, TERM $ZHOME/
#DELAY10
RUN UMPCMON /NAME $WVCMN, NOWAIT, TERM $ZHOME/
#DELAY10
RUN UMPCIP /NAME $WVCIP, NOWAIT, TERM $ZHOME/
#DELAY10
RUN UCLMEAS /NAME $WVCLM, NOWAIT, TERM $ZHOME/
RUN EACOLL /NAME $WVECL,NOWAIT,TERM $ZHOME,PRI 120/

RUN SAMGR /NAME $WSAMR,NOWAIT,TERM $ZHOME,PRI 120/
RUN SAHRLY /NAME $WSAHR,NOWAIT,TERM $ZHOME,PRI 120/

ASSIGN CC-FILE ,WVPPCC
ASSIGN CCE-FILE ,WVPPCCE
PARAM EXECUTION-LOG *
RUN WVPPREF /NAME $WVSEF,NOWAIT ,TERM $ZHOME,PRI 140/

CLEAR ASSIGN CC-FILE
CLEAR ASSIGN CCE-FILE
CLEAR PARAM EXECUTION-LOG

pop #param

5. Edit the “STOPWVPE” configuration file, change the process names to match the ones from the “STRTWVPE” configuration file.

stop $WVPMN
stop $WVLST
stop $WVCL8
stop $WVDRN
stop $WVSKY
stop $WVCMN
stop $WVCIP
stop $WVCLM

status *,prog UMPGATE, stop
status *,prog UMPMEAS, stop
status *,prog EMSLINK, stop
status *,prog TMFMEAS, stop

MEASCOM STOP MEASUREMENT UMPACT, NO ADD

stop $WVECL
stop $WSAMR
stop $WSAHR

6. Edit the “UGATCONF” file and change the port number.

[BASEOBJECT]
OBJECTFILE UMPGATE
OBJECTID OBJID_UMPGATE
PORT 8787
TITLE UMP Gate
MAXPROCESS 20
NUMSTATIC 10
PARAM WEBLOCATIONN /usr/tandem/wvpe
PARAM PATHWAY-01 $SYSTEM.SYSTEM.PATHMON
PARAM EXECUTION-LOG *
ASSIGN PATHWAYS-FILE ,PATHWAYS
ASSIGN SERVERS-FILE ,SERVERS
ASSIGN TERMS-FILE ,TERMS
ASSIGN TCPS-FILE ,TCPS
ASSIGN GROUPS-FILE ,GROUPS
ASSIGN GROUPE-FILE ,GROUPE
ASSIGN CC-FILE ,WVPPCC
ASSIGN CCE-FILE ,WVPPCCE

1. Edit the “UMPCONF” file and change the process names, CPU numbers and EMS collector if required.
   (i.e. Change the ems collector defined by the “COLLECTOR” parameter to a unique name)

— Supported products are NTS, RA and PMC.

SET PRODUCT_NAME RA
— SET EMS Log parameters
SET EVENT_LOG COLLECTOR $0
SET EVENT_LOG SSID 1500
— Set UMPGATE parameters

comment — CPU number on which the UMPCOL8 backup should run
SET UMPCOL8 BACKUP_CPU 2,3,4,5
SET UMPCOL8 BACKUP_RESTART_LIMIT 50

— Set UMPCMON parameters
comment — CPU number on which the UMPCMON backup should run
SET UMPCMON BACKUP_CPU 2,3,4,5
SET UMPCMON BACKUP_RESTART_LIMIT 50

— Set UMPMEAS parameters
SET UMPMEAS SAMPLE_INTERVAL 15
SET UMPMEAS COLLECT_FOR CPU,PROCESS,DISK

— Set UMPSKYI parameters
comment — CPU number on which the UMPSKYI backup should run
SET UMPSKYI BACKUP_CPU 1,2,3,4,5
SET UMPSKYI BACKUP_RESTART_LIMIT 50

— Set EACOLL parameters
comment — CPU number on which the EACOLL backup should run
SET EACOLL BACKUP_CPU 2,3,4,5
SET EACOLL BACKUP_RESTART_LIMIT 50

— Set UMPDRNE parameters
comment — CPU number on which the UMPDRNE backup should run
SET UMPDRNE BACKUP_CPU 1,2,3,4,5
SET UMPDRNE BACKUP_RESTART_LIMIT 50

If necessary, change the EMS collector defined in the “COLLECTOR” parameter of the “UMPCONF” configuration file (default is “$0”) using the following command:
> EMSACOLL /NAME $UMP, NOWAIT/

8. Issue the following command to start the WVP Enterprise host components:

> OBEY STRTWVPE

OSS:

Using OSS mode, set the path to folder (/usr/tandem/wvpe)

Using OSS mode, set the path to /usr/tandem folder within the OSS space (this can be changed to any path).

By default, the path is set to /usr/tandem/wvpe.

You may choose to change this path by changing it in the UGATCONF file within the Web ViewPoint Enterprise subvolume.

1. Create folder wvpe in /usr/tandem location (example: /usr/tandem/wvpe)

Command to create a folder in OSS: mkdir wvpe
cd wvpe

2. Transfer the tar file (which was sent as a part of install package) to the wvpe folder
3. Extract the contents of the tar file using tar -o -xvf wvpe.tar command
4. Edit the host.txt file in the data folder (/usr/tandem/wvpe/data)
5. Change the Nodename to match that of the installation of the host agent.
6. Open your browser and enter the IP address specified in the host.txt file followed by port number (specified in the UGATCONF file within Web viewpoint subvolume)

Example: http://192.168.1.100:8787
To access the lite port, enter the following http://nnn.nnn.n.nnn:8787/#/lite

For Web Viewpoint Enterprise Users:

In order to enable the HTTPS support in Web ViewPoint, users need to follow the steps below:
1) Set the PARAM WVPSECUREHTTP ON & PARAM CONFIG SSLCONF in your STRTWVPE & UGATCONF files. Please click here for more information on how to set the PARAM.
2) Get the SSL certificates from a trusted party(Verisign). Many hosting providers set these certificates for you for fee. Simply ask your system admin.
3) Once you have the certificates. Place them in your Web ViewPoint Enterprise subvolume and edit the SSLCONF file with the location of your certificates as below
SERVKEYPASS      passcode
SERVKEY          SERVKEY
SERVCERT         SERVCERT
CACERTS          CACERT
4) Restart your Web ViewPoint Enterprise by running below commands
OBEY STOPWVPE
OBEY STRTWVPE
5) Final step requires you to change the host.json file on the OSS space. See below for detailed steps:

OSS:

1) Logon to you NonStop in OSS mode
2) Navigate to the directory where you have Web ViewPoint Enterprise files installed (e.g: wvpe)
Example: cd /usr/tandem/wvpe
3) Edit the host.json file in the data folder (/usr/tandem/wvpe/data)
Change the protocol from http to https
Example: “protocol”: “https://”
4) Open your browser and enter the IP address specified in the host.json file followed by slash and web viewpoint Enterprise folder name (created in step 1) to access WebViewPoint Enterprise.
Example:https://nnn.nnn.n.nn:8787/index.html

In order to map the Web ViewPoint’s Subsystem ID to its Subsystem Name for generated EMS messages by Web ViewPoint, the Web ViewPoint EMS template file needs to be installed. This will cause the Web ViewPoint messages to show up as TANDEM.WVP instead of TANDEM.257

For installing the NonStop Web ViewPoint EMS templates, please follow the steps listed below.

1. Logon to the system as SUPER.SUPER. Go to the Web ViewPoint installation Subvolume and run the following command

> Run WVPTMPAK

The above command will extract the ZWVPTMPL file and place it in the current subvolume.

1. Determine the volume where the installation subvolume ZINSAIDS is located.  This subvolume should have been placed on your system when you installed your last SUT-based products
2. Enter the following command at the TACL prompt

> LOAD / KEEP 1 / $.ZINSAIDS.TACLMACS

where $ is where the ZINSAIDS subvolume is located

1. Volume to $SYSTEM.ZTEMPL.  This is the subvolume where the individual product templates are located.
2. Move the new Web ViewPoint template file (ZWVPTMPL) from the sub volume where Web ViewPoint is installed.  For example, if you installed the Web ViewPoint software on $SYSTEM.ZWVP5, then enter the following command

> FUP DUP $SYSTEM.ZWVP5.ZWVPTMPL, *, PURGE, SAVEALL

1. Determine the names and location of your current resident and non-resident template files using the following command

> SCF INFO SUBSYS $ZZKRN

1. Volume to the directory where the template files are located. For this example, assume they are located on $SYSTEM.SYS00
2. Pick a pair of names for your new resident and non-resident template files.  Make sure files do not already exist with these names.  For our example, let us assume that the new names will be:

NewRes (for the new resident template)

NewNRes (for the new non-resident template)

1. Enter the following command to create the new template files

> INSTALL^TEMPLATES NewRes NewNRes CURRENT^TEMPLATES $SYSTEM.ZTEMPL

NewRes and NewNRes are created in your current subvolume, which we had set to $SYSTEM.SYS00 in step G

The Web ViewPoint Enterprise file list can be categorized into to four sections as described below:

• START/STOP
• CONFIGURATION
• OBJECTS/EXECUTABLES
• DATA

File Name	Code	RWEP	Description
STRTWVPE	101	NUNU	Obey script file to start WebViewPoint Enterprise
STOPWVPE	101	NUNU	Obey script file to stop Web ViewPoint Enterprise
STRTPRXY	101	NUNU	Obey script file to start WebViewPoint Enterprise in Proxy mode
STOPPRXY	101	NUNU	Obey script file to stop Web ViewPoint Enterprise in Proxy mode

 

 

File Name	Code	RWEP	Description
SSLCONF	101	NUNU	Configuration file for Secure mode
SNMPOSSI	101	NUNU	Instructions file for SNMPOSS agent
UCNFRA	101	NUNU	Port, PARAM, ASSIGN configuration file for RA module
UGATCONF	101	NUNU	Configuration for the webserver worker program and port
UMPCONF	101	NUNU	Configuration for UMP parameters
UMPFUP	101	NUNU	FUP Obey file to create the UMP data files
UMPCLEAN	101	NUNU	Obey file to clear the data from the UMP data files

File Name	Code	RWEP	Description
BAMCOPY	800/500	NUNU	Tool to copy BAM, BAMD information from AAF to AAH and onwards
DISKCTLR	800/500	NUNU	Collects the storage information (Remote Anlayst)
DOQNM	800/500	NUNU	Main program file for configuration and installation of RA and PMC collector on NonStop
EACOLL	800/500	NUNU	Event analyzer Host Module.
EMSLINK	800/500	NUNU	EMS Reader alternative Program
EVTCXIM	800/500	NUNU	Tool to copy EVENTCX information into the BAM database.
FINFLIB/FINFO	800/500	NUNU	AAAA Privileged code files required to display list of files opened by a process
IPCOPY	800/500	NUNU	To populate the Neighborhood information from the IPLISTTX file
LISTAPP	800/500	NUNU	Listener program for the webserver
MEASHUB	800/500	NUNU	Manages the processing of Measure files
MEASPCSR	800/500	NUNU	Converts the Measure file to UMM files
MSCHDLR	800/500	NUNU	Interacts with Measure to schedule collections
PROCMAN	800/500	NUNU	Process Manager of the webserver
PWYCLTR	800/500	NUNU	Collects Pathway information (Remote Analyst)
PWYPCSR	800/500	NUNU	Processes Pathway information (Remote Analyst)
RASNAP	800/500	NUNU	Main program file for SNAP program for RA
SAGETF	800/500	NUNU	Storage analyzer Client Fragmentation Module.
SAHRLY	800/500	NUNU	Calculate the storages
SAMGR	800/500	NUNU	Storage analyzer Host Module.
SAPROC	800/500	NUNU	Storage analyzer Sub Host Module.
SAWFRAG	800/500	NUNU	Storage analyzer Fragmentation Module.
SETUPRA	800/500	NUNU	Configuration and installation of RA collector on NonStop.
SETUPWVP	800/500	NUNU	Configuration and installation of Web ViewPoint on NonStop.
SNMP	1729	NUNU	SNMP agent receives messages from notification component of WVP and sends out corresponding SNMP traps to the SNMP receiver
SSIDPOP	800/500	NUNU	Utility program used to populate the WVP’s SSIDDB table with all the SSID info defined on the NonStop system. See SSIDPOP for run instructions
SYNC	800/500	NUNU	Tool to manage neighborhood post installation
SYSLOG	1729	NUNU	SYSLOG agent receives messages from notification component of WVP and sends out corresponding SYSLOG traps to the SYSLOG receiver
TMFMEAS	800/500	NUNU	Interacts with SCF subsystem to gather TMF related information
UCLMEAS	800/500	NUNU	Collects the CLIM data
UFTPCFU	800/500	NUNU	Configures the UMPFTP settings
UMONITOR	800/500	NUNU	Collects the alert information
UMPCLIM	800/500	NUNU	Manages the collection of CLIM data
UMPCMON	800/500	NUNU	Monitors and ensures that there are correct number of UMPMEAS instances running
UMPCOL8	800/500	NUNU	Aggregator and reporter of Measure data
UMPDRNE	800/500	NUNU	Monitors the delivery based on subscriptions
UMPFTP	800/500	NUNU	File transfer program
UMPGATE	800/500	NUNU	Worker process for the webserver (Remote Analyst)
UMPHUB	800/500	NUNU	Manages the collection and processing of UMP jobs
UMPMAID	800/500	NUNU	Cleans up files and records based on retention parameters
UMPMEAS	800/500	NUNU	Measure data collector program that runs on each CPU to gather statistics
UMPNTS	800/500	NUNU	Sends NTS site progress status messages (Remote Analyst)
UMPPAK	800/500	NUNU	Web ViewPoint Pak file
UMPPICK	800/500	NUNU	Waits for Measure files to process (Remote Analyst)
UMPQNM	800/500	NUNU	Manages the collection of QNM data
UMPSKYI	800/500	NUNU	Monitors EMS messages and takes action based on subscriptions
UMPSNMP	800/500	NUNU	SNMP Trap Sender
UMPULOAD	800/500	NUNU	Upload files to FTP server.
USUMVIEW	800/500	NUNU	Manages the ticker settings
WPATEVTS	800/500	NUNU	PAK-ed program containing BAM, BAMD for Pathway
WVPEVTS	800/500	NUNU	PAK-ed program containing the BAM, BAMD and UCARRIER files
WVPTMPAK	800/500	NUNU	PAK-ed program containing the WVP EMS template file.

File Name	Code	RWEP	Description
AADB	0	NNUU	Alternate Key Sequenced file for the Event Acknowledge Database
ADB	0	NNUU	Event Acknowledge Database
BAM	0	NUNU	BAM Database for Event Information
BAMD	0	NUNU	BAM Detail Database for Event Information
EVINFDB	0	NNUU	Event Information Database used by Messaging System
EVTCOLL	0	NNUU	Stores the specified collectors per Event Settings Profile
EVTPROFL	0	NNUU	Stores the Event Settings Profile information for the Event Live and Query screens
EVTSEL	0	NNNU	Stores specified subsys selection criteria per Event Settings profile
OWNERDB	0	NNUU	Event Management Database containing user defined Owners
SSIDDB	0	NNUU	SSID Name ID Map Database
TMPLDTL	0	NNUU	Display Template detail Database
TMPLDTLA	0	NNUU	Temp data file used to store template info
TMPLMST	0	NNUU	Display Template master Database
IPLIST	1500	NNUU	File containing the neighborhood information
UCARRIER	1500	NNUU	Phone carriers information repository
ULICENSE	1500	NNUU	Web ViewPoint License repository
UMPBRINK	1500	NNUU	Stores the threshold values
UMPFTPCF	1500	NNUU	Stores the Remote Analyst FTP host information
UMPNOTFY	1500	NNUU	Stores the user profile information.
UMPSKIND	1500	NNUU	Stores the skins related information
UMPSRVRS	1500	NNUU	Stores the SMTP and SNMP server information
UMPUSERD	1500	NNUU	User information repository
USUBSRCB	1500	NNUU	Stores the user profile information.

PARAM LISTENER-PROCESS [STRTWVPE]

This specifies the name to be used for the listener process that is created by the process manager. This is a required param.

PARAM TCP-PROCESS [STRTWVPE]

This specifies the name of the TCP process to be used by the listener process when listening on ports specified in the various configuration files. This is an optional param. Default value is $ZTC0.

PARAM HIDEACKS [YES|NO] [UGATCONF]

This tells the EMSLINK whether to hide acknowledged events or whether to show them as acknowledged.

PARAM SAVEEVENTS [YES|NO] [UGATCONF]

This tells the EMSLINK whether to show the “Save Events to Log” check box on the settings screens. If SAVEEVENTS is NO, the “Save Events to Log” feature is disabled and the check box does not appear. The default value is NO.

PARAM SMTP-PORT   25 [STRTWVPE]
Specifies the SMTP port (i.e. PORT 25) to be used by the WVP Enterprise Delivery module.
If the PARAM is not specified then it defaults to PORT 587.

PARAM FILTERFILE-LOCATION <$vol.subvol> [UGATCONF]

This param specifies the subvolume containing pre-compiled filter files. This list of filter files is displayed on the Events settings screen of WVP.

PARAM WVPSECUREHTTP [ON|OFF] [STRTWVPE, UGATCONF]

This is an optional PARAM. By specifying this PARAM Web ViewPoint/ Web ViewPoint Plus operates in a secure communication via SSL; there by providing confidentiality, integrity and identity. This PARAM should be placed in STRTWVPE, UGATCONG files

PARAM CONFIG SSLCONF [STRTWVPE, UGATCONF]

This param is required when PARAM WVPSECUREHTTP is configured. This PARAM should be placed in STRTWVPE, UGATCONF files

PARAM LITEAUTH [YES|NO] [UGATCONF]

This is used if the lite feature should enforce a logon requirement. If set to YES then logon is required, if set to NO or omitted, then user can access features without logging on (Default: NO)

PARAM EMSLINK-BUSY-MAX [UGATCONF]

This specifies in terms of percentage the limit to which the CPU would be used. If EMSLINK-BUSY-MAX is set at 60, then 60% of the CPU is allocated for processing the events. If this param is not specified, the system decides the amount of CPU to be utilized. If this param is set to 0, the CPU limit is turned off.

PARAM MULTILANGSUPPORT <Language> [UGATCONF]

This specifies whether multi-language character support is required for displaying of EMS messages in Events. Click here for more specific information.

PARAM EMSLINKTIMEOUT [UGATCONF]

This allows the user to specify the amount of time after which EMSLINK should timeout when it does not receive a request from Lite. The scenario for the timeout is within the time of pressing the Stop button and when you want to return/resume. This also applies to pressing the Next and/or Prev buttons.

Default value 5

Minimum value 2

Maximum value 60

PARAM ACTION-COLLECTOR <$Coll> [STRTWVPE]

This specifies the Collector to which the EMS messages must be written to when the alert condition is met and a file is Run/Obeyed. If this PARAM is not specified the EMS messages will not be written to any of the collectors.

PARAM LOOKBACK-DAYS [STRTWVPE]     

This specifies the number of days that can be looked at to build database upon initial run.
Default: 30

PARAM SCROLL-DELAY <value>  [UGATCONF]  

This param controls the speed at which the events are displayed on the Events screen. The value must be greater than 0. As the number increases the delay also increases. It is recommended to not configure a high value.

PARAM EVENTS-PAGE-SIZE  <value> [UGATCONF]  
This allows the user to specify the maximum number of events to store in the browser. Use this param to control the overhead of Events on the browser.

Default value 1000
Minimum value 100  
Maximum value 1000

Also, irrespective of single node or multi node, EVENTS-PAGE-SIZE determine the maximum number of events displayed on the events screen. (Note: In case of multimode, the parent node PARAM EVENTS-PAGE-SIZE determine the maximum number of events to be displayed)

Web ViewPoint Central Router (WCR) is a connectivity subsystem that allows a user to connect to any hp NonStop Server with Web ViewPoint Enterprise installed and under management from a Web ViewPoint Enterprise Window active on any other NonStop Server.

Following are terms presented with the Central Router:

• Web ViewPoint Enterprise Resident: A NonStop Server (whether isolated or part of an Expand network) or Resident with an installed Web ViewPoint Enterprise (H01/L01 & after).
• Web ViewPoint Enterprise Neighborhood: An Expand network of NonStop servers with two or more servers or residents with an installed Web ViewPoint Enterprise  (H01/L01 & after).
• Automated Synchronization: The ability of Web ViewPoint Enterprise installations to maintain a distributed but synchronized library of IP and port addresses for all Web ViewPoint Enterprise installations on the Expand network.
• Neighborhood Inquiry: The ability of a Web ViewPoint Enterprise session to inquire about another Resident of the same Neighborhood (any other resident of the same Expand network).

Note that use of the new terms, “Resident,” and “Neighborhood,” as opposed to “Node” and “Expand,” respectively, are to signify the environment as it applies to Nodes where Web ViewPoint Enterprise is installed. Features described here apply only to Web ViewPoint Enterprise Residents and Neighborhoods.

Web ViewPoint Enterprise Neighborhood

A Web ViewPoint Enterprise Neighborhood can be considered to be a collection of Web ViewPoint Enterprise Residents that are on the same network. The following is assumed to be true of a Neighborhood:

1. There cannot be two Residents belonging to the same System on the same Neighborhood.

                e.g.          SYSA    $A.B       1.1.1.1: 2500       2501
SYSA    $C.D       1.1.1.3: 2500       2501

                The above Neighborhood cannot exist since it has two Residents from the same system.

2. A given Resident can belong only to one Neighborhood.

             e.g.          Neighborhood 1:
SYSA     $A.B       1.1.1.1: 2500       2501
SYSB     $A.B       1.1.1.2: 2500       2501

             Neighborhood 2:
                            SYSA    $A.B       1.1.1.1: 2500       2501
SYSC    $A.B       1.1.1.3: 2500       2501
 

Neighborhoods 1 and 2 both have the same Resident of System A which is not permitted.

Each Resident installed will include a synchronization program called Sync that will be used by the Resident to join/leave a Neighborhood as well as synchronize the entire Neighborhood that the Resident is part of.

Also, during installation, the main Central Router database called IPLIST will be created in the Resident’s home volume. Once the Resident has been initiated into the Neighborhood, this database will store records for all Residents of the neighborhood which include the System name, Volume-Subvolume, IP address and Port number for the Resident.

• The tool needed to configure your NRs is called SYNC. This program is installed in the NonStop subvol you defined for a particular instance of Web ViewPoint Enterprise  Functions of the SYNC program are:

1. Create Neighborhood
2. Join a Neighborhood
3. Leave a Neighborhood
4. Synchronize

• You can create a new Neighborhood on any Resident that you want in that Neighborhood.
• When you join a Neighborhood when prompted for “Enter the System Name of an existing Resident”, make sure you input an existing Resident, not the Node Name you are on. Example:

1. On PROD1 node, I create Neighborhood “WEST”; when this is done PROD1 is automatically a Resident in Neighborhood “WEST”.
2. If I want the LA Node to join Neighborhood “WEST”, then I would logon to LA, run the SYNC program and input PROD1 when prompted for an existing System Name.

• File used for storing the NR configuration is:

NonStop – IPLIST

• If you ever change the IP address of a Resident (i.e. NonStop Node) you will need to use the SYNC program to “Leave Neighborhood” and then use the “Join a Neighborhood” to establish the new IP address in the NR configuration files. The same goes for changes to the Port number in the Web ViewPoint Enterprise installation UGATCONF file.

Consider the following example:

1. Neighborhood TEST1 has NSPROD and YOSPRD defined as Residents.

• NSPROD WVP Instance is running from NSPROD.$DATA1.WVPTEST1 with unique process names. (Note: IPLIST in subvol WVPTEST1 has the Neighborhood details.)
• YOSPRD WVP Instance is running from YOSPRD.$DATA4.WVPTEST1 with unique process names

2. Neighborhood QATST on NSPROD has only NSPROD defined as a Resident.

• NSPROD WVP Instance is running from NSPROD.$DATA2.WVPQATST with unique process names

Method 1:

Each Resident installed will include a program called ‘IPCOPY’ that will be used by the Resident to join/leave a Neighborhood that the Resident is part of.

To join a Neighborhood, users should input all the resident information in the IPLISTTX file present in the Web ViewPoint Enterprise subvolume $volume.subvol:

NOTE: Make sure there are NO extra spaces with in the IPLISTTX file.

Run the below program to join the neighborhood.
> RUN IPCOPY

NOTE: Restart the Web Viewpoint Enterprise Instance.

This populates the neighborhood information to the IPLIST file. Open the IE browser and enter the Web ViewPoint Enterprise URL to verify the nodes. The nodes populated in the IPLIST file will be displayed when clicked on the globe icon on the logon screen as shown in the example below.

To leave neighborhood, just run the below command to purge data from the IPLIST file.

FUP PURGEDATA IPLIST

Restart Web ViewPoint Enterprise, this should remove the neighborhood information from the resident node.

Method 2:

Each Resident installed will include a synchronization program called Sync that will be used by the Resident to join/leave a Neighborhood as well as synchronize the entire Neighborhood that the Resident is part of.

SYNC:

This program should be run to:

• Start a Neighborhood
• Join an existing Neighborhood
• Synchronize all Residents of a Neighborhood
• Leave a Neighborhood.

To run the SYNC program, user should run the following command in their Web ViewPoint Enterprise $volume.subvol:

>run sync

When the program will be run for the first time, the user will be shown a menu screen that looks like this:

********** WVP Central Router Options **********
*                                                                                               *
*        1. Create Neighborhood                                              *
*        2. Join a Neighborhood                                               *
*        3. Exit                                                                            *
*                                                                                               *
*********************************************

For creating a new Neighborhood, Option 1 (Create Neighborhood) is chosen which prompts the user for the Neighborhood name. On entering the name, the Central Router database will be initialized, which will initially have an entry of just the Resident that initialized it.

To initiate other Residents into this Neighborhood, Option 2 (Join) is chosen. In this case, the user needs to specify the name of the Neighborhood as well as the location of any one existing Resident belonging to that Neighborhood. After this step, the user will be prompted to enter the TCPIP process name of the current system.

Using the other Resident’s location information, the program will first update its own Resident’s database with data obtained from the other and then synchronize the databases of all Residents of the Neighborhood to reflect the newly-added Resident’s data.

Once a Resident is part of the Neighborhood, subsequent calls to Sync will show a menu as shown below:

Subsequently, any change to the IP address or Port Number by the user should be communicated to the entire Neighborhood by running Sync again, and selecting option 1 (Synchronize). So if a user makes changes to the IP address or Port Number in the UGATCONF file, he/she needs to run Sync which will automatically update the databases of all Neighbors with the new IP Address/Port Number without the user having to specify the changed IP/port again.

************* WVP Central Router Options **********
*                                                                                               *
*        1. Synchronize                                                             *
*        2. Leave Neighborhood                                              *
*         3. Exit                                                                          *
***********************************************

Note that during synchronization, the database with the most recent “Version” will be used as reference. This ensures that even if a Resident is down during synchronization, running the program at a later time (when it becomes available again), will update its database to the latest state.

If option 2 (Leave Neighborhood) is chosen, the Resident’s entry will be removed from the database of all others belonging to that Neighborhood.

NEIGHBORHOODS:

The Neighborhood section will have the configured Neighborhood listed on the left hand side and the addresses of the Residents belonging to that Neighborhood, on the right side. The user can select which Resident to connect to by selecting the address from the right hand table.

Note the option ‘None’ under the Neighborhoods list. This option will be pre-selected if the Resident that the user connects to is not found in the database.

Get Alert notifications: You can set up alerts for all the metrics you want Web ViewPoint Enterprise to watch for. You may set as many alert conditions as needed.

Before you begin: To modify alert notification settings, you must be assigned the Administrator role. You must be running an SNMP management application in your system environment. Management Information Base (MIB) files are provided via WVPMIB file which will be part of your installation files (within WVP E subvolume). You must set up the SNMP trap receiver with the MIB files to receive SNMP traps from WVP Enterprise.

Step 1: In order to send alerts from WVP to the SNMP receiver, the WVP SNMP component needs to be installed in the OSS space. This component receives messages from notification component of WVP and sends out corresponding SNMP traps to the SNMP receiver.

Please follow the below steps to install the SNMP agent on OSS.
1) Go to OSS space, create a directory named usnmp in the following location /usr/tandem

Commands:
cd /usr/tandem
mkdir usnmp
Example: /usr/tandem/usnmp

2) Transfer the snmp.tar file to the newly created directory
NOTE: snmp.tar file is present within UMPPAK pak file (which is present within your WVP E install subvolume)

You can transfer the snmp.tar file in 2 ways.

Method 1: You can download it from your WVP E subvolume and transfer it to OSS directory via any FTP client
or

Method 2: You can transfer it to OSS side from Guardian via OSH commands by following the below instructions

a) Logon to OSS space, navigate to location where you have WVP E installed (replace VOLUME/SUBVOLUME with your WVP E install volume subvolume on guardian side)
cd /G/VOLUME/SUBVOLUME

b) Check to make sure that snmp file is present within that location

cd /G/VOLUME/SUBVOLUME
ls

c) Now, copy over the snmp file from this location to your OSS location (i.e. to directory you created in step 1)

cp snmp /usr/tandem/usnmp

d) Navigate to /usr/tandem/usnmp location and verify if the file has been copied over by using below commands

cd /usr/tandem/usnmp
ls

e) Rename snmp to snmp.tar by running the below command
mv snmp snmp.tar

3) Extract the contents from the tar file by running the below command.

tar -o -xvf snmp.tar
/usr/tandem/snmp: tar -o -xvf snmp.tar
x snmp4j.jar, 473413 bytes, 925 tape blocks
x umpSNMP.class, 11590 bytes, 23 tape blocks
x umpSNMPStart.sh, 505 bytes, 1 tape blocks

4) Edit umpSNMPStart.sh file
a. Modify the java related parameters
b. If needed, change the directory name from /usr/tandem/dir/ to corresponding one (i.e. added in Step 1).

cd /usr/tandem/dir
to
cd /usr/tandem/usnmp

export CLASSPATH=$CLASSPATH:/usr/tandem/dir/snmp4j.jar:.
to
export CLASSPATH=$CLASSPATH:/usr/tandem/usnmp/snmp4j.jar:.

Note: usnmp is an example directory. You can change that to your desired directory.

5) If the TCP Process is a different from $ZTC0, define the specific process name (add_define =tcpip^process^name file=\$NAME) in the umpSNMPStart.sh file.

#!/bin/sh
cd /usr/tandem/usnmp
export _RLD_LIB_PATH=$_RLD_LIB_PATH:/usr/tandem/javaexth11/lib
export JAVA_HOME=/usr/tandem/nssjava/jdk180_h80/
export JREHOME=$JAVA_HOME/jre
export CLASSPATH=$CLASSPATH:/usr/tandem/javaexth11/lib/tdmext.jar
export PATH=/usr/tandem/javaexth11/bin:$PATH
export APP=umpSNMP
export CLASSPATH=$CLASSPATH:/usr/tandem/usnmp/snmp4j.jar:.
add_define =tcpip^process^name file=\$NAME
run -name=/G/usnmp /usr/tandem/nssjava/jdk180_h80/bin/java $APP

6) Give execute permission to the script file using the below command

chmod 755 ./umpSNMPStart.sh

7) On guardian, add the persistent process information via SCF. To do so, go to SCF prompt, modify the required fields as mentioned below and run the lines (as shown below)
a. Change the below highlighted CPU value if necessary
b. Change the DEAFULTVOL location. This could be the default volume of the user who is logged on to NonStop
c. Make sure the OSS path /usr/tandem/usnmp/umpSNMPStart.sh is the same one you created in Step 1.

ADD PROCESS $ZZKRN.SNMP, &
AUTORESTART 2 , &
CPU 03 , &
DEFAULTVOL $IDEL00.QABKCOL , &
HIGHPIN ON , &
HOMETERM $ZHOME , &
INFILE $ZHOME , &
NAME $USVM0 , &
ASSOCPROC $USNMP , &
OUTFILE $ZHOME , &
PRIORITY 146 , &
PROGRAM $SYSTEM.SYSTEM.OSH , &
SAVEABEND OFF , &
STARTMODE MANUAL , &
STARTUPMSG “-osstty -p /usr/tandem/usnmp/umpSNMPStart.sh <- >>/tmp/umpSNMP.out2>>/tmp/umpSNMP.err” , &
STOPMODE STANDARD , &
TYPE OTHER, &
USERID SUPER.SUPER

8) To start the process (in SCF): START PROCESS $ZZKRN.SNMP

9) Verify that the process is running by running the below command in SCF.

-> Status PROCESS $ZZKRN.SNMP

Symbolic Name Name State Sub Primary Backup Owner
PID PID ID
SNMP $USVM0 STARTED 3 ,1026 None 255,255
SNMP $USNMP STARTED 3 ,1097 None 255,255

10) To stop the process (in SCF): ABORT PROCESS $ZZKRN.SNMP. Now, you can set up the alert to go to SNMP.

Step 2: To configure SNMP alert notifications, complete the following steps:

1. In the menu bar in the web-based GUI, go to Admin > Delivery.
2. Under the SNMP tab, specify new settings or remove existing settings. To specify new settings, input the below fields and click on Submit.

Name:
Specify any name of the SNMP for sending SNMP traps.

IP address:
Specify the host that is configured to receive SNMP traps. You can specify a host name, an IPv4  address, or an IPv6 address depending on what is supported within your environment.

Port:
Specify the port number for receiving SNMP traps. SNMP trap messages are sent to this port when an alert condition is detected. By default, the port is set to 162.

Specifying the below PARAM will enable the user to view the EMS messages in ‘Chinese’, ‘Japanese’ & ‘French’ languages.

Chinese:
PARAM MULTILANGSUPPORT big5

Japanese:
PARAM MULTILANGSUPPORT shiftjis

French:

PARAM MULTILANGSUPPORT WESTERN-EUROPE

After configuring the PARAM in the UGATCONF file, users will have to restart the port and do the following.

• After specifying your desired settings in the Events-Query settings screen, click on ‘Submit’
• It will navigate the user to the Query page and starts to display the EMS events, the page will be display the EMS messages in the selected language.

Applicable until H01AAC-L01AAD versions only. Please follow the below instructions to grant only specific or all permissions to users.

• Logon to Web ViewPoint Enterprise, navigate to ‘Admin – Users’ section
• Add users and grant them permissions (Performance, EMS, Operations or Admin) by un-selecting the sections that you do not want them to access (by default all permissions are selected) or by leaving all buttons selected and giving complete access to WVP Enterprise features.

Note: Add the main user (one who controls all administrative operations of WVP Enterprise) and give all permissions to that user.

• Go to your Web ViewPoint Enterprise subvolume and create a new edit file “USERPERM”
• To enforce the security, edit the USERPERM file and type Y (i.e. Y for yes)
• And run below command
• FUP COPY USERPERM, USETTING
• If you want to disable this enforce security feature then edit the “USERPERM” file and type N (N for No) and rerun the ‘FUP COPY USERPERM, USETTING’ command

Get notifications for events:

You can set up alerts for list of events you want Web ViewPoint Enterprise to watch for. You may set as many alert conditions as needed.

To send alerts, Web ViewPoint Enterprise must connect to a mail server, also known as a Simple Mail Transfer Protocol (SMTP) server. An SMTP server is a service that you can send outbound email messages to. It then relays the messages to whoever they’re addressed to. (It doesn’t handle incoming email.) To set up alerts, you must configure Web ViewPoint Enterprise to communicate with your SMTP mail server.

SMTP information you’ll need

Many organizations already have an SMTP server in-house. Before you continue, ask your IT department if there is an SMTP server that you can use.

Here’s the SMTP server information that you need from your IT department:

• The server address. This is often something like smtp.example.com or mail.example.com, but other addresses are also possible.
• A user name.
• A password.

Some servers don’t require a user name or password because they are only meant for internal use.

You’ll also need to decide on a from address for the alerts that the server sends. When people receive an alert email from Web ViewPoint Enterprise , this is the name that’s on the from line of the message. Because alerts are simply informational, you generally don’t need to worry about who’s on the from line, so people use addresses like no-reply@example.com

After you get the SMTP server information from your IT department, you can follow the below steps to configure and setup alerts.

Step 1: Configure SMTP Server information

1. Logon to Web ViewPoint Enterprise , navigate to Admin – Delivery section
2. Enter the information that you received from your IT department.
3. In the Mail from account box, enter the email address that you want all server emails to be sent from. For example, you might enter or no-reply@example.com.
4. Click Submit.

Step 2: Add Users and Phone Carriers

Users and Phone carriers need to be added prior to setting up the alerts. This will help specify which user you want to send the email or sms alerts to. Phone carrier is required only if you want to setup text/sms alerts (if you do not want to receive any text alerts you can skip the phone carriers section and go to Add Users section)

a) Add Phone Carriers

In the Admin – Phone Carriers section, there is a list of pre-defined phone carriers present. If your phone carrier is not one of them you will need to add your carrier.

1. Logon to Web ViewPoint, navigate to Admin – Phone Carriers section
2. Click on Add button present on the top right corner
3. Enter the information that you received from your IT department.
4. Click Add.

b)  Add Users

1. Logon to Web ViewPoint Enterprise , navigate to Admin – Users section
2. Click on Add button present on the top right corner
3. Enter all the required information in the fields

Note: Phone number and phone carrier fields are optional if you do not want to setup a text alert. However, if you do want to setup a text alert, you will need to enter the phone number and the carrier information.

1. Click Save

Step 3: Set up alerts

Go to the Admin – Alerts menu and click Add

Configure the alerts based on your requirements and click Save.

          Issue 1: If launching WVP Enterprise gives the following error message, then:

1. Check to confirm all the required host components are running as expected.
2. Run STATUS *, PROG * in the Web ViewPoint Enterprise subvol to confirm running components (Example:$VOLUME.SUBVOL> STATUS *, PROG *)Process Pri PFR %WT Userid Program file Hometerm$WVLST B 0,793 160 001 255,255 $IDEL12.AACN27.LISTAPP $ZTN0.#PTUS9ZN$WSAMR B 0,1522 120 001 255,255 $IDEL12.AACN27.SAMGR $ZHOME

   $WVSEF B 0,1674 140 001 255,255 $IDEL12.AACN27.WVPPREF $ZHOME

   $X0FQ 0,1820 158 000 255,255 $IDEL12.AACN27.UMPMEAS $ZHOME

   $WVPMN B 0,1932 160 001 255,255 $IDEL12.AACN27.PROCMAN $ZTN0.#PTUS9ZN

   $X0G0 1,632 160 001 255,255 $IDEL12.AACN27.UMPGATE $ZTN0.#PTUS9ZN

   $WVSKY B 1,1093 158 001 255,255 $IDEL12.AACN27.UMPSKYI $ZHOME

   $WVDRN B 1,1135 158 001 255,255 $IDEL12.AACN27.UMPDRNE $ZHOME

   $X0FR 1,1171 158 000 255,255 $IDEL12.AACN27.UMPMEAS $ZHOME

   $WVCL8 B 2,680 158 001 255,255 $IDEL12.AACN27.UMPCOL8 $ZHOME

   $X0FS 2,712 158 000 255,255 $IDEL12.AACN27.UMPMEAS $ZHOME

   $WVCMN B 2,980 158 001 255,255 $IDEL12.AACN27.UMPCMON $ZHOME

   $WVECL B 2,1044 120 001 255,255 $IDEL12.AACN27.EACOLL $ZHOME

   $X0FT 3,991 158 000 255,255 $IDEL12.AACN27.UMPMEAS $ZHOME

   $X0FV 4,1009 158 000 255,255 $IDEL12.AACN27.UMPMEAS $ZHOME

   $X0FW 5,437 158 000 255,255 $IDEL12.AACN27.UMPMEAS $ZHOME

   $WVSEF 5,486 140 000 255,255 $IDEL12.AACN27.WVPPREF $ZHOME

   $X0FX 5,535 158 000 255,255 $IDEL12.AACN27.TMFMEAS $ZHOME

   $WVDRN 5,712 158 005 255,255 $IDEL12.AACN27.UMPDRNE $ZHOME

   $WVPMN 5,846 160 001 255,255 $IDEL12.AACN27.PROCMAN $ZTN0.#PTUS9ZN

   $WVCLM 5,863 158 000 255,255 $IDEL12.AACN27.UCLMEAS $ZHOME

   $WVSKY 5,1063 158 005 255,255 $IDEL12.AACN27.UMPSKYI $ZHOME

   $WVLST 5,1091 160 000 255,255 $IDEL12.AACN27.LISTAPP $ZTN0.#PTUS9ZN

   $WSAMR 5,1122 120 000 255,255 $IDEL12.AACN27.SAMGR $ZHOME

   $WSAHR 5,1163 120 000 255,255 $IDEL12.AACN27.SAHRLY $ZHOME

   $WVCIP 5,1324 158 000 255,255 $IDEL12.AACN27.UMPCIP $ZHOME

   $WVCL8 5,1379 158 001 255,255 $IDEL12.AACN27.UMPCOL8 $ZHOME

   $WVECL 5,1468 120 000 255,255 $IDEL12.AACN27.EACOLL $ZHOME

   $WVCMN 5,1492 158 000 255,255 $IDEL12.AACN27.UMPCMON $ZHOME

   • UMPDRNE, UMPSKYI, UMPCMON, UMPCOL8, LISTAPP, PROCMAN, EACOLL, SAMGR & SAHRLY need to have a process pair(i.e. 1 primary process and 1 backup process).
   • UMPMEAS processes depend on the number of CPUs on the NonStop (i.e. if 2 CPU NonStop then there must be 2 UMPMEAS processes running)
   • TMFMEAS process must be running.
3. Confirm that the process capacity has not reached for UMPGATE object.
4. UMPGATE processes will start up based on the number of open sessions of Web ViewPoint Enterprise
   (i.e. if you have 3 open browser sessions of WVP E then you will see 3 UMPGATE processes)Note: The maximum number of UMPGATE processes that can be running at once is 20.
   The max value is configurable “MAXPROCESS 20”; users can change this value in the UGATCONF file.

 

1. Issue 2: If launching Web ViewPoint Enterprise gives you a blank screen, then:First try to figure out if the issue is with the host components or OSS compenents. To distinguish that, launch the below URL in any of the browsers (NOTE: Make sure that the IP address is your NonStop IP address and port number is the one you specified in UGATCONF file within your WVP E install subvolume)

   http://nn.nn.nn.nn:8787/homepage?command=GET_NSLIVE

   If your host components setup is correct, you will see the below info when you launch the above URL.

   

 

Entity	Counter	Formula
CPU	% Busy	(CPU-BUSY-TIME CPU / DELTA-TIME CPU) * 100
	Queue Length	(CPU-QTIME CPU / DELTA-TIME CPU)
	Memory	(CURRENTLOCKEDMEMORY / MAXIMUMLOCKEDMEMORY) * 100
IPU	% Busy	(IPU-BUSY-TIME CPU / DELTA-TIME CPU) * 100
	Queue Length	(IPU-QTIME CPU / DELTA-TIME CPU)
Process	% Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
	Receive Queue	(RECV-QTIME PROCESS / DELTA-TIME PROCESS)
	Memory	(PRESPAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PagesToBytes
Disk	% DP2 Busy	(CPU-BUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
	Queue Length	(REQUEST-QTIME DISK / DELTA-TIME DISK)
	% Device Busy	(DEVICE-QBUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
	% Read Busy	(READ-QBUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
	% Write Busy	(WRITE-QBUSY-TIME PROCESS / DELTA-TIME PROCESS) * 100
	Cache Hits	(SUM(C.HITS) /SUM(C.HITS + C.MISSES)) * 100
TMF	% Abort	(ABORT-TRANS PROCESS / BEGIN-TRANS PROCESS) * 100
	TPS	(ztransaction-rate from TMF STATUS command) / 100
	Begin Transactions per second	( BEGIN-TRANS PROCESS / DELTA-TIME PROCESS ) * 10^6
	Abort Transactions per second	(ABORT-TRANS PROCESS / DELTA-TIME PROCESS) * 10^6
	Receive Queue	(RECV-QTIME PROCESS / DELTA-TIME PROCESS)
	Memory used by the process	(PRESPAGES-QTIME PROCESS / DELTA-TIME PROCESS) * PageSizeBytes
	% CPU Busy (IPU) used by this process	(CPU-BUSYTIME PROCESS / DELTA-TIME PROCESS) * 100
Network	Total Sent	Netstat bytes transmitted successfully
	Total Received	Netstat bytes received without errors
CLIM	% Busy	As reported by vmstat on the CLIM
	Memory Used	As reported by vmstat on the CLIM

Support for Web ViewPoint Enterprise is available through HPE’s 24-hour Global NonStop Solution Centers (GNSC) throughout the world. In the U.S. call 1-800-255-5010.

Or you can contact support via https://support.hpe.com/hpesc/public/home

Required Hardware:
HPE NonStop Server
Non-dedicated Windows based PC(s) for browser based User Interface (recommended PC configuration defined below)

Minimum OS Release:
NonStop Kernel release;
H06.03 onward
J06.02 onward
L15.08 onward

Recommended PC hardware configuration for UI functions:

8 GB RAM minimum or higher
CPU Speed 2.40GHz or faster
Microsoft Windows 10 (32bit and 64bit) is the primary OS platform used for most of the WVP E testing.
Windows Server 2016 can also be used.

Required Software:

Measure

Supported Browsers:

Google Chrome 58 or higher (Recommended Browser)
Mozilla Firefox 34 or higher
Microsoft Edge 38 or higher
Microsoft Internet Explorer Ver. 11

In order to configure Web ViewPoint Enterprise to work with DSM/ SCM, the user will need to first use IPSETUP to copy the Web ViewPoint Enterprise Software from the CD to the Server.

Once the Software is present on the Server, you will need to use the DSMSCM Planner Interface to “Receive” the Software into the Archive.

After this is done, you will need to proceed with normal DSM/ SCM operations to create a New Software Revision and the use of the “Build/ Apply” command from within DSM/ SCM to manage the newly received software.

For a detailed explanation of how to use DSM/ SCM and receive new software in DSM/ SCM, you can refer to the DSM/ SCM User’s Guide.

Access the most up-to-date documentation covering the Release history, Quick Install Guides and patches at www.idelji.com/news

Web ViewPoint Support: webviewpoint@hpe.com

We are determined to providing you with the best customer service possible. To improve the experience of our customers we offer Technical Support with many ways to connect through emails, virtual sessions & direct phone calls. If you have any questions or concerns please feel free to email us.Third-party Plug-ins

TBD.

TBD.

TBD.

TBD.