Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | DSPs and building output templates | Using Output Templates to Format Service Output | Using Localized DSPs and Templates | Publishing Localized DSPs and Templates | Publishing a Localized Template to the Server
 
Publishing a Localized Template to the Server
*To publish a localized template to the server
1. Save the template document to a file. Make sure that the default template file has the same name as the localized template file. For example: showorders.html.
2. Place the default template file in the templates directory of the package in which you want the template to reside. For example, to publish a default template in the orders package, you would copy it to:
     Integration Server_directory \packages\orders\templates\
3. Place the localized template file in the templates\localeID directory of the package in which you want the template to reside. You may have to create this directory. The localeID corresponds to a language and country code as defined in RFC 3066 by the W3C. For details on localeID values, see The localeID Value. For example:
*To publish a Japanese template in the orders package, you would copy it to:
     Integration Server_directory \packages\orders\templates\ja\
*To publish an English template in the orders package, you would copy it to:
     Integration Server_directory \packages\orders\templates\en\
*To publish a United Kingdom English template in the orders package, you would copy it to:
     Integration Server_directory \packages\orders\templates\en-GB\
*To publish a United Kingdom English template in the status subdirectory within the orders package, you would copy it to:
     Integration Server_directory \packages\orders\templates\en-GB\status\
Note:
If you have references to other files within your DSP or template (for example, CSS and GIF files), the same localization rules apply. Make sure to publish those files in the appropriate directory for locale.