Ofs16.reference R08.02

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

QUICK REFERENCE

Slide 2

OFS.GLOBUS.MANAGER



Purpose:



Used for synchronous inter-application calls



Syntax OFS.GLOBUS.MANAGER(OFS.SOURCE.ID, OFS.MESSAGE)



Parameters

 



OFS.SOURCE.ID: In parameter. OFS.SOURCE record id of type GLOBUS OFS.MESSAGE : In o& out parameter. Passes in the OFS request and sends back the OFS Response

Other information:

  

Cannot be called from local API such as versions from R5 For internal use within core T24 code Even internally, usage mostly replaced with OFS.POST.MESSAGE

Slide 3

OGM– nice to know stuff

  

In scenarios where OFS.GLOBUS.MANAGER is already loaded in the session, the request is written into the queue specified in the OFS.SOURCE record under IN.QUEUE.DIR field O.G.M may only be used if the write cache is empty OFS.GLOBUS.MANAGER builds up its own OFS.SOURCE record if the OFS.SOURCE record id argument is not supplied.

Slide 4

OFS.POST.MESSAGE



Purpose:



 

Syntax: OFS.POST.MESSAGE(OFS.MESSAGE, OFS.MSG.ID, OFS.SOURCE.ID, OPTIONS) Parameters :

   



Used for asynchronous inter-application calls.

OFS.MESSAGE : In parameter. The OFS message to be processed OFS.MSG.ID: Out parameter. Auto generated message id. OFS.SOURCE.ID: In parameter. OFS source record id of type Globus Options: reserved for future use

Other information:

   

Writes onto a queue named F.OFS.MESSAGE.QUEUE. Queue processed by OFS.MESSAGE.SERVICE Response is written on to an out queue named F.OFS.RESPONSE.QUEUE. OFS.RESPONSE.QUEUE purged using OFS.RESPONSE.SERVICE

Slide 5

OFS.BUILD.RECORD



Purpose:



OFS.BUILD.RECORD is a routine that builds up a OFS message



Syntax:



OFS.BUILD.RECORD(APP.NAME,OFSFUNCT,PROCESS,OFSVERSION,G TSMODE,NO.OF.AUTH,TRANSACTION.ID,RECORD,OFSRECORD) Parameters:

        



APP.NAME : Application Name OFSFUNCT : The function (I, A, R or D) PROCESS :should always be PROCESS or BR.PROCESS OFSVERSION : the version GTSMODE : GTS Control value NO.OF.AUTH : no of authorisers TRANSACITON.ID : transaction id. RECORD : data in dynamic array format OFSRECORD : out parameter which contains the OFS message

Other information:



No provision for user information.

Slide 6

OFS.REQUEST.MANAGER



Purpose:

 



Parameters:

 



THE.MSG: The Ofs message to process TXN.ID: Out parameter. Record id of the transaction .

Other information:





Routine that executes OFS requests Check for OFS message type (transaction, enquiry, clearing) and calls the appropriate code

Cannot be called from local APIs

Triggers

 

MSG.PRE.RTN MSG.POST.RTN

Slide 7