Enabling Dynamic Lookup of BPEL Partner Link Endpoints

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_portBPELConsole 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_portregistry_contextuddiinquiry The uddiLocation property must refer to the inquiry WSDL URL of the Oracle Service Registry. For example: http:hostname.us.oracle.com:42461registryrc7uddiinquiry?wsdl 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.comdocscdE12524_01relnotes.1013e12523bpelrn.- htmBABFFBAH . 5. Configure the client BPEL for HTTP Basic authentication by entering a value for the following properties: • registryUsername=admin • registryPassword=value Note Currenlty, BPEL supports UDDI look up using HTTP Basic authentication only see Section 8.1, HTTP Basic . HTTPSSSL is not supported for this operation. For more information, see Securing the Client with Basic Authentication [http:download.oracle.comdocscd B31017_01integrate.1013b28982service_config.htmBABIIBEI]. 6. Click Apply. Page 291 4.4. Enabling Dynamic Lookup of BPEL Partner Link 7. Get the service key that uniquely identifies the service from Oracle Service Registry. a. Launch the Registry Control console and login as admin. b. Select the Search tab to search the Registry for the partner link service. c. Enter the partner link service name in the Service Name field and click Find service. d. In the Find service search results, click the Find link under the Bindings column. e. Copy the displayed serviceKey prefaced by uddi: to the clipboard. 8. Launch JDeveloper and open your applications .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.

4.5. Enabling Dynamic Lookup of ESB SOAP Endpoints

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:7777registryuddiinquiry 2. If the Oracle Service Registry is secured using HTTP Basic authentication see Section 8.1, 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 Currenlty, ESB supports UDDI look up using HTTP Basic authentication only see Section 8.1, HTTP Basic . HTTPSSSL 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 Page 292

4.5. Enabling Dynamic Lookup of ESB SOAP Endpoints

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.

4.6. Integrating with Oracle Web Services Manager WSM

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 ManagementRegister 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. Page 293

4.6. Integrating with Oracle Web Services Manager WSM