1.28 Notification Process

This topic describes the notification process for processing the parameters.

The notification process is in two layers. In the first layer the notification process as part of jobs in FCJ scheduler sends minimal data required for notification to an internal JMS queue. In the second layer the notification process as part of an MDB that listens on internal JMS queue builds final notifications and sends them to their intended destinations. The Notification Process in Treasury using the jobs scheduler is as follows:

1. The trigger on the base table inserts key details into a static notification log table instead of Oracle AQ.
2. Once Job is triggered, a request is sent to EJB layer from job execution class and the notification log table is polled for unprocessed records.
3. Each unprocessed record is locked.
4. The record is verified against the notification maintenance and checked whether notification is to be sent or not.
5. If notification is to be sent, pre notification message xml is built and it is sent to internal notify_queue (JMS queue).
6. The job is then rescheduled to fire next time based on the previous execution.

The notification process in MDB is as follows:

1. The Notification MDB listens on the internal notify JMS queue.
2. On any message received, the MDB identifies which schema to connect using the JNDI name being present as part of the message xml.
3. Gateway notification processing package is called from MDB in order to build the actual notifications.
4. In MDB the notifications built is processed and sent to the destination specified in corresponding notification.
5. In case of any exception the whole transaction is rolled back.
6. If all notifications are successfully processed then transaction is committed.

The flow chart of notification process in scheduler:

Figure 1-31 Notification Process in scheduler

Description of "Figure 1-31 Notification Process in scheduler"

The flow chart for notification process in MDB:

Figure 1-32 Notification Process in MDB

Description of "Figure 1-32 Notification Process in MDB"

• Process Notification Parameters
  

1.28.1 Process Notification Parameters

1. On the Home page, specify TRDNOTIF in the text box, and click next arrow.
   The Treasury Gateway Notification Maintenance screen is displayed.

   Figure 1-33 Treasury Gateway Notification Maintenance

   
   Description of "Figure 1-33 Treasury Gateway Notification Maintenance"
2. On the Treasury Gateway Notification Maintenance screen, specify the fields.

   For more information on fields, refer to the below table.

   Table 1-31 Treasury Gateway Notification Maintenance- Field Description

   Field	Description
   Notification Code	The system displays a unique code to identify a notification.
   Description	The system displays a brief description of the notification. However, you can modify the description in this screen.
   Operation	Select the type of operation for the notification from the following. Insert- Indicates a new operation of notification function Update- Indicates a modification operation of notification
   Gateway Operation	Specify the gateway operation name to execute query for the mentioned service.
   Gateway Service	Specify the gateway service to be used to get the full screen response.
   Request Node	Specify the gateway IO request node to be used in querying operation.
   Specific Notification	Select the Specific Notification check box to indicate the system to send specific notification. The system handles any deviation from generic notification process by creating specific triggers once you check this field.
   Full Screen Reply	Select the Full Screen Reply check box to indicate that the full screen notification response has to be sent. Otherwise, the primary key response notification is sent.
   Head Office	Select the Head Office check box to send notification only from head office.