Page Four: Dynamic e-business using Web service workflow
UDDI - understanding tModels
UDDI and ebXML Registries/Repositories can be used collaboratively. For example, metadata fields in a UDDI registry can serve as a locator (e.g. a URL) for the associated data stored in an ebXML registry/repository, thereby allowing a UDDI registry to "point to" an ebXML registry/repository. With this in mind, a likely infrastructure model is to use public UDDI registries for basic service advertising, and private ebXML registry/repositories for storage of actual XML resources.
tModels provides a means for businesses to publish information about the specifications and versions of specifications used to design their advertised services within a UDDI registry. This information about specifications is called a tModel within UDDI. The tModel mechanism serves a useful purpose in discovering Web service providers that support a given standard specification. The UDDI API call find_business can be used to located businesses that satisfy a given tModel pattern.
Implementing the Web services workflow
In order for a Web service workflow to be able to support business collaboration using the ebXML standard, it needs to support the ebXML Message Service functionality. Sun Java API for XML Messaging (JAXM) is available as a reference implementation for businesses interested in quickly adopting ebXML Message Service functionality. The Sun ebXML Registry/Repository Implementation (RegRep) can be used to submit, store, retrieve, and manage resources to facilitate ebXML-based business-to-business (B2B) partnerships and transactions. Submitted information may be, for example, XML schema and documents, business process descriptions, business context descriptions, UML models, business collaboration information, core components, or even software components. The RegRep implementation uses Enterprise Java Beans (EJB) technology, which reduces development complexity while providing automatic support for middleware services such as database connectivity, transaction management, scalability, and security.
ebXML Technical Architecture Specification v1.0.4
Business Process and Business Information Analysis Overview v1.0
UDDI API Specification
Sun ebXML Registry/Repository Implementation (RegRep)
Copyright 2002. Reprinted with permission. Cysive, Inc. builds mission-critical business systems for Global 2000 firms to help orchestrate interactions with customers, partners and employees across multiple channels such as web, wireless, voice and Web services.
About the Author:
Pravin R. Morais is a software engineer at Cysive, Inc. where he works in Product Development on the Cymbio Interaction Server. Pravin is a Sun Certified Java Programmer and Java Developer, and has a BS in Electronics and Telecommunication Engineering. Pravin may be reached at email@example.com.
For More Information:
- Looking for free research? Browse our comprehensive White Papers section by topic, author or keyword.
- Are you tired of technospeak? The Web Services Advisor column uses plain talk without the hype.
- For insightful opinion and commentary from today's industry leaders, read our Guest Commentary columns.
- Hey Codeheads! Start benefiting from other time-saving XML Developer Tips and .NET Developer Tips.
- Visit our huge Best Web Links for Web Services collection for the freshest editor-selected resources.
- Choking on the alphabet soup of industry acronyms? Visit our helpful Glossary for the latest lingo.
- Visit Ask the Experts for answers to your Web services, SOAP, WSDL, XML, .NET, Java and EAI questions.
- Discuss this issue, voice your opinion or just talk with your peers in the SearchWebServices Discussion Forums.