Saturday, February 4, 2017

List of System Queues

The queue of messages awaiting authorisation consists of:
  • Messages verified by the Message Approval application (the default message flow). These messages include those NAK'd by SWIFT and routed to verification from the modification queue.
  • SWIFT MT 999 messages, SWIFT FIN System Messages, and SWIFT APC system messages created by an operator through the Message Creation application.
  • FIN messages created by an operator through the Message Creation application, or messages manually corrected through the Message Modification application (including those NAK'd by SWIFT), provided the operator has the proper entitlements and permissions to move these messages directly into the authorisation queue.
  • Messages in CAS format received through the Application Interface when the disposition state requested by the CAS protocol specifies "Authorise" or when routing point "MP_authorisation" is requested.
  • Messages received through the Application Interface, if the message partner does not have the permission to bypass authorisation.
Acceptance criteria: Message instance cannot be a notification.
Assigned MPF: mpa
With the default routing rules, this MPF returns the following result:
  • Success: The message was processed successfully and is valid.
    Messages for the SWIFT network that produce this result are routed to the SWIFT outbound queue (_SI_to_SWIFT).
    Messages for the application (APPLI) network that produce this result are routed to an exit point specified in the message.
This MPF can also return the following result:
  • Failure

_MP_creation (Message Creation)

This is a transient queue for messages created by an operator through the Message Creation application, that is, FIN user-to-user messages (MT 101 to MT 999) and system messages.
A newly created message (when valid) gets queued when an operator invokes one of the commands to move or route the message onwards. If the operator uses the "Route" command, then the MPF invokes the services of the routing software to route the message onto the next queue. If the operator does not use the "Route" command, then the MPF itself moves the message directly into the queue selected by the operator.
Since the message is routed immediately after the MPF completes its processing, there will never be more entries in this queue than the total number of operators entering messages). These entries, however, are barely observable when the queue is monitored, because the time span during which these messages are queued is very short.
Acceptance criteria: Creator MPF must be mpc.
Assigned MPF: mpc
With the default routing rules, this MPF returns the following result:
  • Success: The message was successfully processed (created) and added onto the queue.
    By default, a SWIFT financial message producing this processing result is routed to the verification queue. SWIFT text messages are sent to _MP_authorisation.
This MPF can also return the following results:
  • Failure
  • Discard
  • Invalid message.

_MP_mod_emi_secu (Emission Security Modification)

This is a queue for messages that require authentication or authorisation. A SWIFT or MX message is added to the Emission Security Modification queue if Alliance Entry cannot authenticate it or authorise it. The messages in this queue are mostly input messages.
Acceptance criteria: Creator MPF must be mpc.
Assigned MPF: mpm
With the default routing rules, this MPF returns the following result:
  • Success: The message was successfully processed and is valid.
This MPF can also return the following results:
  • Failure
  • Discard
  • Invalid message.

_MP_mod_rec_secu (Reception Security Modification)

This is a queue for output messages that require authentication (only FIN messages allow authentication to be used). Alliance Entry and SWIFTNet Link use the related security mechanisms to authenticate and authorise output messages. The output messages that Alliance Entry and SWIFTNet Link cannot authenticate or authorise are first routed to this queue. If the message is being sent has failed PKI and digest authentication or the "authorisation to receive" checks, then it is routed to this queue. Then if the authentication, and authorisation are successful, the messages are routed according to the routing rules. If unsuccessful, the messages remain in the queue.
Acceptance criteria: Message instance must be an output message and must be an original instance.
Assigned MPF: mpm
This MPF can return the following results:
  • Success
  • Failure
  • Discard
  • Invalid message.

_MP_mod_reception (Modify After Reception)

This queue is for output SWIFT messages.
Acceptance criteria: Message instance must be an output message and must be an original instance.
Assigned MPF: mpm
This MPF can return the following results:
  • Success
  • Failure
  • Discard
  • Invalid message.

_MP_mod_text (Text Modification)

This is a queue for messages that have failed message validation, or messages that need data modification (only special fields cannot be modified, for example, sender). A SWIFT or MX message is added to the Text Modification queue, in most cases, if any of the following conditions apply:
  • If one or more errors exist in the construction, or syntax of a message, making it syntactically incorrect as far as Alliance Entry is concerned
  • If an error in the content of a message (for example, an incorrect amount) was identified during verification or authorisation
  • If a SWIFT message has been NAK'd by SWIFT due to the message being sent to an unknown address.
Note that any SWIFT message sent to an unknown address is NAK'd by SWIFT. The NAK'd message is added to the Text Modification queue, not the Transmission Modification queue.
Acceptance criteria: Message instance cannot be a notification.
Assigned MPF: mpm
With the default routing rules, this MPF returns the following result:
  • Success: The message was successfully processed and is valid.
This MPF can also return the following results:
  • Failure
  • Discard
  • Invalid message.

_MP_mod_transmis (Transmission Modification)

A SWIFT message is added to this queue if the integrated application address specified for the receiver of a message is not valid.
Acceptance criteria: Message instance cannot be a notification.
Assigned MPF: mpm
With the default routing rules, this MPF returns the following result:
  • Success: The message was successfully processed and is valid.
This MPF can also return the following results:
  • Failure
  • Discard
  • Invalid message.

_MP_recovery

In the event of a FIN cold start, all completed messages that are not yet identified as delivered are re-activated and routed to this queue.
Acceptance criteria: Message instance cannot be a notification.
Assigned MPF: mpa
This MPF can return the following results:
  • Success: The message was successfully processed (verified) and is valid.
    By default, a message producing this processing result is routed to the authorisation queue (MP_authorisation).
  • Failure.

_MP_verification

The queue of messages awaiting verification consists of:
  • FIN messages created by an operator through the Message Creation application, or messages manually corrected through the Message Modification application (including those marked by SWIFT) and following the default message flow
  • SWIFT messages in CAS format received from the Application Interface when the disposition state requested by the CAS protocol specifies "Verify" or when routing point "MP_verification" is requested
  • SWIFT messages received from the Application Interface, if the message partner does not have the permission to bypass verification.
Acceptance criteria: Message instance must be an input message and must be an original instance.
Assigned MPF: mpa
This MPF can return the following results:
  • Success: The message was successfully processed (verified) and is valid.
    By default, a message producing this processing result is routed to the authorisation queue (MP_authorisation).
  • Failure.

_SI_delivery_subset (Delivery Subset Queue)

This queue is assigned to an MPF process which updates the definitions of current SWIFT delivery subsets and the status of future subsets. The messages routed to this queue are notifications related to incoming MT 015, MT 055, and MT 067 messages. The system routing table associated with the SWIFT inbound routing point (_SI_from_SWIFT) creates these messages. The notifications are completed after being processed. The following entries can be found in the queue:
  • Notification related to an incoming MT 067. This response to an MT 047 redefines current subsets.
  • Notification related to an incoming MT 055. This response to an MT 035 redefines current subsets.
  • Notification related to an incoming MT 015 - Delayed NAK. SWIFT cancelled the MT 047 request due to an invalid definition of subset criteria. The notification updates the status of future subsets.
  • Notification related to an outgoing MT 047. This notification updates the status of future subsets.
Acceptance criteria: Message format must be SWIFT
Assigned MPF: _SI_delivery_subset
This MPF can return the following results:
  • Success
  • Failure.

_SI_from_SWIFT (SWIFT Inbound Queue)

This is the transient queue through which all MT messages received from SWIFT are routed to various routing points and exit queues. An incoming SWIFT MT message gets queued on its arrival in the system, and then routed immediately after the MPF completes its processing.
Consequently, there is never more than one entry in the queue at any given point in time. This entry, however, is barely observable when the queue is monitored because the time span during which the message is queued is very short.
Thus, in practice, the message count of this queue always reads "0".
Acceptance criteria: Creator mpf must be _SI_from_SWIFT.
Assigned MPF: _SI_from_SWIFT
With the default routing rules, this MPF can return the following results:
  • Authorisation not present: No authorisation record was found.
    By default, an incoming message producing either of these processing results is routed to the re-authentication queue (_MP_mod_rec_secu).
  • FINCopy service Bypassed: When a Central Institution maintaining a FINCopy service has a problem, one of the fallback options for the Central Institution is to ask SWIFT to set the service into bypass mode. For more information, see the information regarding fallback in the FINCopy Service Description.
    In such a case, the PAC trailers contain no value. It is this criteria that is caught by the routing when you select the result FINCopy service Bypassed.
  • Failure: The incoming message failed authentication, using all three receive keys.
    By default, an incoming message producing this processing result is routed to the re-authentication queue (_MP_mod_rec_secu).
  • Invalid Certificate Policy ID: No valid certificate policy ID was found.
    By default, an incoming message producing this processing result is routed to the re-authentication queue (_MP_mod_rec_secu).
  • Invalid digest: The digest values do not match.
    By default, an incoming message producing this processing result is routed to the re-authentication queue (_MP_mod_rec_secu).
  • Invalid Sign DN: The login and select acknowledgement has not been signed by a valid Sign DN.
    By default, an incoming message producing this processing result is routed to the re-authentication queue (_MP_mod_rec_secu).
  • Not Authorised by RMA: A valid enabled authorisation was found, but the message was not permitted.
    By default, an incoming message producing this processing result is routed to the re-authentication queue (_MP_mod_rec_secu).
  • Signature Auth. failure: The signature verification failed, this result can be applicable to the MAC equivalent or PAC equivalent signature.
    By default, an incoming message producing this processing result is routed to the re-authentication queue (_MP_mod_rec_secu).
  • Success: The incoming message passed checksum validation and authentication successfully.
    By default, a message producing this processing result is routed, according to its message type, to one of the following three exit queues:
    • the statement queue (Statement)
    • the system inbound queue (System)
    • the message inbound queue (Received).

_SI_from_SWIFTNet (SWIFTNet Reception Queue)

This is the transient queue through which all InterAct or FileAct messages received from SWIFTNet are routed to various routing points and exit queues. An incoming MX message gets queued on its arrival in the system, and then routed immediately after the MPF completes its processing.
Consequently, the queue does not contain more than one entry at any given point in time. However, this entry is barely observable when the queue is monitored because the time span during which the message is queued is very short. Thus, in practice, the message count of this queue always reads "0".
Acceptance criteria: Creator mpf must be _SI_from_SWIFTNet.
Assigned MPF: _SI_from_SWIFTNet
This MPF can return the following results:
  • Success: message is routed to the MXReceived queue
  • Failure: message is routed to the MXToBeInvestigated queue
  • Authorisation does not allow message
  • Authorisation not enabled
  • Authorisation not in validity period
  • No authorisation
  • Signature verification failure.
By default, an incoming InterAct message that produces one of these processing results is routed to the re-authentication queue (_MP_mod_rec_secu). For an incoming FileAct message, the message will not be stored in the interface and event 28117 will be generated.

_SI_system_msg (System Outbound Queue)

This is a transient queue for the APC and FIN system message (for example, MT 047 redefine delivery subsets) created using the SWIFT Interface application (SIA).
Since the messages are routed immediately to the SWIFT outbound queue (_SI_to_SWIFT) after the MPF completes its processing, there is never more than one entry in the queue at any given point in time. This entry, however, is barely observable when the queue is monitored because the time span during which the message is queued is very short.
Thus, in practice, the message count of this queue always reads "0".
Acceptance criteria: Creator mpf must be _SI_system_msg.
Assigned MPF: _SI_system_msg
This MPF can return the following results:
  • Success: The message was added successfully onto the queue.
    By default, a message producing this processing result is routed to the SWIFT outbound queue (_SI_to_SWIFT).
  • Failure.

_TR_NOTIF (Traffic Reconciliation Notification)

This queue is used for traffic reconciliation, for example, to match a message report to a message instance. The notification is created in the TR_NOTIF routing point.
Acceptance criteria: Creator mpf must be TR_REC.
Assigned MPF: TR_REC
With the default routing rules, this MPF can return the following results:
  • Delivered
  • Not delivered
  • Delayed delivery.
This MPF can also return the following result:
  • Not matched

_TR_REC (Traffic Reconciliation Received)

This queue contains all the network reports (MT 010, 011, 015 and 019) that must be matched to a message instance.
Assigned MPF: TR_REC
With the default routing rules, this MPF can return the following results:
  • Delivered
  • Not delivered
  • Not matched
  • Delayed delivery.

_Unroutable (Unroutable messages)

This is a queue to manage messages that cannot be successfully routed to any other queue in the case of a message not matching the acceptance criteria of a queue. It is the responsibility of the user to investigate and define what next to do with this message.
Assigned MPF: Dummy_mpfn
This MPF can return the following results:
  • Success
  • Failure.

No comments:

Post a Comment