8. XML-EAI

Design and Implementation Considerations

• Design and Modeling Tools
• Development Tools and Consideration
• Sun’s Java API for XML Processing (JAXP)
• Java API for XML Messaging (JAXM)
• .NET
• Free WSDL Editor – www.capeclear.com/wsdleditor/
• Development snapshot, from p. 14, November 2002, Application Development Trends
• Integration with legacies (47%)
• Integration with packages (43%)
• Skill availability (42%)
• Training (42%)
• Web development (31%)
• Technology standards (25%)
• New/emerging technologies (21%)
• Outsourcing (16%)
• Java (15%)
• Platform selection (14%)
• Requirements consideration
• Functionality
• Performance
• Non-functionality: scalability, reliability, availability, extendibility, etc.
• Deployment Platform and Technologies
• XHTML
• XML
• Use XML as a data interchange format
• Use XML as an intermediate data format
• Use XML as a content format
• Use XML as an operational data format (format for instructions)
• CGI, Servlets, JSP, ASP, etc
• Servlets, Javabean, EJBs http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/web-tier/web-tier5.html
• SOAP
• WSDL
• UDDI
• Server Infrastructure:
• Content servers or Web servers (HTML, XHTML, XML)
• Application servers (middle tire)
• Business and control logic
• Preparing results for presentation
• Data servers (data tier)
• Unify and simplify data access interface
• Aggregate data from various sources
• Consolidate requests and performance improvement
• More servers
• Integration servers
• Portal servers
• Personalization servers

References:

• Kevin Dick, Look at Storage Issues Before You Leap into XML, Application Development Trends, pp. 45-49, http://WWW.ATDMAG.COM