J2EE 5.0 mandates support for Java API for XML Registries (JAXR). Inclusion of a XML Registry with the J2EE 5.0 certified Application Server is optional. JBoss EAP ships a UDDI v2.0 compliant registry, the Apache jUDDI registry. JAXR Capability Level 0 (UDDI Registries) is also supported through Apache Scout integration.
10.21.3.1. Apache jUDDI Configuration
jUDDI registry configuration happens via a MBean Service that is deployed in the
juddi-service.sar archive in the
all server profile. The configuration of this service can be done in the
jboss-service.xml of the
META-INF directory in the
Let us look at the individual configuration items that can be changed.
<!-- Datasource to Database -->
Database Tables (Should they be created on start, Should they be dropped on stop, Should they be dropped on start etc)
<!-- Should all tables be created on Start-->
<!-- Should all tables be dropped on Stop-->
<!-- Should all tables be dropped on Start-->
JAXR Connection Factory to be bound in JNDI. (Should it be bound? and under what name?)
<!-- Should I bind a Context to which JaxrConnectionFactory bound-->
<!-- Context to which JaxrConnectionFactory to bind to. If you have remote clients, please bind it to the global namespace(default behavior).
To just cater to clients running on the same VM as JBoss, change to java:/JAXR -->
Other common configuration:
Add authorized users to access the jUDDI registry. (Add a sql insert statement in a single line)
Look at the script META-INF/ddl/juddi_data.ddl for more details. Example for a user 'jboss'
INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,
VALUES ('jboss','JBoss User','jboss@xxx','true','true');