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

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:7101registryuddiinquiry. Page 287 1.2.3. How To Configure the Inquiry URL, UDDI Service For information, see section Configuring SOA Infrastructure Properties of Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite http:fmwdocs.us.oracle.comdoclibsfmw11gr1ps1_final integration.1111e10226toc.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 Administrators Guide for Oracle SOA Suite http: fmwdocs.us.oracle.comdoclibsfmw11gr1ps1_finalintegration.1111e10226toc.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 Administrators Guide for Oracle SOA Suite. 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.

2. Integrating with Oracle Enterprise Repository

The Oracle Enterprise Repository provides a flexible meta model for cataloguing all assets within the SOA ecosystem and their dependencies. It is primarily used during the plan, design, and build phase of the lifecycle as a single source of truth for service and composite application development. The Oracle Service Registry is a reference point for services that have been deployed into the runtime environment. It is primarily used for programmatic, dynamic discovery and binding by elements of the SOA infrastructure. The Oracle Service Registry typically contains a subset of the metadata from the Oracle Enterprise Repository for runtime discovery. A major use case for Oracle Service Registry is to provide a UDDI interface by which selected Oracle Enterprise Repository content may be accessed or published. The Oracle Service Registry also serves as an integration point for runtime tooling such as Oracle Service Bus OSB, Oracle SOA Suite 11g and JDeveloper. OSB can automatically publish and subscribe to new or modified assets. Registries can also be federated - configurations of systems with single logical repository, and Page 288

2. 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