Web ViewPoint ASAP Plug-in User Guide Version 1.3 Part Number 528941-003 Abstract This manual describes the installation, configuration, and usage of Web ViewPoint ASAP Plug-in Version H01AAG (forward) on a HP NonStop™ system. Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.10 and all subsequent H-series RVUs, until otherwise indicated by its replacement publications.
Table of Contents Introduction................................................................................................................................ 3 1. Web ViewPoint ASAP Installation & Configuration .......................................... 4 1.1. Considerations and Requirements................................................................. 4 1.1.1. General............................................................................................................. 4 1.2. Installation .......
Introduction Web ViewPoint ASAP (WASAP) is a thin web-based interface to HP’s ASAP (Availability Stats and Performance) software. (ASAP allows monitoring the availability and performance of system objects, subsystem domains and application domains.) WASAP is a plug-in product to Web ViewPoint, and therefore requires that Web ViewPoint be installed and operational prior to attempting an install and activation of the plug-in.
1. Web ViewPoint ASAP Installation & Configuration 1.1. Considerations and Requirements 1.1.1. General Hardware HP NonStop Server Software Microsoft Internet Explorer 6.0 and later Java Runtime Environment (JRE) 1.5.12 and later Web View Point – H01ABB and later (Note: Review README file for specifics and compatibility restraints.) Minimum OS Release H06.10 onward J06.03 onward (Note: Review SOFTDOCS for specifics and other important information.
1.2. Installation 1.2.1. Using the New PC-Based Wizard Installer 1. Start the installation wizard. It will ask if you have installed Web View Point. Click YES. 2. The next window gives you the choice of Single Resident or Multi Resident Installation. a. For Single Node select it and click on NEXT. i. The next window will require you to enter the information of the resident and the location.
b. For Multi Node, select it and click on Next. i. In the window below, enter the different node names and IP address/DNS names. Then enter the WVP Subvolume, the ASAP Subvolume( where you want to install ASAP) and the backup sub volume for ASAP. After all the required details are entered, click on APPLY. Then follow the rest of the steps from Step 3. 3. In the screen below you will need to enter the Group User Id and Password.
4. The wizard will check the process names and logon credentials. You will get the window below to verify the files names that will be imported from WVP. Verify the names and click on OK.
5. The wizard will verify the server series, Subvolume and then show the following popup to verify the TCP/IP program name that should be used. The default is TCPIP. Enter the appropriate value and click on OK. 6. In the next screen you will need to enter the environment name which you would like to use and the location of the ASAP database. You can enter multiple environments and databases in this screen. After entering the required values please click on OK.
7. The wizard will stop the process in the WVP, copy required files to the ASAP sub volume. 8. After copying all the files, the wizard will ask if the user wants to restart WVP and show the screen below.. 9. After Web ViewPoint has finished restarting, the wizard will ask if you want to upload your configurations. Uploading your configurations is a good idea, but not mandatory. Click Yes to upload your configurations. 10.
11. After this, the installation status will be displayed and if any errors occurred during the installation, the user will be notified of the same. 12. The following screen will confirm that uploading of configuration is complete. Please click on FINISH to complete the wizard installation of ASAP.
1.2.2. Using DSM/SCM or Manual Installation Web View Point ASAP can be installed using DSM/SCM tool or can be installed manually also. 1. 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. Once the IPSETUP program completes ensure that the files listed below have been transferred in the correct format and the file codes are correct. 2.
WASAP WSATMPAK WASPEVTS The following files have to be transferred in 'ASCII' Mode INSTWASP MAKEDCNF 2. Obey the Install file ‘INSTWVPA’ (read the following instructions first) 2.1. Set your working volume to $system.zwas (or to $volume.subvolume where you have transferred the files) 2.2. Issue ‘OBEY INSTWVPA’ Note: Web ViewPoint ASAP Version 1 generates a limited set of EMS events under SubSystem ID ZWSATMPL (SSID#278). Requiring your input, this performs the following: a.
INSWASAP also creates the data file, WASAPENV in the Web ViewPoint subvolume, with security ‘NNNN’.This file stores information about the configured environments and their locations. Figure showing the Manual installer user-interface. Back to top 2.3 Uninstall WASAP Method 1: WASAP (when installed manually) can be uninstalled by running UIWASAP from the WASAP installation sub volume. It removes WASAP from Web ViewPoint by updating the WVPCONF, WVPMENU, STRTWVP and STOPWVP files.
Method 2: If WASAP was installed using the Wizard, then to uninstall it the configuration files need to be changed manually as described below: Note: Please make sure Web ViewPoint is not running during installation/uninstall of Web ViewPoint ASAP. The following files needs to be changed to uninstall Web ViewPoint ASAP 1. WVPCONF - Remove Section [PLUGINOBJECT] OBJECTFILE $.WASAP1.WASAP OBJECTID OBJID_ZWASAP ......... ......... ASSIGN LICENSE-FILE, LICFILE 2.
Note: WASAP creates and uses a file called “WASAPENV” in the Web ViewPoint subvolume. This file is not deleted by the uninstaller and should be removed /purged manually.
3. Using Web ViewPoint ASAP 3.1 Activating Web ViewPoint ASAP When Web ViewPoint ASAP is first run through the Browser, it tries to activate itself by contacting the activation website over the internet. If you are a new user you will be prompted to enter your registration details. If you have an active Internet connection the activation will happen automatically, if not then the system will provide you with details and handle the registration and activation via email.
When WASAP starts for the first time, it loads the first environment in the list of environments (if there is more than one environment). Subsequently, WASAP remembers the environment last opened and opens that environment when started up the next time. The environment name is displayed in the top left side of the screen.
3. 4. 5. 6. 7. 8. 9. Low use Medium Use High Use Warning Critical Down Questionable Object Object Object Object Object Object Object utilization is low utilization medium utilization high is warning is critical is down is questionable Expanding a System/node shows all the Entities within that system. These Entities are marked with icons similar to the above ones, representing their respective states.
display order of other attributes is determined by the objectives (rank) defined for that particular entity, such that the ranked attributes (if any) appear before the unranked attributes. One cell from each row of data has a state icon to represent the highest state amongst all State Pair Attributes of that row. The tabular data is bi-directionally sortable on any of the columns.
Viewing Object History WASAP allows you to view the Object History for a selected object. You can view the last 5, 10, 15 or 20 collections for the selected object. To view historical data for a row of data, you need to click anywhere on the row. This brings up a popup menu giving the option of selecting between 5, 10, 15 and 20 collections. On selecting one of these options, a new window displays the history for that row in tabular format.
Switching Environments At the time of installing WASAP, the user has the option of specifying upto 20 ASAP environments to monitor. When started from the menu, WASAP loads the default or the last selected environment. You can switch between environments icon in the toolbar. Clicking this icon by clicking on the Change Environment brings up a popup window that shows a dropdown with all available environments.
5 Appendix A. Support Support for Web ViewPoint is available through HP's 24-hour Global Mission Critical Support Centers (GMCSC) throughout the world. In the U.S. call 1-800-255-5010. International numbers see pages 5 through 7 of: http://h20195.www2.hp.com/V2/GetPDF.aspx/c02083951.pdf B. Event Messages This section lists all EMS Events that can be generated specifically from the WASAP application conditions and processing. WASAP EMS SSID: TANDEM.278 or TANDEM.
failed. For backup process, recovery will depend on the specific Guardian error returned. For e.g. Error 2 can be recovered from by providing a valid process handle. WVPASAP 103 : Decompose Error: Relating to function or activity: Primary or backup TERMMAN, SPMON, WASAP or SHUTWAS process trying to retrieve process information from the process handle. Cause: Occurs on the “PROCESSHANDLE_DECOMPOSE_” Guardian procedure call.
WVPASAP 113 : WRITEREADX error : Relating to function or activity: Unable to write to a given process. Cause: The Guardian Procedure call WRITEREADX failed to complete communication with the process. The process may not be running or an invalid buffer or count is specified in the WRITEREADX Guardian Call. Please refer to the Guardian Procedure Manual for a better description of the values returned by WRITEX.
Relating to function or activity: Reading from a file to access contents. Cause: Occurs on the “READX” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This error condition could occur due to various reasons, for e.g. the operation timed out (Error 40). Effect: If the error occurs on the SA Host program, the daily database updates or the one-time loads will not be completed.
WVPASAP 551 TM Primary: Exiting, Limit number of environments to 20. Relating to function or activity: Number of environments specified in STRTWVP file. Cause: The total number of environments configured in the STRTWVP file on the WVP sub volume is more than the allowed maximum (20). Effect: The terminal manager process - TERMMAN will shut down and WASAP will not be accessible. Recovery: Edit the STRTWVP file to include less than or equal to 20 environment(s).
Effect: TERMMAN will shutdown and terminals to issue SSG commands will not be available for SPMON and WASAP processes. Recovery: Restart WASAP WVPASAP 556 TM Primary SSGCheck: Failed Security Setting for ASAP. WASAP will function only for user that started Web ViewPoint. Relating to function or activity: SSG SECURE command issued by the TERMMAN process to configure ASAP for use by all users. Cause: Security permissions don’t permit ASAP to be used by all the users.
Primary : Non-IDEL message received Relating to function or activity: Communicating with the SPM process. Cause: An unrecognized/irrelevant message was transmitted/ received while communicating with the SPM process. Effect: Communication with SPM process would not be complete and SPMON won’t work as expected. Recovery: N/A WVPASAP 561 : Parser Error Relating to function or activity: Getting all the entities configured in the EDL.
WVPASAP 565 WASAP: Attribute cannot be displayed Relating to function or activity: Retrieving an entity’s configured attributes ranks. Cause: Occurs when the all the attribute ranks stored in the DISPCONF file previously don’t match the attribute ranks obtained for the current interval. Effect: Rank map of attributes for that particular entity cannot be displayed. Recovery: N/A.
