Hybrid Integration 10.1 | Integrating On-Premises Applications | Document Conventions | DSPs and Output Templates in Different Languages | Using Localized DSPs and Templates | Publishing Localized DSPs and Templates | Publishing a Localized DSP to the Server
 
Publishing a Localized DSP to the Server
* To publish a localized DSP to the server
1. Save the DSP document in a text file that has a “.dsp” extension. Make sure that the default DSP file has the same name and encoding as the localized DSP file. For example: showorders.dsp.
2. Place the default DSP file in the pub directory of the package in which you want the DSP to reside. For example, to publish a default DSP in the orders package, you would copy it to:
     Integration Server_directory \packages\orders\pub
3. Place the localized DSP file in the pub\localeID directory of the package in which you want the DSP to reside. You may have to create this directory. The localeID corresponds to a language code as defined in RFC 3066 by the W3C. For details on localeID values, see The localeID Value. For example:
*To publish a Japanese DSP in the orders package, you would copy it to:
    \packages\orders\pub\ja\
*To publish an English DSP in the orders package, you would copy it to:
    \packages\orders\pub\en\
*To publish a United Kingdom English DSP in the orders package, you would copy it to:
    \packages\orders\pub\en-GB\
*To publish a United Kingdom English DSP to the status subdirectory within the orders package, you would copy it to:
    \packages\orders\pub\en-GB\status\

Copyright © 2015- 2017 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.