This chapter describes how to configure and use UDDI registries with Oracle Service Bus (OSB) for UDDI import and publish using the OSB Administration Console.
Universal Description, Discovery and Integration (UDDI) registries are used in an enterprise to share Web Services. UDDI provides a framework in which to classify your business, its services, and the technical details about the services you want to expose.
Publishing a service to a registry requires knowledge of the service type and the data structure representing that service in the registry. A registry entry has certain properties associated with it and these property types are defined when the registry is created. You can publish your service to a registry and make it available for other organizations to discover and use. Proxy services developed in Oracle Service Bus can be published to a UDDI registry. Oracle Service Bus can interact with any UDDI version 3.0-compliant registry.
See also "UDDI" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
Use this page to designate a default UDDI registry (see Section 30.3, "Setting Up a Default UDDI Configuration") and to view UDDI registries. Additionally, you can search for registries that you have previously configured.
In the UDDI Registries panel, enter the name of the registry you want to find in the Name field, or enter wildcard characters; use * for multiple characters and ? for single characters. The search returns all the records that satisfy the name criteria.
Click Search.
Click View All to remove the search filters and view all the registries that are configured to work with Oracle Service Bus.
Table 30-1 displays UDDI registry configuration settings.
Table 30-1 UDDI Registry Configuration Settings
| Property | Description |
|---|---|
|
Registry Name |
The name of the registry. The name assigned to a registry when it is first created. You cannot edit the name of a registry after the entry is saved. |
|
Inquiry URL |
The URL of the Inquiry API endpoint used for locating and importing services. |
|
Publish URL |
The URL of the Publish API endpoint used for publishing services. |
|
Security URL |
The URL of the Security API endpoint used for getting an authentication token so that you can publish to the registry. |
|
Subscription URL |
The URL of the Subscription API endpoint used for subscribing to registry changes, creating a registry subscription, and listening for changes to imported services. |
|
User Name |
The user name which is required for user authentication. |
|
Password (Confirm Password) |
The password which is required for user authentication. |
|
Load tModels into registry |
Loads the tModels into the selected registry. This option only has to be selected once per registry. |
|
Enable Auto-Import |
Auto-synchronizes services with the UDDI registry. |
This section includes the following tasks:
Use this page to add and configure UDDI registries. After registries are configured, you can then publish Oracle Service Bus proxy services to them or import business services from them to be used in an Oracle Service Bus proxy service.
You must be in an active session to add a registry.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select System Administration > UDDI Registries.
In the UDDI Registries panel, click Add Registry.
To configure the registry, complete the following steps. Asterisks denote required fields. See Table 30-1 for descriptions of the properties that must be set when adding a registry.
In the Name field, enter a name for the registry.
Follow the Section 2.3, "Resource Naming Restrictions" for naming guidance.
In the Inquiry URL field, enter an inquiry URL in the format: http://host:port/APPLICATION_SERVER_CONTEXT/uddi/inquiry
In the Publish URL field, enter a publish URL in the format http://host:port/APPLICATION_SERVER_CONTEXT/uddi/publishing
In the Security URL field, enter a security URL in the format http://host:port/APPLICATION_SERVER_CONTEXT/uddi/security
In the Subscription URL field, enter a subscription URL in the format
http://host:port/APPLICATION_SERVER_CONTEXT/uddi/subscription
By default, the value for APPLICATION_SERVER_CONTEXT in the installer is registry.
In the Username field, enter the user name to log in to the registry console.
In the Password /(Confirm Password) field enter the password to log in to the registry console.
Select the Load tModel into registry check box to publish the Oracle Service Bus tModels to this registry.
This field is only required when publishing proxy services to this registry.
Select the Enable Auto Import check box to auto-synchronize imported services with the UDDI registry. Any service that is imported with this option selected will be kept in synchrony with the UDDI registry.
Note:
Auto-synchronization is a background process; you cannot reverse it using the session Undo function. Undoing an auto-synchronization change is not permanent as the service will be re-synchronized in the next synchronization cycle. If you want an imported service to stay out of synchrony with the UDDI registry, you have to detach the service to avoid further updates from the registry. See Section 30.6, "Detaching Services."Click Validate to validate the URLs you have provided.
Click Save to configure the registry with the settings provided and save it in the current session.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select System Administration > UDDI Registries.
In the UDDI Registries panel, from the list of available registries, click the name of the registry you want to edit.
You can also search for a specific registry using the Search option. See Section 30.1, "Viewing Configured UDDI Registries."
The UDDI Registry Configuration page displays the configuration properties that define the registry and the following registry-specific information, shown in Table 30-2.
Table 30-2 UDDI Registry Information
| Property | Description |
|---|---|
|
Last Modified By |
The user who made the last configuration change to this UDDI registry resource. |
|
Last Modified On |
The date and time that the last configuration change was made. Click the date and time link to view the change history of this resource. See Section 4.23, "View Change History Page." |
|
References |
The number of objects that this UDDI registry references. If such references exist, click the numeric link to view a list of the references. See Section 4.22, "Viewing References to Resources." |
|
Referenced By |
The number of objects that reference this UDDI registry. If such references exist, click the numeric link to view a list of the objects. See Section 4.22, "Viewing References to Resources." |
|
Description |
A description of the registry. |
At the bottom of the page, click Edit.
On the UDDI Configuration-Edit Registry page, edit the registry configuration parameters.
These properties are described in Table 30-1. You cannot edit the name of the registry.
Click Save to commit the updates in the current session.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.
You can designate one of the configured registries as the default UDDI registry for the domain. See Section 30.2, "Configuring UDDI Registries."
To use the auto-publish functionality, you must first set a default registry. See Section 30.8, "Using Auto-Publish."
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select System Administration > UDDI Registries.
In the UDDI Default Configuration panel, click Select Default.
From the Default Registry Name list, select the name of the registry you want to set as the default registry.
To set a default business entity, choose an entity from the Business Entity list.
Click Make Default.
To change the default registry, click Clear Selection and repeat the above steps.
You can import the following business service types from a UDDI registry into Oracle Service Bus:
WSDL services over HTTP transport.
Oracle Service Bus proxy services that are published to a UDDI registry. This feature is primarily used in multi-domain Oracle Service Bus deployments where proxy services from one domain need to discover and route to proxy services in another domain.
If you only have one registry configured, Oracle Service Bus automatically connects to that registry and retrieves all the business entities and populates the search form. If you have more than one registry configured, the import wizard prompts you to first select the registry from which you want to import services.
On import, the inquiry URL is used to locate a specific service as a registry has several different types of services.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select System Administration > Import From UDDI.
From the Import Registry Name list, select the name of the registry from which you want to import the service, then click Next.
When a single registry is configured in Oracle Service Bus, the initial registry selection page is not displayed as this is the default registry. The registry selection page is only displayed when two or more registries are defined.
Use the Import From UDDI page to search for specific business services and import them. You can search for a service by business entity, by pattern, or by using a combination of both.
Select the business entity name (for example, document Services) from the Entity Name list to search by business entity.
In the Service Name field, enter the pattern (for example, a%) for which you want to search. A list of business services matching the entered search criteria is displayed.
Select the service(s) that you want to import, then click Next.
If you are unable to find a desired service, it may be because you do not belong to the security group with permissions to view its records.
Select the binding templates from which you want to create business services, then click Next.
If a selected service has multiple binding templates, then each of these binding templates results in a business service. In this case you will be prompted to further narrow your selection among the binding templates you want to import.
On the Import UDDI: Select Import Location page select a project from the Project list, select a folder where you want to import your services and associated resources, then click Next.
The Import UDDI: Review and Import Services page displays a list of all of the resources (business services, MFLs, schemas, WSDLs, and so on) that will be created in the system. A warning message is displayed for any resource that cannot be imported.
By default, all the items in the list are marked for import.
Clear the check box next to a specific resource if you already have the resource in your system and want to manually resolve the dependencies.
You can resolve dependencies from the View Conflicts page in the Change Center after the import process is complete. For more information on viewing and resolving conflicts, seeSection 3.9, "Viewing and Resolving Conflicts."
Click Import to start the import process.
A pop-up window is displayed indicating the progress of the import. When the import is complete, the Import Summary page displays the result of the import. A success message is displayed at the top of the page if the import was successful. If one or more resources could not be imported, an error message is displayed.
Go to the Status column for the resource to view the cause of the error.
To view and resolve additional conflicts, click View Conflicts.
To import more services, click Import Another.
To make changes to your selections, click Back.
You can use the Auto-Import Status page to synchronize changes to a service with those present in the registry. Upon any changes to a service in the registry, Oracle Service Bus provides notification of the change on the Auto-Import Status page which lists all out-of-sync services. You can then synchronize the service in the Oracle Service Bus Administration Console with the corresponding service in the UDDI registry.
When configuring a registry, you can select the Enable Auto-Import option which auto-synchronizes imported services with the UDDI registry. Any service that is imported with this option selected will be kept in synchrony with the UDDI registry automatically. See Section 30.2, "Configuring UDDI Registries."
If there is any failure during auto-synchronization, it will be reported on the Auto-Import Status page where you can update it manually.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select System Administration > Auto-Import Status.
On the Auto-Import Status page, select the type of service you want to display from the View list.
Select the check boxes next to the proxy services you want to synchronize with the corresponding services in the registry.
Click Synchronize.
On the next page, click Finish.
When you do not want the service in the Oracle Service Bus Administration Console synchronized with the corresponding service in the registry, you can avoid synchronization by detaching it from the registry in one of the following ways:
"Detaching a Service by Editing its Configuration"
"Detaching a Service From the Auto-Import Status Page"
Detaching a Service by Editing its Configuration
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select the Project Explorer.
Expand the project folder and select the business service you want to detach from the corresponding service in the registry.
At the bottom of the View a Business Service page, click Edit.
Enable the Detach from Registry option. The business service will be detached from the corresponding service in the UDDI registry.
Detaching a Service From the Auto-Import Status Page
You can use this Detach option only when you get notification about the change on the Auto-Import Status page.
On the System Administration > Auto-Import Status page, select the check boxes next to the business services you want to detach from the corresponding services in the UDDI registry.
Services are shown on this page only when there is a change in the original service present in the registry. Not every service is available on this page.
Click Detach.
You can publish your service to a registry and make it available for other organizations to discover and use. All proxy services developed in Oracle Service Bus can be published to a UDDI registry. You can select the business entity under which you want to publish your service and you can publish a number of services at a time.
Before you can publish to a registry, you must have an account with that registry. Oracle Service Bus supports interoperability with version 3.0-compliant UDDI registries. The configuration described in this section assumes you are using Oracle Service Registry.
For information about setting up a user account in Oracle Service Registry, see the Oracle Service Registry product documentation, accessible from http://www.oracle.com/technetwork/middleware/registry/overview/index.html.
Unpublishing a service from a registry is done from the Oracle Service Registry installation.
Select System Administration > Publish to UDDI.
You can only publish when you are not in a session. Exit your session to access the registries list. All the registries to which you have access are displayed in the list of selected registries.
From Publish Registry Name, select the name of the registry to which you want to publish, then click Next.
When a single registry is configured in Oracle Service Bus, the initial registry selection page is not displayed as this is the default registry. The registry selection page is only displayed when two or more registries are defined.
The Publish to UDDI: Select individual Services and Publish page is displayed, showing a list of Oracle Service Bus proxy services and their locations in the project folder. Starting with the topmost project level folder, the details for name, type, and description are shown for all services.
Select the service(s) that you want to publish.
Expand the Project folder to see the proxy services defined. By default the folder and its contents are marked for publishing.
You can select individual items to publish.
From the Publish Services to Business Entity list, select the business entity to which you want to add the service in the registry. This is the business entity under which the service will be classified in the registry.
Click Publish to publish the services.
A confirmation message is displayed indicating that the service was published successfully.
Click Publish Another to return to the Publish to UDDI: select registry page.
You can use auto-publish to automatically publish proxy services to a registry. To do so, you must enable the Publish to Registry option on the Create/Edit a Proxy Service-General Configuration page. See Section 20.2.1, "General Configuration Page." The Publish to Registry option only appears when a default registry exists. See Section 30.3, "Setting Up a Default UDDI Configuration."
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
Select the Project Explorer.
Expand the project folder and select the proxy service you want to edit.
At the bottom of the View a Proxy Service page, click Edit.
Select Publish to Registry, and click Save to commit the updates in the current session.
To end the session and deploy the configuration to the runtime, click Activate under Change Center.
The service is configured to be published to the default registry.
Notes:
When you have successfully published a service to a registry, the option to select the service for auto-publishing to a registry is no longer available.If the service is not successfully published it can be re-published. To re-publish a service, select the service on the Auto-Publish Status page and click Publish.
If the Publish to Registry option is enabled, the proxy services are published as soon as they are created or edited, and the session is activated. You can use the Publish to Registry option with all proxy services, except those using Local Transport.