HP NonStop POS Transaction Analyzer User and Installation Guide Part number: 544409-003 Third edition: 07/2009
Legal notices Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Preface Before You Begin ..................................................................................................................................... 6 Who Should Read This Guide ................................................................................................................... 6 Goals of Documentation ........................................................................................................................... 6 Organization ..................................
-3 4-4 4-5 4-6 Drill-Down on Latest Transactions ................................................................................................... 66 Viewing Violations....................................................................................................................... 68 Viewing Recent/Past Data ............................................................................................................ 69 Creating Thresholds ............................................................
7-10-3 Importing/Restoring Data to SQL Server.............................................................................. 140 7-11 User Not Able to View Default POS/TA Web Page ....................................................................... 141 7-12 User Not Able to Connect to POS/TA Database ............................................................................ 142 7-13 POS/TA Web Page Not Displaying Any Data...............................................................................
Preface HP NonStop POS Transaction Analyzer (POS/TA) provides continuous and real-time monitoring of POS transactions. Before You Begin As the administrator who administers the POS/TA, you should be familiar with the POS environment, HP NonStop Servers, network protocols, Microsoft SQL Server, Microsoft IIS, client/server architecture and basic Microsoft Windows navigation.
Chapter Name Description Appendix G. Threshold Expressions Provides information on Boolean expressions to identify when a threshold is in violation. Appendix H. Transaction Filter Expressions Provides information on the Boolean expressions to filter the transactions that are used to evaluate thresholds. Appendix I. Substitution Parameters Lists the available substitution parameters along with description. Appendix J.
1 HP NonStop POS Transaction Analyzer: Overview This chapter lists the main features of HP NonStop POS Transaction Analyzer (POS/TA) and highlights the advantages this software offers. 1-1 What is HP NonStop POS Transaction Analyzer? HP NonStop POS Transaction Analyzer (POS/TA) is a best-of-breed solution designed to ensure continuous monitoring and management of POS (Point-of-Sale) transaction environments by detecting problems before they occur.
• Continuous and real-time monitoring of POS transactions • Real-Time transfer of POS Transaction Data to the SQL Server • Guarantee delivery of transaction data to the SQL Server • Real-time response code analysis • Real-time calculation of transaction times • Complete breakdown by Nodes, FIID, Interchange, and Retailer for Transaction time and volume • Identify traffic on all resource nodes defined in the targeted logical network • Live Report Groups offer instant snapshots of Key Performan
1-3 Features & Benefits Real-Time Transaction Monitoring The advantages of financial institutions employing real-time transaction monitoring are endless. Examples include on-the-spot customer service, the ability to address technical issues instantly, and the capability to detect fraud as it occurs. POS/TA processes transaction logs in real-time to provide statistics, such as Approved and Denied Transactions.
Pin-Point Impact of Outages POS/TA provides the opportunity of tracking the effect of outages on your business in real-time as and when they occur. You can immediately see when and where a problem occurs on your POS network, identify the root-cause and take steps to rectify the problem before it affects your customers. This helps you to deliver across-the-board extreme customer service.
1-4 POS/TA Architecture POS/TA provides details about POS transactions processed and recorded in the POS transaction log (PTLF) file. It identifies traffic on all resource nodes defined in the targeted logical networks, with data collection triggered by disk-write I/O on the PTLF.
1-4-1 POS/TA Backend Components The POS/TA installation on the HP NonStop Server installs the following components on the backend. • $PTPnn $PTPnn is the POS/TA Record collector component installed on the HP NonStop Server. It collects and transfers data from the POS transaction log file (PTLF) to a temporary database called PTLFDB. A single NonStop backend might have multiple $PTPnn processes, one for each LNET configured within the environment.
1-4-2 POS/TA Front-End Components The POS/TA consists of the following components installed on the front-end. • POS/TA Database The POS/TA Database (POSDB) is installed on a system which has SQL Server installed on it. It can reside on an independent system or coexist with other POS/TA components. • POS/TA Application Server The POS/TA Application Server includes various POS/TA services, for example: POSLOGGER Service, POSSTATGEN Service, POSMON Service and Elink.
2 Installing HP NonStop POS Transaction Analyzer This section covers the procedure to install POS/TA on the Microsoft Windows and on the POS HP NonStop environment on HP NonStop Server. 2-1 Configuration Requirements and Dependencies 2-1-1 HP NonStop Server • Any NonStop System – S Series or NS Integrity • Software Release from G06 to H06.
2-2 Contents of Installation Exe POS/TA Database The POSTA_DatabaseInstallation.exe contains components necessary to install POS/TA Database on a Windows workstation. The self-extracting exe file includes the following: POS Database For collecting the transaction details logged in the POS transaction log file. HP NonStop POS Transaction Analyzer User and Installation Guide Contains detailed installation and usage information for POS/TA. POS/TA Application Server The POSTA_ApplicationServerInstallation.
2-3 Prerequisites Before installing POS/TA, ensure that the following tasks have been accomplished: 1. The user installing POS/TA must have Administrator rights/privileges on the system. 2. Before starting the installation, it is recommended that you exit from any other Windows programs that are running. 3.
15. User IDs for installing POS/TA on a NonStop Server need to have FUP CREATE and READ access rights to the BASE24 files (LCONF). 16. Product License Key to run the POS/TA components on the NonStop Server.
2-4 Installing POS/TA on Windows 2-4-1 Overview Installing POS/TA involves installing the following components in the same sequence. • POS/TA Database: This involves installing the POS/TA database, remotely or locally. • POS/TA Application Server: This involves installing the following applications: Elink, POS/TA Logger, POS/Maintain, Stat Generator, Stat Adjustment, Recovery, Command & Control and Monitoring. This also includes a purge service that deletes old records from the database.
Figure 2-2 Adding the Log on as a service Policy to a User • Domain: Create a user on Domain Server having “Log on as a service" right. Make sure that the password is not blank. SQL Server Authentication Mode Create a user with Database Creator rights on the SQL Server.
2-4-3 Installing POS/TA Database Step A: Starting Up Double-click on the POSTA_DatabaseInstallation.exe to start the installation process. Install Shield prepares the Setup program for use and the POS Transaction Analyzer Database Setup Welcome screen is displayed. Click on the Next button to continue with POS/TA Database Setup. Step B: License Agreement The License Agreement screen is displayed.
Step C: Destination Location Figure 2-6 POS Transaction Analyzer Database Setup Choose Destination Location Screen The Choose Destination Location screen shows the path of the folder where POS/TA Database files will be installed by default. Use the Browse button to specify a directory other than the default. To move on with the installation process, click on the Next button.
Step E: Option Type The Select Option Type screen is displayed. Select the database option that best suits your needs. Choosing the Create POSDB Database and Tables option will create POSDB database and tables. You need to have the Database Creator rights for creating the database and tables. Choosing the Create only POSDB Tables option will create only the POSDB tables. It is assumed that the POSDB database has been created manually. You need to have the POSDB database db_owner and public rights.
Step G: Confirm Entries and Copy Files Figure 2-10 POS Transaction Analyzer Database Check Setup Information Screen The Check Setup Information screen displays the current settings, which have been selected so far. In case you want to change any of the settings, you can do so by going back to the particular screen before you start copying the program files. NOTE: You should check the location of the directory where POS/TA Database is to be installed.
Step I: Setup Complete Figure 2-12 POS Transaction Analyzer Database Setup Completed Screen The POS Transaction Analyzer Database Setup Completed screen denotes the completion of the Setup process. Click on the Finish button to complete the Setup process. This completes the POS/TA Database Setup process.
2-4-4 Installing POS/TA Application Server Step A: Starting Up Double-click on the POSTA_ApplicationServerInstallation.exe to start the installation process. The POS Transaction Analyzer Application Server message box is displayed, which prompts you to make sure that the POS/TA Database is installed on the network. Figure 2-13 POS Transaction Analyzer Application Server Message Box Click on the OK button to continue.
Step B: License Agreement Screen The License Agreement screen is displayed. Figure 2-15 POS Transaction Analyzer Application Server Setup License Agreement Screen Review the software license agreement and click on the Yes button to continue with the installation. Figure 2-16 POS Transaction Analyzer Application Server Setup Type Screen The Setup Type screen prompts you to select the type of setup required. Most users are recommended to use the Complete setup type.
Step D: Database Server Figure 2-17 POS Transaction Analyzer Application Server Setup Database Server Screen The Database Server screen is displayed. Select the Database Server where the POS Transaction Analyzer Database POSDB exists using the Database Server field. You can also browse for the Database Server using the Browse button. The default port used by the SQL Server is 1433.
Step F: Transaction Data Retention Period Configuration Figure 2-19 POS Transaction Analyzer Application Server Transaction Data Retention Period Configuration Step G: Confirm Entries and Copy Files Figure 2-20 POS Transaction Analyzer Application Server Setup Check Setup Information Screen The next screen, Check Setup Information, displays the current settings, which have been selected so far.
Step H: Elink Configuration – HP NonStop Configuration Figure 2-21 POS Transaction Analyzer Application Server Setup Elink Configuration Screen The Elink Configuration screen is displayed. Enter the HP NonStop Node name and IP Address in the respective fields and click on the Next button to continue. Step I: Elink Configuration – POS/TA Port Figure 2-22 POS Transaction Analyzer Application Server Setup Elink Configuration Screen The Elink Configuration screen is displayed again.
Step J: Adding More NonStop Nodes Figure 2-23 POS Transaction Analyzer Application Server Question Box Next, Setup confirms if more HP NonStop nodes are to be added. To add more nodes click on the Yes button. To continue without adding more nodes, click on the No button. Step K: Rebooting the System It is recommended to reboot the system to complete the installation. The POS Transaction Analyzer Application Server Installation message box is displayed. Click on the OK button to continue.
Step M: POS/TA Configuration Client Figure 2-26 POS/TA Configuration Client Screen The POS/TA Configuration Client screen is displayed. It lists the component and configuration categories. This program allows you to edit the configuration settings of various POS/TA components. Click on the Save button to save the settings. The POS/TA Configuration Client message box is displayed. Figure 2-27 POS/TA Configuration Client Message box Click on the OK button.
Step N: Create TelnetScript file POS/TA Application Server creates a TelnetScript sample file (NodeName_TelnetScript ) in the bin folder where POS/TA files are stored by default. The file contains the information for each node. A sample file has been provided below for your reference.
2-4-5 Installing POS/TA Web Server Step A: Starting Up Double-click on the POSTA_WebServerInstallation.exe to start the installation process. Install Shield prepares the Setup program for use and the POS Transaction Analyzer Web Server message box is displayed. Figure 2-28 POS Transaction Analyzer Web Server Message Box Before installing POS/TA Web Server make sure that the POS/TA Database and POS/TA Application Server are installed on the network.
Step D: License Agreement The License Agreement screen is displayed. Figure 2-31 POS Transaction Analyzer Web Server Setup License Agreement Screen Review the software license agreement and click on the Yes button to continue with the installation. Figure 2-32 POS Transaction Analyzer Web Server Setup Choose Destination Location Screen The Choose Destination Location screen shows the path of the folder where POS/TA Web Server files will be installed by default.
Step F: Database Server Figure 2-33 POS Transaction Analyzer Web Server Setup Database Server Screen The Database Server screen is displayed. Select the Database Server where the POS Transaction Analyzer Database POSDB exists using the Database Server field. You can also browse for the Database Server using the Browse button. The default port used by the SQL Server is 1433.
Step H: Confirm Entries and Copy Files Figure 2-35 POS Transaction Analyzer Web Server Setup Check Setup Information Screen NOTE: You should check the location of the directory where POS/TA Web Server is to be installed. In case the location has to be changed after installation, you will have to reinstall the software. Click on the Next button to continue. The program begins copying files to the directory specified.
Step K: Setup Completed Figure 2-38 POS Transaction Analyzer Web Server Setup Completed Screen The POS Transaction Analyzer Web Server Setup Completed screen denotes the completion of the Setup process. Click on the Finish button to complete the Setup process.
2-5 Upgrading POS/TA to Version 2.0 This section explains the procedure to upgrade from a previous version of POS/TA version 2.0. 1. Stop the Elink Services and the POS/TA Services using the Start->Programs->HP SST->POS TA->Application Server->Stop POS TA Agents option. 2. Take a backup of the POS/TA database on the SQL Server. 3. To upgrade the POS/TA Database, run the POSTAUPGRADE.sql database upgrade script using the SQL Analyzer. 4.
5. The next step is to upgrade the POS/TA Application Server. a. Run the POS/TA Application server installation exe. The POS Transaction Analyzer Application Server message box is displayed with the information that before continuing with the upgrade, it is recommended to take a backup of the INI files and close all POS/TA Application server components running on the system. Figure 2-39 POS Transaction Analyzer Application Server Message Box Click on the OK button to continue. b.
c. The Database Server screen is displayed. Select the Database Server where the POS Transaction Analyzer Database POSDB exists using the Database Server field. You can also browse for the Database Server using the Browse button. The default port used by the SQL Server is 1433. In case the SQL Server is listening on a port other than the default port, specify the information in the , format.
e. The Transaction Data Retention Period Configuration screen is displayed. Enter the transaction data retention period in days in the Transaction Data Retention Period Day(s) box. The default value is 7. The installation will take the default values for Alerts and Stat data retention periods. These values can be modified after the installation, if required. Figure 2-43 POS Transaction Analyzer Application Server transaction Data Retention Period Configuration Click on the Next button to continue. f.
g. The POS Transaction Analyzer Application Server Update Completed screen denotes the completion of the upgrade process. Click on the Finish button to complete the process. h. It is recommended to reboot the system for proper functioning. The POS Transaction Analyzer Application Server Maintenance message box is displayed. Figure 2-46 POS Transaction Analyzer Application Server Maintenance Message Box Click on the OK button to continue. NOTE: Clicking on the OK button does NOT reboot the system.
b. The POS Transaction Analyzer Web Server Setup Welcome screen is displayed with the information that the wizard will update the installed POS/TA Web Server version 1.5 to version 2.0. Click on the Next button to continue. Figure 2-48 POS Transaction Analyzer Web Server Setup Welcome Screen c. The Database Server screen is displayed. Select the Database Server where the POS Transaction Analyzer Database POSDB exists using the Database Server field.
d. The POS/TA Application Server Configuration screen is displayed. Enter the system Name or the IP address of the PC where POS/TA Application Server is installed in the IP Address field. Click on the Next button to continue. Figure 2-50 POS Transaction Analyzer Web Server Setup Application Server Configuration Screen e. The POS Transaction Analyzer Web Server Update Completed screen denotes the completion of the upgrade process. Click on the Finish button to complete the process.
3 Getting Started This chapter details the steps for starting and checking status of various POS/TA components. 3-1 Starting POS/TA on NonStop Server Use the following command to start the POS/TA on the HP NonStop Server. $prod.test 85> RUN STRTPTLF Use the RUN STOPPTLF command to stop the POS/TA backend components. 3-2 Starting POS/TA Application Server on Windows The next step is to start the Elink Services and the POS/TA Services (to collect the data into the POS/TA database).
3-4 Accessing POS/TA Web Server POS/TA provides platform and location independence by giving the ability to monitor POS transactions through a web-browser like the Microsoft Internet Explorer. NOTE: If you are accessing POS/TA web page using Microsoft Internet Explorer, you must turn off the popup blocker feature to allow the application to function properly. To access the POS/TA web page click on Start->Programs->HP SST->POS TA->Web Server->Transaction WebPage option.
Associated with each logon is a profile, which determines the information a user can view. The admin logon has special privileges, and can edit the profiles and passwords of other users. You need to enter the user name and the password in the User Name and Password fields respectively, to access the POS Transaction Analyzer web page. NOTE: The default administrator User Name is admin and Password is posadmin. You can change the password by editing the Admin profile.
3-5 Admin Privileges NOTE: This function can only be accessed by the POS/TA Administrator or a user with Admin privileges. To access the Admin dialog box, click on the Admin option in the POS/TA web page Tools menu. Figure 3-2 POS/TA Tools Menu Admin Option • Add a new user • Modify properties and privileges of a user • Delete a user Getting Started This displays the Admin dialog box.
3-5-1 Adding a New User 1. Click on the Admin option in the POS Transaction Analyzer web page Tools menu. 2. This displays the Admin dialog box. The Create a New User area allows you to create a new user. Enter the new user name in the User Name field. Figure 3-3 Admin Dialog Box 3. Enter the password for the specified user in the Password field. 4. Click on the Add User button. 5. This will add the new user in the Existing Users list.
3-5-2 Modifying a User Follow the steps given below to change the password and privileges for an existing user: 1. Click on the Admin option in the POS Transaction Analyzer web page Tools menu. This displays the Admin dialog box. Getting Started Figure 3-4 Admin Dialog Box 2. Select the user whose password is to be modified from the Existing Users list. 3. If you want to specify a new password for the user, enter the new password in the Set Password to field. 4.
5. Select the required privileges from the Set Privileges list. The following privileges can be assigned: 6. • Admin Privileges: Assign administrator privileges like adding, modifying and deleting users. • Create or Modify Views: Assign the rights to create/modify views. • Create or Modify Thresholds: Assign the rights to create/modify thresholds. • View Thresholds: Assign the rights to view thresholds. • View Alerts: Assign the rights to view Alerts.
4 Working with HP NonStop POS Transaction Analyzer 4-1 POS/TA Interface Figure 4-1 POS/TA Web Interface POS/TA web interface displays the transaction details at the following entity levels. The data displayed can be sorted by clicking on the column headers.
Node The Node entity in the POS Transaction Analyzer page displays the POS transaction information for the various configured HP NonStop nodes. Logical Network The Logical Network entity in the POS Transaction Analyzer page displays the POS transaction information for the various configured logical networks. Issuer FIID The Issuer FIID entity in the POS Transaction Analyzer window displays the POS transaction details at the Issuer FIID level.
4-2 Configuring Views The POS/TA is equipped with a pre-defined Live view. You will be able to view the transaction information of all the entities right after you login to the POS/TA web interface. You can also create your own views and panels depending on your business specific requirements.
3. Enter the name of the view in the dialog box click on the OK button. The view will be added in the Current Views box. Figure 4-4 My Views Dialog Box with a View Added 4. Click on the Save Changes button to save the changes. NOTE: Clicking on the Save Changes button creates an empty view. To add information to the view, you will have to add panels to the views. All the views created will be listed in the drop-down box next to the Configure Views link in the main POS Transaction Analyzer page.
4-2-2 Creating Panels for a View Once you create views, you need to add panels to it. The panels define the entity types that would be displayed in the view. Perform the following steps to create panels for a view: 1. Click on the Configure Views link on the main POS Transaction Analyzer web page to access the My Views dialog box. 2. Select the view to add panels using the Current Views list. 3. Click on the View Panels button. Figure 4-5 View Panels Button in My Views Dialog Box 4.
5. Clicking on the New Panel button displays the corresponding dialog box. Enter the name of the new panel in the Panel Name box. Select the desired entity to be displayed in the panel from the Entity Type list. Click on the OK button to close the New Panel dialog box. Figure 4-7 New Panel Dialog Box 6. The View Panels dialog box will be displayed with the new panel name added to the Panels in this view box. Repeat the step 3 to step 5 to add more panels to the view.
4-2-3 Renaming a View Perform the following steps to rename an existing view: 1. Click on the Configure Views link in the main POS Transaction Analyzer web page to access the My Views dialog box. 2. Select the view to be renamed from the Current Views box and click on the Rename button. Figure 4-9 My Views Dialog Box 3. The Explorer User Prompt dialog box is displayed. Figure 4-10 Explorer User Prompt Dialog Box Enter the new name of the view and click on the OK button.
4-2-4 Deleting a View Perform the following steps to delete an existing view: 1. Click on the Configure Views link on the POS Transaction Analyzer main page to access the My Views dialog box. 2. Select the view to be deleted from the Current Views box and click on the Delete button. Figure 4-11 My Views Dialog Box 3. A confirmation box is displayed. Click on the OK button to delete the selected view. Figure 4-12 Microsoft Internet Explorer Confirmation Box 4.
4-2-5 Changing View Order The configured views are listed in the drop-down list box to the left of the Configure Views link in the POS Transaction Analyzer page. Figure 4-13 List of Views Created in the Drop-Down Box To change the order of views displayed in the drop-down box perform the following steps. 1. Click on the Configure Views link to access the My Views dialog box. 2. Use the Move Up and Move Down buttons to change the order of views. 3.
4-2-6 Renaming a Panel Perform the following steps to rename an existing panel: 1. Click on the Configure Views link to access the My Views dialog box. 2. Select the view whose panel is to be renamed from the Current Views box and click on the View Panels button to display the View Panels dialog box. Figure 4-15 View Panels Dialog Box 3. Select the panel to be renamed from the Panels in this view box and click on the Rename button. The Explorer User Prompt dialog box is displayed.
4-2-7 Deleting a Panel from the View Perform the following steps to delete an existing panel: 1. Click on the Configure Views link to access the My Views dialog box. 2. Select the view, from which panel(s) is to be deleted, from the Current Views box and click on the View Panels button to display the corresponding dialog box. 3. Select the panel to be deleted from the Panels in this view box and click on the Delete button. A confirmation box is displayed.
4-2-9 Changing Panel Options POS/TA allows you to select the columns to be displayed for the selected entity in a panel. You can also customize some of the display setting for a view. To change the panels options perform the following steps. 1. Click on the Configure Views link to access the My Views dialog box. 2. Select the view whose display setting are to be changed from the Current Views box and click on the View Panels button to display the View Panels dialog box. 3.
• Entity Group This option enables you to select the Entity Group defined for the entity and displays the grouped entities in a view. • Available Columns This option enables you to select the columns to be displayed in the selected entity view. Select the columns from the list and click on the Add button to add the column to the Selected Columns list. The out-of-the-box available columns in the list which can be added are as follows: Column Name Description Name Name of the Entity.
4-3 Drill-Down on Latest Transactions POS/TA provides you with the ability to drill-down and view details of latest transactions for the particular entity. The drill-down feature displays the details of the last ten transactions for the selected entity. Perform the following steps to view the last ten transactions for an entity. 1. Click on the entity name in the Name column. This will display the View Latest Transactions hyperlink for the selected entity.
The Latest Transactions window displays the following details: Table 4-2 Latest Transactions Column Name Description POS Device Time Date and time when the transaction occurred Trans. Type Transaction type Resp. Code Response code of the transaction Revl. Code Reversal code of the transaction Amount Amount associated with the transaction Bin Issuer BIN associated with the transaction.
4-4 Viewing Violations POS/TA provides the ability to log violations on thresholds, depending on the option(s) selected in the Alert Logging area in the Threshold Detail dialog box. You have an option to: • Log alerts to POS/TA database: Viewed using the POS/TA GUI • Log events to Windows NT Event log: Viewed using the Windows NT Event Viewer • Log events to NonStop Node This section provides details on how to view violations logged to the POS/TA database.
4-5 Viewing Recent/Past Data POS/TA provides you with the ability to switch to a specific date and time and view the transaction details. You can specify the data retention time in the database during installation. To view data for a particular date and time, perform the following steps. 1. Click on the Go to Date/Time link. This will display the Select the date/time to position the view box in the POS Transaction Analyzer web page.
2. Select the month, date, year, hour and minute for which you want the data in the Select the date/time to position the view box. Click on the Go button to get the information. The data for the selected date and time will be displayed. Figure 4-23 Selected Date/Time Information Displayed You can scroll back and forth within an interval of 5 minutes to view specific information. To scroll back and forward, click on or icons, respectively.
4-6 Creating Thresholds POS/TA provides you with the ability to create thresholds to ensure nonstop monitoring of POS transactions. Creating a threshold defines the acceptable operational values for specific transactions. The POS/TA Thresholds page enables you to create, modify and delete thresholds. 4-6-1 Creating New Thresholds Perform the following steps to create thresholds: 1. Click on the Tools link on the POS Transaction Analyzer web page. 2.
4. The Threshold Details page is displayed. Figure 4-26 Threshold Details Page Enter the threshold name in the Threshold Name field. 5. The Severity box allows you to set the severity levels as Information, which is the default severity level, Warning, Minor, Major and Critical. Specify the Severity level using the Severity box. 6. Specify the security of threshold in the Security box. The options available are: Private, Read Access to Everyone and Full Access to Everyone. 7.
9. Define a SQL function as a condition in the Active Condition field. The SQL function will return the Boolean values (0/1). If the Monitoring check-box is selected and the Active condition holds true, the threshold will violate. For example, for getApproval()=1, if the function returns 1 and the value defined is also 1, the condition is activated. NOTE: The SQL function will consider all the alert formatting parameters as input parameters. 10.
Figure 4-27 POS/TA New Thresholds Added NOTE: The Thresholds to display drop-down list in the Thresholds web page gives you the option to view all the thresholds created by the current user or to view all the thresholds created by all the users.
4-6-2 Modifying an Existing Threshold Perform the following steps to modify an existing Threshold: 1. Click on the Thresholds option in the Tools menu to access the Thresholds page. This page displays a list of existing thresholds depending on the option selected in the Thresholds to display drop-down list. 2. Click on the Modify link corresponding to the threshold that you want to modify. The Threshold Details page is displayed. 3. Make the required changes and click on the Apply button.
4-7 Acknowledging Alerts POS/TA logs an alert message whenever a configured threshold condition is met. The software provides you with the ability to acknowledge alerts, enabling you to close alerts which have been resolved or the ones you prefer to ignore. This function can be performed using the Alerts option in the POS/TA Tools menu. Perform the following steps to acknowledge alerts: 1. Click on the Alerts option in the Tools menu.
NOTE: Alerts displays 50 alerts/page. You can use the the previous alerts, use the hyperlink to list the next 50 alerts. To view link. 3. Select the check boxes corresponding to the alerts which you want to acknowledge. To select all the alerts click on the Check All button at the bottom of the page. You can use the Uncheck All button to deselect all the check boxes. 4. Click on the Acknowledge Checked Alerts button to acknowledge the selected alerts. 5.
4-8 Create a Query POS/TA provides you with the ability to query on the transactions based on specified criteria. Perform the following steps to start a query. 1. Click on the Query option in the Tools menu. Figure 4-30 POS Transaction Analyzer Tools Menu with the Query Option 2. The Query page is displayed with various fields. Figure 4-31 Query Page Select the Start Time and Interval values in the corresponding fields. To specify the query interval as 24 hours, click on the Select All Day button. 3.
4. You can use the Edit Display Fields link to select the fields from the selected Query table, which will be used for specifying the filtering criteria. Clicking on the link displays the Query Display Fields page. By default five fields will be displayed in the selected list box after adding a new table. Figure 4-32 Query Display Fields Page 5. Select the field(s) to be displayed from the available fields box and move to the selected fields box using the > and >> buttons.
Defining a Standard Filter a. Select the Conditional Operator using the corresponding drop-down box. b. The next step is to select the Field on which the condition has to be applied. The fields available in the drop-down list depend on the Query Table selected for the query. c. Use the Operator box to select the operator. The options available are '=' (Equal to) and '!=' (Not Equal to). d. Specify the Value in the corresponding box.
4-8-1 Access Query Page from External Link POS/TA also provides add on functionality for accessing the query page directly from an external link. Follow the steps given below to access the query page from an external link: 1. Create a filter using the Query page and assign a name and filter condition to the new filter. For example, creating a Test filter with the following condition: accttype like %1% NOTE: The filter condition should be defined only in the Custom Filter. 2.
4-9 Checking the Node Status Clicking on the NonStop Node Status option in the POS Transaction Analyzer Tools menu displays the NonStop Node Status window. Figure 4-35 NonStop Node Status The NonStop Node Status window displays the HP NonStop Node configuration added during the time of POS/TA installation along with the Date/Time information of the last transaction on the node and its status. The following status are available: • Online: The node is online. • Offline: The node is offline.
4-10 Import Entities POS/TA provides the ability to import your business specific entities to its environment. This feature can be used in scenarios where the names of certain entities have been modified or new entities have been added. The feature can be accessed using the Import Entities option in the POS Transaction Analyzer web page Tools menu. Figure 4-36 POS Transaction Analyzer Tools Menu with the Import Entities Option Follow the steps listed to import Entities: 1.
2. 3. 4. Specify the following information in the displayed dialog box: • Entity Type: The Options available are Acquirer FIID, Bin, Issuer FIID, Logical Network, Node, Response Code, Retailer FIID, Transaction Type and Authorizer. • CSV File: The path for the CSV file with the entity information. The file size should be less than 4 MB (4096 KB). • Separator: The separator used in the CSV file. • Column Name Header: Check this box in case the CSV file has column headers.
5. Click on the Submit button to continue importing Entities for the selected Entity Type. The Import Entities dialog box is displayed with the status of the import. Figure 4-39 Import Entities Dialog box Working with HP NonStop POS Transaction Analyzer This completes the procedure to Import Entities.
4-11 Manage Entities POS/TA provides the ability to modify entity configurations for a particular entity type. To manage entities use the Manage Entities option in the POS Transaction Analyzer web page Tools menu. Figure 4-40 POS Transaction Analyzer Tools Menu with the Manage Entities Option The Manage Entities page is displayed. Select the entity type from the Entitytypes drop-down menu and click on the Extract button.
Clicking on the Extract button displays the Manage Entities page with the list of entities available for the selected Entity Type. Figure 4-42 Manage Entities Page NOTE: You can change the number of entities listed by modifying the “EntitiesMaxResultPages" parameter in the Web Config file. The parameter takes values in the range of 1 to 500. Default value is 15. NOTE: You can use the hyperlink to list the next 15 entities.
POS/TA provides parameters to calculate statistics for entities. The list of entities depends upon the entity type selected. To edit the entity configurations, click on the Edit link. This enables the fields for editing. Figure 4-43 Manage Entities Page For an Entity, the following can be configured using the Manage Entities page. • Entity Description: Description for the Entity • Options: • Stat: Select the check box to calculate the statistics for the entity.
4-12 Manage Entity Types POS/TA provides the ability to configure the settings of Entity Types. To manage entity types use the Manage Entity Types option in the POS Transaction Analyzer web page Tools menu. Figure 4-44 POS Transaction Analyzer Tools Menu with the Manage Entity Types Option This displays the Manage Entity Types page. The following functions can be performed using the page.
Click on the New link to create a new entity type. The New Entity Type screen is displayed. Figure 4-46 New Entity Type Screen Specify the following information: • Name: Name of the entity type. • Display Name: Display Name of the entity type. • Statistics and Monitoring options: Select the following options to calculate the bit parameters. • • Statistics: Select the check box to calculate the statistics for the entity type.
Click on the Delete link to delete the selected entity type. Figure 4-47 Delete Entity Types Message Box Working with HP NonStop POS Transaction Analyzer Clicking on the Delete button displays a message box. Click on OK to confirm the deletion of the selected entity type. This will mark the selected entity type as deleted.
4-13 Import Owner FIIDs POS/TA provides the ability to import your business specific Owner FIIDs to its environment. This feature can be used in scenarios where the names of certain Owner FIIDs have been modified or new Owner FIIDs have been added. To import FIID’s access the Import Owner FIIDs option in the POS Transaction Analyzer web page Tools menu. Figure 4-48 POS Transaction Analyzer Tools Menu with the Import Owner FIIDs Option Follow the steps listed to Import Owner FIIDs: 1.
3. Click on the Extract button. To reset the fields in the dialog box, use the Reset button. 4. The information is extracted and displayed in the Import Entities page. The following fields are displayed: • FIID • FIID Name Select the values for the fields using the corresponding drop-down boxes. Select the Modify Existing check box in case you want to modify the existing values. Figure 4-50 Import Owner FIIDs Page 5. Click on the Submit button to continue importing Owner FIIDs.
4-14 Command and Control POS/TA provides a group of BESTATUS commands in order to check the HP NonStop status. The following commands can be run from the command prompt as well as the POS/TA user interface. • BESTATUS SYSTEM • BESTATUS COLL • BESTATUS COLL, DETAIL • BESTATUS SAF • BESTATUS RECOVERY • BESTATUS ALL To run the commands from the GUI, use the Command And Control option in the POS Transaction Analyzer web page Tools menu.
Select the command from the Select Command drop-down menu and the Node on which the command is to be executed using the Select Node drop-down box. This enables the Execute Command button. Figure 4-53 Execute BE Command Window Click on the Execute Command button to run the command. The command output is displayed in the Command Result area.
If the command has already been executed and the same command is executed again, the Last Execution Time is displayed. To view the result of the command last executed, click on the Display Last Executed Result button. Figure 4-55 Execute BE Command Window To execute the command again, click on the Execute Command button.
4-15 Adding Custom Fields in the Transaction Table Follow the steps listed below to add custom fields in the transaction table. 1. Make the following changes in the POS/TA backend. a. Specify the declaration and implementation specifications for the custom variable data in the “copyCustomData” function in the “USRPTLFC” file. b. Copy the variable data in the “txVarData” variable defined in the “copyCustomData” function. c. Specify the total length of the variable data in the “CUSTOM-DATA-LEN” parameter.
4-16 Missed Transaction Recovery POS/TA provides a method for recovering any missing transactions. This procedure involves configuration changes both on the HP NonStop Server and the Windows front-end environment. This topic provides information on how to configure recovery of missing transactions. Configuration Changes on the HP NonStop Server 1. Set the RECOVERY parameter to ON in the PTLFCONF file. 2.
Configuration Changes on the Windows Front-end Environment To configure POS/TA Windows environment for the recovery of missing transactions, you can follow any of the following two methods. Manually Configuring the .ini File Configure the following Operational parameters in the POSRecovery.ini file. This file is located the bin folder where POS/TA files are stored by default. • Nonstop Node: Name of the NonStop Node. For example: NODE1.
Delete Inactive File from Recovery POS/TA provides a method for deleting any missed/inactive file from the recovery session file (RECSPCTL). Following is the syntax to delete the inactive file. RUN RECVPTLF -Delete A sample output has been provided for your reference. RUN RECVPTLF -Delete \TAND1.$AUDIT.SSTPOS.PO081225 Volume \TAND1.$AUDIT.SSTCMN Volume \TAND1.$AUDIT.SSTPOS RUN \TAND1.$AUDIT.SSTCMN.sstdef add ADD DEFINE =ptlfdb, CLASS MAP, FILE $AUDIT.SSTPOS.
This chapter provides information on the reporting feature of POS/TA. 5-1 Reports Overview The POS/TA provides reports that allow you to evaluate your POS environment status and performance, hence keeping the POS network running at a maximum efficiency. It discovers the causes of problems and failure to comply with your SLA.
5-2 Getting Started with POS/TA Reports The reporting feature of POS/TA can be accessed using the Reports option in the POS Transaction Analyzer page Tools menu. Figure 5-1 POS Transaction Analyzer Tools Menu with the Reports Option This will display the Create Your Own Reports Group page if no groups have been configured. If you have already created Reports Group(s), the View Reports Group page will be displayed. Figure 5-2 Create Your Own Reports Group Page You can perform the following tasks. 1.
POS/TA provides the ability to create groups of frequently used reports to make the reporting process more efficient. 5-3-1 Creating a Reports Group Perform the following steps to create a Reports Group. 1. Click on the Reports option in the Tools menu in the POS Transaction Analyzer web page. 2. This will display the Create Your Own Reports Group page if no groups have been configured. If you have already created Reports Group(s), the View Reports Group page will be displayed.
5-3-2 Modifying a Reports Group Perform the following steps to modify an existing Reports Group. 1. Click on the Reports option in the POS Transaction Analyzer Tools menu. This displays the View Reports Group page. 2. Select the Modify option in the Reports Group menu to modify a Reports Group. Figure 5-4 Reports Group Menu 3. The Modify Reports Group page is displayed. Select the Reports Group you want to modify using the Reports Group field. Figure 5-5 Modify Reports Group Page 4.
Perform the following steps to view a Reports Group. 1. Click on the Reports option in the Tools menu. This displays the View Reports Group page. Figure 5-6: View Reports Group Page 2. In the View Reports Group area, select the group to be viewed using the Reports Group drop-down box. 3. The Choose settings for Reports Group area enables you to specify the following parameters for generating the reports in the group. a.
h. Week From / Week To: Specify the week interval for which the reports are to be generated. This option is available if the Weekly option is selected in the Report Type field. i. 4. Month From /Month To: This option is available if the Monthly option is selected in the Report Type field. Specify the interval for which the reports are to be generated. Click on the Submit button to view the Reports Group.
Perform the following steps to delete a Reports Group. 1. Click on the Reports option in the Tools menu. 2. In the displayed View Reports Group page click on the Delete option in the Reports Group menu. 3. The Delete Reports Group page is displayed. Select the Reports Group to be deleted using the Reports Group drop-down box. Figure 5-8 Delete Reports Group Page 4. Click on the Delete button. 5. A confirmation box is displayed. Click on the OK button to continue with the deletion process.
5-4 Individual Reports 5-4-1 Introduction The Individual Reports link can be used to access the individual reports, which are displayed in the View Individual Report page. Figure 5-10 View Individual Report Page To view a report, select the report from the Select Report box and specify the parameters using the Choose Settings for Report area.
The following parameters are required to generate a report. Entity Type: The entity type for which the report is to be generated. For example, Issuer FIID, Retailer FIID, Acquirer FIID, Logical Network, Node, Response Code, Transaction Type and Authorizer. The drop-down box will display the entity types for which stats are being collected. Select : The entities for the Entity Type selected in the previous field.
5-4-5 Transaction Activity Report The Transaction Activity report displays the number of transactions for the specified report parameters. The report has the facility to show the number of transactions in thousands or millions, depending on the data available. The values displayed on the edges of the bars show an approximate value. The exact values are available on a mouse-over action as tool tips.
The Response Time Analysis report displays the average response time for the specified report parameters.
5-4-7 Response Code Analysis Report The Response Code Analysis report displays the response code analysis for the specified report parameters. Figure 5-13 Response Code Analysis Report NOTE: Response Code Analysis report also provides the summarization of total Number Of Transactions available in the report.
The Transaction Summary report displays the transaction activity summary for the specified report parameters. Figure 5-14 Transaction Summary Report NOTE: Transaction Summary report also provides the summarization of all the columns available in the report.
5-4-9 Transaction Approvals/Denials/Reversals Percentage Report The Transaction Approvals/Denials/Reversals Percentage displays the transaction approval, denial, and reversal percentage for the specified report parameters.
The Transaction Type analysis report displays the number of transaction for various transaction types, for example, Balance Inquiry, PIN Change for the specified report parameters. Figure 5-16 Transaction Type Analysis Report NOTE: Transaction Type Analysis report also provides a summarization of total Number Of Transactions occurred.
6 Uninstalling HP NonStop POS Transaction Analyzer This chapter provides instructions on how to uninstall POS/TA from the workstation. The uninstallation of POS/TA on Windows involves uninstalling the following components in the specified sequence: • POS/TA Web Server • POS/TA Application Server • POS/TA Database 6-1 Uninstalling POS/TA Web Server Follow the steps given below to uninstall the POS/TA Web Server components from the workstation.
Step D: Rebooting the System It is recommended to reboot the system for proper functioning. The POS Transaction Analyzer Web Server Uninstallation message box is displayed. Click on the OK button to continue. NOTE: Clicking on the OK button does NOT reboot the system. It is recommended to reboot the system after uninstalling the POS/TA Web Server.
6-2 Uninstalling POS/TA Application Server Follow the steps given below to uninstall POS/TA Application Server. NOTE: Before beginning the uninstallation, ensure that none of the POS/TA components are running. If the machine has Terminal Server installed, make sure that the User session is in the install mode during uninstallation. To change the mode, type “change user /install” at the command prompt or use Control Panel Add or Remove Programs to uninstall POS/TA Application Server.
Step D: POS/TA Services Status Information The POS/TA Services Status Information screen is displayed. Uninstalling HP NonStop POS Transaction Analyzer Figure 6-6 POS Transaction Analyzer Application Server Setup Box The screen displays the status of all the POS/TA services. For a successful uninstallation, the status of all the services should be STOPPED.
6-3 Uninstalling POS/TA Database Follow the steps given below to uninstall the POS/TA Database components from the workstation. NOTE: Before continuing please ensure that the POS/TA Application Server is uninstalled. If the machine has Terminal Server installed, make sure that the User session is in the install mode during uninstallation. To change the mode, type “change user /install” at the command prompt or use Control Panel - Add or Remove Programs to uninstall POS/TA Database.
7 Troubleshooting HP NonStop POS Transaction Analyzer This chapter provides information on the common troubleshooting queries. POS/TA provides you with simple, easy to use utilities and log files to troubleshoot common problems & queries. 7-1 General Troubleshooting Checklist 1. Check if POS/TA is up & running and healthy. You can use the STATPTLF tool to check the status of POS/TA. 2. Check if POS/TA has READ access to the PTLF files. 3.
7-2 POS/TA Tracing 7-2-1 On Windows Elink Tracing The Elink configuration file Elink.cfg file can be used to enable tracing. To enable tracing, change the value of the parameter SET ELINK TRACE to PROGRESS or ERROR. By Default the value of the parameter is set to ERROR. In this scenario, only the errors will be logged. Use the PROGRESS value for detailed tracing, in which case all the data coming from the backend will be traced. The information is logged in the elink.log file.
7-2-2 On HP NonStop Server You can enable tracing in the PTLFCONF file for diagnostic purpose. The PTLFLOG file is the default log file where the messages are logged. You can refer to the PTLFLOG file to check if there are any error indications. For example, you can check the collector where the POS/TA backend is logging the EMS events to identify any problems. FUP COPY the PTLFLOG file in order to check for errors. Follow the steps listed below to enable tracing in the HP NonStop Server environment. 1.
7-4 BESTATUS Utility POS/TA provides a group of BESTATUS commands in order to check the HP NonStop status. BESTATUS SYSTEM Command The BESTATUS SYSTEM command provides the status of the POS/TA components on the HP NonStop Server. A sample output has been provided for your reference.
BESTATUS COLL Command The BESTATUS COLL command provides the status of the PTLF collectors. A sample output has been provided for your reference. RUN BESTATUS COLL -begin of display----------------------------------------------------------------------BESTATUS - Display status of HP POS Transaction Analyser Version : Build Date 11FEB2009 21:52:39 Copyright: Copyright 2009 Hewlett-Packard Development Company, L.P. LCT: 2008-10-30 15:57:31 Coll.
BESTATUS COLL, DETAIL Command BESTATUS COLL, DETAIL command provides the detailed status of the PTLF collectors. A sample output has been provided for your reference. RUN BESTATUS COLL, DETAIL -begin of display--------------------------------------------------------------BESTATUS - Display status of HP POS Transaction Analyser Version : Build Date 11FEB2009 21:52:39 Copyright: Copyright 2009 Hewlett-Packard Development Company, L.P. System: TAND1 Coll.
05:00-05:59 00000000 00000000 00000000 17h00-17h59 00000000 00000000 00000000 06:00-06:59 00000000 00000000 00000000 18h00-18h59 00000000 00000000 00000000 07:00-07:59 00000000 00000000 00000000 19h00-19h59 00000000 00000000 00000000 08:00-08:59 00000000 00000000 00000000 20h00-20h59 00000000 00000000 00000000 09:00-09:59 00000000 00000000 00000000 21h00-21h59 00000000 00000000 00000000 10:00-10:59 00000000 00000000 00000000 22h00-22h59 00000000 00000000 00000000 11:00-11:59 00000000 00000000 00
BESTATUS SAF Command The BESTATUS SAF command provides the detailed information of the store and forward database. A sample output has been provided for your reference. RUN BESTATUS SAF -begin of display--------------------------------------------------------------BESTATUS - Display status of HP POS Transaction Analyser Version : Build Date 11FEB2009 21:52:39 Copyright: Copyright 2009 Hewlett-Packard Development Company, L.P.
BESTATUS RECOVERY Command The BESTATUS RECOVERY command provides the information on the offline recovery. A sample output has been provided for your reference. RUN BESTATUS RECOVERY -begin of display--------------------------------------------------------------BESTATUS - Display status of HP POS Transaction Analyser Version : Build Date 11FEB2009 21:52:39 Copyright: Copyright 2009 Hewlett-Packard Development Company, L.P.
BESTATUS ALL Command The BESTATUS ALL command provides the brief information about the PTLF collectors, SAF and the offline recovery. A sample output has been provided for your reference RUN BESTATUS ALL -begin of display---------------------------------------------------------BESTATUS - Display status of HP POS Transaction Analyser Version : Build Date 01MAR2009 02:06:50 Copyright: Copyright 2009 Hewlett-Packard Development Company, L.P.
Name exists in file -------------------------- -------- -------- in file $dattn1.PTLV601.po090304 Yes 00027191 -------------------------- -------- -------TOTAL Yes -------- Recover -------- 00028244 -------- to recover 00001053 -------- -------- 1.
7-5 CLEANUP Utility The cleanup utility can be used to clean up the temporary database (PTLFDB, MastDB, PTLKEYDB) and delete/purge the PTLFLOG file. CAUTION: Do not use this utility until recommended by an HP support personnel. A sample output has been provided for your reference. $DATTN1 J812POS 53> RUN CLEANUP Volume $DATTN1.J812CMN Volume $DATTN1.J812POS RUN $DATTN1.J812CMN.SSTDEF ADD ADD DEFINE =tlfdb, CLASS MAP, FILE $DATTN1.A812db.tlfdb ADD DEFINE =tlfmastdb, CLASS MAP, FILE $DATTN1.A812db.
7-6 ZTOFFSET Utility The ZTOFFSET utility is used to display the closest offset in PTLFDB file for a given transaction time stamp. This Utility is used where transactions are occurring on two nodes: Primary Node and Disaster Recovery (DR) Node. In this scenario, the transactions stored on Primary Node get replicated on Disaster Recovery Node. When the Primary Node is down due to any failure, the data gets simultaneously stored on the Disaster Recovery node.
7-7 Node Management Utility The Node Management utility is a command line utility to modify the node configuration in the Elink configuration file as well as in the POS/TA Database. Table 7-1 Arguments for Node Management Utility for Database Information Database Authentication Mode Argument Description SQL Authentication -server= The server name. Default: Local -db= The Database name. Default: POSDB -sqlauth Use SQL authentication.
3. To modify nodes: a. While using SQL authentication nodemgt.exe -modifynode –node=”\NODE1” –newIP=“111.111.111.111” – newPort=”6666” –server=(local) –db=POSDB -sqlauth –username=sa – password=***** b. While using Windows authentication nodemgt.exe -deletenode –node=”\NODE1” –server=(local) –db=POSDB 7-8 POS/TA Maintenance Procedure Follow the steps listed below for changing the Node, IP address and port number for POS/TA. Stop POS/TA on the front-end and on the HP NonStop Server. 2.
7-9 Troubleshooting a Full Transaction Log When the transaction log becomes full, the SQL Server Database Engine issues an error. The response to such a situation will depend on the condition(s) that caused the log file to fill. For more details and options available for responding to a full transaction log, refer to Microsoft documentation. 7-10 POS/TA Data Backup & Recovery It is suggested that POS/TA Database backup is performed using the Full Recovery Model.
4. The Choose a destination screen is displayed. a. Select the Destination as Text File using the corresponding box. b. Select/specify the text file name using the File name box. c. Click on the Next button. 5. The Specify Table Copy or Query screen is displayed. Figure 7-3 DTS Import/Export Wizard – Specify Table Copy or Query Screen a.
b. Select the Use a query to specify the data to transfer option when you want to specify an SQL query result set data to be exported into the text file. Click on the Next button. The Type SQL Statement screen is displayed. You can either write an SQL query manually in the Query statement box, or use the Query Builder button to automatically build the query using a wizard.
7. The Save, schedule, and replicate package screen is displayed. Use this screen to save the DTS package. You can also choose to replicate the data or schedule the package to be executed at a later time. Select the Run Immediately check box to start the process of exporting data to the specified .txt file immediately. In case you want to schedule the process, select the Schedule DTS package for later execution check box.
7-10-2 Using Windows BCP Command Line Utility The BCP command line utility is used for exporting the SQL data from an SQL Server to a text file or to other SQL Servers. Use the following command to export data from the POS/TA database table to a .txt file. bcp queryout –c –U –S Where: is an SQL query. For example: Select * from .dbo.
7-11 User Not Able to View Default POS/TA Web Page The problem may be occurring because of the following reasons: • Network Connection Outage For the clients to view POS/TA web pages, the network connection with the Web Server should be up & running. Check if the network connection is working. • Web Server Problem You may need to (re)register the ASP.NET file extensions with the IIS Server. To do this, perform the following steps: a.
7-12 User Not Able to Connect to POS/TA Database NOTE: If you get any database access related errors, the issues should be forwarded to the application/database administrators responsible for the POS/TA product. The steps discussed here are for application/database administrator and not for the end user. If the users are not able to connect to the POS/TA Database, check the SQL installation on the system. The problem may occur if SQL Server was installed in Windows Authentication Mode. Suggestions 1.
The next step is to permit access to the database. Select the Database Access tab page. Select the Permit check box next to the POSDB database. Also select the db_owner check box in the Database roles for area.
Click on the OK button. The new login will be displayed in the SQL Server Enterprise Manager. Figure 7-11 SQL Server Enterprise Manager 2. Check if the User ID/Password to Access the POS/TA Database has been Changed. The POS/TA application administrator has the information regarding the User-ID/Password being used by POS /TA Application Server and the Web Server to access the POS /TA database.
7-13 POS/TA Web Page Not Displaying Any Data Figure 7-12 No Stats Available Message in POS Web Page 7-14 User Unable to Install POS Transaction Analyzer Services In case if the POS/TA services do not get installed on your system after installing POS Transaction Analyzer, you need to install them manually using command prompt.
7-15 User Unable to Create Views The user is getting the following validation error while creating new views. Figure 7-13 Server Error in POS/TA Application Suggestions If tag in the web.config file (Drive:\Inetpub\wwwroot\POSTA)is commented then please remove the comments, else you may receive errors while creating new views.
Appendix A Installation Information POS/TA Database 1. User Name The user in whose name POS/TA is registered. Example: John Smith 2. Company Name The company in whose name POS/TA is registered. Example: ABC Inc. 3. Destination Location The directory on the workstation where POS/TA Database is to be installed. 4. SQL Server Name The SQL Server where POS/TA Database will be created or already exists. 5. SQL Server Port The port where the Microsoft SQL Server is listening. Default: 1433 6.
POS/TA Application Server 1. User Name The user in whose name POS/TA is registered. Example: John Smith 2. Company Name The company in whose name POS/TA is registered. Example: ABC Inc. 3. Destination Location The directory on the workstation where POS/TA Application Server is to be installed. 4. SQL Server Name The SQL Server where POS/TA Database will be created or already exists. 5. SQL Server Port The port where the Microsoft SQL Server is listening. Default: 1433 6.
POS/TA Web Server 1. User Name The user in whose name POS/TA is registered. Example: John Smith 2. Company Name The company in whose name POS/TA is registered. Example: ABC Inc. 3. Destination Location The directory on the workstation where POS/TA Web Server is to be installed. 4. SQL Server Name The SQL Server where POS/TA Database will be created or already exists. 5. System Name/IP Address The System Name/IP address where POS/TA Application Server is installed. 6.
HP NonStop Server 1. POS/TA Product Key The POS/TA license key provided by HP. 2. HP NonStop Node Name The Name of the HP NonStop Node where backend Elink is configured. Example: \NODE 3. User ID and Password for NonStop Node The User ID and Password for HP NonStop Node. 4. POS/TA Temporary Volume.Subvolume The Volume.Subvolume where the POS/TA installation files will be copied. 5. POS/TA Installation Subvolume The Subvolume where POS/TA will be installed. Example: $prod.test 6.
Appendix B PTLFCONF File Parameters Description KEY License Key COLL CollectorName ON|OFF to log events. Default: OFF SSID SSID to use for event logging Default: TANDEM.269 PROD-BASENUM Product Base Number for logging events (Default 0).
Parameter Description AUTO-RECV-TIME To enable recovery of data for specified duration of hours in online mode Default: 0 CUSTOM-DATA-LEN To specify the size in bytes of the customer specific extra tokens or data Default: 0 RECOVERY To enable/disable the recovery of missing transactions. ON|OFF Default: OFF SAF-CATCHUP-CONFIG To configure the catchup process.
Appendix C This section provides a list of fields in the POS database and the mapped fields in the PTLF file. A sample USRPTLFC file to populate transaction date/time and card number in user-defined fields from the PTLF record is also described in this section. Table 3 Mapping of PTLF File with Transaction Table Fields in POS Database Fields in PTLF File transactionID Description Unique number for a transaction. It can be treated as the primary key. acctType auth.tran_cde.
Table 3 Mapping of PTLF File with Transaction Table Fields in POS Database Fields in PTLF File Description transactionAmount auth.amt_1 The transaction amount requested. For adjustment transactions, this field contains the original amount. For purchase with cash back transactions, this field contains the total amount (purchase plus cash back). The cash back amount is contained in the auth.amt_2 field. For preauthorization completions, this field contains the completed amount. entryTime auth.
Mapping of User-Defined Fields with PTLF Fields POS/TA provides user-defined fields which can be mapped to fields in the PTLF record. 1. Set the USER-TOKENS parameter in the PTLFCONF file to YES. 2. Amend USRPTLFC file on the POSTA subvolume on the NonStop to populate the required PTLF record in the user fields. 3. Stop the POS/TA environment using the STOPPTLF command. 4. Compile USRPTLFC using the RUN ZTCMPTLF command to generate new executables for PTLFCOLL and PTLFRECV programs. 5.
/* Field 1 is going to show the Transaction Time */ /***************************************************/ memcpy(fld1, ptlfRec->u_ptlf_auth_buf.ptlf_auth_buf.auth.tran_dat.yy,2); fld1 += 2; *fld1 = '/'; fld1++; memcpy(fld1, ptlfRec->u_ptlf_auth_buf.ptlf_auth_buf.auth.tran_dat.mm,2); fld1 += 2; *fld1 = '/'; fld1++; memcpy(fld1, ptlfRec->u_ptlf_auth_buf.ptlf_auth_buf.auth.tran_dat.dd,2); fld1 += 2; *fld1 = ' '; fld1++; memcpy(fld1, ptlfRec->u_ptlf_auth_buf.ptlf_auth_buf.auth.tran_tim.
Appendix D Transaction Types Transaction Type Description 10 Normal purchase 11 Preauthorization purchase 12 Preauthorization purchase completion 13 Mail/phone order 14 Merchandise return 15 Cash advance 16 Card verification 17 Balance inquiry 18 Purchase with cash back 19 Check verification 20 Check guarantee 21 Purchase adjustment 22 Adjustment - merchandise return 23 Adjustment - cash advance 24 Adjustment - purchase with cash back 25 Card Activation 26 Additional Card
Appendix E Reversal Codes This section lists the Reversal Codes along with their description.
Appendix F Response Codes Response Code Description 000 APPROVED WITH BALANCES 001 APPROVED WITHOUT BALANCES 002 APPROVED WITH COUNTRY CLUB 003 APPROVED WITH MAYBE STATUS (ID REQUIRED) 004 APPROVED WITH PENDING IDENTIFICATION 005 APPROVED BLIND 006 APPROVED WITH VIP STATUS 007 APPROVED ADMIN TRANSACTION 008 APPROVED - NNEG FILE 009 APPROVED WITH COMMERCIAL STATUS 050 DECLINED 051 EXPIRED CARD 052 PIN TRIES EXCEEDED 053 SHARING IS NOT ALLOWED 054 NO SECURITY BOX 055 INVALID T
Response Code Description 077 PRE AUTHS LIMIT REACHED 078 DUPLICATE TRANSACTION 079 MAX ONLINE REFUNDS LIMIT REACHED 080 MAX OFFLINE REFUNDS LIMIT REACHED 081 MAX CRED PER REFUND REACHED 082 NUMBER OF TIMES THE CARD USES LIMIT EXCEEDED 083 MAX REFUND CRED LIMIT EXCEEDED 084 CUSTOMER SELECTED NEG REASON 085 INQUIRY NOT ALLOWED 086 OVER FLOOR LIMIT 087 MAX NUM REFUND CREDITS EXCEEDED 088 PLACE CALL FOR REFERRAL 089 CARD STATUS INACTIVE OR CLOSED 090 REFERRAL FILE FULL 091 NEGATI
Description 201 INCORRECT PIN 202 CASH ADV LESS THAN MIN 203 NEED ADMIN CARD 204 ENTER LESSER AMOUNT 205 INVALID ADVANCE AMOUNT 206 CAF NOT FOUND 207 INVALID TRAN DATE 208 INVALID EXPIRE DATE 209 INVALID TRANSACTION CODE 251 PURCHASE WITH CASH BACK 252 NO DEBIT CRD SUPPORT 900 PIN TRIES EXCEEDED 901 EXPIRED CARD 902 NEG CAPTURE CARD 903 CAF CAPTURE STATUS 904 CASH ADV LESS THAN MIN 905 USES LIMIT EXCEEDED 906 DELINQUENT 907 OVER LIMIT TABLE 908 AMOUNT OVER MAX 909 C
Appendix G Threshold Expressions POS/TA uses Boolean expressions to identify when a threshold is in violation. If the Boolean threshold expression evaluates to true, the threshold is considered to be in violation. Following are some examples of valid Boolean expressions: TotalTransactions > 100 This expression will cause the threshold to be violated for an entity when the total transactions exceed 100. TotalTransactions > 10 and PercentDenials > 5.
Field Name Field Type Description PercentNetUnavailErrors Integer Percent net unavailable errors PercentUnableToAuthErrors Integer Percent unable to authenticate errors HighestResponseTime Integer Maximum response time RepeatedDenials Integer Consecutive denials Year Integer Year part of the current Stat time. Month Integer Month part of the current Stat time. Day Integer Day part of the current Stat time. Hour Integer Hour part of the current Stat time.
Appendix H Transaction Filter Expressions POS/TA also supports using Boolean expressions to filter the transactions that are used to evaluate thresholds. If the Boolean expression evaluates to true, the transaction is added to the result set that will be used to evaluate the threshold, otherwise the transaction is ignored. Some examples of valid transaction filter Boolean expressions: acctType = “31” This expression will enable only entities with account type equal to 31 to be displayed.
Operator Reference Operator Description = Equal To < Less Than > Greater Than <= Less Than Or Equal To >= Greater Than Or Equal To != Not Equal To and Logical And or Logical Or Appendix H The following operators can be used within expressions: Appendix H 165
Appendix I Substitution Parameters POS/TA provides the following substitution parameters that can be used for creating customized Alert text messages that will be generated for threshold violations. For example, to view Entity Name in the alert text on Alerts page, specify the alert text as Entity Name = %EntityName%. Parameter Description %EntityName% Name of the entity %EntityType% Type of entity %EntityCode% Entity ID specific to the entity name.
Description %Day% Day part of the current Stat time. %Hour% Hour part of the current Stat time. %Minute% Minute part of the current Stat time.
Appendix J Configuration Parameters POSCommandControl Configuration Parameters Section: Data Source Configuration Parameter Description Data Source Name of the Database Server Initial Catalog Name of the database User ID Name of the database user Password Database password Windows Authentication Whether windows authentication mode is to be used or not Section: Operational Parameters Parameter Description MaxLogFileLen Log File Length size in Kb.
POSLOGGER Configuration Parameters Section: Data Source Configuration Parameter Description Name Name of the database User Name Name of the database user Password Database password Use Credential Enabled Whether credentials are to be used or not Section: Operational Parameters Description Fraction Time Logging Enabled Fraction time (milliseconds) in the database. Default: 0 Log Level Log level settings for problem tracing.
Parameter Description Performance Stats Enabled Collect performance stats. Default: 0 Performance stats interval (secs) Collect Performance stats after the specified period in seconds. Default: 30 Log File Name Name of the log file. Default: poslogger.log Validation and Repair Enabled Enable/disable validation and repair of transactions. Default: 1 Log Repaired Transaction Enabled Enable/disable logging of repaired transaction.
Description Default Alert Event Text The default alert event text. Default: %EntityTypeName% %EntityName% is in violation for threshold %ThresholdName% : %Used% Default Alert Subject The default alert subject. Default: %ThresholdID%.%EntityTypeName%.%EntityName% Default Normal Alert Subject The default normal alert subject. Default: %ThresholdID%.%EntityTypeName%.%EntityName% Restart after failure (secs) The parameter retries the failed operation after configured time.
Parameter Description Ignore Alerts Time (Mins) Checks the Transaction Time Interval for which the alert is to be generated with the Latest App Server (LCT/GMT). If the difference between the Alert Generation Transaction Time and the Latest App Server is greater than a configurable amount of duration (in Minutes), then the alerts will not be generated. DB Transaction Time Local Indicates if the transaction time is stored in LCT/GMT time format.
Description MaxStatGenIntervalMins The maximum Stat Gen interval in minutes. It can only generate 15 min past transactions stats. For example MaxStatGenIntervalMins is set to 15 mins. IF StatGen is down for 60 minutes between 10 AM – 11AM but the logger was logging transactions during that time. When StatGen is started, for example, at 11AM, the Statgen will skip statistics for transaction 10 - 10:45 and generates stats from 10:40 onwards.
Parameter Description DailyStatsPurgeIntervalDays Retention period for the dailystats table. Default: 365 HourlyStatsPurgeIntervalDays Retention period for the hourlystats table. Default: 30 StatsPurgeIntervalDays Retention period for the stats table. Default: 7 AlertsPurgeIntervalDays Retention period for the alerts table. Default: 15 TransactionsPurgeIntervalDays Retention period for the transactions table.
POSRECOVER Configuration Parameters Section: Data Source Configuration Parameter Description Name Name of the database User Name Name of the database user Password Database password Use Credential Enabled Whether credentials are to be used or not Section: Operational Parameters Description Nonstop Node Name of the NonStop Node Default: ”” Fraction Time Logging Enabled Enable fraction time logging Default: 1 Use LocalTime Enabled Enable use of local time Default: 1 Maximum Log File Length (K
Parameter Description Maximum Number of Failure The Maximum Number Of Failure parameter shutdown the service after configured number of failures (in this case, NT service manager will not start the service). If this parameter is 0 then service never shutdown except abnormal termination/kill /exception (in this case NT service manager starts the service after configured time in service’s recovery properties). Default: 0.
Description QueryTimeoutSecs Maximum allowed time for the query execution on SQL server. Default: 900 EntityTypeSeperator The delimiter used to separate combined entitytypes. Default: “:” LogFileName Name of the log file. Default: PosStatAdj.log MaxLogFileLen Log File Length size in Kb. MaxNumOldLogFiles Maximum number of old log files. Default: 4 LogErrorsToEventLog Log the error messages to the windows event log.
Parameter Description QueryTables Displays the list of Query tables available on the Query page. Default: Transactions ConsolePosStatAdj Configuration Parameters Section: Data Source Configuration Parameter Description Data Source Name of the Database Server InitialCatalog Name of the database User Name Name of the database user Password Database password Windows Authentication Whether windows authentication mode is to be used or not.
ELINK Configuration Parameters Parameter Description SET ELINK TRACE Specify the Elink trace levels. The values available are: • None: Does not log any message. • Error: Logs all the error messages • Warning: logs all the error and warning messages. • Progress: Logs all the error messages, warning messages and information messages. SET ELINK LOGFILE Name of the log file. Default: elink.log SET ELINK REMOTEPORT Port used for remote connection.
NOTE: The Configurable Codes in the .ini files will support alphanumeric values from this release onwards. The codes should be given accordingly in full format as they are inserted in the database.
Appendix K POS/TA EMS Event Details The following table lists the POS/TA EMS events, considering PROD-BASENUM = 2000 in the PTLFCONF file.
Internal Message ID EMS Event ID* Text Message 29 2029 SETMODE Failed on file, Error Detail= 30 2030 SETMODE Failed on file, Error Detail= 31 2031 Failed to during #B24POS registration, Error Detail= 32 2032 Failed to during #END registration, Error Detail= 37 2037 Failed during READX from , Last-File System Error= 46 2046 Error during FILE_SETPOSITION_ PTLFDB,
EMS Event ID* Text Message 70 2070 fCheckInterval SIGNALTIMEOUT ERROR 71 2071 fHealthInterval SIGNALTIMEOUT ERROR 72 2072 safStatInterval SIGNALTIMEOUT ERROR 73 2073 PTLFFILE '' closed. Records Read: , Records Processed:, Records Rejected: 74 2074 PTLFFILE '' closed.
Internal Message ID EMS Event ID* Text Message 107 2107 SETMODE Failed on file, Error Detail= 108 2108 Error during reading < RECSPCTL file> error-detail 109 2109 Nothing to recover offline .
Appendix L EMS Event ID Text Message 339 Successful on address(:) 340 Keep Alive option turned ON 344 ElinkUpOn::Remote Elink Connection Established 344 ClientRegFrom:: Client Connection Established 345 ElinkDownOn:: Client Connection Lost 345 ClientRegFrom::Remote Elink Connection Lost Appendix L Elink EMS Event Details Appendix L 185
Appendix M Error Messages Service Errors Description POSLOGGER Could not start service For some reason the Windows service manager could not start the service. Could not query service For some reason the Windows service manager could not query about the service. Could not open service For some reason the Windows service manager could not open handle about the service. Could not connect to the SCM service Could not connect to the Windows Service Control Manager.
POSSTATGEN POSMON Errors Description Failures exceed allowable limit. Shutting down. If the failure to start the service exceeds the maxNumFailures value set in the ini file this error will be logged Required parameter ConnectionInfo not set The parameters specified for database connection are not sufficient. Could not open database connection Could not connect to the database with the given DB connection info.
Service Errors Description Couldn't access Service Control Manager Unable to access the Service Control Manager. Could not uninstall service Unable to uninstall the service. Cannot uninstall running service Unable to uninstall as the service is running. Could not register service handler The application could not register itself as a service with the service handler. Init() : Couldn't load config file The application cannot load the configuration ini file POSMON is already running.
Errors POSMAINTAIN Scheduled actions did not complete successfully Description The specified maintain operation schedule failed. The reason description will also be logged. Could not open logfilename The application fails to open the specified log file. DB Errors The errors that shoot from the database will be logged with the specific description.
Appendix N Implementing Dynamic Metric POS/TA supports the feature of implementing dynamic metric to add user defined columns in the stats table. Follow the steps given below to add dynamic metric in POS/TA: 1. Create a SQL function that defines the logic to evaluate the corresponding metric. 2.
Acquirer The acquirer is the organization which, under arrangement with and on behalf of an issuer, discharges the obligations owed by that issuer to the relevant cardholder when the cardholder undertakes a transaction via an access point owned/controlled by the acquirer. As a result, the acquirer engages in interchange activities with that issuer. Approvals Any transaction that is approved by the card holder’s bank (issuer).
TPS Transactions per second (TPS) is a metric used to measure database performance. URL Uniform Resource Locator: The address identifies the location of a Web page on the World Wide Web.
Index HP NonStop POS Transaction Analyzer: POS/TA, 8 $PTPLG, 13 $PTPLK, 13 $PTPMN, 13 $PTPnn, 13 $PTPRD, 13 I A L Acquirer FIID, 54 Admin Privileges, 49 Alerts, 76 Authorizer, 54 Latest Transactions, 66 Logical Network, 54 B Maintenance Procedure, 135 MAST-DB, 13 Backup & Recovery, 136 BCP Command Line Utility, 140 BESTATUS, 13 BESTATUS Utility, 124 Bin, 54 C CLEANUP Utility, 132 Collector, 13 Configuration Client, 32 Configuration Parameters, 168 Create a Query, 78 Creating a View, 55 Creating Th
Document Feedback Form We would appreciate your comments on the HP NonStop POS Transaction Analyzer User and Installation Guide. After you have read the Guide and used the software, please take a few moments to complete this form and return it to appropriate HP product support service. Guide 1. The organization of the Guide makes it easy to locate topics quickly. Strongly Disagree 1 2. Strongly Agree 2 3 4 The appearance of the pages makes it easy to locate information quickly. Strongly Disagree 1 3.
9. The level of writing in this book is: Too Basic Just Right Too Technical (Please be specific.) Do you have any other suggestions for improvement? Document Feedback Form 10.
