-
Notifications
You must be signed in to change notification settings - Fork 0
Administration
There are several different ways to administrator and configure jUDDI. This section will outline and/or link to relevant information to assist you.
If you want to change the port Tomcat listens on to something non-standard (something other than 8080):
jUDDI Server (Tomcat) - This assumes you are using the jUDDI server bundled with Apache Tomcat. For other application servers, consult their documentation, however the juddiv3.properties must still be altered. . edit conf/server.xml and change the port within the <Connector> element . edit webapps/juddiv3/WEB-INF/classes/juddiv3.properties and change the port number jUDDI Portal . edit webapps/uddi-portlets/WEB-INF/classes/META-INF/uddi.xml and change the port numbers within the endpoint URLs . edit pluto/WEB-INF/classes/server.xml and change the port within the <Connector> element
There are a few options for deploying jUDDI to another application server and/or web service stack. . Grab the default prebuilt war file and modify it to work in your environment . Download the source code for jUDDI and run the maven integration script. Use the following steps
*Target platform Tomcat and Derby using OpenJPA and CXF. Both OpenJPA and CXF are packaged up in the juddiv3.war. <pre> mvn clean package -P openjpa </pre>
*Target platform Tomcat and Derby using Hibernate and CXF. Both Hibernate and CXF are packaged up in the juddiv3.war. <pre> mvn clean package -P hibernate </pre>
*Target platform Tomcat and Derby using OpenJPA and Apache Axis2. Both Hibernate and Axis2 are packaged up in the juddiv3.war. <pre> mvn clean package -P axis2 </pre>
*Target platform JBoss-6.x and HSQL using Hibernate and JBossWS-native. The juddiv3.war relies on Hibernate and JBossWS-native in the appserver. <pre> mvn clean package -P hibernate-jbossws-native </pre>
*Target platform JBoss-6.x and HSQL using Hibernate and JBossWS-cxf. The juddiv3.war relies on Hibernate and JBossWS-cxf in the appserver. <pre> mvn clean package -P hibernate-jbossws-cxf </pre>
KNOWN ISSUES <pre> I. 15:14:37,275 SEVERE [RegistryServlet] jUDDI registry could not be started. org.apache.commons.configuration.ConfigurationException: java.util.zip.ZipException: error in opening zip file: org.apache.commons.configuration.ConfigurationException: org.apache.commons.configuration.ConfigurationException: java.util.zip.ZipException: error in opening zip file
Workaround: deploy juddiv3.war as a directory (not a zip file).
II. JBoss-5.x Note that configuration 3 and 4 will also run on JBoss-5.x, but you may run into the following: ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] (main) [domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolve]::Message=src-resolve: Cannot resolve the name 'ns1:Signature' to a 'element declaration' component.
for which there is the following workaround:
-
unzip the deployers/jbossws.deployer/jbossws-native-core.jar and add the xmldsig-core-schema.xsd in the schema directory,
10293 Fri May 27 14:40:40 EDT 2011 schema/xmldsig-core-schema.xsd
-
and edit the
META-INF/jbossws-entities.properties
by adding a line at the bottom saying:
http\://www.w3.org/2000/09/xmldsig#=schema/xmldsig-core-schema.xsd
</pre>