Using the Verivo Test Page to Troubleshoot

Using the Verivo Test Page to Troubleshoot

 The Verivo Test Page is a browser based tool, residing on the AppServer that will allow you to isolate components to determine where a point of failure is occurring. The Verivo Test Page allows for the following tests:

  • Test Login
  • Test Authentication
  • Confirm External Data is Accessible
  • Test a Configuration Download
  • Manually Test Device Screen Requests

 The main function of using the Test Page is to determine whether the issue is relegated to a device or client side proxy (if the test page is successful and does not replicate a device experiencing an issue) or if the issue is relegated to the configuration, database, or server (if the Test Page produces the same error or issue as the device).  


Test Login:

Use: Testing whether a user can login from the test page.

Benefit: Confirms whether the issue is with the configuration, database, or server OR whether the issue is with the user’s device client side proxy (BES, DMZ etc.) or networking issue. 

  1. Emulate a login by setting the following information in the relevant fields: 
  • Select appropriate application from the App field (e.g., John Test).
  • Enter your username in the UserID field  if applicable(e.g., mpdemo).
  • Enter your password in the Password field if applicable(e.g., mpdemo).
  • For the purposes of this log in test, all other fields can be kept at default regardless of the Platform you are using. 

      2. After setting the above info, click the Test Login button twice.

1.png

 

This emulates a login and you should see results returned at the bottom of the Test Page.

 2.png

 

   3.  Results:

  • If the same user is not able to login on the Test Page and does not see the above Successful login then the issue is occurring either on the AppServer, Database or Configuration.
  • If the same user is able to login to the Test Page but cannot on his device the issue is with the user’s device, client file, client proxy, or network related issue (before it hits the AppServer).

 

Test Authentication

Use: You can test your authentication mechanism on the Test Page.

Benefit: Confirms whether authentication works and if the authentication issue is with the configuration, database, or server OR whether the authentication issue is with the user’s device client side proxy (BES, DMZ etc.) or networking issue. 

  1. Follow the steps above in Test Login.
  2. Results:
  • If the same user is not able to login on the Test Page and does not see the above Successful login then the authentication issue is occurring either on the AppServer, Database or Configuration.
  • If the same user is able to login to the Test Page but cannot on his device the authentication issue is with the user’s device, client file, client proxy (most likely in this case), or network related issue (before it hits the AppServer).


Confirm External Data is accessible

Use: You can test external data sources using the Test Page.

Benefit: If you are getting an error on your device while accessing external data this is a useful tool as the Test Page will often times display more detailed error information as to the cause of the issue. 

  1. Follow the Instructions in Test Login.
  2. Take the SessionID at the bottom after a successful login and paste it into the SessionID section.

 3.png

         3. Select a screen and then Select the Run Screen Test button. (Note some screens may require additional parameters or previous drill downs to     access them. Place this in the DrillDrownID section).

 4.png

 

         4. This screen will return the data it is configured to return in the View Logs section at the bottom (In my example a list of Agents).

 5.png

 

5.  Results:

  • If data does return you have confirmed there is no issue for the user from a configuration perspective to obtain this data. Furthermore if you see differing results then that would point to a device side issue.
  • If data does not return then often a more detailed error message will present itself down below.

 

Test a Configuration download

 Use: You can confirm whether a configuration can be properly downloaded.

Benefit: Confirms whether your configuration can be properly downloaded. This simulates a device after login when it attempts to download the configuration. 

  1. Follow the steps for Test Login.
  2. Take the SessionID at the bottom after a successful login and paste it into the SessionID section.
  3. Select Run Config Test button.

 6.png

 

         4.   Results:

  • If you are successful you should see your configuration display down at the bottom, with different sections of the Configuration Listed. If you are able to Download the Configuration this determines that the server has no issue producing it. If you are having issues downloading it to the Device it is likely that the size of the configuration is too big or there is a network, device, or client proxy issue.
7.png
  • If you are not successful it is possible that your configuration is corrupt. An error message should appear with additional information.


Manually Test Device Screen Requests

Use: Testing whether a user can obtain data for a device request.

Benefit: Allows you to see additional error information should a user not be able to access a screen within the configuration on the device. 

  1. Have the user reproduce the issue on their device.
  2. Launch AppStudio.
  3. Select the App in question.
  4. Once it has loaded select the Log icon.
  5. Sort the Logs by this user’s User ID.
  6. Select the Submit button.

 8.png

      7.  Look in the logs for the screen in question (In my example this is Agent’s List). You should locate a:  ###Entering Service log line (see above)

      8.  Copy this full log line into a text editor (for my example see below).

http://beef.pyxismobile.com/scott72/mp/mdmController.aspx?action=2888&ViewID=3791&UserID=z7sGFKqTYCw~&AppID=1000&Platform=BB&SessionID=Q54KfEuuKbO1e1pWkg1+oRRUYEWj8FwcXTq30Oqx445L8/bhta+R9Q~~   ts= ###       cqis3qu0tx4cjveazvuip0s0

      9.   Select and copy only the URL to the Session ID which ends in ~~

http://beef.pyxismobile.com/scott72/mp/mdmController.aspx?action=2888&ViewID=3791&UserID=z7sGFKqTYCw~&AppID=1000&Platform=BB&SessionID=Q54KfEuuKbO1e1pWkg1+oRRUYEWj8FwcXTq30Oqx445L8/bhta+R9Q~~

     10.   Paste this into the URL field in the Manual Test Section of the Test Page.

     11.   Select the Run URL button.

 9.png

     12.   This should return data for that particular screen (In my case the List of Agent’s) at the bottom.

 10.png

 

Results:

  • If data is returned then you should expect data to be returned to the user’s device.
  • If data is not returned on the test page then additional error information will present itself at the bottom of the Test Page.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk