PANTHEON™ Help

 Toc
 PANTHEON Help - Welcome
[Collapse]PANTHEON
 [Collapse]Guides for PANTHEON
  [Expand]Guide for PANTHEON
  [Expand]Guide for PANTHEON Retail
  [Expand]Guide for PANTHEON Vet
  [Expand]Guide for PANTHEON Farming
 [Collapse]User Manuals for PANTHEON
  [Collapse]User Manual for PANTHEON
   [Expand]Getting Started
   [Expand]User Manual for eBusiness
   [Collapse]Settings
    [Expand]Subjects
    [Expand]Items
    [Expand]POS
     Manufacturing
    [Collapse]Program
     [Expand]Document types
      Reports
      Texts for Document Types
      Document Texts
      Delivery Methods
     [Expand]Loyalty Cards
     [Collapse]Administration Panel
      [Expand]Right click on Administration Panel tree
      [Expand]Settings
       Menu
      [Expand]Security
      [Expand]Users and Groups
       Versions/Upgrades
      [Collapse]Database
        Import/Export Data
       [Collapse]Performance (Analytical panel)
        [Collapse]Ping and Trace
          Analysing Ping
          Analysing Trace
        [Expand]Performance
       ZEUS
       OTOS
      Dashboard of Components
      Dashboards of Reports
      Ad-Hoc Analyses
      ARES
      SQL Editor
    [Expand]Personnel
     Calendar
    [Expand]Financials
    [Expand]Customs
    [Expand]Documentation
    [Expand]Program
     Change user
   [Expand]Orders
   [Expand]Goods
   [Expand]Manufacturing
   [Expand]Service
   [Expand]Help
   [Expand]Personnel
   [Expand]Financials
   [Expand]Analytics
  [Expand]User Manual for PANTHEON Retail
  [Expand]User manual for PANTHEON Vet
  [Expand]User Manual for PANTHEON Farming
[Collapse]PANTHEON Web
 [Collapse]Guides for PANTHEON Web
  [Expand]Guide for PANTHEON Web Light
  [Expand]Guide for PANTHEON Web Terminal
  [Expand]Guide for PANTHEON Web Legal
  [Expand]Old products Archive
 [Collapse]User Manuals for PANTHEON Web
  [Expand]Getting started PANTHEON Web
  [Expand]User Manual for PANTHEON Web Light
  [Expand]User Manual for PANTHEON Web Terminal
  [Expand]User Manual for PANTHEON Web Legal
  [Expand]Old products Archive
[Collapse]PANTHEON Granules
 [Collapse]Guides for PANTHEON Granules
  [Expand]Personnel Granule
  [Expand]Travel Orders Granule
  [Expand]Documents and Tasks Granule
  [Expand]Dashboard Granule
  [Expand]B2B Orders Granule
  [Expand]Field Service Granule
  [Expand]Fixed Assets Inventory Granule
  [Expand]Warehouse Inventory Granule
 [Collapse]User Manuals for PANTHEON Granules
  [Expand]Getting started
  [Expand]Personnel Granule
  [Expand]Travel Orders Granule
  [Expand]Documents and Tasks Granule
  [Expand]B2B Orders Granule
  [Expand]Dashboard Granule
  [Expand]Field Service Granule
  [Expand]Fixed Assets Inventory Granule
  [Expand]Warehouse Inventory Granule
  [Expand]Archive
[Expand]User Site

Load Time: 2546.9064 ms
"
  1000006093 | 225505 | 413441 | Updated
Label

Analysing Trace

With the slowed working of the database, the speed of connection with the server must be checked. That is why there are two basic parameters available, which help us diagnose the problem. The parameters are ping and trace.

The Trace parameter tells us how the web package travels from the server to the work station (which path it takes). If there are a lot of transitions between routers, the speed of the data will fall (it will be lower than optimal).

The Ping/Trace panel can be accessed by clicking the Performance panel, located in the Administration panel.

HINT

On the Ping/Trace panel, we can check the performance speed (ping) for the available Datalab services:

  • Edgar
  • DMS
  • DMS Link
  • Hosting IP
  • UserSite

 

CASE SUMMARY

Accountant Ashley carries out regular work tasks in the program, but the processes after clicking are carried out much slower than usual. Because of this, she informs the IT department of this situation. The person responsible from the IT department first checks the basic parameters for the web connection with the Edgar server.

The person responsible does this in the following way:

  1. Pinging the server
  2. Tracing the server

 

1. Pinging the server

The person responsible from the IT department first wants to check the performance speed of the connection to the Edgar server.

For a detailed step-by-step description, see chapter Analysing ping.

2. Tracing the server

In the second step, the person responsible wants to check the trace of the web package trip which was sent during the ping analysis.

For this purpose, the person responsible clicks the button for the Edgar server on the Ping/Trace panel.

HINT

In the Trace log window, the data is displayed as soon as you carry out the first step – pinging the server.

The program returns the result.

In the Trace log window, the person responsible sees the following:

  • A log of the trace of the web package trip to a server with the IP address 91.199.61.60 was carried out;
  • the data travelled via one additional router with the IP address 192.168.83.1 before it reached the IP address of the Edgar server (IP address: 91.199.61.60)

Since the result is appropriate, the person responsible dismisses the possibility that the slow performance of the database was caused by the Trace parameter.

HINT

In the same way, the person responsible carries out the Trace analysis for all available Datalab services:

  • Edgar
  • DMS
  • DMS Link
  • Hosting IP
  • UserSite

 

 

 

 

 

Rate this topic
Was this topic usefull?
Comments
Comment will also bo visible in forum!