Assigning an Output Template to a Service
Use of an output template to format service output is optional. You assign an output template to a service using the Properties view in Designer.
When using output templates, keep the following points in mind:
A service can have at most one output template assigned to it at a time. You can dynamically change the output template assignment at run time, however. For more information, see
Applying Output Templates
Arbitrarily.
You can assign the same output template to more than one service.
If you assign an existing output template to a service, the output template must reside in the
Integration Server_directory \packages\
packageName\templates directory, where
packageName is the package in which the service is located.
Note: If you assign an output template to a service and later copy that service to a different package, you must copy the output template file to the Integration Server_directory \packages\packageName\templates directory of the new package. (If you copy an entire package, any output templates will be included automatically.) If the template file has a file extension other than .html, rename the file extension as “.html” so that Designer will recognize its contents.
The server treats the case of the file name differently depending on which operating system you are using. For example, on a case-insensitive system such as Windows, the server would see the names “template” and “TEMPLATE” as the same name. However, on a case-sensitive system such as UNIX, the server would see these as two different names. If you are trying to assign an existing output template and you enter a file name in the wrong case on a UNIX system, the wrong file name could be assigned as the output template for your service.
For steps for assigning an output template to a service, see webMethods Service Development Help.