This section list allows you to enable and disable sections to be viewed by the At-a-Glance screen. By default, this screen displays all the enabled reporting options with check marks in them and is the default view displayed when started up.
If you would like to customize this view simply unselect the desired options and then click At-a-Glance in the list to view the edited list. Should you need to restore default view settings, hit refresh at the top of this list to bring back the default values.
Clicking on a single option will narrow down the view to that section specifically.
- The first line displays the current time, day, and date
- The second line displays the following from left to right:
- How long the UTG has been running in the dd:hh:mm:ss format
- The build number. In this example, the build is 3015
- An f after the build number indicates the UTG is running in Stand Alone and other indicators will appear in trace
- The number of UTG threads created out of 90, or the maximum configured for the UTG. In this example, the number of threads created is 16 out of 90.
- The approximate amount of RAM allocated to the UTG.
- The countdown, in seconds, until the UTG refreshes its internal thread identifier list.
- The time the UTG started in the hh:mm:ss format.
- The day the UTG started.
- The date the UTG started in the mm/dd format
- The third line displays the current UTG status and any of the following may appear:
- Running – the normal status when the UTG is operating
- !UNMANAGED! - The UTG is not registered\connected with the Shift4 Datacenter. In support, you will almost exclusively only see this if the UTG was forcibly shut down the previous time it was running. It should not affect processing.
- Pre-Shutdown, Shutdown Pending, Shutdown Start (countdown), Shutdown, and Shutdown Now – A series of statuses as the UTG is being stopped
- Prepare Update, Pending Update, Update Start (countdown), Update Now, and Update Launched: A series of statuses as the UTG automatically updates
The device thread example above will break down by color what information is shown and in what order it will appear. This will be the same for all devices configured in the UTG.
- [Thread Assignment] (Green) This section will increment each time a new thread is added to the UTG, this is to a max of 300 threads. This limit includes Interface Threads and Devices.
- [Device Type] (Orange) This section Indicates what the Device type that is selected in the Tune-up is. It is possible to see Similar Device Types of different names. For Instance, Ingenico iPP320 RBA, or Ingenico IPP320 CAN depending on the type of loaded software for your device.
- [API TID] (Purple) This section shows what the API TID we have configured in the UTG Tune-up. This Section can contain Alpha and Numeric Characters.
- [Device Name] (Pink) This section shows what the device thread name is in the UTG Tune-up. This Section can contain Alpha, Numeric, and Special Characters.
- [Device Status] (Blue) section shows what communication is occurring with the device. This should change whenever an action is performed, and it should display the current action; or when not in use it should scroll between Idle, listening, looking for other work, or waiting. If you see the status gets stuck on Start-Up, Abort Failure, or Pause this means the device is unable to communicate or is configured improperly and should be reviewed
The express manager is enabled by default and is located directly under the devices section in the UTG SA. This displays the status of requests sent and received between the UTG and Shift4 data centers in the TCP Client and Routes rows.
The TcpClient (Highlighted in Orange) row shows that this UTG is registered as a trusted entity with Shift4’s data center and that it has obtained a list of encryption keys from Shift4. “Key Page Success” will be displayed if the UTG has successfully connected to the data center and obtained an encryption key list. Any other message here means that the data center cannot validate this UTG client as trusted, or the UTG was unable to connect to the data center.
Errors that occur while connecting will be displayed in plain text on the TcpClient Row.
Some errors are also visible in the Alerts Section at the top of the Stand Alone highlighted in red. (Example of Alert below.)
Note: The Alerts section will only show if the UTG is experiencing an issue requiring correction on the PC or Shift4 configuration.
The “next key page” denotes when the UTG will automatically obtain a new set of encryption keys from the Shift4 data center. This also occurs every time the UTG makes a new connection to the data center.
- The Routes (Highlighted Blue) row shows how long the UTG has been in its current state and the number of requests and responses that have been made/received from the POS to the data center in total since its last connection. It also displays when it has successfully downloaded a new list of Active Routes (IP’s) to our data center
- The Updates (Highlighted Green) row displays when the next scheduled check for updates will occur for the UTG if auto-update is requested
The Global Status section gives you more detailed information regarding the UTG’s communication status to the Shift4 data center and the UTG’s offline procedures. This section is enabled by default and is highlighted green on the UTG Stand Alone.
When starting the UTG Stand Alone a message of WaitKeyPage, Connection Needed no connection, KeyPage Required KeyPage not available, Offline Key Okay, KeyPage not available, or No Failures will display in this section.
Once the UTG is able to establish a connection to the data center the message will change to “Ready No Failures” if no errors are encountered and a connection will show in citadel logs.
If an error should occur during connection the UTG would remain in an offline state. On the far-right side of the Global Status section, you can find out if this UTG has the UTG Secure Offline Stand In enabled and what parameters are configured for this. When disabled, you will see the message of “Never”. When configured this section displays Custom, Low, Medium, or High. Followed by the number of failed transactions needed and the time span in seconds in which that number of failures must occur to place the UTG in offline mode. In the example, the UTG is configured for a Custom offline level of 2 failures within 240 seconds.
The Interface thread(s) displays the status of the configured interface threads in the UTG Tune-up. This thread will be named after whatever "Name" was assigned to the thread name. If an error is encountered with biding to the IP or TCP Port this section will turn red indicating it has failed in binding.
All interface types will have a standard set of fields that need to be populated and some will have specialized fields unique to that connection type. See the color-coded TCP/SSL thread below for more information.
All information on this line will be visible on the UTG configuration page once the UTG has connected to the data center and uploaded the configuration.
- [Thread Name] (RED) The Task Description from the UTG API Interface Tab. Essentially the name of the thread.
- [Status] (ORANGE) State of communication with the Configured Interface. Waiting indicates that the thread is idle and listening for transactions.
- [Host IP] (YELLOW) The Configured Host Address for this Interface. The IP interface on which the UTG is listening for transactions.
- [Port] (GREEN) The Configured Listen Port (TCP Port) for this Interface displayed in hex (decimal displays in parenthesis).
- [Masking] (BLUE) Sates wither card information is sent unmasked or masked. This should always be masked.
- [Offline Stand-in Threshold] (PURPLE) This field shows what dollar amount the offline threshold is set to. See the UTG Quick Installation Guide>Configuring interfaces for more information.
- [Encryption Threshold] (BLACK) The Encryption Threshold field will only be present on connections that utilize SSL/TLS to communicate. Examples would be TcpSslAPI, HttpSslAPI, or CloudSslAPI.
In addition, if you are working with an Oracle Interface using the OPI Driver, additional fields for transaction tracking will show below the interface line and above the request section, These are Oracle Dispatcher and Oracle History and they work similarly to the Requests and History Sections of the UTG Stand Alone but they only focus on OPI communications for the configured thread.
The request section highlighted in yellow shows and displays active "tasks" being handled by the UTG. Typically, tasks are completed very quickly and may appear for only a moment.
When active a message of "x" Wait will be displayed. The x represents the number of tasks waiting to be completed by the UTG. Tasks in this sense don't just mean transactions, this is all active communication between the UTG and its connected sources. (If you are trying to track processing requests see the Summery and History Sections of the Stand Alone)
Routes are connections to Shift4's data centers. The route score displayed in the UTG Standalone will be based on the "Max Score" setting inside the UTG Tune-Up under the tab "Express". The default is "10". This follows the same logic employed by the Shift4 Probe utility where a higher score indicates higher latency in the connection. A Perfect connection is "0"
Summary and History
Summary: This section displays the Fastest Transaction, Slowest Transaction, and Most Recent Transaction. This information can be used to gauge response times when troubleshooting issues with slow response times.
History: This section will show the last ten transactions processed through the UTG. It will give identifying information such as Date, Time, API Function, S4 Merchant, Invoice, and Amount to help identify transactions for troubleshooting communication issues.
The Offline Manager section provides information on transactions processed while the UTG is in an Offline state.
The Blue highlighted section depicts how many requests have been placed into pending completion awaiting the restoration of the UTG computer's Internet Connection.
The Green highlighted section shows the total number of requests and transmits that are sent to and from the UTG since it entered an offline state.
- Rx = Request to UTG
- Tx = Transmit from UTG
The Purple highlighted section will show the last few requests that were processed as well as the UTG's response to this request while the UTG was in the Offline state.