1.7 Approach

This topic provides information on approach using the jobs scheduler.

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® FLEXCUBE Investor Servicing for generated and unsent 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 to build 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 as part of an MDB, that listens on internal JMS queue identifies the message from queue and calls the incoming messages service package in backend to process the message. Additionally, the MDB can be made an independent unit to listen on external JMS to process incoming messages.

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

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

The Incoming EMS processes in MDB are as follows:

1. An MDB that listens on the internal EMS incoming queue will receive the message.
2. The media details are identified and incoming message processing package in backend is called to process the message.
3. In case of any exception while processing, message will be sent to a deferred queue.
4. In case of messages directly arrive to JMS queue instead of a folder; the same MDB will be configured to listen on specific queue.