The Outgoing EMS Process happens in two layers.

The EMS process as part of jobs in FCJ scheduler, polls the outgoing message table of Oracle Banking Corporate Lending 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 is part of an MDB that listens on the internal JMS queue to build the final message and to send to their intended destinations.

The Incoming EMS Process happens in two layers.

The EMS process as part of jobs in FCJ scheduler, which polls the pre-configured folder for messages and sends the messages read, to EMS internal queue.

The EMS process is part of an MDB, that listens to the internal JMS queue identifies the message from the queue, and calls the incoming messages service package in the backend to process the message. Additionally, the MDB can be made an independent unit to listen to external JMS to process incoming messages.

The Incoming EMS Process as part of the 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.

EMS processes in MDB are as follows:

An MDB that listens on the internal EMS incoming queue will receive the message.

The media details are identified and the incoming message processing package in the backend is called to process the message.

In case of any exception while processing, message will be sent to a deferred queue.

In case of messages directly arrive to the JMS queue instead of a folder; the same MDB will be configured to listen on a specific queue.