Using Oracle Service Registry in Soa Suite 11g

Oracle released a new version of Oracle Service Registry and this 11.1.1.2.0 version is compatible with Soa Suite 11g. In this blog I will show you, how you can use the OSR UDDI Services in Soa Suite 11G. Basically this are steps I did in this blog. Start with installing OSR , Make an UDDI connection in JDeveloper, Add a Business Entity in the OSR, Publish a Soa Web Service to the UDDI registry ( We will do this in JDeveloper ) , Use this Web Service UDDI reference in an other composite and configure the Soa Suite so it can lookup this service in the UDDI registry.

We start by downloading OSR and Oracle Weblogic 11G ( 10.3.2 or 10.3.1 ) .
Install Oracle Weblogic and unpack the OSR zip. Open command and set the java home and path.

set JAVA_HOME=c:\oracle\wls1032\jdk160_14_R27.6.5-32
set PATH=%JAVA_HOME%\bin;%PATH%
java -jar oracle-service-registry-11.1.1.jar

I choose for a standalone registry

We need to install OSR in a folder located in the Weblogic 10.3.2 middleware home.

OSR need to have a repository

I decided to use a datasource for connecting to the OSR repository

I select the domain option, this will create a new Weblogic domain template.

We are finished with installing OSR and now we can create a new Weblogic domain. Start the configuration wizard. We need to select the Oracle Service Registry Option.

When you install OSR on the same server as your Soa Suite server then you can better change the port number of the adminserver else you can get port conflicts and or config.xml corruption.

Start the OSR admin server ( startWeblogic.cmd in your domain home ) and from the domain bin folder we can start the OSR server( startManagedWeblogic osr_server1 )

Start JDeveloper 11g R1 PS1 and add a new UDDI Registry Connection. We need to provide the UDDIv2 inquiry url ( http://server:7101/registry/uddi/inquiry)

In the resource palette we can see the created UDDI Server.

To fill this registry we need to create our own Business entity. Go the registry control console ( http://laptopedwin.wh.lan:7101/registry/uddi/web )





We can go back to JDeveloper resource palette and open the Soa application server connection. Open the right composite application and select the Web service we want to publish to the OSR. Use the right mouse button and select publish WSDL to UDDI.

Provide the username and password and select your own Business Entity.

When we refresh the OSR UDDI connection we can see the Service under the business entity.

To get more UDDI information over this service we can select the service and use the right mouse button to generate a report.

We are ready to use this UDDI service in a composite application. Add the Web Service adapter to the composite and we will lookup the WSDL in the resource palette. Go to the OSR Registry connection and select the service under the Business Entity

We need to choose if we want to lookup this web service for every soa instance in the UDDI server or only once during deployment.
This is how the ws binding looks like in the composite.xml, No hard coded endpoints.

 <reference name="HelloService" ui:wsdlLocation="BPELProcess1.wsdl">
   <interface.wsdl interface="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.interface(BPELProcess1)"/>
   <binding.ws port="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)"
               location="orauddi:/uddi:d798e4c0-f4ab-11de-8e46-d0e4b9a18e45">
     <property name="oracle.soa.uddi.serviceKey" type="xs:string" many="false">uddi:d798e4c0-f4ab-11de-8e46-d0e4b9a18e45</property>
   </binding.ws>
 </reference>

Last step is to provide the UDDI v2 inquiry url, No need to specify the user and password. After this you need to restart the Soa Server.

Finally test your composite services with the UDDI Service references.