Monday, February 6, 2017

Queues and Routing

A queue is where Alliance Access stores message instances.
A routing point is where message transformation takes place in Alliance Access.
Routing points consist of these elements:

• a queue where messages are stored
• a message processing function
• a set of routing rules.

An exit point is a special routing point that Alliance Access uses to route message instances to
external applications (message partners). The system configures generic exit points to allow
default processing of all kinds of messages by default, but operators can define their own exit
point for specific routing purposes. In addition to these exit points, operators can also create
user-defined queues for other needs.

Additional queues are sometimes also available while installing the ADK component. Those
queues are considered as ADK queues.

Messages are routed and processed in Alliance Access until they reach their final destination.
The processing of messages takes place at "routing points" where the messages are stored in
queues. These can be divided into system queues and user-defined queues and exit points.
Associated with a routing point is a Message Processing Function (MPF) which typically
fetches, processes and then routes (according to the routing rules associated with the routing
point) the messages in the queue at the routing point.

Each routing point queue can be controlled by holding or releasing it to stop and start the flow of
messages. Queue thresholds can be set to generate warnings when the number of messages
in a queue reaches a specified level. Also, if a message is older than the maximum message
age limit that is set, then the queue is put in an exceptional state and an event (by default
configured as an alarm) is logged.

3 comments:

  1. Dear,
    I have a question concerning the ADK queue in SWIFT:
    In the Exit Point configuration (in SAA 7), we can choose the messages processing order: PRIORITY or FIFO.
    But in the queues type ADK, we don't have the option to choose the messages processing order. Is there a default processing order for ADK queues? Or it depends on the developed components?
    Thanks in Advance

    ReplyDelete
  2. You must read product manual. For example when you install SIDE SafeWatch, it installs PRE-DEFINED QUEUES and message processing function.

    OFCS-IN > OFCS Detect > if Success sends the message to Addresse

    ReplyDelete
  3. Incorrect
    It depends on the defined routing.
    Furthermore detect function is applicable when u have a triggered violation from a rank 90+ on safewatch. Only the built in alliance queue and create queue will allow you to choose processing order. Adk queue will be moved based on the defined integrated rules only

    ReplyDelete