Home

Oracle Part Number E51575-01

1. 6 2 2 1 CheckBookNew This is the operation code for creating new Cheque Book in Oracle FLEXCUBE It involves the following messages CheckBookNew Req Full This is the request message to create new cheque book in Oracle FLEXCUBE UBS An external system which intends to create a new cheque book has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CheckBookNew Req lO This is the request message to create new cheque book in Oracle FLEXCUBE UBS An external system which intends to create the cheque book has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for creating a new cheque book CheckBookNew Res Full This is the response message which is sent back to the external system when a new cheque book is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CheckBookNew Res PK This is the response message which is sent back to the external system when anew cheque book is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primar
2. Corporate deposit operations are logically grouped under a service called FCUBSLDService Oracle FLEXCUBE supports the following operations under this service LDActivateSimulate DeleteLDSIMContract QueryLDSIMContract LDVamiCreateSim LDVamiQuerySim QueryLDPaymentSim CreateLDPaymentSim 6 2 4 1 LDActivateSimulate This is the operation code for activating corporate deposits simulation in Oracle FLEXCUBE It involves the following messages LDActivateSimulate Req Full This is the request message to activate corporate deposits simulation in Oracle FLEXCUBE UBS An external system which intends to activate corporate deposits simulation has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen 6 8 ORACLE LDActivateSimulate Req IO This is the request message to activate corporate deposits simulation in Oracle FLEXCUBE UBS An external system which intends to activate corporate deposits simulation has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for activating corporate deposits simulation LDActivateSimulate Res Full This is the response message which is sent back to the external system when corporate deposits simulation is successfully activated in Oracle FLEXCUBE
3. This manual is intended for the following User User Roles IT department members responsible for Input functions for maintenance related to the integration gateway Acronyms and Abbreviations FLEXCUBE UBS FLEXCUBE Universal Banking Solution Organization The manual is organized in the following manner Chapter 1 About this Manual gives information on the intended audience It also lists the various chapters covered in this User Manual Chapter 2 Gateway Functions An Overview explains the features of this module Chapter 3 External System Maintenance explains the maintenance of external systems and the various processes involved Chapter 4 Message Formats explains the different message formats Chapter 5 FLEXML Adapter Message Conversion explains details about the FLEXML Adapter Conventions Used in this Manual Important information is preceded with the symbol 1 1 ORACLE 1 2 Glossary of Icons This User Manual may refer to all or some of the following icons Copy a iB gt a ue Delete row Option List 1 2 ORACLE 2 Execute Query Refer the Procedures User Manual for further details about the icons 1 3 ORACLE 2 1 2 2 2 2 1 2 Gateway Functions An Overview Introduction Integration of different applications and solutions is a key area in today s systems A variety of specialized applications deployed on disparate platforms and using differ
4. An external system which intends to query LD payment simulation has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying LD payment simulation e QueryLDPaymentSim Res Full This is the response message which is sent back to the external system when LD payment simulation is successfully queried in Oracle 6 10 ORACLE FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 2 4 7 CreateLDPaymentSim This is the operation code for creating LD Payment Simulation in Oracle FLEXCUBE It involves the following messages e CreateLDPaymentSim Req Full This is the request message to create LD payment simulation in Oracle FLEXCUBE UBS An external system which intends to create LD payment simulation has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e CreateLDPaymentSim Reg lO This is the request message to create LD payment simulation in Oracle FLEXCUBE UBS An external system which intends to create LD payment simulation has to send the request in the specified format The format of the message is called Input only which has on
5. By DOCS Date Time Modification Number authorized ance Authorized By Date Time iv Open In the above screen you need to specify the following details External System Select an external system for which you wish to provide access rights The adjoining option list displays all the external systems you have maintained in the External Systems Detailed screen Function ID Select a Function ID from the list of values by clicking the adjoining option list The function ids are invoked from Gateway Functions 3 4 ORACLE 3 2 1 Action Select an action for the external system from the option list provided Service Name This displays the service name based on the Function ID and Action you select Operation Code This displays the Operation Code based on the Function ID and Action you select Viewing External System Function Details You can view the access rights details which have already been defined using the External System Functions Summary screen as shown below You can invoke this screen by typing GWSEXFUN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External System Functions Summary Authorization Status Record Status External System LH Function Action Search Advanced Search Reset Export Records per page 115 lt 1 of ara Go to Page C Authorization Status Record Status External System
6. FLEXCUBE UBS Inbound Application Gateway provides XML based Services These services consist of one or more Operations These operations can be invoked by any external system to perform the relevant operation in Oracle FLEXCUBE UBS The services supported by the Gateway are listed below e FCUBSFTService e FCUBSAccService e FCUBSDDService e FCUBSLDService e FCUBSCustomerService FCUBSFTService All funds transfer operations are logically grouped under a service called FCUBSFT Service Oracle FLEXCUBE supports the following operations under this service e CreateMt101 e AuthorizeMt101 e DeleteMt101 e ModifyMt101 e QueryMt101 e CreateFTContract e AmendFTContract e QueryFTContract 6 2 1 1 CreateMt101 This is the operation code for creating Mt101 message in Oracle FLEXCUBE It involves the following messages e CreateMt101 Req Full This is the request message to create Mt101 message in Oracle FLEXCUBE UBS An external system which intends to create Mt101 message has to send the request in the format specified The format of the message Is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e CreateMt101 Req IO This is the request message to create Mt101 message in Oracle FLEXCUBE UBS An external system which intends to create Mt101 message has to send 6 1 ORACLE the request in the specified format The form
7. The format of the message is called Primary Key response which includes only the primary key fields of the cheque book in the Oracle FLEXCUBE data store 6 2 2 3 CheckBookQuery This is the operation code for querying new Cheque Book in Oracle FLEXCUBE It involves the following messages e CheckBookQuery Req Full This is the request message to query a cheque book in Oracle FLEXCUBE UBS An external system which intends to query a cheque book has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e CheckBookQuery Req lO This is the request message to query a cheque book in Oracle FLEXCUBE UBS An external system which intends to query a cheque book has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying a cheque book e CheckBookQuery Res Full This is the response message which is sent back to the external system when a cheque book is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CheckBookQuery Res PK This is the response message which is sent back to the external system when a c
8. UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen LDActivateSimulate Res PK This is the response message which is sent back to the external system when an existing corporate deposits simulation is successfully activated in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the corporate deposits simulation in the Oracle FLEXCUBE data store 6 2 4 2 DeleteLDSIMContract This is the operation code for deleting LD simulation contract in Oracle FLEXCUBE It involves the following messages DeleteLDSIMContract Req Full This is the request message to delete LD simulation contract in Oracle FLEXCUBE UBS An external system which intends to delete LD simulation contract has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen DeleteLDSIMContract Req lO This is the request message to delete LD simulation contract in Oracle FLEXCUBE UBS An external system which intends to delete LD simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for deleting LD simulat
9. applied to convert the message from FLEXML format to GW format 7 GW EJB component is invoked which processes the request and replies with a message in gateway format 8 XSLT is applied to convert GW reply message to FLEXML format 9 The reply message is logged in table if the value of the property file parameter FXG_MSG_LOG_FLG ts Y 10 Reply message in FLEXML format is send back to the external system Outbound FLEXML Adapter An outbound adapter notifies any internal events within Oracle FLEXCUBE to the external system For eg internal events associated with static maintenances or transactions that happen in Oracle FLEXCUBE need to be communicated to the external system FLEXML uses the handoff mechanism to transfer data to the external system whereas Gateway uses notification process for the same Handoff messages contain complete transaction information but notification message contains only the primary key of the transaction Processing Outbound Messages The outbound messages to the external system are processed as follows 1 Outbound adapter receives request notification XML message from the notification queue 2 Notification code is retrieved from the notification message 3 Using XSLT maintenance table and notification code query XSLT handoff XSLT and all the externals system names related to the notification code are retrieved by the adapter 4 Query XSLT is applied to convert GW notification XML message to
10. e FCUBS_ BODY This node contains the actual payload of a message The contents of this node will vary for each message 4 2 ORACLE FCUBS HEADER 4 2 1 FCUBS HEADER The tags under FCUBS HEADER have been described below SOURCE This indicates the name of the External system that is the source of the message UBSCOMP This indicates the Oracle FLEXCUBE component of the message whether FCIS or FCUBS MSGID 4 3 ORACLE This unique ID identifies each message incoming or outgoing in Oracle FLEXCUBE Every message will have a distinct message ID CORRELID This is the id using which any system which has sent a request to FC UBS can correlate to the response In the External system maintenance the Correlation Pattern can be configured for each external system It can be maintained that either the MSGID or the CORRELID of the request message is returned back as the CORRELID in the response message Depending on this maintenance Oracle FLEXCUBE will set either the MSGID or the CORRELID of the request message in the response message USERID For request messages this ID is used to submit message requests Oracle FLEXCUBE will process this request using this id For response messages the value of this will be null BRANCH This indicates the Oracle FLEXCUBE Branch Code where the request message needs to be processed If the BRANCH is missing in the header request message will be transmitted
11. request message to create transaction in Oracle FLEXCUBE UBS An external system which intends to create transaction has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen Create Transaction Req lO This is the request message to create transaction in Oracle FLEXCUBE UBS An external system which intends to create transaction has to send the request in the specified format The format of the message Is called Input only which has only those fields that are actually required for creating a transaction CreateTransaction Res Full This is the response message which is sent back to the external system when transaction is successfully created in Oracle FLEXCUBE UBS The 67 ORACLE format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen Create Transaction Res PK This is the response message which is sent back to the external system when a transaction is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the transaction record in the Oracle FLEXCUBE data siore 6 2 3 2 QueryDDTransaction This is the operation code for querying DD Transaction in Oracle FLEXCUBE
12. sent back to the external system when a TD simulation is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the TD simulation in the Oracle FLEXCUBE data store 6 2 2 5 QueryGenAdvice This is the operation code for querying GenAdvice in Oracle FLEXCUBE It involves the following messages QueryGenAdvice Req lO This is the request message to query GenAdvice in Oracle FLEXCUBE UBS An external system which intends to query GenAdvice has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying GenAdvice QueryGenAdvice Res Full This is the response message which is sent back to the external system when GenAdvice is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 2 3 FCUBSDDService All the demand draft operations are logically grouped under a service called FCUBSDDService Oracle FLEXCUBE supports the following operations under this service CreateTransaction QueryDDTransaction 6 2 3 1 CreateTransaction This is the operation code for creating transaction in Oracle FLEXCUBE lt involves the following messages Create Transaction Reg Full This is the
13. will communicate with Oracle FLEXCUBE Define a valid queue name as the Default Response Queue Dead Letter Queue If the messages received are non readable such messages are directed to Dead Letter Queue defined for the external system If the Dead Letter Queue is not defined such messages will be redirected to a queue with the name of the request queue appended with E XSD Validation Required Check this box to indicate if the request message should be validated against its corresponding XSD Register Response Queue Message ID Check this box to indicate if the message ID provided by the Response Queue should be logged when a response message is posted into the queue 3 1 1 5 Specifying External System Queue Details The External System Queues list contains the In Queue and Response Queue lists To add a record to the External System Queues list click add icon To delete a record from the list select the record using its check box and then click delete icon In Queue Specify the name of the queue from which the messages were received The name of the queue will help identify the external system This is required only if an incoming message does not display the source of the message An In Queue is mapped to only one External System You can map multiple queues to a source System will allow a source to post messages to multiple queues 3 2 ORACLE Response Queue You can define Response Qu
14. 1 7 1 INTRODUCTION ciu ai 7 1 T2 HANDLING PLANNEDOUTAG E Sisi EER IAEE ANE 7 1 laad A nn E E E O E O N E A E 7 1 Laa INTA E esp eeu os ct OU E O O 7 1 23 TAOS os 7 2 7 2 4 Host Up Slari Replay irom POSS altos 7 2 Tava PT ind 7 3 7 3 SERVICES SUPPORTED DURING OUTAGE Sida dia 7 4 7 3 1 AR A E o DO II E 7 4 7 3 2 RT COC OCI APM Sn II Ee eee ae ee PC ee ee eee 7 4 7 3 3 o AMM o a UU 7 4 7 3 4 ERIN AA Un NI ee ee eT 7 4 7 3 5 TELE CEDE PO Rn Ae a SP 7 4 7 3 6 TC ECD ED S oe ne ee a nen aE eee nT eae E 7 4 TIN PEUBSACO IV eee ee ene Ee Ee een en en eee re 7 4 7 3 8 PEU BS CUSTOMS INC ceca onaas 7 5 7 3 9 DG 05 5501 0 OU A ito 7 5 CUBOS 2 x eee ee en A A ee eee ae ee ee 7 5 ck IN A ee oe See 7 5 Pda PE UN SS COI T E EEA EEEE AEAEE A E 7 5 Tado TOC TS SVU IV CC sararea EENE 7 5 ORACLE 1 1 1 1 2 1 About this Manual Introduction This manual is designed to help you quickly get acquainted with the Integration Gateway of Oracle FLEXCUBE It provides an overview to the module and provides information on using the Integration Gateway module of Oracle FLEXCUBE You can further obtain information specific to a particular field by placing the cursor on the relevant field and striking lt F1 gt on the keyboard Audience
15. 1 PUESIA AA O UE A aeons ties 4 3 4 2 2 Ta 0 PAM E e O O UE REO o E 4 5 4 3 ORACLE FLEXCUBE NOTIFICATION sssssssccccsccsssecscccccsccassessccccsecasssssscccesensssssssccesseassessscecees 4 6 4 3 1 FCULS NOTIFICATION HEADER 4 7 FLEXML ADAPTER MESSAGE 0 4444444444444444 5 1 5 1 MINTO IC IOI TEE ETT EE ENEN EETA E ESE AEE AI EAE EAEE 5 1 5 2 INBOUND FICE Wil ADAPTER oiiae E R R iras 5 1 5 2 1 Processing Incoming FLEXML Request Message 5 2 5 3 OUTBOUND PLE XIVilo ADAPTER siprann E C i 5 2 5 3 1 Processing Outbound Messages 3 2 232 Mapping FLEXML Format Messages to Gateway Formal 5 3 6 ANNEXURE BIST OF MESSAGES cinc 6 1 6 1 INTRODUCTION ocio 6 1 6 2 INBOUND APPLICATION INTEGRATION SERVICES 6 1 6 2 1 De GS G5 AE a E das 6 1 6 2 2 PUBS ACES IVC a ae eT RE ne Dee ee E E ens ee TOS ee ee 6 5 6 2 3 POCOO DINO tados 6 7 6 2 4 UA 6 8 6 2 5 FEUBS CUSTOMERS its 6 11 7 PLANNED OUTAGE SUPPORT SERVER ccccccssscccscccccscccsccccsccccscccccsccccsccccssccccscccccsccccscccceecscees 7
16. 2 2 2 2 4 MDB Based Asynchronous Deployment Pattern 2 2 2 OUTBOUND APPLICATION INTEGRATION 2 3 2 4 RESPONSIBILITIES OF INTEGRATION GATEWAY 2 3 2 0 DEPLOYMENT OF ORACLE FLEXCUBE INTEGRATION GATEWAY ssseeeececeeeeeeeeeeeeeeeeeennaeeeeeeeseeeeeees 2 3 2 6 DEPLOYMENT PATTERNS FOR APPLICATION INTEGRATION cccceeeseeeeesennnneececeeeeeeeeeeeseeeeeennaaaaeeeeeeeeeeeees 2 3 2l PLEXMLADAPTER 0 gt 2 5 EXTERNAL SYS PRM MAINTENANCE 3 1 3 1 DEEINING AN EXTERNAL SYSTEM noni ia 3 1 3 1 1 VIEWING External System Details cirip innn ta 3 3 Idaz Accessing Services GHG OPeErd ONS lt a ci 3 4 3 2 DEFINING ACCESS RIGHTS TO AN EXTERNAL SYSTEM scisesiscsaveravacavasavevavavavoeseageeseavensboedvasseecevevseoesvegteocness 3 4 3 2 1 Viewing External System Function 1 5 3 5 322 Defining Access Rights to a User ID 3 6 3 2 3 0 2 3 6 3 2 4 Specifying Upload Source Pro CLCNCES ie 3 7 3 3 INC
17. 99999 LIABID gt lt CCATEG gt Individual lt CCATEG gt lt COUNTRY USA lt ICOLINTRY gt 3 16 z Local intranet 2 ORACLE 3 5 1 Querying Outgoing Message Browser 3 6 You can query the list of outgoing messages using the Outgoing Message Browser Summary screen You can invoke this screen by typing GWSOTBRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Outgoing Message Browser Summary Message Reference Number bud Branch Related Message Reference r External System Service Name Operation Code Message Identification Ae Correlation Identification Response Queue Message Identification User Identification Their User Identification d Branch Date Server Date Stamp 2 Message Status Search Advanced Search Reset Export Records per page 15 BEEE of 1 BEE Go to Page Message Reference Number Branch Related Message Reference External System Service Name Operation Code Message Identific This query screen can be used to search for outgoing messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty t
18. FCUBS_HEADER gt lt FCUBS_BODY gt lt Cust Static Create Res Full gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C lt CTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt LIABID gt lt CCATEG gt Individual lt CCATEG gt lt COUNTRY gt USA lt ICOUNTRY gt a Local intranet 3 13 ORACLE 3 4 1 Querying Duplicate Message Browser You can query the list of duplicate messages using the Duplicate Message Browser Summary screen with functions for search You can invoke this screen by typing GWSPBROW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Duplicate Message Browser Summary Message Refernce Number AZ Branch External System Message Identification 2 Request Queue Message Identification Correlation Identification Service Name Operation Code User Identification Their User Identification Server Date Stamp 12 Status Search Advanced Search Reset Export Records per page 15 2 Ek of 1 BEE Go to Page Message Refernce Number Branch External System Message Identification Correlation Identification Request Queue Message Identific This query screen can be used to search for duplicate messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The searc
19. Function Action Authorization Status Record Status 4 Authorized C Closed U Unauthorized O Open This summary screen can be used to search for external system functions which match any of the following criteria e Authorization Status e External System e Record Status e Action e Function The Result list shows the external system functions which match your query The search functions available are 3 5 ORACLE 3 2 2 3 2 3 Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Defining Access Rights to a User ID For a User ID to access a request message you can individually map each Function ID to a User ID You can provide access to functions only if the Function IDs provided in Gateway Functions are valid Maintaining Upload Source Details Oracle FLEXCUBE facilitates upload of data from an external source The details of the source from which data has to be uploaded need to be maintained in Oracle FLEXCUBE using the Upload Source Maintenance screen You can invoke the Upload Source Maintenance screen by typing CODSORCE in the field at the top right corner of the Applic
20. GW query message and handoff XSLT is applied to convert GW reply to FLEXML format handoff message 5 The handoff queue name is retrieved using external system maintenance 5 2 ORACLE 6 The handoff message is logged in table if the value of the property file parameter FXG_MSG_LOG_FLG ts Y 7 Handoff XML message is send to each external system 5 3 2 Mapping FLEXML Format Messages to Gateway Format FLEXML uses DTDs to define the structure of an XML document whereas Gateways use XSDs for the same Extensible Style Sheet Language XSL an XML based transformation language is used to convert XML documents from one format to another The mapping can be done using any of the following methods e Optional Attribute Map Approach X Path language is used to map between the two XML formats e Mandatory Attribute Map Approach the mandatory attributes in the target XML document are mapped in this case 5 3 ORACLE 6 1 6 2 6 2 1 6 Annexure List of Messages Introduction This chapter lists out the various messages that fold under the purview of the following Gateway services e Inbound application integration used when any external system needs to add modify or query information within Oracle FLEXCUBE e Outbound application integration used when any external system needs to be notified of the various events that occur within Oracle FLEXCUBE Inbound Application Integration Services Oracle
21. Gateway Setvices Version 11 1 INT1368 ORACLE FCUBSV UM 11 1 0 0 0 0 0 August 2010 Oracle Part Number E51575 01 ORACLE FINANCIAL SERVICES ORACLE Document Control Author Documentation Team Group UBPG A Created on October 01 2008 Revision No Final Updated by Documentation Team Reviewed by Approved by Software Quality Development Testing teams Assurance Team Updated on August 06 2010 Reviewed on August 06 Approved on August 06 2010 2010 ORACLE Gateway Services 1 5 Table of Contents ABOUT THOLS MANU Acce S 1 1 1 1 INTRODUCTION pronta copas 1 1 1 1 1 ANTEC as 1 1 Acronyms AAA e 1 1 1 1 3 Oo O A eae a des E A l 1 1 1 4 CONVENTIONS Used i THIS MONUI aii irete e Aa 1 1 2 GLOSSARY OF ICONS oropesa 1 2 GATEWAY FUNCTIONS AN OVERVIEW 2 1 2 1 K OnO O rc Roe aetnaacs 2 1 22 INBOUND APPLICATION INTEGRATION a 2 1 2 21 EJB Based Synchronous Deployment Pattern 2 1 222 Web Services Based Synchronous Deployment 13 11 2 2 ZL HTTP Servlet Based Synchronous Deployment Pattern
22. ION gt lt SOURCE_OPERATION gt lt SOURCE_USERID gt lt SOURCE_USERID gt lt DESTINATION gt SIEBELCRM lt DESTINATION gt lt FCUBS_HEADER gt m lt Cust Static Create Res Full gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C CTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt LIABID gt lt CCATEG gt Individual lt CCATEG gt lt COUNTRY USA lt ICOLINTRY gt El x Local intranet tt ne ORACLE 3 3 1 Viewing Incoming Message Details The summary of all messages received from the external system can be viewed using the Incoming Message Browser Summary screen as shown below You can invoke this screen by typing GWSINBRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Incoming Message Browser Summary Message Refernce Number 5 Branch Message Identification Request Queue Message Identification External System Correlation Identification Operation Code Their User Identification Service Name User Identification Branch Date Server Date Stamp a az 75 E gt z Message Status Flexcube Reference Number Search Advanced Search Reset Export Records per page 15 v E 1 of 1 T d Message Refernce Number Branch External System Message Identification Correlation Identification Request Queue Message Identific Go to Page
23. It involves the following messages QueryDDTransaction Req Full This is the request message to query DD Transaction in Oracle FLEXCUBE UBS An external system which intends to query a DD transaction has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen QueryDDTransaction Req lO This is the request message to query DD Transaction in Oracle FLEXCUBE UBS An external system which intends to query a DD transaction has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying a DD transaction QueryDDTransaction Res Full This is the response message which is sent back to the external system when DD Transaction is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryDDTransaction Res PK This is the response message which is sent back to the external system when DD Transaction is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the DD transaction in the Oracle FLEXCUBE data store 6 2 4 FCUBSLDService
24. OMING MESSAGE BROWSER sorpresita 3 8 3 3 1 Viewing Incoming Message Details 3 11 34 DUPLICATE MESSAGE BROWSER 3 12 3 4 1 Querying Duplicate Message BrowSeT 3 14 3 5 OUTGOING MESSAGE BOWSER somera dsc 3 15 3 5 1 Querying Outgoing Message 7036 3 17 3 6 DEFINING NOTIFICATION MESSAGEG cccceessesssseeececccceceeeeeeeseesstsesscceeaaaaccceeeeesessecesetssceeasaaaceeeeeeeesees 3 17 3 6 1 Viewing Installed Notification Details 3 18 3 7 DEFINING THE NOTIFICATIONS ENROUTES sssseeeeeeeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 3 20 3 7 1 Viewing SUMMATY 67 11 3 20 3 8 MAINTAINING MT TASK DETAI Ss 3 21 MESSAGE FORMA TS riein 4 1 4 1 NTO ON coren n E aa 4 1 4 2 ORACLE FLEXC UBE ENVELOPE pestes sio dintel noise dista 4 2 4 2
25. ORACLE Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results 3 1 2 Accessing Services and Operations 3 2 In a message it is mandatory to maintain a list of Service Names and Operation Codes This information is called Gateway Operations A combination of every such Service Name and Operation Code is mapped to a combination of Function ID and Action Every screen in Oracle FLEXCUBE is linked with a function ID This information is called Gateway Functions You can gain access to an external system using the Gateway Functions The Function IDs mapped in Gateway Functions should be valid Function IDs maintained in Oracle FLEXCUBE Hence for every new Service or Operation being introduced it is important that you provide data in Gateway Operations and Gateway Functions Refer the Message Formats chapter for more information on Services and Operations Defining Access Rights to an External System You can define access rights to an external system using the External System Functions Detailed screen You can invoke this screen by typing GWDEXFUN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External System Functions Detailed External System az Description Function Action Service Name Operation Code Fields Input
26. Outage Start Using the restore point the request data will be synchronized from host server to POSS Before the planned outage the server state has to be changed into S Sleep from A to indicate that the server will be down as soon as the synchronization starts During synchronization if any new request comes to the bean the gateway layer will reject the request and a XML error message will be generated Once the synchronization is completed the server state will be changed into U Unavailable which indicates the bean that the host server is down and from then on any request that comes will be processed at POSS 7 2 3 7 2 4 Host Down and POSS Up When the host is down and POSS is up the server state will be U During this time all the requests that reach the bean will be served at POSS The bean picks up the JNDI details of POSS from the properties file establishes a connection and sends the request which will be logged into a table at the backend The log table will have details which will indicate if e the response has been built successfully e the request has to be replayed at the host during replay e any error has occurred and oracle SCN The response is sent back to the bean which will send the response to the end point Host Up Start Replay from POSS Once the host is up a REPLAY ROUTINE which is a java routine is carried out which consists of the following steps e The server sta
27. Outbound Application Integration is also called the Oracle FLEXCUBE Notify Application Integration layer This application layer sends out notification messages to the external system whenever events occur in Oracle FLEXCUBE The notification messages generated by FCUBS on the occurrence of these events will be XML messages These XML messages are defined in FCUBS in the form of XML Schema Documents XSD and are referred to as FCUBS formats For more information on FCUBS formats refer the Message Formats chapter in this module Responsibilities of Integration Gateway The primary responsibilities of Oracle FLEXCUBE Integration Gateway include the following e Authentication e Duplicate recognition e Validation e Routing e Logging of messages Deployment of Oracle FLEXCUBE Integration Gateway Message communication incoming or outgoing from to an external system in Oracle FLEXCUBE will happen only through an Oracle FLEXCUBE Integration Gateway Hence it becomes the first point of contact or last point of contact with the database in message flow The Oracle FLEXCUBE Integration Gateway can be deployed to support both the distributed and single schema deployments of Oracle FLEXCUBE e Distributed deployment of FCUBS In this situation the database components of the Gateway are deployed as two or more schemas gt The messaging schema as part of SMS schema in the SMS and or HO instance gt The business schema s in the various bran
28. S An external system which intends to modify an account structure has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e AccountStructureModify Req IO This is the request message to modify an account structure in Oracle FLEXCUBE UBS An external system which intends to modify an account structure has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for modifying account structure e AccountStructureModify Res Full This is the response message which is sent back to the external system when an account structure is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e AccountStructureModify Res PK This is the response message which is sent back to the external system when an account structure is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the account structure in the Oracle FLEXCUBE data store 6 2 5 3 AccountStructureQuery This is the operation code for querying an account structure in Oracle FLEXC
29. SLD services are e Create LD Contract e Create LD Payment FCUBSAcc Service The operations that are supported under FCUBSAcc services are e Create CustAcc e Check Book New 7 3 8 FCUBS Customer Service The operations that are supported under FCUBS Customer services are Create Customer Modify Customer Modify CustAcc Query CustAcc 7 3 9 FCUBSIL Service The operations that are supported under FCUBSIL services are Close ILSweep Delete ILSweep Query ILSweep Modify ILSweep Create ILSweep Close ILGroup Delete ILGroup Query ILGroup Modify ILGroup Create ILGroup 7 3 10 FCUBSLC Service The operations that are supported under FCUBSLC services are Create LCContract Modify LCContract 7 3 11 FCUBSFX Service The FCUBSFX services support the Create FX Contract operation 7 3 12 FCUBSCG Service The FCUBSCG services support the Create Stop Payment operation 7 3 13 FCUBSSwitch Service The FCUBSSwitch services support the Switch Transaction operation ORACLE Gateway Services August 2010 Version 11 1 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 www oracle com financial_ services Copyright 2010 Oracle Financial Services Software Limited All rights reserved No part of this work may be reproduced stored in a retrieval system adopted or transmitted in any
30. This summary screen can be used to search for incoming messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results 3 11 ORACLE 3 4 Duplicate Message Browser If Oracle FLEXCUBE Integration Gateway identifies a duplicate message it will be sent to the Duplicate Messages Browser You can invoke the Duplicate Message Browser Summary screen by typing GWSPBROW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Duplicate Message Browser Summary Message Refernce Number aZ Branch External System Message Identification Request Queue Message Identification Correlation Identification Service Name Operation Code User Identification Their User Identification Server Date Stamp La Status Search Advanced Search Reset Export Records per page 15 wl E of 1 EE Go to Page d Message Refernce Number Bran
31. UBE It involves the following messages e AccountStructureQuery Reg Full This is the request message to an account structure in Oracle FLEXCUBE UBS An external system which intends to query an account structure has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e AccountStructureQuery Req lO This is the request message to query an account structure in Oracle FLEXCUBE UBS An external system which intends to query an account structure has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying account structure e AccountStructureQuery Res Full This is the response message which is sent back to the external system when an account structure is successfully queried in Oracle FLEXCUBE 6 12 ORACLE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AccountStructureQuery Res PK This is the response message which is sent back to the external system when an an account structure is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the
32. You can choose the appropriate one Effective Date Specify the date from which the gateway message maintenance becomes effective Effective date should be equal to or greater than the application date 3 22 ORACLE 4 1 4 Message Formats Introduction Data exchanged between Oracle FLEXCUBE and the external systems will be in the form of XML messages These XML messages are defined in FCUBS in the form of XML Schema Documents XSD and are referred to as FCUBS 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 e lt OPERATION gt _ lt MESSAGE EXCHANGE PATTERN gt REQ e lt OPERATION gt _ lt MESSAGE EXCHANGE PATTERN gt _RES Where e lt OPERATIONS gt refers to an Oracle FLEXCUBE operation like CREATECUSTACC e lt MESSAGE_EXCHANGE_PATTERNsS refers to the request response message patterns exchanged The Message Pattern is of the following types gt FS Full Screen This indicates that the payload will contain all the elements on the corresponding Oracle FLEXCUBE screen gt 10 Input Only This indicates that the payload will contain the only input elements on the corresponding Oracle FLEXCUBE screen gt PK Primary Key This indicates that the payload will contain only the Primary Key elements of the corresponding Oracle FLEXCUBE screen lt MESSAGE_EXCHNAGE_PATTERN gt is
33. a combination of message patterns The lt MESSAGE_EXCHNAGE_PATTERN gt available in FLEXCUBE is shown below e FSFS Full Screen Request and Full Screen Response e IOPK Input Only Request and Primary Key Response e IOFS Input Only Request and Full Screen Response Non Query Formats Example Consider the Operation CREATECUSTACC The root node of messages under this operation will be as under e CREATECUSTACC_FSFS_REQ FCUES HEADER FCUBS BODY CREATECUSTACC_FSFS_REO EH E e CREATECUSTACC_FSFS_RES 4 1 ORACLE FCUBS HEADER FCUBS BODY CREATECUSTACC _FSFS_RES 4 e CREATECUSTACC_IOPK_REQ FCUBS HEADER FCUBS BODY CREATECUSTACC_JOPK_REQ El e CREATECUSTACC_IOPK_RES FCUBS HEADER FCUBS BODY CREATECUSTACC_IOPK_RES HE Query Formats Example Consider the Operation QUERYCUSTACC The root node of messages under this operation will be as under e QUERYCUSTACC_IOFS_REQ FCUBS HEADER FLCUBS BODY QUERYCUSTACC_IOFS_REQ E e QUERYCUSTACC_IOFS_RES FCUBS HEADER QUERYCUSTACC_IOFS_RES E FCUES_ BODY 4 2 Oracle FLEXCUBE Envelope A standard gateway message in the Oracle FLEXCUBE Envelope contains two main components namely e FCUBS HEADER This is a node that forms the header of the FCUBS Envelope The tags under the header portion of a message will identify a partner system a service an operation user branch etc These tags are constant across all messages
34. account structure in the Oracle FLEXCUBE data store 6 13 ORACLE 1 1 7 2 7 2 1 7 2 2 7 Planned Outage Support Server Introduction Planned Outage Support Server POSS is the data replica of the host server and facilitates the channels to support the database server without any downtime during the planned outages When POSS is active e 00 will not run e Non Channel Interface has to be switched off e ELCM enterprise has to be switched off e Messaging and notification cannot be done A new server state XML Is created for which the path is decided based on the entry in the properties file The XML will contain a parameter lt SERVERSTATE gt which can have any of the following values e A Available e S Sleep e U Unavailable e R Replay Gateway EJB will take the request information from the SSB when the full session bean retains the information Handling Planned Outages The various stages of planned outages are described as below Host Up When the request comes from the channel it will reach the Gateway EJB or MDB and the bean check for the state of server If the server state is A Available the bean picks up the JNDI host server details from the properties file and add a parameter to the xml which implies that the request is being served at the host Then the request will be processed at the back end and the response from the back end will reach the bean and then to the endpoint
35. acle FLEXCUBE UBS An external system which intends to modify an MT101 message has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for modifying MT101 message ModifyMt101 Res Full This is the response message which is sent back to the external system when Mt101 message is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen ModifyMt101 Res PK This is the response message which Is sent back to the external system when Mt101 message is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the MT101 message in the Oracle FLEXCUBE data store Oracle FLEXCUBE allows modification only before the first authorization 6 2 1 5 QueryMt101 This is the operation code for querying Mt101 message in Oracle FLEXCUBE It involves the following messages e QueryMt101 Req Full This is the request message to query Mt101 message in Oracle FLEXCUBE UBS An external system which intends to query an MT101 message has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the correspon
36. and processed in Head Office branch MODULEID This indicates the module ID SERVICE This provides details on the various services of Oracle FLEXCUBE For every incoming message in Oracle FLEXCUBE the service name is mandatory OPERATION This indicates the functional operation SOURCE_OPERATION This indicates the functional operation as registered in Oracle FLEXCUBE SOURCE_USERID This is the User ID with which the request message was invoked from the SOURCE DESTINATION For incoming messages the destination will be Oracle FLEXCUBE For response messages system will populate the SOURCE of the request message as DESTINATION MULTITRIPID This is a unique id which indicates overrides 4 4 ORACLE FUNCTIONID This indicates the Oracle FLEXCUBE Function ID MSGSTAT This indicates whether the transaction is a SUCCESS or FAILURE ADDL This is used to send additional parameters e parameters not available in Oracle FLEXCUBE 4 2 2 FCUBS BODY The FCUBS BODY will contain the actual payload to perform the respective transaction The contents of the payload will vary for each operation The following snapshot shows a sample FCUBS BODY of QUERYCUSTACC operation FCUBS_ BODY will contain additional nodes for error response and warning response A diagrammatic representation of the Error response is as shown below a IRType FCUBS_ERROR_RESP E S ERROR E E 4 5 ORACLE 4 2 2 1 FCUBS ERROR RESP The erro
37. at of the message is called Input only which has only those fields that are actually required for creating MT101 message CreateMt101 Res Full This is the response message which is sent back to the external system when an Mt101 message is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CreateMt101 Res PK This is the response message which is sent back to the external system when an Mt101 message is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the MT101 message in the Oracle FLEXCUBE data store 6 2 1 2 AuthorizeMt101 This is the operation code for authorizing MT101 message in Oracle FLEXCUBE It involves the following messages AuthorizeMt101 Req Full This is the request message to authorize Mt101 message in Oracle FLEXCUBE UBS An external system which intends to authorize has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen AuthorizeMt101 Req lO This is the request message to authorize Mt101 message in Oracle FLEXCUBE UBS An external system which intends to authorize MT101 message has
38. ation tool bar and clicking the adjoining arrow button e Upload Source Maintenance Source Code Description Base Data From Flexcube Fields Input By DOCS Date Time Modification Number E authorized ance Authorized By Date Time B open The following details need to be captured here Source Code Specify a code for the for the source from which data has to be uploaded to Oracle FLEXCUBE Description Give a small description for the source code specified Base Data From FLEXCUBE Check this box to indicate if base data has to be uploaded from Oracle FLEXCUBE 3 6 ORACLE 3 2 4 Specifying Upload Source Preferences You can set preferences for upload of data from an external source in the Upload Source Preferences Maintenance screen You can invoke the Upload Source Preferences Maintenance screen by typing CODUPLDM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Upload Source Preferences Maintenance Source Code Module Code Error Handling On Override Ignore On Exception Reject Post Upload Status Authorized Purge Days Calender C Allow Deferred Processing Allow EOD with Deferred Allow Delete Input By DOCS Date Time Modification Number We authorized j Cancel Authorized By Date Time a Open The following details are captured here Source Code Select Source Code from the option list Depend
39. ave been described below SOURCE This indicates the name of the External system or the source of the message MSGID This is the unique reference number generated by Oracle FLEXCUBE NOTIF_REF_NO This unique reference number identifies each notification message generated in Oracle FLEXCUBE BRANCH This indicates the branch in which notification has been triggered NOTIF_CODE This indicates the code for the notification that has been triggered DESTINATION For incoming messages the DESTINATION should be Oracle FLEXCUBE For response messages system will populate the SOURCE of the request message as DESTINATION Refer Service Documentation available under Gateway for details about each message 4 7 ORACLE 5 1 5 2 5 FLEXML Adapter Message Conversion Introduction FLEXML Adapter is a component which facilities the communication between existing FLEXML enabled systems and newer version of Oracle FLEXCUBE based on Gateways The messages are converted from FLEXML format to Gateway format and vice versa The diagram given below indicates that the adapter acts as a middle layer facilitating the exchange of messages between FLEXML based systems and the Oracle FLEXCUBE database Flexml Enabled _ External System _ Adapter Gateway The different channels used by the adapter to communicate with the gateway can be categorized as follows e Inbound FLEXML Adapter e Outbound FLEXML Adapter I
40. called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen AmendF TContract Req lO This is the request message to amend FT contract in Oracle FLEXCUBE UBS An external system which intends to amend FT contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for amending an FT contract AmendFT Contract Res Full This is the response message which is sent back to the external system when FT contract is successfully amended in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AmendFT Contract Res PK This is the response message which is sent back to the external system when an existing FT contract is successfully amended in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the FT contract in the Oracle FLEXCUBE data store 6 2 1 8 QueryFTContract This is the operation code for querying FT contract in Oracle FLEXCUBE It involves the following messages e QueryFTcontract Reg Full This is the request message to query FT contract in Oracle FLEXCUBE UBS An external system which intends to query FT contract has to send the reques
41. ch External System Message Identification Correlation Identification Request Queue Message Identific 3 12 ORACLE Click Text View button in the Duplicate Message Browser Summary screen to view the duplicate messages in the text format Y Text View Web Page Dialog lt xml version 1 0 NOTIFICATION lt mins http cube itler comnotity MOTIF POS HOFF gt FCUBS_NOTIF_HEADER SQURCE FLEXCUBEs SOURCE eMSGID 908224 0000022532 MSGID MOTIF _REF_Moex082240000021 457 MOTIF_REF_Mcre BRANCH 4ED ERANCH lt MNOTIF_ CODE NOTIF_ POS HOFF MOTIF_CODE lt DESTINATION MOTIFY DEST _GUEUE2 DESTINATION F CUBS _NOTIF_HEADERS FCUBS_NOTIF_IDENTIFIER BIZDT 03 JUL 00 BIZ0DT S F CUBS _NOTIF_IDENTIFIER lt _NOTIFICATION Click XML View button in the Duplicate Message Browser Summary screen to view the duplicate messages in the following format 3 Gateway Browser Window Microsoft Internet Explorer DER F CUBS ENVELOPE lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt MSGID gt 9062070000001652 lt MSGID gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAV1 lt USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCUBSCustomerService lt SERVICE gt lt OPERATION gt CreateCust lt OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_USERID gt lt SOURCE_USERID gt lt DESTINATION gt SIEBELCRM lt DESTINATION gt lt
42. ch schemas in the branch instance s e Single schema deployment of FCUBS In this situation the database components of the Gateway messaging and business are both deployed as part of the single Oracle FLEXCUBE schema 2 3 ORACLE 2 6 Deployment Patterns for Application Integration Business Nature of Oracle Integration Needs Integration FLEXCUBE Deployment Pattern Inbound Synchronous FLEXCUBE UBS Recommended Transactions into EJB Oracle FLEXCUBE FLEXCUBE UBS This can be used if the external HTTP Servlet system cannot communicate to Oracle FLEXCUBE using EJB FLEXCUBE UBS This can be used if the external Web Services system chooses to communicate only through Web Services Asynchronous FLEXCUBE UBS This can be used if the external MDB system chooses to communicate only through JMS queues Inbound Queries Synchronous FLEXCUBE UBS Recommended into Oracle EJB FLEXCUBE FLEXCUBE UBS This can be used if the external In Servlet system cannot communicate to Oracle FLEXCUBE using EJB FLEXCUBE UBS This can be used if the external Web Services system chooses to communicate only through Web Services Asynchronous FLEXCUBE UBS This can be used if the external MDB system chooses to communicate only through JMS queues Handoffs from Asynchronous FLEXCUBE UBS Recommended Oracle FLEXCUBE Notify 2 4 ORACLE 2 7 FLEXML Adapter Oracle FLEXCUBE Gateway is the common channel for data exchange between Oracle FLEXCUBE and
43. ding Oracle FLEXCUBE front end screen QueryMt101 Req IO This is the request message to query Mt101 message in Oracle FLEXCUBE UBS An external system which intends to query an MT101 message has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying an MT101 message QueryMt101 Res Full This is the response message which is sent back to the external system when Mt101 message is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryMt101 Res PK This is the response message which is sent back to the external system when Mt101 message is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the MT101 message in the Oracle FLEXCUBE data store 6 3 ORACLE 6 2 1 6 CreateFT Contract This is the operation code for creating FT contract in Oracle FLEXCUBE It involves the following messages CreateFT Contract Req Full This is the request message to create FT contract in Oracle FLEXCUBE UBS An external system which intends to create FT contract has to send the request in the format specified The format of the message is called Full screen which includes all the fiel
44. ds input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CreateFTContract Reqg lO This is the request message to create FT contract in Oracle FLEXCUBE UBS An external system which intends to create FT contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for creating an FT contract CreateFT Contract Res Full This is the response message which is sent back to the external system when FT contract is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CreateFTContract Res PK This is the response message which is sent back to the external system when an FT contract is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the FT contract in the Oracle FLEXCUBE data siore 6 2 1 7 AmendFTContract This is the operation code for amending FT contract in Oracle FLEXCUBE It involves the following messages e AmendFTContract Reg Full This is the request message to amend FT contract in Oracle FLEXCUBE UBS An external system which intends to amend FT contract has to send the request in the format specified The format of the message is
45. ent infrastructure need to be able to communicate and integrate seamlessly with Oracle FLEXCUBE in order to exchange data The Oracle FLEXCUBE Integration Gateway referred to as Gateway in the rest of the document will cater to these integration needs The integration needs supported by the Gateway can be broadly categorized from the perspective of the Gateway as follows e Inbound application integration used when any external system needs to add modify or query information within Oracle FLEXCUBE e Outbound application integration used when any external system needs to be notified of the various events that occur within Oracle FLEXCUBE Inbound Application Integration Oracle FLEXCUBE Inbound Application Gateway provides XML based interfaces thus enhancing the need to communicate and integrate with the external systems The data exchanged between Oracle FLEXCUBE and the external systems will be in the form of XML messages These XML messages are defined in FCUBS in the form of XML Schema Documents XSD and are referred to as FCUBS formats For more information on FCUBS formats refer the Message Formats chapter in this User Manual FCUBS Inbound Application Integration Gateway uses the Synchronous and Asynchronous Deployment Pattern for addressing the integration needs The Synchronous Deployment Pattern is classified into the following e Oracle FLEXCUBE EJB Based Synchronous Inbound Application Integration Deployme
46. essage based approach without wanting to use SOAP as the standard In this deployment pattern the external system will make an HTTP request to the Oracle FLEXCUBE servlet For this deployment pattern Oracle FLEXCUBE will display a single servlet The actual request will be in the form of an XML message This XML message is embedded into the body of the HTTP request sent to the Oracle FLEXCUBE servlet After the necessary processing is done in Oracle FLEXCUBE based on the request the response is returned to the external system as an XML message which is once again embedded within the body of the response HTTP message The transaction control for the processing will stay with the Oracle FLEXCUBE 2 2 ORACLE 2 2 4 MDB Based Asynchronous Deployment Pattern 2 3 2 4 2 5 The MDB deployment pattern is used in integration scenarios where the external system connecting to Oracle FLEXCUBE wants to connect to Oracle FLEXCUBE using JMS queues This is especially applicable to systems such as the following e Systems that prefer to use JMS queues based approach without wanting to wait for the reply Here external system sends messages in XML format to request queue on which an MDB is listening When a message arrives on the queue it is picked up for processing After the necessary processing is done in Oracle FLEXCUBE based on the request the response is sent to the response queue as an XML message Outbound Application Integration The
47. et to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results 3 19 ORACLE 3 7 3 7 1 Defining the Notifications Enroutes You can invoke the Notification Enroutes Detailed screen by typing GWDNTFEN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Notifications Enroute Detailed Branch Code Notification Code Description lla Description Destination Mame Fields Input By DOCS Date Time Modification Number WB authorized Cancel Authorized By Date Time a Open In Notification Enroutes Detailed screen you define the following details Branch Specify a branch for which you wish to define a topic If you want to use a single topic for all branches and for a given notification code you can use a wildcard Once you select a Branch Code the corresponding description is displayed Notification Code Select a notification code from the list of notification codes provided You can indicate a wildcard 2 If a single topic needs to be used for all notifications in a branch Topic Queue Name Define a topic or a queue here If you define a topic you can assign multiple notification codes for a branch In case of a queue you ca
48. ete an MT101 message has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for closing MT101 message DeleteMt101 Res Full This is the resoonse message which is sent back to the external system when Mt101 message is successfully deleted in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen DeleteMt101 Res PK This is the response message which is sent back to the external system when Mt101 message is successfully deleted in Oracle FLEXCUBE UBS The 6 2 ORACLE format of the message is called Primary Key response which includes only the primary key fields of the MT101 message in the Oracle FLEXCUBE data store 6 2 1 4 ModifyMt101 This is the operation code for modifying Mt101 message in Oracle FLEXCUBE It involves the following messages ModifyMt101 Req Full This is the request message to modify Mt101 message in Oracle FLEXCUBE UBS An external system which intends to close an MT101 message has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen ModifyMt101 Req lO This is the request message to modify Mt101 message in Or
49. eue for every In Queue This is required only when the External System fails to display the queue name on posting a request message into the In Queue 3 1 1 Viewing External System Details The details of previously defined external Systems can be viewed using the External System Summary screen as shown below You can invoke this screen by typing GWSEXSYS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External system Summary Authorization Status s Record Status External System A Default Response Queue Dead Letter Queue Search Advanced Search Reset Export Records per page 15 v Fre 1 of in iz Go to Page C Authorization Status Record Status External System Default Response Queue Dead Letter Queue Authorization Status Record Status A Authorized C Closed U Unauthorized O Open This summary screen can be used to search for external systems which match the data specified for any of the following criteria e Authorization Status e External System e Dead Letter Queue e Record Status e Default Response Queue The Result list shows the external systems which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search 3 3
50. external systems But older versions of Oracle FLEXCUBE use FLEXML Gateway to interact with the external systems The message or communication format of FLEXML is different from that of the gateway Hence in order to facilitate the exchange of messages between such systems Oracle FLEXCUBE uses a conversion mechanism called the FLEXML Adapter FLEXML Adapter converts messages from FLEXML format to gateway format and vice versa For more details on the conversion mechanism of FLEXML Adapter refer the chapter FLEXML Adapter Message Conversion 2 5 ORACLE 3 External System Maintenance 3 1 Defining an External System You need to define an external system that will communicate with the Oracle FLEXCUBE Integration Gateway You can define an external system using the External System Detailed screen You can invoke this screen by typing GWDEXSYS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External System Detailed External System Correlation Pattern gt External System Request Message ID vi Description Message Exchange Pattern Queue Request Message Input Only vw Default Response Queue Response Message Full Screen Dead Letter Queue _ XSD Validation Required C Register Response Queue Message ld External System Queues O In Queue Response Queue Fields FTP Parameters Input By DOC3 Date Time Modificati
51. form or by any means electronic mechanical photographic graphic optic recording or otherwise translated in any language or computer language without the prior written permission of Oracle Financial Services Software Limited Due care has been taken to make this document and accompanying software package as accurate as possible However Oracle Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the accompanying Software System Furthermore Oracle Financial Services Software Limited reserves the right to alter modify or otherwise change in any manner the content hereof without obligation of Oracle Financial Services Software Limited to notify any person of such revision or changes All company and product names are trademarks of the respective companies with which they are associated
52. h functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results 3 14 ORACLE 3 5 Outgoing Message Bowser Once the incoming messages have been processed a response message will be sent to the external systems along with the status of the processed messages The response messages will be displayed in the Outgoing Message Browser You can invoke the Outgoing Message Browser screen by typing GWDOTBRW in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button 4 Outgoing Message Browser Web Page Dialog Message Reference Number 3082200000021 373 External System ACUMEN Message Identification Correlation Identification Message Status Error Service Mame FCUBSSIService Operation Code GuerySlContract Branch CHO Flexcube Reference Mumber User Identification TANUAU Their User Identification Server Date Stamp 2008 08 07 15 04 31 Response Queue Message Branch Date Related Message Reference 608220000001 4943 aueue Mame Repair Reason Text View ML View In the Outgoing Message Browser screen you can view the details of
53. he values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Defining Notification Messages 3 17 ORACLE 3 6 1 The outgoing message browser also displays the notification messages Every time the database layer receives a notification message it updates the outgoing message browser to display the same At the branch level you can maintain notification codes for each branch You can do this using the Notifications Installed screen You can invoke the Notifications Installed Detailed screen by typing GWDNTFIN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button e Notifications Installed Detailed Branch Code az Branch Name Notification Code az Description Fields Input By DOC3 Date Time Modification Number KM authorized c Cancel Authorized By Date Time B open In this screen you need to specify the following details Branch Code Select a branch code for which you wish to assign a notification code Once you select the branch code the corresponding description is displayed Notification Code From the list of values select a notification code you wish to link with the branch This will be used to generate notifications for the entire bra
54. heque book is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the cheque book in the Oracle FLEXCUBE data store 6 2 2 4 CreateTDSim This is the operation code for creating TD simulation in Oracle FLEXCUBE It involves the following messages e CreateTDSim Req Full This is the request message to create TD simulation in Oracle FLEXCUBE UBS An external system which intends to TD simulation has to send the request in the format specified The format of the message is called Full screen which 6 6 ORACLE includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CreateTDSim Req IO This is the request message to create TD simulation in Oracle FLEXCUBE UBS An external system which intends to TD simulation has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for creating TD simulation Create TDSim Res Full This is the response message which is sent back to the external system when a TD simulation is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CreateTDSim Res PK This is the response message which is
55. ing on the source code you select here data is uploaded from that source into Oracle FLEXCUBE Module Code You can choose to upload data from a source directly onto a module in FLEXCUBE Indicate the module into which you would like to upload data from a given source On Override Oracle FLEXCUBE generates override messages in case it encounters any discrepancies during data upload You can choose to do any of the following e Ignore Select this option to ignore such error messages and continue with the upload process e Put on Hold Select this option to put the record on hold for user intervention later e Reject Select this option to reject the record On Exception In case a serious error occurs during data upload Oracle FLEXCUBE generates an error message You can choose to put the record with the error on hold In such a case choose Put on Hold from the list of options available If you would like to reject the record altogether choose Reject Post Upload Status If you would like to automatically authorize the data that is uploaded into Oracle FLEXCUBE choose the Authorize option here 3 7 ORACLE 3 3 If you would like the record to be put on hold choose this option in this field If you would like the record to be unauthorized choose the Unauthorized option in this field The record will not be authorized automatically on upload You will have to manually authorize the data Purge Da
56. ion contract DeleteLDSIMContract Res Full This is the response message which is sent back to the external system when LD simulation contract is successfully deleted in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen DeleteLDSIMContract Res PK This is the response message which is sent back to the external system when an existing LD simulation contract is successfully deleted in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the LD simulation contract in the Oracle FLEXCUBE data store 6 2 4 3 QueryLDSIMContract This is the operation code for querying LD simulation contract in Oracle FLEXCUBE It involves the following messages DeleteQueryLDSIMContract Req lO This is the request message to query LD simulation contract in Oracle FLEXCUBE UBS An external system which intends to query LD simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying LD simulation contract DeleteQueryLDSIMContract Res Full This is the response message which is sent back to the external system when LD simulation contract is successfully queried in Oracle FLEXCUBE UBS The format of the message is called F
57. ly those fields that are actually required for creating LD payment simulation e CreateLDPaymentSim Res Full This is the response message which is sent back to the external system when LD payment simulation is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CreateLDPaymentSim Res PK This is the response message which is sent back to the external system when an LD payment simulation is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the LD payment simulation in the Oracle FLEXCUBE data store 6 2 5 FCUBSCustomerService Customer related operations are logically grouped under a service called FCUBSCUustomersService Oracle FLEXCUBE supports the following operations under this service e AccountStructureNew e AccountStructureModify e AccountStructureQuery 6 2 5 1 AccountStructureNew This is the operation code for creating Account Structure in Oracle FLEXCUBE It involves the following messages e AccountStructureNew Req Full This is the request message to create account structure in Oracle FLEXCUBE UBS An external system which intends to create account structure has to send the request in the format specified The format of the message is called Full
58. m Res PK This is the response message which is sent back to the external system when an LD VAMI simulation contract is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the LD VAMI simulation in the Oracle FLEXCUBE data store 6 2 4 5 LDVamiQuerySim This is the operation code for querying LD VAMI Simulation contract in Oracle FLEXCUBE It involves the following messages e LDVamiQuerySim Reg lO This is the request message to query LD VAMI simulation contract in Oracle FLEXCUBE UBS An external system which intends to query LD VAMI simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying LD VAMI simulation e LDVamiQuerySim Res Full This is the resoonse message which is sent back to the external system when LD VAMI simulation contract is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 2 4 6 QueryLDPaymentSim This is the operation code for querying LD Payment Simulation in Oracle FLEXCUBE It involves the following messages e QueryLDPaymentSim Reg lO This is the request message to query LD payment simulation in Oracle FLEXCUBE UBS
59. n define only one notification code for each branch Viewing Summary screen You can view and query the list of notifications enroute using the Notifications Enroutes Summary screen You can invoke this screen by typing GWSNTFEN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 20 ORACLE 3 8 Notifications Enroute Summary Authorization Status Record Status Branch Code la Notification Code Destination Name 1i Search Advanced Search Reset f Export Records per page 15 rll of 1 FE Go to Page Ji C Authorization Status Record Status Branch Code Notification Code Destination Name Authorization Status Record Status A Authorized C Closed U Unauthorized O Open This summary screen can be used to search for notifications enroute which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh button to refresh the list of results Maintaining MT Ta
60. nbound FLEXML Adapter Inbound FLEXML Adapter provides an XML based interface for the FLEXML enabled external system to communicate with Oracle FLEXCUBE database It converts the messages from FLEXML format to gateway format and invokes GW EJB which handles further processing of the message The following communication mechanisms are available to process the incoming FLEXML messages e EJB Inbound Adapter This is used if the external system is compatible with EJB interface The external system invokes the adapter using EJB interface API method 5 1 ORACLE 9 2 1 9 3 9 3 1 e MDB Inbound Adapter This is used if the external system is JMS compatible The external system invokes the adapter by sending message to JMS Queue Processing Incoming FLEXML Request Message The inbound adapter processes an incoming request message in FLEXML format as follows 1 Adapter receives the request message in FLEXML format 2 The request message is logged in table if the value of the property file parameter FXG_MSG_LOG_FLG ts Y 3 XML message is validated using FLEXML DTD 4 Ifthe message is invalid the adapter generates parser error message in FLEXML format and sends it back to external system If the message is valid the source name service name and operation type is retrieved from the message 5 Based on source name service name and operation type request and reply XSLT file name is retrieved from database 6 XSLT is
61. nch Once you select the notification code the corresponding description is displayed In addition to maintaining a notification code for a given branch you can also specify a topic or a queue to which the notification messages should be sent You can define a topic queue for a given branch and notification code in the Notifications Enroute screen Viewing Installed Notification Details You can view and query the list of notification messages using the Notifications Installed Summary screen You can invoke this screen by typing GWSNTFIN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 18 ORACLE Notifications Installed Summary Authorization Status Record Status Branch Code EH Notification Code Search Advanced Search Reset Export Records per page 15 FBE r O 1 EE Go to Page C Authorization Status Record Status Branch Code Notification Code Authorization Status Record Status A Authorized C Closed U Unauthorized O Open This Summary screen can be used to search for notification messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Res
62. nt Pattern e Oracle FLEXCUBE Web Services Based Synchronous Inbound Application Integration Deployment Pattern e Oracle FLEXCUBE HTTP Servlet Based Synchronous Inbound Application Integration Deployment Pattern Asynchronous Deployment Pattern is e Oracle FLEXCUBE MDB Based Asynchronous Inbound Application Integration Deployment Patten EJB Based Synchronous Deployment Pattern The Enterprise Java Beans EJB deployment pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE is EJB literate i e the external system is capable of interacting with Oracle FLEXCUBE based upon the EJB interface In this deployment pattern the external system will use the RMI IIOP protocol to communicate with the Oracle FLEXCUBE EJB 2 1 ORACLE In this deployment pattern the EJB displayed by Oracle FLEXCUBE will be a stateless session bean The actual request will be in the form of an XML message After the necessary processing is done in Oracle FLEXCUBE based on the request the response is returned to the external system as an XML message The transaction control for the processing will stay with the Oracle FLEXCUBE EJB 2 2 2 Web Services Based Synchronous Deployment Pattern 2 2 3 The web services deployment pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE wants to connect using standards based inter operable web services This deployment pa
63. on Number authorized Authorized By Date Time Open The various details required by the External System Detailed screen are described below 3 1 1 1 Specifying External System Details External System Specify a name for the external system This should be the same as the Source in an incoming message Description Specify a brief description for the External System 3 1 1 2 Indicating Correlation Pattern Request You can define a way in which the external system should correlate its request message with the response message You can choose Message ID of a request message as the Correlation ID in the response message Alternatively you can choose Correlation ID of a request message and maintain it as the Correlation ID of the corresponding response message 3 1 ORACLE 3 1 1 3 Specifying Message Exchange Pattern Request Message You can choose the Request message to be Full Screen or Input Only If you select Full Screen as the request message the response message will also display Full Screen Response Message You can choose the Response message to be Full Screen or Record Identification Msg You can select Record Identification Msg as the response message only if you select Input Only in the request message 3 1 1 4 Specifying Queue Details Default Response Queue You can define a response queue for each of the In Queue s through which the External System
64. r response message will be sent from Oracle FLEXCUBE when errors are raised in a transaction The error response will have another tag ERROR within it ERROR The ERROR node will have tags for error code and error description The ERROR node will be generated for each error raised by FCUBS 4 2 2 2 FCUBS WARNING RESP 4 3 The warning response message will be sent when overrides are raised in a transaction The Warning response will have another tag WARNING within it WARNING This node will have tags for warning code and warning description The WARNING node will be generated for each override raised by FCUBS Oracle FLEXCUBE NOTIFICATION The notification messages are generated in a standard format The notification messages will consist of two main components FCUBS NOTIF_HEADER This forms the header portion of a notification message This contains a standard set of tags that can identify a notification These tags are constant across all notification messages FCUBS NOTIF_IDENTIFIER This will identify the maintenance records based on the information provided under this node The contents of this node will vary for each notification A diagrammatic representation of FCUBS NOTIFICATION is as shown below FCUBS_HOTIF_HEADER FCUBS_HOTIF_IDENTIFIER FCUBS NOTIFICATION e E 4 6 ORACLE FCUBS NOTIF_HEADER 4 3 1 FCUBS NOTIFICATION HEADER The tags under FCUBS NOTIFICATION HEADER h
65. screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e AccountStructureNew Req lO This is the request message to create account structure in Oracle FLEXCUBE UBS An external system which intends to create account structure has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for creating account structure 6 11 ORACLE e AccountStructureNew Res Full This is the response message which is sent back to the external system when account structure is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e AccountStructureNew Res PK This is the response message which is sent back to the external system when a new account structure is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the account structure in the Oracle FLEXCUBE data store 6 2 5 2 AccountStructureModify This is the operation code for modifying account structure in Oracle FLEXCUBE It involves the following messages e AccountStructureModify Req Full This is the request message to modify an account structure in Oracle FLEXCUBE UB
66. sk Details Using the Gateway Maintenance Detailed screen you can maintain the basis for creation of MT tasks for Gateway message You can invoke this screen by typing STDGWINT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 21 ORACLE A Gateway Maintenance Delailed Web Papo Dialog Gale Away Maintenance Perch Coda External Stem bakie Codes CA Operation Code Tack intiation Required Etteciive Date 3 OueryChkbiRisq E fe 11 11 2007 ME Authorizes Cancel M open In this screen you can specify the following details Branch Code Specify the branch code of the bank This adjoining option list displays all valid branches maintained in the system You can choose the appropriate one External System Specify the name of the external system This adjoining option list displays all the external systems maintained in the system You can choose the appropriate one Module Code Specify the module name This adjoining option list displays all the modules maintained in the system You can choose the appropriate one Service Name Specify the service name of the module selected This adjoining option list displays all the service names maintained in the system You can choose the appropriate one Operation code Specify the operation code of the service This adjoining option list displays all valid operation codes maintained in the system
67. t in the format specified The format of the message is called Full screen which 6 4 ORACLE includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen QueryFTContract Req IO This is the request message to query FT contract in Oracle FLEXCUBE UBS An external system which intends to query FT contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying an FT contract QueryFTContract Res Full This is the response message which is sent back to the external system when FT contract is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryFTContract Res PK This is the response message which is sent back to the external system when FT contract is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the FT contract in the Oracle FLEXCUBE data store 6 2 2 FCUBSAccService All account operations are logically grouped under a service called FCUBSAccService Oracle FLEXCUBE supports the following operations under this service CheckBooKNew CheckBookModify CheckBookQuery CreateTDSim QueryGenAdvice
68. te will be changed from U to R Replay mode e The replay routine will get the requests from the log table at POSS for which response building has been completed and these will be replayed to the host e The replay routine logs all message logs and places the message onto Oracle AQ on the Host database e Multiple processes equal to the number of locks defined start the request processing based on SCN e Each process will replay the requests on to the host by calling a procedure in the service router e Once a record is replayed the thread updates the log table indicating that the replay of this record is complete When the server state is R and any new request comes to the bean it will execute a DAO to check for records in POSS that need to be replayed to the host If any such record is found the new request is sent to POSS else the server state is changed from R to A When the server state is R the bean also slows down the processing of new requests to ensure there is a switch over back to host The following chart will depict a clear picture of request information that pass on to the various stages that are discussed Change server state to S after Sync change state toA All Sync POSS to header replayed complet Incomplete e Replay Complete Add param HOST to header Send request to HOST i l Send request
69. the messages sent to the external systems You can also view the messages in the XML format or the Text format 3 15 ORACLE Click Text View button to view the response message in text format as shown below Y Text View Web Page Dialog version 1 0 Y FEUBS NOTIFICATION xming htte cube iflex comnotity Mogi POS FCUBS_NOTIF_HEADER SOURCE FLEXCUBE SOURCE MSGID 9082240000022832 lt MSGID NOTIF_REF_NO x082240000021 457 lt NOTIF_REF_NO BRANCH 4ED lt BRANCH lt NOTIF_CODESNOTIF_ POS HOFF MOTIF_CODE DESTINATIONSNOTIFY_DEST_QUEUE2 DESTINATION FCUBS_NOTIF_HEADER FCUBS_NOTIF_IDENTIFIERS lt BIZDT 03 JUL 00 lt BIZDT FCUBS_NOTIF_IDENTIFIER FCUBS NOTIFICA TION gt E Gateway Browser Window Microsoft Internet Explorer e E ENM ECO FE m lt SOURCE gt FLEXCUBE lt SOURCE gt lt MSGID gt 9062070000001652 lt MSGID gt lt CORRELID gt lt CORRELID gt lt JSERID gt SAURAYV1 lt USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCU BSCustomerService SERVICE gt lt OPERATION gt CreateCust lt OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_USERID gt lt SOURCE_USERID gt lt DESTINATION gt SIEBELCRM lt DESTINATION gt lt FCUBS_HEADER gt lt FCUBS_BODY gt lt Cust Static Create Res Full gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C CTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU
70. to 8055 i incomplete lt Reject the Change Replay Routine E request state to U Log request l additionally in a separate table Process request build response Update POSS Start log table gt synchronization Process request build response Send error message Response 7 2 5 ELCM Impact When the request comes two ELCM gateways are deployed pointing towards the Host and the POSS The external interface at ELCM will be switched off and the transactions which are initiated through FLEXCUBE will be serviced 7 3 7 3 1 7 3 2 7 3 3 7 3 4 7 3 5 7 3 6 1 3 1 Services Supported during Outage The following Services are supported during Planned Outage FCUBSFT Service The operations that are supported under FCUBSFT services are e Cancel FT Contract e Create FT Contract FCUBSPC Service The operations that are supported under FCUBSFT services are e Create PC Contract e Create PC Maint e Close PC Contract e Create PC ClientAgg FCUBSSI Service The operations that are supported under FCUBSSI services are e Create SI Contract e Close SI Contract FCUBSTD Service The operations that are supported under FCUBSTD services are e Create TDAcc e Query TDRedemption FCUBSCL Service The FCUBSCL services support the Save Payment operation FCUBSLD Service The operations that are supported under FCUB
71. to send the request in the specified format The format of the message is called Input only which has only those fields that can be used to query AuthorizeMt101 Res Full This is the response message which is sent back to the external system when Mt101 message is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AuthorizeMt101 Res PK This is the response message which is sent back to the external system when Mt101 message is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the MT101 message in the Oracle FLEXCUBE data store 6 2 1 3 DeleteMt101 This is the operation code for deleting Mt101 message in Oracle FLEXCUBE It involves the following messages DeleteMt101 Req Full This is the request message to delete Mt101 message in Oracle FLEXCUBE UBS An external system which intends to delete MT101 message has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen DeleteMt101 Req 1O This is the request message to delete Mt101 message in Oracle FLEXCUBE UBS An external system which intends to del
72. ttern is especially applicable to systems which meet the following broad guidelines e Systems that are not EJB literate i e such systems are not capable of establishing connections with Oracle FLEXCUBE based upon the EJB interface and or e Systems that prefer to use a standards based approach In this deployment pattern the external system will use the SOAP Simple Object Access Protocol messages to communicate to the Oracle FLEXCUBE web services The services displayed by Oracle FLEXCUBE are of a message based style i e the actual request will be in the form of an XML message but the request will be a payload within the SOAP message After the necessary processing is done in Oracle FLEXCUBE based on the request the response is returned to the external system as an XML message which will be a payload within the response SOAP message The transaction control for the processing will stay with the Oracle FLEXCUBE HTTP Servlet Based Synchronous Deployment Pattern The HTTP servlet deployment pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE wants to connect to Oracle FLEXCUBE using simple HTTP messages This is especially applicable to systems such as the following e Systems that are not EJB literate i e are not capable establishing a connections with Oracle FLEXCUBE based upon the EJB interface and or e Systems that prefer to use a simple http m
73. ull screen response which 6 9 ORACLE includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 2 4 4 LDVamiCreateSim This is the operation code for creating LD VAMI Simulation contract in Oracle FLEXCUBE It involves the following messages e LDVamiCreateSim Req Full This is the request message to create LD VAMI simulation contract in Oracle FLEXCUBE UBS An external system which intends to create LD VAMI simulation contract has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e LDVamiCreateSim Req lO This is the request message to create LD VAMI simulation contract in Oracle FLEXCUBE UBS An external system which intends to create LD VAMI simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for creating LD VAMI simulation e LDVamiCreateSim Res Full This is the resoonse message which is sent back to the external system when LD VAMI simulation contract is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen LDVamiCreateSi
74. xt format Click Text View button to view the incoming messages in text format as shown below 3 9 ORACLE Y Text View Web Page Dialog FCUBS_REQ_EN y gt lt FCUBS_HEADER gt SOURCE gt 4 CUMEMPDs SOURCE UBSCOMP FCUBS JBSCOMP MSGIDI gt CORRELID USERID NIT2 sUSERID BRANCH CHO BRANCH MODULEID FPD MODULEID lt SERVICE FCUBS Acc AddrService SERYVICE gt OPERA TION CreateCust4ccAddr fOPER4 TIOn SOURCE _OPERATION Transactionvey lt SOURCE_ OPERA TION FCUBS_HESDER FCUBS_BOD Y lt Pdc hMaster 101 gt PROCD PDD2 PRDCD lt BRHN CHO lt BRH lt REML CNO 223333001 sREMATNO BENACNO gt 4 4234 BENACH lt INSTRNO 983886 lt INSTRHO A A gt lt A T 1 000 44 1 T gt lt YALDT 2000 07 03 lt Y 4L0T CLGPRO NADE lt CLGPRD gt lt RTNGNO gt 555570001 000 RTHMNGhE lt EMNDPNT gt 2222 EMDPRT gt lt SRBANK CHO lt 1SRARNK gt lt SRBRA 1000 lt 01SRBRH Click XML View button to view the Gateway Browser Window screen which displays the messages in XML format E Gateway Browser Window Microsoft Internet Explorer A E ENYELOPE gt gt REA LERS lt SOURCE gt FLEXCUBE lt SOURCE gt lt MSGID gt 9062070000001652 lt MSGID gt lt CORRELID gt lt CORRELID gt lt JSERID gt SAURAYV1 lt USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCU BSCustomerService SERVICE gt lt OPERATION gt CreateCust lt OPERATION gt lt SOURCE_OPERAT
75. y key fields of the cheque book record in the Oracle FLEXCUBE data store 6 5 ORACLE 6 2 2 2 CheckBookModify This is the operation code for modifying new Cheque Book in Oracle FLEXCUBE It involves the following messages e CheckBookModify Reg Full This is the request message to modify a cheque book in Oracle FLEXCUBE UBS An external system which intends to modify a cheque book has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e CheckBookModify Req 1O This is the request message to modify a cheque book in Oracle FLEXCUBE UBS An external system which intends to modify a cheque book has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for modifying a cheque book e CheckBookModify Res Full This is the response message which is sent back to the external system when a cheque book is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CheckBookModify Res PK This is the response message which is sent back to the external system when a cheque book is successfully modified in Oracle FLEXCUBE UBS
76. ys Calendar Specify the days maintained for purging of the data uploaded Allow Deferred Processing Check this option to defer processing of amendment and cancellation uploads Allow EOD with Deferred Check this option to proceed even if the records exist in the deferred processing log If it is unchecked then the EOD process halts until the deferred process log is cleared Allow Delete Check this option to delete the process log Incoming Message Browser The messages received from the external system will be displayed in the Incoming Message Browser You can invoke the Incoming Message Browser screen by typing GWDINBRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 8 ORACLE 3 Incoming Message Browser Web Page Dialog Message Refernce Number 608224000001 6307 External System ACUMEN Message Identification Correlation Identification Message Status Success Service Mame FCUBSSR Service Operation Code CreatesRContract Branch AAA Flexcube Reference Mumber User Identification SHASHANK Their User Identification Branch Date Queue Mame Server Date Stamp 2008 08 11 15 10 19 Request Queue Message Identification Repair Reason Missing Error Code ML View Text View In the Incoming Message Browser screen you can view the details of the messages received from the external systems You can also view the messages in the XML format or the Te

Oracle Part Number E51575-01

Contents

Download Pdf Manuals

Related Search

Related Contents