Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | DSPs and building output templates | Using Output Templates to Format Service Output | Creating DSPs and Templates in Other Languages | Creating a Default DSP or Template
 
Creating a Default DSP or Template
 
Points to Remember
Before publishing your localized DSPs or templates to Integration Server, it is recommended that you create a default DSP or template. This prevents errors from being displayed when a client machine’s locale does not match any localized DSPs or templates within the package on the server. If this occurs, an error appears to the user unless a default DSP or template is present. If it is present, that file appears instead of the error.
You create a default DSP or template like any other DSP or template; however, it must have the same filename and encoding as the localized DSP or template. Create the default file with UTF-8 encoding to reduce difficulty in localizing later into other languages. In addition, keep the contents of this file generic, because it is displayed for all languages and locales except for the ones for which you provided localized files.
You can create the default file in any language. Select the language for the file carefully, because the default file will be displayed to all users for who you did not supply a specific file for their locale (or to those users who did not set their browser to request a language).
The default file is located at the root directory of published DSPs and templates in a package. For details on creating DSPs or templates, see Using Dynamic Server Pages (DSPs) or Using Output Templates to Format Service Output. For details on publishing the default DSP or template to the server, see the next section.