Integrating with Oracle Enterprise Repository

multiple registries one for each major environment or stage in the lifecycle are common. The Oracle Enterprise Repository and the Oracle Service Registry are synchronized using the Oracle Registry Repository Exchange Utility. The enterprise metadata repository capabilities of Oracle Enterprise Repository together with the comprehensive support for UDDI v3 in Oracle Service Registry provide customers with the capability for managing and governing the full SOA lifecycle. Together, Oracle Enterprise Repository and Oracle Service Registry provide organizations with a system of record for managing their enterprise assets in order to provide visibility, reusability, and traceability throughout the enterprise. For more information about integrating Oracle Enterprise Repository with OER Exchange Utility and Oracle Service Registry, see their OTN pages http:otn.oracle.comgotooer and http:otn.oracle.comgotoregistry respectively.

3. Integrating wih Oracle Service Bus

Oracle Service Bus is the enterprise service bus for use with Oracle WebLogic Server. For OC4J, see Section 4.3, Integrating with Enterprise Service Bus ESB Designer . Oracle Service Bus is part of the Oracle family of service-oriented architecture SOA products. Oracle Service Bus manages the routing and transformation of messages in an enterprise system. Combining these functions with its monitoring and administration capability, Oracle Service Bus provides a unified software product for implementing and deploying your Service-Oriented Architecture. You can use Oracle Service Bus to import services from Oracle Service Registry and then publish Oracle Service Bus proxy services back to Oracle Service Registry. Oracle Service Bus imports business services from Oracle Service Registry. Proxy services are configured to communicate with the business services in the proxy service message flow. The proxy services can then be published back to Oracle Service Registry and made available for use by other domains. For more information on integrating Oracle Service Registry with the Oracle Service Bus, see: • UDDI in the Oracle Service Bus User Guide [http:download.oracle.comdocscdE13159_01osbdocs10gr3userguide uddi.html] • UDDI in Using the Oracle Service Bus Console [http:download.oracle.comdocscdE13159_01osbdocs10gr3 consolehelpuddi.htmlwp1130934] • Working with UDDI Registries in Using the Oracle Service Bus Plug-ins for Workshop for WebLogic [http: download.oracle.comdocscdE13159_01osbdocs10gr3eclipsehelptasks.htmlwp1129462] • UDDI Registries in the Oracle Service Bus Deployment Guide [http:download.oracle.comdocscdE13159_01osb docs10gr3deployintro.htmlwp1418846] • UDDI in Best Practices for Deploying Oracle Service Bus Resources [http:download.oracle.comdocscdE13159_01 osbdocs10gr3pdfdeploybestprac.pdf]

4. Oracle SOA Suite 10.1.3

4.1. Integrating with Oracle JDeveloper

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 Page 289

4.1. Integrating with Oracle JDeveloper

For more information, see: • Section 4.1.1, Connecting to Oracle Service Registry from JDeveloper • Section 4.1.2, Using the JDeveloper Integration • Section 4.2, Integrating with BPEL Designer • Section 4.3, Integrating with Enterprise Service Bus ESB Designer

4.2. Integrating with BPEL Designer

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.

4.3. Integrating with Enterprise Service Bus ESB Designer

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.

4.4. Enabling Dynamic Lookup of BPEL Partner Link Endpoints

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

4.4. Enabling Dynamic Lookup of BPEL Partner Link Endpoints