Oracle SOA Suite 11g  Locate

Oracle SOA Suite provides a complete set of service infrastructure components for designing, deploying, and managing composite applications. Oracle SOA Suite enables services to be created, managed, and orchestrated into composite applications and business processes. Composites enable you to easily assemble multiple technology components into one SOA composite application. Oracle SOA Suite plugs into heterogeneous IT infrastructures and enables enterprises to incrementally adopt SOA.

You can use Oracle SOA Suite with the following versions of OSR:

For more information about Oracle Service Registry, visit the following URL:

http://www.oracle.com/technology/goto/registry

[Note]Note
  • This section does not describe how to configure OSR against the embedded Oracle WebLogic Server in Oracle JDeveloper.

  • OSR 11g deploys to WebLogic Server 11 (10.3.1 or later)

This section describes how to integrate Oracle Service Registry with Oracle SOA Suite 11g. It contains the following topics:

Integrating with Oracle JDeveloper  Locate

To create a connection between the Oracle Service Registry and JDeveloper:

  1. Go to Oracle JDeveloper.

  2. Select File > New > Connections > UDDI Registry Connection to create a UDDI connection.

  3. Enter a connection name.

  4. Enter an inquiry endpoint URL. For example: http://myhost.us.oracle.com:7001/registry/uddi/inquiry

  5. Ensure that the Business View option is selected.

  6. Click Next.

  7. Click Test Connection.

  8. If successful, click Finish. Otherwise, click the Back button and correct your errors.

Configuring Oracle Service Registry at Runtime  Locate

Oracle SOA Suite uses the SCA standard as a way to assemble service components into a SOA composite application. SCA provides a programming model for the following:

  • Creating service components written with a wide range of technologies, including programming languages such as Java, BPEL, C++, and declarative languages such as XSLT. The use of specific programming languages and technologies (including web services) is not required with SCA.

  • Assembling the service components into a SOA composite application. In the SCA environment, service components are the building blocks of applications.

SCA provides a model for assembling distributed groups of service components into an application, enabling you to describe the details of a service and how services and service components interact. Composites are used to group service components and wires are used to connect service components. SCA helps to remove middleware concerns from the programming code by applying infrastructure declaratively to composites, including security and transactions.

The key benefits of SCA include the following:

  • Loose coupling

    Service components integrate with other service components without needing to know how other service components are implemented.

  • Flexibility

    Service components can easily be replaced by other service components.

  • Services Invocation

    Services can be invoked either synchronously or asynchronously.

  • Productivity

    Service components are easily integrated to form a SOA composite application.

  • Easy Maintainance and Debugging

    Service components can be easily maintained and debugged when an issue is encountered.

The Oracle Service Registry (OSR) provides a common standard for publishing and discovering information about web services. This section describes how to configure OSR against a separately installed Oracle SOA Suite environment:

Publishing and Browsing the Oracle Service Registry  Locate

This section provides an overview of how to publish a business service. For specific instructions, see the documentation at the following URL:

http://www.oracle.com/technology/goto/regrep

[Note]Note

The best practice for publishing services is using Oracle Enterprise Repository and the Exchange Utility tool.

For more information, see Integrating with Oracle Enterprise Repository

To Manually Publish a Business Service
  1. Go to the Registry Control: http://hostname:port/registry/uddi/web

  2. Click Publish > WSDL.

  3. Log in when prompted.

  4. Complete the fields on this page to specify the access point URL and publish the WSDL for the business service. The following screen provides details.

[Note]Note

If you later change your endpoint location, you must also update the WSDL location in the Registry Control. Otherwise, UDDI invocation fails during runtime. To change the WSDL location:

  1. Log in to the Registry Control.

  2. Navigate to the service.

  3. Change both URLs within the port type and binding information using the model key.

How to Configure a SOA project to Invoke a Service from the Registry  Locate

To configure a SOA project to invoke a service from the registry:

  1. Open the SOA project in which to create a reference to the business service.

  2. Drag a Web Service icon into the External Services swimlane. The Create Web Service dialog appears.

  3. To the right of the WSDL URL field, click the icon to select a WSDL.

  4. From the list at the top, select Resource Palette.

  5. Expand the navigational tree.

  6. Expand UDDI Registry > Business Services.

  7. Select the published business service, and click OK. The following screen provides details.

    The UDDI Deployment Options dialog appears.

  8. Select one of the following deployment options:

    • Dynamically resolve the SOAP endpoint location at runtime.

    • Dynamically resolve the concrete WSDL location at runtime.

    The following screen provides details.

  9. Click OK. You are returned to the Create Web Service dialog.

  10. See the following section based on your selection in the UDDI Deployment Options dialog.

Dynamically Resolving the SOAP Endpoint Location   Locate
  1. Complete the remaining fields in the Create Web Service dialog, and click OK. The Create Web Service dialog looks as shown in the following screen.

  2. Verify the wiring of the reference with the appropriate service component.

Dynamically Resolving the WSDL Endpoint Location  Locate
  1. Complete the remaining fields in the Create Web Service dialog, and click OK. The Create Web Service dialog looks as shown in the following screen.

  2. Verify the wiring of the reference with the appropriate service component.

How To Configure the Inquiry URL, UDDI Service Key, and Endpoint Address for Runtime  Locate

You can set the inquiry URL, UDDI service key, and endpoint address during runtime in Oracle Enterprise Manager Fusion Middleware Control Console.

To configure the inquiry URL, service key, and endpoint reference for runtime:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control Console and navigate to Common Properties, as shown in the following screen.

  2. Specify values for the following properties:

    • In the SOA Infrastructure Common Properties page, specify the same UDDI inquiry URL in the Inquiry URL text box, as shown in the following screen, that you specified in the Create UDDI Registry Connection wizard. For example, http://TST.myhost.com:7101/registry/uddi/inquiry.

      For information, see section "Configuring SOA Infrastructure Properties" of Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suitehttp://fmwdocs.us.oracle.com/doclibs/fmw/11gr1ps1_final/integration.1111/e10226/toc.htm.

    • In the Properties page of the reference binding component, you can change the endpoint reference and service key values created during design time. For information, see section "Configuring Service and Reference Binding Component Properties" of Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suitehttp://fmwdocs.us.oracle.com/doclibs/fmw/11gr1ps1_final/integration.1111/e10226/toc.htm.

  3. Restart the SOA Infrastructure.

  4. Exit Oracle Enterprise Manager Fusion Middleware Control Console.

  5. To see endpoint statistics, return to the Registry Control.

  6. Go to the Manage page and check statistics to see the increase in the number of invocations when not cached (the first time).

    Caching of WSDL URLs occurs by default during runtime. If a WSDL URL is resolved using the orauddi protocol, subsequent invocations retrieve the WSDL URLs from cache, and not from OSR. When an endpoint WSDL obtained from cache is no longer reachable, the cache is refreshed and OSR is contacted to retrieve the new endpoint WSDL location. As a best practice, Oracle recommends that you undeploy services that are no longer required in Oracle Enterprise Manager Fusion Middleware Control Console and used by the SOA Infrastructure. Endpoint services that are shut down or retired (but not undeployed) are still reachable. Therefore, the cache is not refreshed.

    If you move the business service WSDL from one host to another, ensure that you change the location in the Registry Control. No change is required in Oracle JDeveloper or Oracle Enterprise Manager Fusion Middleware Control Console.

    You can optionally increase the amount of time that the WSDL URL is available in cache for inquiry by the service key. For more information, see "Configuring Service and Reference Binding Component Properties" of Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

    [Note]Note

    In 11g, caching occurs automatically. If you are using Oracle SOA Suite 10.1.3, caching is supported by setting the CacheRegistryWSDL property to true in bpel.xml. Setting this property to false disables caching.