3. Ofs Batch Mode

Open Financial Service

TEMENOS EDUCATION CENTRE Warning: This document, is protected by copyright law and international treaties. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under applicable law.” Information in this document is subject to change without notice

Session 3 - Objectives

At the end of this session you should be able to

  

Configure OFS.SOURCE for Batch mode Configure EB.PHANTOM Input and test OFS messages in the Batch mode

Slide 2

OFS.SOURCE

 

OFS.SOURCE contains the parameters for setting up a OFS connection into T24. Usually different OFS source records are used for each connection

Slide 3

3

OFS.SOURCE Key Fields To Understand Now Id Source Type In Queue Dir Out Queue Dir Syntax Type

Sample Data to fill out Id : TEST.BATCH Source Type :BATCH

Slide 4

4

OFS.SOURCE cont Key Fields To Understand Now Id Source Type In Queue Dir Out Queue Dir Syntax Type

Sample Data to fill out Id : TEST.BATCH Source Type :BATCH In Queue Dir :TRGIN

Slide 5

5

OFS.SOURCE cont Key Fields To Understand Now Id Source Type In Queue Dir Out Queue Dir Syntax Type

Sample Data to fill out Id : TEST.BATCH Source Type :BATCH In Queue Dir :TRGIN Out Queue Dir : TRGOUT Syntax Type : OFS

Slide 6

6

EB.PHANTOM

  

EB.PHANTOM controls all phantom and interactive jobs in T24. The control parameters for phantoms such as the name of the program to execute, sleep time etc are specified here We need to make OFS.QUEUE.MANAGER run as a phantom in order for OFS to pick up requests from the IN queue and process it.

Slide 7

7

EB.PHANTOM Key fields with sample data Fields

Sample data

Id

OFS.BATCH

Status

Blank or ACTIVE

Phant Stop Req

Blank or STOP

Run Mode

PHANTOM

Sleep secs

2

Globus In Pipe

NONE

Globus Out Pipe

NONE

Gts User Id

OFSUSER1

Ofs Source

TEST.BATCH

Run Routine

OFS.QUEUE.MANAGER

Slide 8

8

Running the Phantom



Verify the EB.PHANTOM record

Output of where command

Slide 9

9

Testing the batch mode

    

Sample enquiry ENQUIRY.SELECT,,INPUTT/123456,%ACCOUNT Create a record in your input queue (i.e. within TRGIN with an id of say ENQACCT). Enter the your enquiry into this record Once processed, the request will be removed from the IN queue . The response is written to the OUT queue into a record with the same id.

OFS.QUEUE.MANAGER

Slide 10

Check the output



Does your output look like this ?

Output of CT TRGOUT ENQACCT

Slide 11

One more test – a Transaction Request

ACCOUNT, /I/PROCESS, INPUTT/123123,,CUSTOMER=100724,CATEGORY=1001, CURRENCY=USD

Note:

 

All the mandatory fields of the application have to be filled. The id will be automatically generated by the system.

Slide 12

Check the output



Check if the output in your out queue looks like this

39087//1,CUSTOMER=100724:1:1,CATEGORY=1001:1:1,ACCOUNT.TITLE.1=AAA SHIPPING COMPANY OF PANAMA:1:1,SHORT.TITLE=AAA SHIPPING COMPANY OF PANAMA:1:1,POSITION.TYPE=TR:1:1,CURRENCY=USD:1:1,CURRENCY.MARKET=1: 1:1,ACCOUNT.OFFICER=27:1:1,CONDITION.GROUP=2:1:1,PASSBOOK=NO:1:1,OP EN.CATEGORY=1001:1:1,CHARGE.CCY=USD:1:1,CHARGE.MKT=1:1:1,INTEREST.C CY=USD:1:1,INTEREST.MKT=1:1:1,ALT.ACCT.TYPE=LEGACY:1:1,ALLOW.NETTIN G=NO:1:1,SINGLE.LIMIT=Y:1:1,RECORD.STATUS=INAU:1:1,CURR.NO=1:1:1,IN PUTTER=2_OFSUSER1___OFS_TEST.BATCH:1:1,DATE.TIME=0811012041:1:1,CO. CODE=GB0010001:1:1,DEPT.CODE=1:1:1

Slide 13

Controlling the Phantom

Key fields with sample data Fields

Sample data

Status (No input)

Blank or ACTIVE

Phant Stop Req

Blank or STOP

Slide 14

14

Workshop 3.1

Test the following OFS messages you wrote in workshop 1.1  Write a OFS message to input a SECTOR record with id 1200



Write a OFS message to input a new ABBREVIATION called UL for listing the USER records.



Write a OFS message to input a CUSTOMER record in T24. Use zero authorisers in your message

Slide 15

15

Workshop 3.2 – Enquiry Type Messages



Create a Enquiry type request to find the list of INDUSTRY records found inT24 environment.



Create an Enquiry type request to find the current day’s balance summary of an ACCOUNT (say for example 29987). (TIP: Use the enquiry ACCT.BAL.TODAY)

Slide 16

16

Authorize the transaction



How do you authorise?



To authorise the transaction, use the following message syntax. ACCOUNT,/A/PROCESS,AUTHOR/654321,39087



Did the record get authorised ? No? Why not?

Slide 17

17

Authorise …

39087//1,CUSTOMER=100724:1:1,CATEGORY=1001:1:1,ACCOUNT.TITL E.1=AAA SHIPPING COMPANY OF PANAMA:1:1,SHORT.TITLE=AAA SHIPPING COMPANY OF PANAMA:1:1,POSITION.TYPE=TR:1:1,CURRENCY=USD:1:1,CURRENCY.M ARKET=1:1:1,ACCOUNT.OFFICER=27:1:1,CONDITION.GROUP=2:1:1,PA SSBOOK=NO:1:1,OPEN.CATEGORY=1001:1:1,CHARGE.CCY=USD:1:1,CHA RGE.MKT=1:1:1,INTEREST.CCY=USD:1:1,INTEREST.MKT=1:1:1,ALT.A CCT.TYPE=LEGACY:1:1,ALLOW.NETTING=NO:1:1,SINGLE.LIMIT=Y:1:1 ,RECORD.STATUS=INAU:1:1,CURR.NO=1:1:1,INPUTTER=2_OFSUSER1__ _OFS_TEST.BATCH:1:1,DATE.TIME=0811012041:1:1,CO.CODE=GB0010 001:1:1,DEPT.CODE=1:1:1

In the OFS response , what is the user id shown in the INPUTTER field?

Slide 18

Problem-SAME AUTHORISER

  

When you sent another message via OFS to authorize this record (using the same BATCH mode), you should have got an error message “EB.RTN.SAME.NAME.AUTHORISER/INPUTTER” This is because the user context for a Batch mode is that of GTS user When you use the same batch record for inputting and authorising, you use the same GTS user and therefore the inputter and authoriser will be the same.

Slide 19

19

Solution-SAME AUTHORISER



To overcome this, set the field SAME.AUTHORISER in OFS.SOURCE to YES.



When this field is set, the same phantom can be used for input as well as authorization.

Discuss : What other solutions can you use?

Slide 20

20

Workshop 3.3



Write a OFS message to authorise the SECTOR record with id 1200



Write a OFS message to authorise the new ABBREVIATION called UL

Slide 21

21

Workshop 3.4 – Batch messages

   

Bank XYZ has it’s own software for capturing new account details. Since it uses T24 as the backend, the new account details are sent in a group to T24 using OFS. You will simulate a batch of messages to create 4 accounts. Use only a single batch file to store all 4 messages. Make sure that you input one message with missing parameters. Check what happens to the messages that come after this.

Slide 22

Quiz

Description

Who am I?

You can see me (a process) in the background when you verify EB.PHANTOM When OFS.QUEUE.MANAGER is run as a phantom, I supply the SMS context for OFS You use me( a field) to stop the phantom I specify the name of the file that is used as a queue

Slide 23

Important Points

      

Batch mode allows us ‘pump’ messages in a queue. A queue may be a folder or a particular file within a folder The important fields to setup in OFS.SOURCE are Id,Source Type, In.Queue.Dir,Out.Queue.Dir,Syntax.Type EB.PHANTOM must be configured to invoke OFS.QUEUE.MANAGER. The important fields in EB.PHANTOM are Status , Phant Stop Req , Run Mode,Sleep secs,Globus In Pipe,Globus Out Pipe,Gts User Id,Ofs Source,Run Routine When the Run Mode is specified as Phantom, the background process runs under the SMS context of the user given in this field. This user name is updated in the audit fields of OFS based transactions. The Same Authoriser field in OFS.SOURCE is used to overcome the issue of “same authoriser / inputter”

Slide 25

Summary

You should now be able to

  

Configure OFS.SOURCE for Batch mode Configure EB.PHANTOM Input and test OFS messages in the Batch mode

Slide 26