Page History
...
After resolving the substitution markers, the LANSA Web Plugin returns the updated HTML, including the resolved system and partition information so it can request additional resources from the Application Server. The HTML code will look something like this:
<!DOCTYPE html> <html lang="en" style="height:100%"> <head> <meta charset="utf-8" /> <meta name="mobile-web-app-capable" content="yes"> <meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-touch-fullscreen" content="yes"> <meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> </head> <body style="height:100%; margin-left:0px;margin-right:0px;margin-top:0px;margin-bottom:0px"> <script src="/lansa14/lansa_14_1_0_0/lansa.js"></script> … <script> (function(LANSA){ if(!LANSA)\{document.write("Failed to load lansa.js");return\} LANSA.init(\{part:"dem",sys:"lansa14",lang:\{def:"ENG",code:\{"ENG":"En-US","FRA":"fr_FR","JPN":"ja-JP","LLL":"En-US"\}\}\}); LANSA.showPage("XVLWEBTST"); }(window\["LANSA"\])) ≺/script≻ <noscript>This page requires JavaScript.</noscript>
</body> </html>
Take notice of the following lines where the system and partition qualifying information have been added into the HTML:
...
<script src="/lansa14/lansa_14_1_0_0/lansa.js"></script>
...
...
...
LANSA.init(\{part:"dem",sys:"lansa14",
...
...
Also notice the HTML specifies the languages supported at runtime, as well as which language will be used as the default if no language parameter is supplied on the URL. The ISO Codes associated with each language are identified too.
LANSA.init(\{part:"dem",sys:"lansa14",lang:\{def:"ENG",code:\{"ENG":"En-US","FRA":"fr_FR","JPN":"ja-JP","LLL":"En-US"\}\}\});