Page 1 of 1

Migrating from V11 Web Event to V14 VL Web

Posted: Fri Apr 12, 2019 6:07 am
by cheese
I have a few questions about migrating our software from LANSA 11 web-event to LANSA 14.

We have a multi-client system that needs some flexibility on the way we deploy and customize the look and feel our software to each of our clients.

With whom could I discuss this approach for LANSA 14?
My main questions are on how to:
1. Create one or more Page template layout to use: header, footer, menu,
so that the site has a uniform structure, and all new web page will use the same structure and components without the need to redefine them on each new page we create
2. Include, customizable static html file, that can be edited by 3rd party without LANSA
This would be used for customizations, like logos, promotions, colors, stylesheets, etc
3. Custom html components to be able to customize pages to integrate with other sites:
is there a way to use in LANSA 14 web pages the web components we have already defined in LANSA 11?
I have went through the widgets exercise in the elearning, but I am not sure this would be the best way to add customized web parts, it seems it will require a recompile of programs and re-deploy to all our clients if for example a 3rd party integration changes
4. Custom JavaScript, and eternal javascript, to integrate with other sites and services
We will need to integrate custom Javascript, ours or of 3rd parties with the LANSA programs, exchanging data
Again widget might be useful, but I am wondering about changes and deployment
5. XML services, implement to offer and consume
I there a way on LANSA to be able to define XML interface to access and consume 3rd party web services?
and to create XML (not only SOAP) interfaces that other sites can access?
(managing also the CORS settings)
6. JSON services, implement to offer and consume
Same as before,
I there a way on LANSA to be able to define JSON interface to access and consume 3rd party web services?
and to create JSON (not only SOAP) interfaces that other sites can access?
(managing also the CORS settings)
I understand that servermodules might expose some JSON interface, but I will need more details on how to control and define the signatures of parameters and service names, and how to access 3rd party JSON web service