How to configure UDDI Server with in EDK with a 4.5WS?

Question

I'm trying to develop a crawler service using EDK5.0.1 with a 4.5ws portal.
To do this job, I have to deploy and coufigure a UDDI Server which is a requirement for services in 4.5ws.
After develping and deploying a crawler service, I created gadget server in the 4.5ws portal, and tried to add remote data source, but the popup window for datasource seems not to be able to find the crawler service and showed 'Empty Gadget Server'.
I think I set up the uddi server with a wrong way, but I don't know what I have to do more to set a uddi server.
Actually, after developing crawler service and sci service, I deployed these with DeployServlet which is a deploy toolkit offered by EDK.
With this deploying result, I modified the uddi.xml file and put that file into c:\program files\Plumtree\ptedk\5.0\devkit\config\java\uddi folder.
Is there any things to set for uddi server?
Can anybody provide me any advise on this?
Any help would be appricated.

Answer 1

The UDDI is used with web services in 4.5x. This is best described as a phone book of URLS for any web services installed in that machine. Those URLS will then point to the individual web services.
In 5.0 the UDDI server is not needed since it is replaced with the "Remote Server" and "Web Services" tabs. HOw to setup a UDDI with TOMCAT
UDDI can be setup to run with TOMCAT and I believe this is the only one provided in the EDK installer in the ptedk\5.0\devkit\java directory
Here's a little TOMCAT information. Web applications are deployed in a folder called "webapp". This case, we have a uddi server installed and it's in a folder called "uddi". So, our file structure for the UDDI server looks like: /webapp - tomcats web application folder /uddi - the uddi application /WEB-INF - standard WEB-INF directory stores java classes, jars and any descriptor files. server-config.wsdd - this is the web service descriptor file for this uddi server - provided by plumtree web.xml - this is the web.xml descriptor file for how the web services in this application will be loaded and run - provided by plumtree /lib - contains the jar files for the uddi server - provided by plumtree The server-config.wsdd file should be the only item that the user needs to modify. Within the file (XML based), there should be the following tag: <!--service for uddi server--> <service name="MessageService" provider="java:MSG" style="message"> <parameter name="allowedMethods" value="find_tModel find_business find_binding"/> <parameter name="className" value="com.plumtree.remote.uddi.UDDIServer"/> <!-- enter the base url for your services. The individual urls will be appended to this url--> <parameter name="baseUrl" value="http://rickc-loaner:81/ntcws/"/> <!-- Enter true if this is dotnet, leave at false if the service is java--> <parameter name="isDotNet" value="true"/> <!-- enter only the urls and names required for your service. For a java crawl, this would be crawler name, documentProviderRpc, containerProviderRpc, sciDataSourceRpc, sciCrawlRpc, and sciCardRpc if using remote card submission--> <!-- Enter the crawler name. This is the name that will show when expanding the remote server--> <parameter name="crawlerName" value="NT File CWS"/> <!-- Enter the auth name. This is the name that will show when expanding the remote server--> <parameter name="authName" value=""/> <!-- Enter the relative url to the rpc (Java) document provider soap endpoint --> <parameter name="documentProviderRpc" value="DocumentProviderSoapPort"/> <!-- Enter the relative url to the rpc (Java) container provider soap endpoint --> <parameter name="containerProviderRpc" value="ContainerProviderSoapPort"/> <!--sci values: the url for datasource, crawl and card may be the same--> <!-- Enter the relative url to the rpc (Java) sci data source soap endpoint --> <parameter name="sciDataSourceRpc" value="SciSoapPort"/> <!-- Enter the relative url to the rpc (Java) sci crawl soap endpoint --> <parameter name="sciCrawlRpc" value="SciSoapPort"/> <!-- Enter the relative url to the rpc (Java) sci card soap endpoint --> <parameter name="sciCardRpc" value=""/> <!-- note that relative auth only works in rpc for 4.5--> <!-- Enter the url to the auth provider soap endpoint --> <parameter name="authProvider" value=""/> <!-- Enter the relative url to the sync provider soap endpoint --> <parameter name="syncProvider" value=""/> <!-- Enter the relative url to the auth sci (rap) soap endpoint --> <parameter name="authSci" value=""/> <!-- Enter the relative url to the doclit (.NET) document provider soap endpoint --> <parameter name="documentProviderDoclit" value="documentprovidersoapbinding.asmx"/> <!-- Enter the relative url to the doclit (.NET) container provider soap endpoint --> <parameter name="containerProviderDoclit" value="containerprovidersoapbinding.asmx"/> <!--sci values: the url for datasource, crawl and card may be the same--> <!-- Enter the relative url to the doclit (.NET) sci data source soap endpoint --> <parameter name="sciDataSourceDoclit" value="xuiservice.asmx"/> <!-- Enter the relative url to the doclit (.NET) sci crawl soap endpoint --> <parameter name="sciCrawlDoclit" value="xuiservice.asmx"/> <!-- Enter the relative url to the doclit (.NET) sci card soap endpoint --> <parameter name="sciCardDoclit" value="xuiservice.asmx"/> </service> This tag contains the information that will be specific to the user's deployment of the web service (CWS or AWS).First off: <parameter name="baseUrl" value="http://machinename:81/ntcws/"/>
This is the location of the web server that has the target web service installed. THIS CANNOT BE "localhost". This has to be a resolvable machine name or IP address. In 5.0 this is the Remote Web Service settings. Second, you need to set the type of web service. <!-- Enter true if this is dotnet, leave at false if the service is java--> <parameter name="isDotNet" value="true"/> If your app server hosting the web service is dotnet, you need to set this to "true". This is equivalent to the Document encoding setting in 5.0. .NET supports Document/Literal incoding instead of RPC for Java. Third, name your web services. This is the name that will display in the drop down list in 4.5WS when you decide to create a remote data source. <!-- Enter the crawler name. This is the name that will show when expanding the remote server--> <parameter name="crawlerName" value="NT File CWS"/> <!-- Enter the auth name. This is the name that will show when expanding the remote server--> <parameter name="authName" value=""/> This is the web service name property when you create a new web service in 5.0. Next are the configuration settings for your particular web service: <!-- Enter the relative url to the rpc (Java) document provider soap endpoint --> <parameter name="documentProviderRpc" value="DocumentProviderSoapPort"/> <!-- Enter the relative url to the rpc (Java) container provider soap endpoint --> <parameter name="containerProviderRpc" value="ContainerProviderSoapPort"/> <!--sci values: the url for datasource, crawl and card may be the same--> <!-- Enter the relative url to the rpc (Java) sci data source soap endpoint --> <parameter name="sciDataSourceRpc" value="SciSoapPort"/> <!-- Enter the relative url to the rpc (Java) sci crawl soap endpoint --> <parameter name="sciCrawlRpc" value="SciSoapPort"/> <!-- Enter the relative url to the rpc (Java) sci card soap endpoint --> <parameter name="sciCardRpc" value=""/> <!-- note that relative auth only works in rpc for 4.5--> <!-- Enter the url to the auth provider soap endpoint --> <parameter name="authProvider" value=""/> <!-- Enter the relative url to the sync provider soap endpoint --> <parameter name="syncProvider" value=""/> <!-- Enter the relative url to the auth sci (rap) soap endpoint --> <parameter name="authSci" value=""/> <!-- Enter the relative url to the doclit (.NET) document provider soap endpoint --> <parameter name="documentProviderDoclit" value="documentprovidersoapbinding.asmx"/> <!-- Enter the relative url to the doclit (.NET) container provider soap endpoint --> <parameter name="containerProviderDoclit" value="containerprovidersoapbinding.asmx"/> <!--sci values: the url for datasource, crawl and card may be the same--> <!-- Enter the relative url to the doclit (.NET) sci data source soap endpoint --> <parameter name="sciDataSourceDoclit" value="xuiservice.asmx"/> <!-- Enter the relative url to the doclit (.NET) sci crawl soap endpoint --> <parameter name="sciCrawlDoclit" value="xuiservice.asmx"/> <!-- Enter the relative url to the doclit (.NET) sci card soap endpoint --> <parameter name="sciCardDoclit" value="xuiservice.asmx"/> These are equivalent to setting the Document provider URL, Container Provider URL, Remote UI URL etc etc that are in 5.0 web services settings. Once you have installed the UDDI server, and started TOMCAT, you should be able to hit the services list at:http://machinewithuddi:8080/uddi/services This will become your Remote Gadget Server URL and you should be good to go!!