Querying the registry


To find a WSDL or end point URL for a web service in the registry when configuring a Set Fields filter action to consume a web service, you can search the registry using the AR System Web Services Registry Query form in a browser.

To cause AR System server to query the registry for an end point URL at run time, you can use a special syntax in the End Point field of the Set Fields filter action.

Using the Registry Query form at design time

To search the registry for a registered web service and obtain the WSDL or End Point URL for use in a Set Fields filter action, complete the following procedure.

To query the registry

  1. In a browser, open the AR System Web Services Registry Query form in Search mode.
    WebServicesRegistryQueryForm.gif
  2. Enter the known information about the web service in the form, and click Search.
    • You can use Java regular expression wildcards in the fields Business Name, Application Name, Web Service, and Version. For example, enter BM* to match "BMC Software, Inc." or BM. to match "BMC."
    • You can search on all fields in the form, except the WSDL URL and End Point URL fields. These fields are populated by the search results.
    • Search values are hierarchical. You can search on either the Business Name or the Application Name alone, but to search the remaining fields, you must also enter values in each of the preceding fields. For example, to search on the Web Service field, you must also enter values in the Business Name and Application Name fields. The field hierarchy is Business Name > Application Name >Web Service >Interface Version > Category List.
    • To use more than one category in the search, use a semicolon-separated list in the Category List field, for example, name1=value1; name2=value2. In the search results, the Category List is also populated using this syntax.
  3. When the search results are returned, open the correct entry, and then cut and paste the returned WSDL into the Set Fields action in the Web Services filter.
    The AR System server parses the WSDL, and the web service end point appears in End Point field.

Obtaining an End Point URL at run time

To cause the AR System server to search the registry for the end point URL at run time, enter a search phrase that includes a keyword, a registry key, and an optional list of categories in the End Point field of the Set Fields filter action. The registry key must provide enough information to obtain an unambiguous result. The key can include a list of categories associated with the web service. At run time, the AR System server builds the key using the values provided and retrieves the correct end point URL from the Registry.

To build the registry key, use the keyword SRC:Registry;KEY::, followed by name-value pairs separated by semicolons, in the following format:

SRC:Registry;KEY::BN=<businessName>;AN=<appName>;W=<webService>;WV=<webServiceVersion>

For example:

SRC::Registry;KEY::BN=BMC;AN=ARSystem;W=HelpDesk;WV=5.0

The element SRC:Registry;KEY, followed by two colons ( :: ), acts as a keyword to direct the AR System server to search the registry for the correct entry.

The registry key consists of these elements:

  • BN—The Business Name (required)
  • AN—The Application Name (required)
  • W—The Web Service name (required)
  • WV—The Web Service Version (optional—If there is no web service version, this field is not required.)

To further narrow the search, include an optional list of categories following the registry key. The registry key must precede the category list.

The category list is also constructed of name value pairs separated by semicolons, in this format:

CN1=CV1; CN2=CV2

In this example, CN is replaced by the Category Name and CV by the Category Value, for example, Location=Paris; Owner=Marie.

The category list is separated from the registry key by another set of two colons (:: ). For example:

SRC:Registry;KEY::BN=BMC;AN=ARSystem;W=HelpDesk;WV=5.0::Location=Paris

You can enter the category list directly if you know the category names and values. Alternatively, you can enter field names in which the values will be supplied. For example:

SRC:Registry;KEY::BN=BMC;AN=ARSystem;W=HelpDesk;WV=5.0::$8$ or $8$=$536870913$

If you use field references, test to verify that they are correct. The AR System server returns an error if the value is incorrect, and the filter action will fail.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*