9 Viewing, Registering, and Publishing Web Services
This chapter includes the following sections:
9.1 Introduction to Registering Web Services and Sources
A key feature of the web services model is the ability to make web services widely available and discoverable. UDDI is one approach to publishing and discovery of web services that centralizes information about businesses and their services in registries. Another emerging alternative standard is the Web Services Inspection Language (WSIL) specification.
Oracle Enterprise Manager Fusion Middleware Control can register web services that are published in WSIL documents and UDDI v3 registries. Any service that is available in a WSIL document or a UDDI v3 registry can be registered within Enterprise Manager.
You can also register meta information, or a profile, for sources of services to help you manage your registered services within Enterprise Manager. Once you register a source and assign it a logical name, you do not need to specify connectivity information, such as a URL for a WSDL, in the future. A domain can have multiple registered sources, and each registered source can have multiple registered services. Once you register a source, you can easily look up services that you can register to the source.
Service names and corresponding WSDLs must be unique within a registered single source. Once you have registered a service, an attempt to register another service with the same name, or a different name but the same WSDL URL as another service, is not valid.
Once you register a web service, you can later, more conveniently, reference the service from a selection list within Enterprise Manager. For example, when testing a web service as described in Testing Web Services, instead of specifying a WSDL, you can click the Search icon and then select the WSDL from the list of registered services.
This section includes the following topics:
9.1.1 Understanding UDDI Basics
Universal Description Discovery & Integration (UDDI) is an industry initiative that aims to enable businesses to quickly, easily, and dynamically find and carry out transactions with one another. A populated UDDI registry contains cataloged information about businesses; the services that they offer; and communication standards and interfaces they use to conduct transactions.
The owners of web services publish them to the UDDI registry. Once published, the UDDI registry maintains pointers to the web service description and to the service. The UDDI allows clients to search this registry, find the intended service, and retrieve its details. These details include the service invocation point as well as other information to help identify the service and its functionality.
9.1.2 Understanding WSIL Basics
WSIL defines an Extensible Markup Language (XML) format for referencing web service descriptions. These references are contained in a WSIL document, and refer to web service descriptions (for example, WSDL files) and to other aggregations of web services (for example, another WSIL document or a UDDI registry).
WSIL documents are typically distributed by the web service provider. These documents describe how to inspect the provider's web site for available web services. Therefore, the WSIL standard also defines rules for how WSIL documents should be made available to consumers of web services.
The WSIL model decentralizes web service discovery. In contrast to UDDI registries, which centralize information on multiple business entities and services, WSIL makes it possible to provide web service description information from any location. Unlike UDDI, WSIL is not concerned about business entity information, and does not require a specific service description format. It assumes that you know who the service provider is and relies on other standards for web service description, such as WSDL.
9.1.3 Viewing Registered Sources and Web Services
Follow the steps in this section to view and edit a registered source and web service.
9.1.4 Registering a Source
You can register web service sources of the following types: UDDI v3 registry import, WSIL import from URL, or WSIL import from file.
To register a source:
9.1.5 Registering Web Services from a UDDI Source
Follow the steps in this section to register web services from a registered UDDI source.
9.1.6 Registering Web Services from a WSIL Source
Follow the steps in this section to register web services from a registered WSIL source.
9.2 Introduction to Publishing Web Services to UDDI
You can publish web services to UDDI from a registered UDDI source and from the web services summary page for ADF and Java EE applications. Registered UDDI sources are listed in the Registered Sources and Services page, which includes all sources and services registered in a domain. The Web Services summary page lists the web services in an application.
Note:
You need to use a proxy to publish a service to UDDI, since this requires access to URLs outside of your firewall. For more information about the required proxy settings, see "Configuring the Proxy Server for UDDI".
If your services are already in Oracle Enterprise Repository (OER) then you should use the OER Exchange Utility to publish those services to Oracle Service Registry.
The following procedures describe how to publish web services to UDDI.
9.2.1 Publishing a Web Service to UDDI from a Registered Source
Registered UDDI sources are listed in the Registered Sources and Services page, which includes all sources and services registered in a domain.
To publish a web service to UDDI from a registered source:
9.2.2 Publishing a Web Service to UDDI from an Application
You can publish web services to UDDI from the web services summary page for ADF and Java EE applications.
To publish a web service to UDDI from an application:
9.2.3 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 9-1. You can set them as environment variables, or in Oracle WebLogic startup files.
Table 9-1 Java System Properties Used to Specify the Proxy Server for UDDI
Property | Description |
---|---|
|
Flag that specifies that the WebLogic proxy properties should be used. |
|
Name of the host computer on which the proxy server is running. |
|
Port to which the proxy server is listening. |
|
List of hosts that should be reached directly, bypassing the proxy. Separate each host name using a | character. |
For example:
set PROXY_SETTINGS="-DproxySet=true -Dhttp.proxyHost=www-proxy.example.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|${HOST}|*.example.com"