Welcome to this session on Open Financial Service.

You will learn to enhance the

functionality of OFS by attaching routines at appropriate trigger points.

Trigger Routines -R15 1

 At the end of this session you should be able to
1. Describe the trigger points in the 4 different OFS modes
2. Write programs and attach them at these trigger points

Trigger Routines -R15 2

 Where do we attach OFS trigger routines ? OFS allows you to attach routines to
[Link] at specified trigger points.
Who launches these routines? These are launched by core OFS routines at different
points in the life cycle of a message
What purpose do OFS routines serve? These routines serve to convert or map the
message format , update local applications and populate the in queue automatically

Trigger Routines -R15 3

 The core OFS routines and the trigger routines that are launched by them are given below.

[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

[Link]
[Link]
[Link]
[Link]
[Link]

The [Link] & [Link] are launched by [Link]. The core OFS
routines [Link], [Link] & [Link] by directly or
indirectly launch [Link].

Trigger Routines -R15 4

 Let’s look at some of these routines;
[Link]
The routine specified here will be executed just BEFORE a message is
processed by OFS
Typically such a routine could convert or map the data received into the
required OFS message format.
Common variables will not be accessible to these routine.
This routine is executed in both the batch and telnet modes
[Link]
The routine specified here will be executed AFTER each message has been
processed but prior to sending back to it’s origin.
This helps convert the message from OFS to external format
The Common variables not available
This routine is also common to batch and telnet modes.

Trigger Routines -R15 5

 [Link]
This routine is called by the [Link] just prior to the
message been processed but after the [Link] has been triggered.
The Common variables are available at this stage.
This routine does not allow you to alter the message.
It is typically used to update local applications.
[Link]
This routine is called by the [Link] just AFTER the
message been processed but before the [Link] is called.
The Common variables are available at this stage.
This routine does not allow you to alter the message.
It is typically used to update local applications.
[Link]
This routine ise xecuted when the input directory defined in [Link] is
empty, i.e. there are no messages to process.
Typically such a routine could be used to populate the input directory with
OFS messages derived from a third party source.

Trigger Routines -R15 6

 [Link]
This routine is triggered when the Queue Manager service is started
[Link]
This routine is triggered when the Queue Manager service is closed

Trigger Routines -R15 7

 The table given here shows some of the trigger routines used within model bank.

Trigger Routines -R15 8

 Let us take a closer look at some trigger routines and their need with the help of a few
scenarios. The routines we will look at are

1. [Link]
2. [Link]
3. [Link]

Trigger Routines -R15 9

 A third party system is posting messages to T24. It sends messages in own format.
Each message contains a message id, transaction type, debit account, debit currency,
amount, credit account, credit currency. These details are written in simple comma
delimited format into a sequential file.
You need to convert the message into an OFS format

Trigger Routines -R15 10

 1. What are the things we need to do?
2. We need a place , a folder, where the third
party system can put it’s messages
3. Solution: Define a [Link] record of
type BATCH. Define the [Link]
where messages can be stored
4. We need to convert the messages to OFS
format
5. Solution: Write a routine to convert. Use
[Link]

Trigger Routines -R15 11

 Enter, compile the code shown above.
Make sure you register it in [Link].

Trigger Routines -R15 12

Trigger Routines -R15 13
 The bank also requires that the FT id generated by T24 and the message id are stored
in a separate CSV file for auditing and tracking.

Trigger Routines -R15 14

 We need to store the transaction id and message id in a file.
Solution: Write a routine to store the details on a file. What type of trigger routine? A
[Link] type.

Trigger Routines -R15 15

 Enter, compile the code shown above.
Make sure you register it in [Link].

Trigger Routines -R15 16

Trigger Routines -R15 17
 A sample [Link] record is shown above. Notice the two trigger routines
[Link] and [Link].

Trigger Routines -R15 18

 An [Link] entry for running OFS in batch mode is shown on this page.

Trigger Routines -R15 19

 •Verify the [Link] record to start the OFS Batch phantom.
•Enter a transaction using the CSV format into a file in the [Link] containing
transaction id, transaction type, debit account, debit currency, amount, credit account,
credit currency
•Check if you have received an output in the [Link]
•Check if you have a file called [Link] in the same [Link]

Trigger Routines -R15 20

 The bank has received Funds Transfer requests from various sources. These FTs are
still in an un-authorised state. The bank wants an OFS message to be automatically
created to authorise any each FundsTransfer record in an INAU status.

Trigger Routines -R15 21

 We need to form the OFS messages (that will authorise the FTs)
Solution : We need to write a routine
What will we do with these messages?
Solution: Write them into a queue. Yes, that would mean use OFS Batch mode and
it’s corresponding In Queue.
But when does this routine run?
Solution : Obviously, before the message is formed.

Trigger Routines -R15 22

 What are the routines that you cannot use?
•You cannot use a routine that is triggered for each message
That is, we cannot use - [Link],[Link], [Link], which can
be triggered for each message
•Which routines are not triggered for each message?
•[Link], [Link], [Link]

Trigger Routines -R15 23

 When the IN QUEUE is not populated, we write a routine to populate the IN QUEUE
and attach it to the [Link] field in [Link]

Trigger Routines -R15 24

 Enter, compile the code shown above.
Make sure you register it in [Link].

Trigger Routines -R15 25

Trigger Routines -R15 26
Trigger Routines -R15 27
Trigger Routines -R15 28
 Notice the In Dir Rtn added in this [Link]!

Trigger Routines -R15 29

 This screenshot shows the corresponding [Link] record to run the OFS Batch
process using the given [Link].

Trigger Routines -R15 30

 [Link] a FT
[Link] the [Link] record to start the
OFS Batch phantom.
[Link] if the [Link] is populated
[Link] if your have received an output in the
[Link]

Trigger Routines -R15 31

Trigger Routines -R15 32
 You should now be able to
1. Describe the trigger points in the 4 different OFS modes
2. Write programs and attach them at these trigger points

Trigger Routines -R15 34