3.4.6 Monitoring JMS Queues

This topic describes the systematic instructions to Monitoring JMS Queues.

OFSLL uses MDB infrastructure as an interface for asynchronous communication with third party integrated applications and all the outgoing communications through all the interfaces are tracked in JMS Queues tab.

The JMS Queues tab in System Monitor screen facilitates as a dashboard to monitor the status of all the configured MDB (Message-driven Bean) queues and provides a statistics of the total messages/requests that are sent from OFSLL to external system along with their status.

The JMS Queues tab has the following sub tabs:
  • Status sub tab - to view the last status of configured MDB
  • Messages sub tab
    • To view the list of configured interfaces and total messages triggered to the interface.
    • To view the status of response for the message received from the interface.
    • To Re-submit failed messages.
To view the status of all the configured MDB
  1. On the Dashboard, click Dashboard. Under Dashboard, click System Monitor. Under System Monitor, click JMS Queues. Under JMS Queues, click Status.

    The Status screen displays.

  2. For more information on fields, refer to the field description table.

    Table 3-16 Status

    Field Description
    Service Displays the name of the message service suffixed by MDB to differentiate the different MDB services.
    Description Displays the description or abbreviated name of MDB interface.
    Last Updated Status
    Displays the status of MDB interface. Following are the status displayed:
    • UNKNOWN - indicates that no MDB infrastructure is connected or status ping message is not sent to that MDB.
    • SUBMITTED - indicates that a dummy ping message is sent to MDB.
    • RUNNING - indicates that the message is consumed by MDB infrastructure.
    • STOPPED - indicates if MDB infrastructure is down.
  3. In the Status section, select the required service for which user need the status and Click JMS-MDB_Status_button button. On clicking, a dummy ping is sent to the interfaced server and status in Last Updated Status column is updated as SUBMITTED.
  4. Click Refresh refresh button, to fetch the latest status and the response received is updated in Last Updated Status column.
To view all messages triggered to configured MDB
  1. On the Dashboard, click Dashboard. Under Dashboard, click System Monitor. Under System Monitor, click JMS Queues. Under JMS Queues, click Messages.

    The Messages screen displays.

    Figure 3-8 JMS Queues - Messages



  2. In the Messages section, filter the list of messages using the following options:

    Table 3-17 Messages

    Field Description
    Company Select the required Company from the drop-down list to view JMS message at company level. The list is populated only with those Company Definitions to which user have been provisioned access. By default, ALL is selected.
    1 Day All the types of jobs selected in Jobs Type section in last one-day.
    1 Week All the types of jobs selected in Jobs Type section in last one-week.
    1 Month All the types of jobs selected in Jobs Type section in last one-month.
    By Date All the types of jobs selected in Jobs Type section for specific duration. User can specify a date range (within 3 months) in Start Dt and End Dt fields using the adjoining calendar.
    Refresh Refresh The Messages section displays the list of configured interfaces and the total of messages exchanged between OFSLL and MDB in Submitted, Completed, Failed and Resubmitted status. Click Refresh refresh button to update the latest status.
  3. In the Messages section, user can view the following details:

    Table 3-18 Messages

    Field Description
    Service Displays the name of the message service suffixed by MDB to differentiate the different MDB services.
    Description Displays the description or abbreviated name of MDB interface.
    Submitted Displays the total count of requests submitted.
    Completed Displays the total count of requests completed.
    Failed Displays the total count of requests failed.
    Resubmitted Displays the total count of only those requests which are failed and resubmitted again for processing.
To ‘Re-submit’ failed messages
  1. The Message Details section below displays the list of messages sent to the interface with the following details:

    Table 3-19 Message Details

    Field Description
    View User can click View to display the selected record in message details section.
    Refresh Refresh In the Message Details section, select the message in Failed status. Click Refresh refresh button to update the latest status.
    Message ID View the system generated MDB message ID
    Request Type View the message request type
    Request SubType View the message request sub type
    Message Type View the message identifier
    Status View the message processing status
    Response

    This column data is displayed only for Webhook MDB.

    View the HTTP Header received as response during Webhook event action invocation.

    Message Content View the message content
    Time View the message time stamp
  2. Click Re-submit. The details are triggered again for processing and the Resubmitted counter in Messages section is updated along with other counters.

Response Message Details

This section is enabled, if Events or Webhook type of MDB service is selected in Message section and displays the request Message Details that is propagated to external system for the posted event action.

To view ‘Response Message Details’ of an Event
  1. Select the required record from the Message Details section and click Show File.

    The first 50 characters of the request in json format is displayed since the default preference selected is Beginning in View option and # of Characters is set to 50.

  2. User can customize the preference using View Option (Beginning/End) and specifying the number of characters to be displayed.
  3. Also user can click Show All to display the complete request.