Software AG Products 10.7 | Administering Integration Server | Managing Services | Fully Qualified Service Names
 
Fully Qualified Service Names
 
Package Names and Service Names
HTTP URL Aliases for Services
The fully qualified service name is comprised of two parts: a folder identifier and the service name. The folder identifier consists of one or more folder names. The service name is a single name of the service.
Use a folder to group related services together. When a folder contains other folders, the nested folders are called subfolders. For example, if you have several services that involve financial information, you might create a folder named "Finance" to hold the services. Within the financial services, there might be services that are for personal finances. You might create a subfolder named "Personal" to hold those services.
Use any name for the service name. For example, if one of the financial services obtains stock quotes, you might name the service, "StockQuote."
To specify a fully qualified service name, identify the folder portion, then a colon (:), then the service name:
folder:service
For example, if the "StockQuote" service is in the "Finance" folder, the fully qualified service name is:
Finance:StockQuote
If the folder portion identifies more than one folder, separate each folder name with a period.
folder.subfolder1.subfolder2:service
For example, if the "HomeLoan" service is in the "Personal" folder, which is contained in the "Finance" folder, the fully qualified service name is:
Finance.Personal:HomeLoan
The fully qualified name of each service must be unique within the server. In addition, the fully qualified name of a service cannot be the same as the fully qualified name of any specification or document type that resides on the server.
Note:
The watt.server.illegalNSChars setting in the server.cnf file (which is located in the IntegrationServer_directory\instances\instance_name\config directory) defines the characters that you cannot use when naming folders and services. To view or change this setting, use the Settings > Extended page from the Integration Server Administrator as described in page Working with Extended Configuration Settings.