Using Fusion Middleware Control, select WebLogic Domain then Web Services Do one of the following:

Advanced Administration 14-11 ■ Service Definition Location is prepopulated with the URL location of the service definition This field is read-only. ■ UDDI Source is a logical name for the UDDI registry source. Choose the UDDI source from the list. This field is required. ■ Business Name is the name of the data structure in the UDDI registry. It is assumed that the business has already been registered in the UDDI. Choose the business name from the list. This field is required. Figure 14–9 Publish Service to UDDI Dialog Box

5. Click OK to connect to the external UDDI registry and register the Web service.

Upon successfully registering the service, a confirmation message displays. Any errors during the operation will result in an error message. Configuring the Proxy Server for UDDI To access URLs outside of your firewall, you must use a proxy to publish a service to UDDI. Before starting Oracle WebLogic, you must set the Java system properties defined in Table 14–1 . You can set them as environment variables, or in Oracle WebLogic startup files. For example: set PROXY_SETTINGS=-DproxySet=true -Dhttp.proxyHost=www-proxy.us.oracle.com Note: The list contains the UDDI sources registered in the domain that have been enabled for publishing. For more information about registered sources, see Registering Web Services and Sources on page 14-1. Table 14–1 Java System Properties Used to Specify the Proxy Server for UDDI Property Description proxySet=true Flag that specifies that the WebLogic proxy properties should be used. http.proxyHost=proxyHost Name of the host computer on which the proxy server is running. http.proxyPort=proxyPort Port to which the proxy server is listening. http.nonProxyHosts=hostna me | hostname | ... List of hosts that should be reached directly, bypassing the proxy. Separate each host name using a | character. 14-12 Oracle Fusion Middleware Security and Administrators Guide for Web Services -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|{HOST}|.us.oracle.com Auditing Web Services Auditing describes the process of collecting and storing information about security events and the outcome of those events. An audit provides an electronic trail of selected system activity. An audit policy defines the type and scope of events to be captured at run time. Although a very large array of system and user events can occur during an operation, the events that are actually audited depend on the audit policies in effect at run time. You can define component- or application-specific policies, or audit individual users. You configure auditing for system components, including Web services, and applications at the domain level using the Audit Policy page. You can audit SOA, ADF, and WebCenter services. Figure 14–10 Audit Policy Page The audit policies table, at the center of the page, displays the audits that are currently in effect. The table includes the following information: ■ Name—Name of the system components and applications that you can audit. ■ Enable Audit—Identifies the components and applications for which auditing is currently in effect. ■ Filter—Specifies any filters that are currently in effect. The following table summarizes the events that you can audit for Web services and the relevant component.