JAX - R

Saranya.R

JAX R
Providers Capability profiles

Architecture

UDDI and ebXML

UDDI (Universal Description, Discovery, and Integration) is an XMLbased registry for businesses worldwide to list themselves on the Internet. Its ultimate goal is to streamline online transactions by enabling companies to find one another on the Web and make their systems interoperable for e-commerce. UDDI is often compared to a telephone book's white, yellow, and green pages. The project allows businesses to list themselves by name, product, location, or the Web services they offer. UN/CEFACT is the same group responsible for EDIFACT, one of the electronic commerce standards more heavily used throughout the European and Pacific continents (the U.S. primarily uses its own version, called X12). Hence, it's my belief that if this work can meet some modicum of maturity and gain a modest following, it's clearly in line for promotion to the throne of e-commerce. That said, this effort is clearly understaffed and the work completed to date seems to illustrate a rudimentary understanding of e-commerce without having actually been part of a real solution.

JAX R information model

Classification of registry data

Home > Business and Economy > Shopping and Services > Financial Services > Banking > Banks > By Region > U.S. States > Connecticut U.S. States > Connecticut > Cities > Manchester > Business and Shopping > Business to Business >

Classification of registry objects

Taxonomy
Internal NAICS is an example of an internal taxonomy, because the scheme and all the codes are available inside the JAXR provider External An example of an external taxonomy is the microsoftcom:geoweb:2000 scheme (based on the ISO 3166 standard) in the Microsoft registry

Association of registry data

Association class

JAX R API
Registry service 3 sub services The BusinessLifeCyleManager interface, used for creating objects based on the information model The BusinessQueryManager interface, used to query the registry using objects from the information model The DeclarativeQueryManager interface, used to execute statement type queries on the registry

 JAX R API

Connecting
// Set the properties for the factory Properties environment = new Properties(); environment.setProperty("javax.xml.registry.queryManagerURL", QUERY_URL); environment.setProperty("javax.xml.registry.lifeCycleManagerURL", PUBLISH_URL); // Instantiate the factory and create a connection from it ConnectionFactory connfactory = ConnectionFactory.newInstance(); connfactory.setProperties(environment); Connection connection = connfactory.createConnection(); // Authenticate the username and password with the registry PasswordAuthentication passwdAuth = new PasswordAuthentication(uddiusername, uddipassword.toCharArray()); Set credentials = new HashSet(); credentials.add(passwdAuth); connection conn.setCredentials(credentials); // Obtain a reference to the registry service RegistryService registryservice = connection.getRegistryService();

CRUD

Get and find

Declarative queries

JAX R and UDDI

Table 12.4: Mapping of UDDI Inquiry API to JAXR

JAXR BusinessQueryManager
findServiceBindings findOrganizations findAssociatedObjects

UDDI method
Find_binding find_business find_related_business

findServices
findConcepts and findClassificationSchemes

find_service
find_tModel

JAX R and ebXML

Figure 12.19: ebXML registry browser

Mapping of ebXML Registry Information Model to JAXR No mapping is required from the JAXR model to the ebXML Registry Information Model, because they are identical (e.g.,Organization interface in JAXR maps to an Organization object in RIM, etc.) Also, JAXR supports all features and functionality defined by OASIS for the ebXML registry.

To sum up.
In this chapter, we looked at JAXR and its functionality. So, why is this API important, and why should developers use it? For businesses to communicate with their partners and forge relationships, not only do they need to expose their functions as Web services, they also need to publish them in a manner accessible by different partners. Using open standards such as XML, UDDI/ebXML registry, and SOAP eliminates the dependence between disparate hardware and software stacks and facilitates a loosely coupled architecture. JAXR removes the dependence between applications and nonstandard toolkits by giving developers a rich, simple, standard extension API to communicate with registry providers using these very same open standards. It allows applications accessing XML registries to remain vendorneutral and portable across disparate registry implementations .

Thank you