Quercus Message Link Monitor<>

Transactions screen

The Transactions screen allows you to see all the messages within Message Link. The screen is shown below:

Searching and filtering

There is a search region which allows you to both search for a message (search is performed on the Message ID and ID columns) and filter the messages by:

Message Queue — the queue that stores the message

Message Type — the type of the message (i.e. Biographic Data, Course Data, etc)

Status — the status of the message (Ready, Processed, Expired, etc)

Columns displayed

There are two different sets of columns displayed in the Transactions report. There is a list of core columns which are displayed for all the queues, but also some queue specific columns, which are displayed depending on which queue has been selected.

Core columns

Message ID — Is the ID of the message — internally generated by Quercus Plus

Message Type — Is the type of the message (Course Data, Biographic Data, etc)

Enq Time — represents the time when the message was enqued by either Quercus Plus (if it is an Outbound message), or by an external system (if it is an Inbound message)

Deq time — represents the time when the message was dequeued by either Quercus Plus (if it is an Inbound message), or by an external system (if it is an Outbound message)

Status — is the status of the message. Possible statuses are:

Ready — message is ready to be consumed

Waiting — message will be consumed after the waiting period will pass

Processed — message was already processed/dequeued and will remain in the queue for a given retention time

Expired — the message has not been dequeued because either the expiration time has passed, or because the maximum number of dequeue attempts specified for the queue has been reached.

Queue-specific columns

Initial Queue

Table Name — name of the parent table against which the UPDATE/INSERT operation took place

Object ID — Parent table record ID, against which the UPDATE/INSERT operation took place

Out and In Queues

ID — Is a quick way to find the messages related to a person, a course, a module, etc. For each message type, this column stores a value of a relevant field.

The message types along with the message related field that is displayed in this column:

Course Data — Course Code

Biographic Data — Student ID Number

Module Data — Module Code

Student Enrolment — Student ID Number

Fee Transaction — Student ID Number

XML — by following this link, you will be able to see the message XML payload.

In Queue

Validation Status — Messages that have failed the validation process — resulting in having a corresponding message in the Hospital Queue, will have this field set to “INVALID”.

Hospital Queue (apart from the fields specific to the Out and In queues)

Validation Failure Code — represents the message In validation failure code

Validation Failure Description — shows a more detailed description of the failing reason

Apart from filtering on Message Type, the Hospital Queue view allows you to filter the messages on the Validation Failure Code as well. Below you may find the list of possible values:

Message Type field is empty

Message Type field is invalid

Message ID field is empty

GUID field is empty

Surname field is empty

Course Code field is empty

Course not found

Course Instance Code field is empty

Course Instance Code field is invalid

Course Instance not found

Module Code field is empty

Module not found

Academic Session field is empty

Academic Session field is invalid