Table of Contents

  1. Main Messages
  2. Demo: Physical Description
  3. Starting The JAXR Demo
  4. Running the JAXR Demo
  5. Stopping the JAXR Demo
  6. Frequently Asked Questions
  7. Troubleshooting

Main Messages

Demo: Physical Description

Starting the JAXR Demo

Running the JAXR Demo

This section describes the actual running of the demo. It is suggested that you run the demo on the demo machine while you run the slides on a second machine and use the demo to illustrate various talking points. If that is not possible you may have to switch between slides and demo window during demo. The demo assumes that the MegaDB test database is being used by the registry. That database is loaded using the createMegaDB target in ebxmlrr module.

Note that actions you must perform are described in bold and underlined.
 

ebxmlrr provides a Registry Browser and JAXR API

Arbitrary Content Management

Standardized Metadata


User Defined Taxonomies

Content Publishing


 

Content Discovery Using Ad Hoc Queries

Internationalization features

SOAP and HTTP Interface

Authentication Based on XML Digital Signatures


 

Stopping the JAXR Demo

Frequently Asked Questions

General Questions

Q: What are the Main differences between ebXML and UDDI?
A: On surface they mat appear similar but they are very different animals altogether.

ebXML Registry is a general purpose content management system capable of managing arbitrary content. It is much like a relational database for arbitrary content. It provides automatic content-specific  validation and cataloging of any type of submitted content. It supports complex arbitrary ad hoc quires using SQL and XML filter query syntax. It is a knowledge management system capable of being a taxonomy server. The taxonomies may be arbitrary and user-defined and can be used to classify any type of content. Any two content instances may be related in arbitrary relationships thus giving meaning to content. ebXML registry is a distributed object database. It is also an event notification engine. It provides digital signature based security by design since its inception and not as an afterthought. Its information is extensible so you can define new types of objects within the model.

UDDI in comparison is very specifically designed for simple registration/lookup of businesses and services. It only supports 4 types of things (business, service, binding, tModel) and does that in a rigid way. You can only search using pre-defined queries (no ad hoc queries), it does not have a repository and cannot handle arbitrary content (thus no content validation or cataloging). It only supports a fixed set of taxonomies and does not allow user-defined taxonomies. It supports only fixed relations between Organizations. Its information model is not extensible. As someone from Boeing put it, "UDDI is a one trick pony".
 

Q: How are organizations using ebxmlrr
A: Due to its flexibility ebXML Registry is being used in a wide array of domains. Some of the use cases are:

-Taxonomy server

-Ontology server

-Web Service registry

-Business Process Catalog server

-GeoSpatial data server

-Medical Guidelines server

-eGov forms servers

-XACML Policy Server (coming soon)

Q: How is ebXML Registry adoption. Who is using it?
A: ebXML Registry is being adopted by entire verticals, governments, fortune 500 companies and SMEs.

Here are some examples:

Adobe: PDF-XML Forms  for eGov

Apelon: Medical guidelines registry

COSMOS: Statistical data registry

eGov: Australia, Canada, Finland

GM: ebCPA, ebBP registry

HL7: Conformance Profile registry

Republica: CC/BIE registry - eGov

RosettaNet: Dictionary of RN artifacts

SDMX: Global debt statistics registry

Sun: Web Services registry
 

Q: What is the role of JAXR in J2EE(TM)?
A:  JAXR provides access to business registries within the J2EE platform. It is a key part of the J2EE platform's support for web services.
Q: What is the relationship between JAXR and ebXML Registry standard?
A: JAXR is a Java API for accessing business registries. The JAXR API supports dominant registry standards. ebXML Registry specification is a United Nations and OASIS sponsored standard for business registries. ebxmlrr provides access to any ebXML Registry 1.0 compliant registry.
 

Q: Where can I find more information?
A: Please see links below
 

[1] Comparison of Directories (e.g. LDAP), Basic Registry(e.g. UDDI) and Advanced
Registries (e.g. ebXML Registry)

http://ebxmlrr.sourceforge.net/ebxmlrr-spec/Registry_Capability_Matrix.html

[2] ebXML Registry Presentations

http://ebxmlrr.sourceforge.net/presentations/ebXMLRegistryV3OverviewIncludesV2.sxi

http://www.oasis-open.org/committees/regrep/presentations/kbreiningerstandardstrackmonday.ppt

http://www.oasis-open.org/committees/regrep/presentations/finalforumdistribution_012103_1.ppt
 

[3] ebXML Registry Technical Committee

http://www.oasis-open.org/committees/regrep/

[4] Latest ebXML Registry Specifications

 http://ebxmlrr.sourceforge.net/ebxmlrr-spec/ebRIM-v2.35.doc

 http://ebxmlrr.sourceforge.net/ebxmlrr-spec/ebRS-v2.35.doc

[5] Java API for XML Registries

http://www.jcp.org/en/jsr/detail?id=93

[6] Royalty Free Open Source Implementation of ebXML Registry and JAXR

http://ebxmlrr.sourceforge.net

http://ebxmlrr.sourceforge.net/presentations/ebxmlrr-xmlEurope2003.sxi (latest slides)
 

Technical Questions

 

Troubleshooting

This section provides a troubleshooting guide if the tests for demo setup fail.
 

System running slow after many hours of running

Functional Problems and Failures

If all else fails contact Farrukh Najmi.