Leveraging Service Directories in the Case Study

The concept of a service directory is central to the concept of sharing your application and locating other potential partners. Your application will be ready for the day that you can allow your program to locate new business partners without intervention from management, but you will not push forward to deploy such grandiose mechanisms. More important than technical coolness is a dose of reality and simple pragmatic deployment. Your company will enter business partner query criteria by hand and only allow your program to select known business partners for now.

From the requirements presented in Chapter 2, "Introducing the P.T. Monday Case Study," the service directory fulfills only a couple of key requirements, shown in Table 5-1.

Table 5-1: Business Requirements




The application shall have the ability to integrate bean suppliers into the company's value chain.


The application shall embrace open standards for the external API.

All of the Web Service infrastructure pieces build up only a few essential requirements of system integration with external business partners. Only when you start building business objects and processes can you see how your application fulfills the concrete requirements, such as providing notifications or access to particular types of data.

Identifying Important Classes and Files in the Case Study

Table 5-2 shows the primary code discussed in this chapter that you should browse in the downloaded source code.

Table 5-2: Sample Location





com\servicefoundry\books\ webservices \util

This program contains the UDDI code presented in this chapter. The program publishes, queries, and deletes UDDI information from the IBM test registry. You must obtain a user ID from the IBM test registry and replace the uddiUserId and uddiPassword properties in the build.properties file.

Using Ant Targets to Run the Case Study

Table 5-3 describes the targets to run for the ant environment to see the programs and chapter samples in operation. Before running any samples, be sure you read and perform all of the install steps in Appendix A.

Table 5-3: Ant Targets




Publishes entries to the UDDI directory and tests that the entries can be subsequently located using the UDDI query mechanisms


Removes entries from the UDDI directory

Web Service Patterns
Web Services Patterns: Java Edition
ISBN: 1590590848
EAN: 2147483647
Year: 2003
Pages: 190

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net