|
With the Advanced Search tab, the user can search the UDDI
registry using any combination of Names,
Keys, tModels,
Discovery URLs, Categories, and
Identifiers. Furthermore, it is also possible to specify
the entity level in the tree to start searching from. All of these options
combine to provide a very powerful search facility.
It is possible to specify search criteria for any of the categories listed
above by right-clicking on the folder node in the Enter Search
Criteria tree and selecting the Add menu option.
It is possible to enter more than 1 search criteria of the same type, e.g. 2
search criteria of type Keys.
It is important to note that the tModel URIs shown in the resulting tree may
not all be categorized as "wsdlSpec" according to the uddi-org:types
categorization system. The user may choose to load any of these URIs as a
WSDL file, but they will be warned if it is not categorized as "wsdlSpec".
The following list explains how to add a search criteria for each of the
types listed in the Enter Search Criteria tree. All search
criteria are configured by right-clicking on the folder node and selecting
the Add menu option.
Names:
Simply enter a name to be used in the search in the Name
field on the Name Search Criterion dialog. For example,
the name could be the name of a businessEntity.
As with all name searches, the name is a partial or full name pattern with
wildcards allowed as specified by the SQL-92 LIKE
specification. The wild-card characters are percent '%', and underscore '_',
where an underscore matches any single character and a percent matches zero
or more characters.
A name search criterion may be used for businessEntity, businessService, and
tModel level searches.
Keys:
On the Key Search Criterion dialog, you can specify a key
to search the registry for in the Key field. The key value
is a UUID (Universally Unique Identifier) value for a registry object.
The Key Search Criterion can be used on all levels of
searches.
If 1 or more keys are specified with no other search criteria, the keys are
interpreted as the keys of the selected type of registry object and used for
a direct lookup, as opposed to a find/search operation. For example, if the
user enters "key1" and "key2" and selects the businessService entity type,
the search will retrieve the businessService object with key "key1", and
another businessService with key "key2".
If a key is entered with other search criteria, then a key criterion will be
interpreted as follows:
-
For a businessService entity lookup, the key will be the businessKey of
the services
-
For a bindingTemplate entity lookup, the key will be the serviceKey
of the binding templates
- Not applicable for any other object type
tModels:
The user can enter a key in the tModel Key field on the
tModel Search Criterion screen. The key entered should
correspond to the UUID of the tModel associated with the type of object we
are searching for.
A tModel search criterion may be used for businessEntity, businessService,
and bindingTemplate level searches.
Discovery URLs:
Enter a URL in the Discovery URL field on the
Discovery URL Search Criterion dialog. The Use
Type field is optional, but can be used to further fine-grain the
search by type.
A Discovery URL search criterion may be used for businessEntity level
searches only.
Categories:
The user must select a previously configured categorization system from the
Type dropdown on the Category Search
Criterion dialog. The dropdown is pre-populated with a list of
common categorization systems. A new categorization system can be added by
clicking the Add button.
On the Add/Edit Category dialog, enter a
Name, Description, and UUID
for the new category type in the fields provided.
Once the categorization system has been selected or added, the user must
enter a value to search for in the Value field. The
Name field is optional.
Identifiers:
A previously configured identification system must be selected from the
Type dropdown on the Identifier Search
Criterion dialog. The content of this dropdown is pre-populated
with well-known identification systems. To add a new identification system,
click the Add button.
On the Add/Edit Identifier dialog, enter a
Name, Description, and UUID
for the new identifier in the fields provided.
|