Oracle SOA Suite 10.1.3  Locate

Integrating with Oracle JDeveloper  Locate

The current release of Oracle JDeveloper can use the Oracle Service Registry in the following ways:

  • Create a persistent connection to a Registry instance or cluster

  • Query the Registry using the UDDI v3 inquiry API

  • Retrieve a service WSDL and generate a client-side proxy for the service

For more information, see:

Integrating with BPEL Designer  Locate

BPEL Designer, which is integrated into the JDeveloper environment, allows you to graphically design BPEL processes by dragging and dropping elements into the process and editing their property pages. This eliminates the need to write BPEL code. By integrating BPEL Designer with Oracle Service Registry, you can also search the Registry for services that you can add as partner links to your BPEL process.

To make Oracle Service Registry accessable to Oracle BPEL Designer:

  1. Create a connection to the Registry instance as described in Connecting to Oracle Service Registry from JDeveloper.

  2. Open the BPEL process (*.bpel) file to launch the BPEL Designer.

  3. Right-click in the Partner Links area in the right or left margins of the BPEL Designer view.

  4. Click Create Partner Link.

  5. Click the flashlight icon under WSDL Settings to launch the Service Explorer.

  6. Expand the UDDI Registry node and select the appropriate Oracle Service Registry connection.

  7. Select the Service Provider node representing the business entity the service is published under, then select the service WSDL you want to add as a partner link.

Integrating with Enterprise Service Bus (ESB) Designer  Locate

The ESB Designer allows you to query an Oracle Service Registry instance to select a service to create as an ESB Service or ESB adapter in your Design tab.

To integrate Oracle Service Registry with ESB Designer:

  1. Right click the ESB project (that is, the *.esb file) in JDeveloper.

  2. Select either Create ESB Service or Create Adapter Service.

  3. Click the flashlight icon under WSDL Settings to launch the Service Explorer.

  4. Expand the UDDI Registry node and select the appropriate Oracle Service Registry connection.

  5. Select the Service Provider node representing the business entity the service is published under, then select the service WSDL you want to add.

Enabling Dynamic Lookup of BPEL Partner Link Endpoints  Locate

BPEL Server is now able to query an Oracle Service Registry instance to retrieve the latest endpoint for a service defined as a partner link within a BPEL process. This feature requires that the UDDI serviceKey be added to the bpel.xml file created for the BPEL process.

To enable dynamic lookup of BPEL Partner Link Endpoints:

  1. Open Oracle BPEL Control using either of the following:

    • From the Windows Start menu, select: Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > BPEL Control, or

    • Launch a browser and navigate to the following URL:

      http://ohs_host:ohs_port/BPELConsole

      Where :

      • ohs_host is the address of the Oracle Application Server host machine; for example, server07.company.com

      • ohs_Port is the HTTP listener port assigned to OHS

  2. Select the Configuration tab.

  3. Select the Domain tab.

  4. Specify the target Oracle Service Registry instance to query for the partner link endpoint by entering a value for the uddiLocation property.

    The URI has the following format:

    http://ohs_host:ohs_port/registry_context/uddi/inquiry

    The uddiLocation property must refer to the inquiry WSDL URL of the Oracle Service Registry. For example:

    http://hostname.us.oracle.com:42461/registryrc7/uddi/inquiry?wsdl

    [Note]Note

    There can be only one Oracle Service Registry reference in an Oracle BPEL Process Manager Installation at any point in time.

    For more information, see http://download.oracle.com/docs/cd/E12524_01/relnotes.1013/e12523/bpelrn.htm#BABFFBAH.

  5. Configure the client (BPEL) for HTTP Basic authentication by entering a value for the following properties:

    • registryUsername=admin

    • registryPassword=value

    [Note]Note

    Currenlty, BPEL supports UDDI look up using HTTP Basic authentication only (see HTTP Basic). HTTPS/SSL is not supported for this operation.

    For more information, see Securing the Client with Basic Authentication.

  6. Click Apply.

  7. Get the service key that uniquely identifies the service from Oracle Service Registry.

    1. Launch the Registry Control console and login as admin.

    2. Select the Search tab to search the Registry for the partner link service.

    3. Enter the partner link service name in the Service Name field and click Find service.

    4. In the Find service search results, click the Find link under the Bindings column.

    5. Copy the displayed serviceKey (prefaced by uddi:) to the clipboard.

  8. Launch JDeveloper and open your application's *.bpel file in the BPEL Designer.

  9. Double-click the desired partner link.

  10. In the Edit Partner Link dialog, select the Property tab.

  11. Select Create and add a property. For property name, use registryServiceKey and for property value paste the UDDI service key value you copied from Registry Control.

  12. Click Apply.

  13. Click OK.

  14. Build and package your application and redeploy.

Enabling Dynamic Lookup of ESB SOAP Endpoints  Locate

ESB Server can query an Oracle Service Registry instance to retrieve the latest SOAP endpoint for a service.

To enable dynamic lookup of ESB SOAP Endpoints:

  1. Edit the esb_config.ini file, once per server (for location-based lookup performance), and add the following line:

    • uddiInquiryURL=http://localhost:7777/registry/uddi/inquiry

  2. If the Oracle Service Registry is secured using HTTP Basic authentication (see HTTP Basic), edit the esb_config.ini file, once per server (for location-based lookup performance), and add the following lines:

    • uddiUser=admin

    • uddiPassword=value

    [Note]Note

    Currenlty, ESB supports UDDI look up using HTTP Basic authentication only (see HTTP Basic). HTTPS/SSL is not supported for this operation.

  3. Add an endpoint property to the ESB SOAP Service either in the ESB Control or JDeveloper project.

    For example, in the corresponding .esbsvc file, add the following:

    <endpointProperties>
    <property name="registryServiceKey" value="uddi:oracle:customersvc"/>
    </endpointProperties>"
                
  4. Define a second binding (access point) in the Oracle Service Registry where type is wsdlDeployment and value is the WSDL location.

Integrating with Oracle Web Services Manager (WSM)  Locate

By integrating Oracle Service Registry with Oracle WSM, you can query the Registry to find a service to register at a gateway enforcement component. The selected service will be secured at the gateway.

You integrate Oracle Service Registry with Oracle WSM through the Oracle Web Services Manager Console.

To integrate Oracle Service Registry with Oracle Web Services Manager:

  1. Click Policy Management>Register Services in the Oracle Web Services Manager Console.

  2. Click the Services link for the gateway component you want to use.

  3. Click Import Services.

  4. Supply the Inquiry URL for the target Oracle Service Registry you want to query in the Discovery Service URL field.

  5. Click Display Services.

  6. Check the box for each service you want to register at the gateway.

  7. Click Import when finished.