Implicit and Explicit Universal Names

Every service or document type that exists on Integration Server has an explicit or an implicit universal name.

An explicit universal name is a universal name that you specifically assign to a service or document type with Designer. When you assign an explicit universal name, you must specify both the namespace name and the local name.

An implicit universal name is automatically derived from the name of the service or the document type. The implicit name acts as the universal name when a service or document type does not have an explicit universal name. The server derives an implicit name as follows:

The namespace name is the literal string http://localhost/ followed by the fully qualified name of the folder in which the service or document type resides on the Integration Server.

The local name is the unqualified name of the service or document type.

The following table shows the implicit names for a variety of service names:

	The service’s implicit universal name is...
Fully qualified service name	Namespace name	Namespace name
gl.journals:jrnlEntry	http://localhost/gl.journals	jrnlEntry
gl.journals.query:viewJournals	http://localhost/gl.journals.query	viewJournals
orders:postPO	http://localhost/orders	postPO

Note: It is possible for an implicit name to match the explicit name of another service. When this condition exists, the explicit name takes precedence. That is, when a universal name is requested, Integration Server searches its registry of explicit names first. If it does not find the requested name there, it looks for a matching implicit name.