4.1 Introduction
Data exchanged between Oracle Banking Trade Finance and the external systems will be in the form of XML messages. These XML messages are defined in OBTF in the form of XML Schema Documents (XSD) and are referred to as ‘OBTF formats’. An XML Schema is uniquely identified by its Namespace and its Root Element (root node).The root node for XSDs of gateway messages will be generated as per the following pattern:
- <OPERATION>_<MESSAGE EXCHANGE PATTERN>_REQ
- <OPERATION>_<MESSAGE EXCHANGE PATTERN>_RES
- <OPERATION> refers to an Oracle Banking Trade Finance operation like QueryContract.
- <MESSAGE_EXCHANGE_PATTERN> refers to the request & response message patterns exchanged. The Message Pattern is of the following types:
- FS (Full Screen) -This indicates that the payload will contain all the elements on the corresponding Oracle Banking Trade Finance screen.
- IO (Input Only) - This indicates that the payload will contain the only input elements on the corresponding Oracle Banking Trade Finance screen.
- PK (Primary Key): This indicates that the payload will contain only the Primary Key elements of the corresponding Oracle Banking Trade Finance screen.
<MESSAGE_EXCHNAGE_PATTERN> is a combination of message patterns. The <MESSAGE_EXCHNAGE_PATTERN> available in OBTF is shown below:
- FSFS - Full Screen Request and Full Screen Response
- IOPK - Input Only Request and Primary Key Response
- IOFS - Input Only Request and Full Screen Response
Non-Query Formats
For example, consider the Operation ‘CREATECONTRACT’. The root node of messages under this operation will be as under:
- CREATECONTRACT_FSFS_REQ
- CREATECONTRACT_FSFS_RES
- CREATECONTRACT_IOPK_REQ
- CREATECONTRACT_IOPK_RES
Query Formats
For example, consider the Operation ‘QUERYCONTRACT’. The root node of messages under this operation will be as under:
- QUERYCONTRACT_IOFS_REQ
- QUERYCONTRACT_IOFS_RES