1.5.1 Building a Complete Example Throughout the book, a Foreign Exchange trading Web application example will be built. To build a complete application (see Figure 1-3), you can follow the examples and concepts in the book to wrap an existing business service as Web Services (for example, using JWSDP's wsdeploy or Axis), publish it in a Service Registry (for example, using JAXR), expose the business service via a Message Provider (for example, using JAXM), and/or parse data from the business partners using JAXP and XSLT. Figure 1-3. Building a Complete Example  1.5.2 Chapter Overview The "Chapter Overview" highlights the main ideas of each chapter for both quick preview and recapitulation. For Example: -
Web Services, units of business services and components , is positioned as the next IT strategy for enterprises . The enabling technologies are built on top of Java and XML. They are also referenced as "Java Web Services" or "XML Web Services." -
The Web Services technology stack includes the transport layer (such as SOAP), a service description language (such as WSDL), and transaction routing and service negotiation (such as BP). -
Web Services has many associations with CORBA. Some perceive Web Services technology is a reincarnation of Application Service Provider and CORBA. -
Microsoft's version of Web Services is .NET, with C# as one key development language. Sun, IBM, and other technology vendors are using Java as the key underlying technology. 1.5.3 Objectives The "Objectives" section identifies the learning objectives of each chapter to help you appreciate why and how the technology is used. For Example: -
To identify the root and derivation of Web Services technologies -
To have an appreciation of the underlying Web Services technologies, their benefits, and when to use them -
To establish some guidelines in choosing a Web Services developer tool and platform in the marketplace -
To illustrate four steps to enable a simple application for Web Services -
To illustrate what Web Services solutions are available on the market, along with their benefits and limitations 1.5.4 Best Practices and Pitfalls The "Best Practices and Pitfalls" section suggests industry-best practices and pitfalls for the specific Web Services technology. You can use this section as a checklist for good design practice or pitfalls to avoid. For Example: Pitfalls -
Do not try to have too many dependencies or items that require longer lead time (for example, do not try to SOAP-enable a mainframe platform). -
Do not start implementation without senior management support. -
Do not start a pilot using a mission-critical functionality. -
Do not involve a big team in the pilot. Start with a small team. 1.5.5 Case Study The "Case Study" section illustrates how the technology is used, its critical success factors, and its implementation pitfalls. For Example: Challenges A medium-size listed financial institution in Hong Kong wants to reduce its operating costs associated with supporting legacy systems on a mainframe. The corporation has been innovative and reputable in providing securities trading, retail banking, and credit card services to the local market. The CEO is concerned about implementing new technology for technology's sake and believes that not all legacy systems need to be migrated to UNIX, as they are fairly stable. Is it relevant to introduce Web Services technology to meet its challenge? |
1.5.6 Paper and Pencil The "Paper and Pencil" section provides some study questions and simple hands-on exercises for practice. For Example: Hands-on Lab. Download the Web Services Developer Pack from http://java.sun.com . Install and configure it according to the Installation Guide. Based on the sample sniplet tradeOrder.xml in the text below (see Figure 1-4), write your first JAXM-SOAP program with your favorite editor or your favorite Integrated Developer Environment to send the following XML message: Figure 1-4 Trade Order in XML (tradeorder.xml) <trade> <tradeHeader> <partyTradeIdentifier> <partyReference href="#XYZ"/> </partyTradeIdentifier> <partyTradeIdentifier> <partyReference href="#ABC"/> </partyTradeIdentifier> <tradeDate>2002-01-15</tradeDate> </tradeHeader> <fxSimpleOption> <productType>Nondeliverable Option</productType> <buyerPartyReference href="#XYZ"/> <sellerPartyReference href="#ABC"/> <expiryDateTime> <expiryDate>2002-04-09</expiryDate> <hourMinuteTime>1000</hourMinuteTime> <businessCenter>USNY</businessCenter> </expiryDateTime> <exerciseStyle>European</exerciseStyle> </fxSimpleOption> </trade> 1.5.7 Resources and References The "Resources and References" section lists useful and relevant articles, magazines, books, and URLs for further reading. URLs provide a frequently updated link to major Web Services resources where books may become outdated . For Example: -
Web Services Resource Web Sites http://www. webservices .org http://www.theserverside.com/home/index.jsp -
Web Services Overview John Hagel III and John Seely Brown. " Your Next IT Strategy ." Harvard Business Review, October 2001. IBM Web Services Overview Team. " Web Services Architecture Overview ." IBM, September 2000. http://www-106.ibm.com/developerworks/library/w-ovr/ Lawrence Wilkes. " Web Services ”Right Here, Right Now ." IBM, 2002. http://www.3.ibm.com/software/solutions/webservices/pdf/cbdi.pdf  |
