An Overview of the Message System

Introduction

The Messaging System module of Oracle Banking Treasury Management is designed to handle outgoing and incoming messages. The module supports various types of media. Besides standard media modes like Mail, Telex and SWIFT, other media types also can be used which are supported by the Media Control System (MCS) installed at the node at which the database of the branch is installed. Oracle Banking Treasury Management gives native support for media like Mail, Telex, and SWIFT using EMS as the MCS.

While defining a product, specify the messages to be generated for the events occurs during the lifecycle of contracts. During such events, the message will be automatically generated and sent to the customer’s address through the specified media and in the format and language that is maintained for the customer–message combination.

While entering the details of a contract, choose to generate or suppress the message. There is an option to prioritize the urgency with which a SWIFT message should be generated.

Features Provided for Processing Outgoing Messages

In the case of outgoing messages, the module provides for the generation of messages using formats that can be defined. Maintaining message formats ensure consistency across the branches of the bank. The module provides a host of features to enter or authorize test words and to interface with media control systems to generate the message.

Several customers addresses for a given media: With multi-branch setup, the customers of the bank can operate their accounts from several locations. Based on the convenience of the customers, send messages to locations of their choice. Oracle Banking Treasury Management provides for the setting up of several addresses for a given customer-media combination. In addition, associate a language with an address. All messages sent to the address will be expressed in the language that is defined.

Free format messages: In the course of daily banking operations, it might required to generate messages that are not automatically generated by the system or to communicate a message that is very specific to a customer. It is possible to personalize a message by defining a free format message and linking it to a customer-address combination. Whenever the message is to be generated it will bear the personalized format that is defined.

MCS maintenance: The messages that are sent from and delivered to the bank are transmitted and received from external sources to Oracle Banking Treasury Management. These external sources are called Media Control Systems (MCS). In a distributed environment, the database of a branch is located in a node or server. The MCS of the messages is also installed in a node. Thus, while defining an MCS, specify the node in which it is installed.

Features Provided for Processing of Incoming Messages

In case of incoming messages, set up various message queues and direct incoming messages to them and also grant selective access to the queues to personnel at the bank who are authorized to handle incoming messages.

Archival and Retrieval of Information

Archival is the process of storing old messages for future retrieval. While defining messaging preferences for the branch, specify the number of days for which an outgoing message should be kept in the Outgoing Message Browser. Messages will be automatically archived after the number of days specified for the branch. Retrieve the messages that have been archived at any time and process them just as any other messages.

Set- up Messaging Preferences

Specify messaging preferences that will govern the workflow aspects of the messaging system module at the branch. Specify the following preferences:

The number of days for which outgoing messages should be kept in the Browser for every branch
Whether a testword is required for Telex messages
The activities on a message that requires authorization
The PDE (Possible Duplication Emission) Archival period
The text for duplication check
The Hold Mail text to be displayed
The Swift Key arrangement values
Whether Authorization is required for the actions like Cancel, Hold, Change Node, Test Word. etc. on a generated message.

Message Notification Process

The messages that are sent from and delivered to your bank are transmitted and received from sources that are external to Oracle Banking Treasury Management and these external sources are called Media Control Systems (MCS).

In a distributed environment, the database of a branch is located in a node or server. The MCS of the messages are also installed in a node. Thus, while defining an MCS you need to also indicate the node in which it is installed.

Outgoing EMS Process

The Outgoing EMS Process is in two layers. The EMS process as part of jobs in FCJ scheduler, polls the outgoing message table for generated and un-send messages. The job then sends minimal data about the message to be handed off, to an internal JMS queue. The EMS process as part of an MDB that listens on internal JMS queue builds final message and sends to their intended destinations.

The ‘EMS out’ job is available as factory shipped.

The Outgoing EMS Process as part of jobs scheduler is as follows:

Once the job is triggered, it polls outgoing messages table for generated and unsent messages.
Each message is then sent to an internal JMS queue.
The job is then rescheduled to fire next time.

The Outgoing EMS Process in MDB is as follows:

An MDB listens on the internal EMS outgoing queue and it builds the final message sent to intended destinations.
In case of any exception while processing, message is sent to a deferred queue.

The following diagram illustrates outgoing EMS process in scheduler.

Figure 1-1 Outgoing EMS process in scheduler

Figure 1-2 Outgoing EMS process in MDB

Incoming EMS Process

The Incoming EMS Process is in two layers. The EMS process as part of jobs in FCJ scheduler, polls the pre configured folder for messages and sends the messages read, to EMS internal queue. The EMS process as part of an MDB listening on internal JMS queue, identifies the message from queue and calls the incoming messages service package to process the message. The ‘EMS in’ job is available as factory shipped.

The Incoming EMS Process as part of jobs scheduler is as follows:

Once the job is triggered, it polls for messages in a folder (Configured for incoming messages).
Each message is then sent to an internal JMS queue.
The job is then rescheduled to fire next time.

The Incoming EMS Process in MDB is as follows: 

An MDB that listens on the internal EMS incoming queue receives the message.
The media details are identified and incoming message processing package is called to process the message.
In case of any exception while processing, message is sent to a deferred queue.
In case of messages directly arriving to JMS queue instead of a folder; the same MDB is configured to listen on specific queue.

Figure 1-3 Incoming EMS process in Job Scheduler

Figure 1-4 Incoming EMS process in MDB