7/31/2019 JAX - R

1/19

JAX - R

Saranya.R

7/31/2019 JAX - R

2/19

JAX RProvidersCapability profiles

7/31/2019 JAX - R

3/19

Architecture

7/31/2019 JAX - R

4/19

UDDI and ebXML UDDI (Universal Description, Discovery, and Integration) is an XML-

based registry for businesses worldwide to list themselves on theInternet. Its ultimate goal is to streamline online transactions byenabling companies to find one another on the Web and make theirsystems interoperable for e-commerce. UDDI is often compared to a

telephone book's white, yellow, and green pages. The project allowsbusinesses to list themselves by name, product, location, or the Webservices they offer.

UN/CEFACT is the same group responsible for EDIFACT, one of theelectronic commerce standards more heavily used throughout theEuropean and Pacific continents (the U.S. primarily uses its ownversion, called X12). Hence, it's my belief that if this work can meetsome modicum of maturity and gain a modest following, it's clearly inline for promotion to the throne of e-commerce. That said, this effort isclearly understaffed and the work completed to date seems to illustratea rudimentary understanding of e-commerce without having actually

been part of a real solution.

http://searchsoa.techtarget.com/definition/XMLhttp://searchsoa.techtarget.com/definition/XML

7/31/2019 JAX - R

5/19

JAX R information model

7/31/2019 JAX - R

6/19

Classification of registrydata

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 >

7/31/2019 JAX - R

7/19

Classification of registryobjects

7/31/2019 JAX - R

8/19

Taxonomy Internal

NAICS is an example of an internal taxonomy, because thescheme and all the codes are available inside the JAXRprovider

External

An example of an external taxonomy is the microsoft-

com:geoweb:2000 scheme (based on the ISO 3166 standard)in the Microsoft registry

7/31/2019 JAX - R

9/19

Association of registrydata

Association class

7/31/2019 JAX - R

10/19

JAX R API Registry service

3 sub services

The BusinessLifeCyleManager interface, usedfor creating objects based on the information model

The BusinessQueryManager interface, used to query theregistry using objects from the information model

The DeclarativeQueryManager interface, used to executestatement type queries on the registry

7/31/2019 JAX - R

11/19

JAX R API

7/31/2019 JAX - R

12/19

Connecting// Set the properties for the factory Properties environment = newProperties(); 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();

7/31/2019 JAX - R

13/19

CRUD

7/31/2019 JAX - R

14/19

Get and find

7/31/2019 JAX - R

15/19

Declarative queries

7/31/2019 JAX - R

16/19

JAX R and UDDI

Table 12.4: Mapping of UDDI Inquiry API to JAXR

JAXR BusinessQueryManager UDDI method

findServiceBindings Find_binding

findOrganizations find_business

findAssociatedObjects find_related_business

findServices find_service

findConcepts and find_tModelfindClassificationSchemes

7/31/2019 JAX - R

17/19

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 RegistryInformation Model, because they are identical

(e.g.,Organization interface in JAXR maps to an Organization objectin RIM, etc.) Also, JAXR supports all features and functionality definedby OASIS for the ebXML registry.

7/31/2019 JAX - R

18/19

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 forgerelationships, not only do they need to expose their functions asWeb services, they also need to publish them in a manner

accessible by different partners. Using open standards such asXML, UDDI/ebXML registry, and SOAP eliminates the dependencebetween disparate hardware and software stacks and facilitates aloosely coupled architecture.

JAXR removes the dependence between applications andnonstandard toolkits by giving developers a rich, simple,

standard extension API to communicate with registry providersusing these very same open standards.

It allows applications accessing XML registries to remain vendor-neutral and portable across disparate registry implementations .

7/31/2019 JAX - R

19/19

Thank you