Push Instance Monitor

Basic Search Parameters

• Mobile Application: Name of the mobile application. Use the drop-down menu to choose the correct mobile application.
• Scenario ID: Type of push, selected from the drop-down menu, to search for in the pushes in the application
• Time Limit: Use the drop-down menu to select a window of time. The default is set to All, which is equal to selecting all push instances. All instances are available unless the historical logs have been purged in SAP.
• Recipient User ID: User ID receiving the push
• Status Included: Status of the push instance on the middleware server. Choosing no status returns all push instances on the mobile application. Multiple statuses can be chosen for the search. The following are the different status levels and their meanings:
  • NEW - Set when data in SAP has changed and the system configuration indicates that a push process is needed. No other information is available or set when status is in the NEW stage.
  • ENQUEUE - Set when the push process program is running on the data that triggered the push process. During this time, the data is locked so that it cannot be changed during the push process.
  • PROCESS - Standard status. The push process agent processes the instance in the push register and determines the proper recipients of the push data. The push data have been prepared for each recipient in the outbound queue in order for Agentry to pick it up.
  • CANCEL - Set for a push instance if there are subsequent newer push instances in the push register for the same work order. In this case, only the last push instance is processed in order to prevent multiple pushes for the same work order sent to the same mobile device.
  • COMPLETED - Set when either no recipient is determined or all push recipients for the push have CLNT_CONF status with respect to the recipient’s push message.
  • SRV_COMP - Set for a push instance when all recipients have SRV_CONF status with respect to the individual push recipient’s push message. If there are multiple push messages for the same work order and the recipients are waiting for Agentry to pick up the work orders, only the latest push event is sent to Agentry and the rest are set to SRV_CONF automatically by the push fetch BAPI. This prevents multiple copies of the same work order sent to each client.
• Max. No. of Records: Default is set to 2,000. Type in maximum number of records returned.
• Search: Click Search to initiate the search process. If no results are valid in the search parameters, the message No Data Found displays in the Search Results table. If valid data is returned, it displays in the Search Results table according to the Settings and Filter setup configured by the administrator.

When you click Search in the Basic Search Parameters section, the Search Result table is populated, based on the parameter settings you selected.

Subscriber View Tab

The Subscriber View tab on the Push Instance Monitor panel provides a recipient list containing all users and detailed information about the push instance associated with their user IDs.

Push Instance Detail - Subscriber View

• User Name: Name of user who received the push instance
• Current Status: Status of the push instance at the time the search was performed
• Creation Time: Time the push instance was created
• Client Confirmation Time: Time and date that the client confirms it has received the push
• Server Confirmation Time: Time and date when the middleware server confirmed it received the push in its cache
• Cancellation Time: Time and date of a manual or automatic cancellation of a push. For example, if a new push is created, the old pushes can be manually cancelled, as they are now out of date.
• Expiration Time: Time and date of a push expiration. If a client does not pick up a push before it expires, it is shown here.
• Middleware Server Connection By User: Name of the Agentry server that the user is connected to.
• Outbound Message ID: Message ID
• Internal Package ID: Data package ID
• OTrigger Proc. Time: Time and date when the outbound trigger was processed

Push Scenario Info Tab

The Push Scenario Info tab on the Push Instance Monitor panel provides technical information about the selected push instance highlighted in the Search Result table. Information displayed in this tab is created and configured using the Configuration portal, Push Scenario Definitions panel.

Push Instance Detail - Push Scenario Info

• Scenario ID: Name of the push instance scenario
• Validity (Hr): Hours that the push scenario remains valid after the initial push to clients
• Mobile Application: Name of the mobile application where the push instance resides
• Source Type: Type of source object associated with the push scenario
• Source Object: Name of the mobile data object that contains the push scenario. The source object is created or modified in the Mobile Data Object configuration panel in the Configuration portal.
• Source Handler: Class handler associated with the source object for the push scenario
• Subscriber Type: Corresponds to the Subscriber Type in the Subscriber Settings section of the Push Scenario Definition panel in the Configuration portal.
• Distribution Type: Corresponds to the Distribution Type in the Distribution Settings section of the Push Scenario Definition panel in the Configuration portal. MDO, or mobile data object, is the only setting available.
• Distribution Object: Name of the distribution object that is set in the Distribution Settings section of the Push Scenario Definition panel in the Configuration portal.
• Distribution Handler: Name of the distribution handler associated with the mobile data object contained in the push instance. The distribution handler is selected or changed in the Mobile Data Object Configuration panel, General Setting tab in the Configuration portal.