Assigning, Editing, or Viewing an Explicit Universal Name
To ensure interoperability with other vendor’s implementations of SOAP, Software AG recommends that you always assign explicit universal names to those document types that you want to make available to SOAP clients.
When you assign an explicit universal name, you must enter values in both the Namespace name and Local name fields. If you specify one field but not the other, you will receive an error message when you attempt to save the service or document type. You will not be permitted to save it until you specify both parts of the universal name.
If you move a service or document type, or a folder containing a service or document type, Designer retains the explicit universal name. If you copy a service or document type, or a folder containing a service or document type, Designer does not retain the explicit universal name.
Earlier versions of the webMethods SOAP implementation did not include the http://localhost/ prefix as part of an implicit name. However, the server is backward compatible. It will resolve QNames that clients submit in either the old form (without the http prefix) or the new form (with the http prefix).
To assign, edit, or view a universal name
1. In Package Navigator view, double-click the service or document type whose universal name you want to assign, edit, or view.
2. In the editor, click the service’s or document type’s title bar to give the service or document type the focus.
3. If you want to assign or edit the universal name, specify the following in the Universal Name category of the Properties view:
In this field... | Specify... |
Namespace name | The URI that will be used to qualify the name of this service or document type. You must specify a valid absolute URI. |
Local name | A name that uniquely identifies the service or document type within the collection encompassed by Namespace name. The name can be composed of any combination of letters, digits, or the period (.), dash (-) and underscore (_) characters. Additionally, it must begin with a letter or the underscore character. Note:
Many webMethods users use the unqualified portion of the service name as the local name. |
4. Click File > Save.