Integrating with Oracle JDeveloper

1.2. Configuring Oracle Service Registry at Runtime

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:

1.2.1. Publishing and Browsing the Oracle Service Registry

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.comtechnologygotoregrep Note The best practice for publishing services is using Oracle Enterprise Repository and the Exchange Utility tool. For more information, see Section 2, Integrating with Oracle Enterprise Repository Page 283

1.2.1. Publishing and Browsing the Oracle Service Registry

To Manually Publish a Business Service 1. Go to the Registry Control: http:hostname:portregistryuddiweb 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 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.

1.2.2. How to Configure a SOA project to Invoke a Service from the Registry

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. Page 284

1.2.2. How to Configure a SOA project to Invoke a Service from the Registry