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 | Requesting a Localized DSP
 
Requesting a Localized DSP
To process a localized DSP, you request it from a browser using the following URL format:
    http://hostName:portNum/packageName/fileName.dsp
For details on the values in the URL, see Requesting DSPs.
Examples
The following URL retrieves showorders.dsp from a package named ORDER_TRAK on a server named rubicon:
    http://rubicon:5555/ORDER_TRAK/showorders.dsp
If the client machine has a Japanese locale:
*Integration Server looks for:
Integration Server_directory \packages\ORDER_TRAK\ja-JP\showorders.dsp
*If not found, then it looks for just the language code of the localeID as follows:
Integration Server_directory \packages\ORDER_TRAK\ja\showorders.dsp
*If not found, then it looks for the next language listed in the browser language settings. If another language is not listed, then it looks for a default DSP at:
Integration Server_directory \packages\ORDER_TRAK\showorders.dsp
*If a default DSP does not exist, then an error appears in the browser.
The following URL retrieves showorders.dsp from the STATUS subdirectory in a package named ORDER_TRAK on a server named rubicon:
    http://rubicon:5555/ORDER_TRAK/STATUS/showorders.dsp
If the client machine has a United States English locale:
*Integration Server looks for:
Integration Server_directory \packages\ORDER_TRAK\STATUS\ en-US\showorders.dsp
*If not found, then it looks for just the language code of the localeID as follows:
Integration Server_directory \packages\ORDER_TRAK\STATUS\en\ showorders.dsp
*If not found, then it looks for the next language listed in the browser language settings. If another language is not listed, then it looks for a default DSP at:
Integration Server_directory \packages\ORDER_TRAK\STATUS\showorders.dsp
*If a default DSP does not exist, then an error appears in the browser.