1. Using XML Transactions Presented By Tony Alwardt The Boeing Company

2. Introduction Provides a common dialect to be used between two are more parties

3. Benefits Fewer Schemas to Maintain and Develop Against Schema performs initial required data validation instead of application software Transactions give XML tags context sensitive meaning System integrators only deal with transactions they require The ability to tie requests and responses together Provides built in error elements for every transaction Readily supports Synchronous & Asynchronous Communication Readily supports Batch Processing Supports Passing Application Level Security Credentials

4. Multiple Schemas System 1 XML Transaction Type 1 Request System 2 XML Schema 1 XML Transaction Type 1 Response XML Transaction Type 2 Request XML Transaction Type 2 Response System 3 XML Schema 3 XML Schema 2 XML Schema 4

5. Integrated Schema XML Transaction Type 1 Request Integrated XML Schema XML Transaction Type 1 Response XML Transaction Type 2 Request XML Transaction Type 2 Response System 1 System 2 System 3

6. Validation (Traditional Schema Use) XML Document XML Schema Schema verifies that the XML document is in the correct format. Software Library Software verifies that the XML document contains the appropriate required XML elements/attributes. System 1 System 2

7. Validation (Transaction Schema Use) XML Document XML Schema Schema verifies that the XML document is in the correct format and that the required XML elements/attributes exist. Software Library This block is potentially no longer required. System 1 System 2

8. Context Sensitive Meaning JCNARN001 Demo 2005 SN0001 MAN001 Add Work Orders Transaction

9. Context Sensitive Meaning JCNARN001 Demo2005 SN0001 A1 Update Work Orders with Indictments

10. Context Sensitive Meaning JCNARN001 Demo2005 SN0001 CARD001 TRFDV A1 Update Work Orders with Repairs

11. Easier Integration via Transactions Example: 5 Available Transactions User 1User 2 3 Transactions Used by User 12 Transactions Used by User 2

12. Request/Response Model Supports echoing the request in the response (Especially useful with asynchronous systems) Master Key XYZ Master Key XYZ Response Request

13. Error Processing Required “ResultCode” element exists in every transaction response Master Key XYZ Communication Error. Master Key XYZ Result Info

14. Synchronous vs. Asynchronous Processing Readily supports Synchronous & Asynchronous Communication XML Document Synchronous Communication XML Document System 1 System 2

15. Synchronous vs. Asynchronous Processing Readily supports Synchronous & Asynchronous Communication XML Documents Asynchronous Communication XML Documents Echoing the initial request with the response enables Asynchronous Communication. System 1 System 2

16. Batch Transaction Processing Readily supports Batch Processing XML Requests XML Responses The schema can support sending multiple request transactions in one XML Document. The same applies for response transactions. System 1 System 2

17. Application Level Security Credentials Application Level Security Credentials can be included in a Request Transaction. String String String 1967-08-13 14:20:00-05:00 Master Key XYZ Security Info

18. Questions ?