1 / 19

BIS – Bridging to Web Services

BIS – Bridging to Web Services. Confidential. 2006. Nedgroup Life Assurance Company Limited. Co. Reg. No. 1993/001022/06. Nedgroup Life Assurance Company Limited is a joint venture between Old Mutual SA Limited and Nedbank Limited. We are an authorised financial services provider. .

annabella
Download Presentation

BIS – Bridging to Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BIS – Bridging to Web Services Confidential. 2006 Nedgroup Life Assurance Company Limited. Co. Reg. No. 1993/001022/06. Nedgroup Life Assurance Company Limited is a joint venture between Old Mutual SA Limited and Nedbank Limited. We are an authorised financial services provider.

  2. About Nedgroup Life Web Services XML Consuming (Using) Services Exposing (Providing) Services BIS as a Consumer BIS as a Provider The LOA Bridge Other Plans Presentation Outline

  3. Joint Venture between NedBank and Old Mutual (50/50) Leverage off Nedbank Network Infrastructure/Desktop support/Operations (ie. Batch processing, BIS administrator)etc Bond Cover, credit protection (ie. Credit cards, overdraft cover), Funeral cover Over 100 staff Primary systems - BIS (level 10.1.E4) & Gateway 8 BIS developers and 2 Gateway developers (specialised) About Nedgroup Life

  4. Rapidly becoming the standard way that systems collaborate. Strategic policy in Nedbank Group Based on “REQUEST” & “RESPONSE” HTTP Protocol. “REQUEST “ and “RESPONSE” are strings in XML. Web Services

  5. On-Line, Real-Time Collaboration Lower operational overhead No FTP, eMail or Physical file transfer Parties only have to agree on the XML Schema Technology becomes irrelevant Becoming easier to develop .Net capabilities Numerous third-party tools “The Truth” is in one place. No replication or synchronization issues Web Services - Benefits

  6. eXtensible Mark-up Language. Tag-Based string format. Numerous tools for constructing, validating, parsing and rendering XML. XML + XSL = HTML Schema definition .NET Framework tools XMLReader, XMLWriter Many published standards GPS – GPX, GIS – GML, Open Document format. OFX – Open Financial Exchange The B2B war is over; XML won! What is XML?

  7. Construct a XML request Instantiate the service Send the REQUEST / Get the RESPONSE. Parse the response. How do you “consume” a web service?

  8. Create software that :- Accepts a REQUEST string Parses and interprets the REQUEST Returns a RESPONSE or ERROR Expose the service How do you “expose” a web service?

  9. The Good News Easy to construct XML REQUEST in output area Can Instantiate a class and invoke it’s methods @CCC, @CCI, @CCR The Bad News No easy way of parsing the response String size limitation. How can BIS work a web-service consumer?

  10. Method 1 ICE thinking. How? Component receives the REQUEST. Parses the REQUEST. STARTS a run with parameters Waits for RESPONSE file to be created by BIS. Delivers the RESPONSE How can BIS work as a web service provider?

  11. Method 2 JduP Thinking How? Fatter component that Receives the request Parses the request Accesses BIS via ODBC – run started as “stored procedure” Formats the RESPONSE How will BIS work as a web service provider?

  12. How Could we integrate BIS with the world out there?

  13. The LOA Bridge – BIS Subroutine @ . --------------Get or count matching claims---------------------- @0060:(<Id1>,<Id2>,<EncName>,<DoB>,<Init>,<GName>,<GetOrCount>,<FO>) @ . rdb . @ Dc d12=d11(<DoB>) <DoB12>a11 . @ If <DoB12>(1-1) = '*' Ldv <Dob12>='' . ; . @ CCC,0197 'MapperBridge.MapperBridge' <Handle>i8 <Msg>s80 . instantiate /c @ Brk . '<'ENVELOPE ASSEMBLY="D:\Program Files\mapperBridge\LOABridge.DLL" CLASS="LOABridge.Portal" METHOD="Service"> '<'REQUEST TYPE="<GetOrCount>MATCHINGCLAIMS" ID1="<id1>(p)" ID2="<id2>(p)" DOB="<DoB12>(p)" INITIALS="<Init>(p)" GIVENNAME="<GName>(p)" ENCODEDSURNAME="<EncName>(p)"/'>' '<'/ENVELOPE'>' @ brk rnm -2 chg <EL>h1 chr$ 12 . @ brk . @ CCI,0199 <Handle>,'SendReceive' BSTR (-2,<EL>) (-0,<EL>) <Msg>s80 . @ If <FO> = '' RETURN ; . want to reformat from "raw" form /c @ Rnm -1 rsr 0070 .

  14. MapperBridge Gets:- <ENVELOPE ASSEMBLY="D:\Program Files\mapperBridge\LOABridge.DLL" CLASS="LOABridge.Portal" METHOD="Service"> <REQUEST TYPE="COUNTMATCHINGCLAIMS" ID1="" ID2="" DOB="23 NOV 1952" INITIALS="" GIVENNAME="" ENCODEDSURNAME=""/> </ENVELOPE>

  15. MapperBridge:- Creates an instance of LOABridge Invokes the “Portal.Service” Passes it:- <REQUEST TYPE=“GETMATCHINGCLAIMS" ID1="" ID2="" DOB="23 NOV 1952" INITIALS="" GIVENNAME="" ENCODEDSURNAME=""/>

  16. LOABridge:- Parses REQUEST and returns RESPONSE to MapperBridge <RESPONSE TYPE="SUCCESS"> <MATCHCLAIM LOCATIONNAME="SAGE LIFE LIMITED" LOCATION="2" KEY="7965"> <dsLOCClaim xmlns="http://tempuri.org/dsLOCClaim.xsd"> <LOCClaim> <CLMLocation>2</CLMLocation> <CLMKey>7965</CLMKey> <CLMEncodedSurname>CHE </CLMEncodedSurname> <CLMGivenName xml:space="preserve"> </CLMGivenName> <CLMInitials>JE</CLMInitials> <CLMDoB>1951-12-23T00:00:00+02:00</CLMDoB> <CLMNotifyDate>2001-09-04T00:00:00+02:00</CLMNotifyDate> <CLMRefNumber>064359698</CLMRefNumber> <CLMEventDate>2001-01-12T00:00:00+02:00</CLMEventDate> <CLMClaimCode>Death</CLMClaimCode> <CLMIDNumber>6401130667086</CLMIDNumber> <CLMSyncStatus>S</CLMSyncStatus> </LOCClaim> <LOCReason> <CLMLocation>2</CLMLocation> <CLMKey>7965</CLMKey> <CLMReasonImpairment>C57.9</CLMReasonImpairment> </LOCReason> <LOCCategory> <CLMLocation>2</CLMLocation> <CLMKey>7965</CLMKey> <CLMCatKey>2</CLMCatKey> </LOCCategory> </dsLOCClaim> </MATCHCLAIM> </RESPONSE>

  17. MapperBridge Formats a Report . Extracted Data *Lev.T. Name . Value * .Y. . *===.=.==============================.========================================== |1 |E|RESPONSE | *1 |A|TYPE |SUCCESS |2 |E|MATCHCLAIM | *2 |A|LOCATIONNAME |PROFESSIONAL PROVIDENT SOCIETY INSURANCE C *2 |A|LOCATION |82 *2 |A|KEY |744 |3 |E|dsLOCClaim | *3 |A|xmlns |http://tempuri.org/dsLOCClaim.xsd |4 |E|LOCClaim | |5 |E|CLMLocation |82 |5 |E|CLMKey |744 |5 |E|CLMEncodedSurname |MAR |5 |E|CLMGivenName |Christoffel |5 |E|CLMInitials |CJ |5 |E|CLMDoB |1952-11-23T00:00:00+02:00 |5 |E|CLMNotifyDate |2004-09-08T00:00:00+02:00 |5 |E|CLMRefNumber |236684 |5 |E|CLMClaimCode |Medical |5 |E|CLMIDNumber |521123509006 |5 |E|CLMSyncStatus |S |4 |E|LOCReason | |5 |E|CLMLocation |82 |5 |E|CLMKey |744 |5 |E|CLMReasonImpairment |M24.6

  18. Other Plans Bridge to MS Word for correspondence Bridge to Internal Home Loans Bridge to Home Loan Originators Quotation Service Generic Excel bridge External Business Objects?? etcetcetcetcetcetcetc

  19. QUESTIONS???

More Related