1.9.2 Existing LANSA for Web Installation
Existing LANSA for the Web System earlier than V10.0
If you have LANSA Web Applications with an interface generated by the Web Functions Wizard before Version 10.0, changes made with the Web Functions Wizard will have some impact on your existing Web functions.
The Web Functions Wizard V10.0 includes new layout schemas and has modified the menu build process significantly.
If you have a pre V10.0 Web Application built using the Wizard and want to make minor changes to the presentation interface, continue to use the Web Functions Wizard V9.0 or V9.1.
If you have a pre V10.0 Web Application built using the Wizard and want to overhaul the interface, consider using the Web Functions Wizard V10.0 for a new "look-and-feel" for your Web Application. In this case, existing menus will be automatically converted to the Wizard V10.0 format but may need to be reviewed to select new button styles and so on. Menus must then be rebuilt. If you rebuild your menus using the Web Functions Wizard, you must also rebuild your Layout, and vice versa. For more details, refer to 1.9.3 Converting a Web Application from Wizard V9.1 to V10.0.
Once you run the Wizard V10.0 over your application, you will no longer be able to view all the menu definitions in Wizard V9.0 or V9.1, if you choose to revert to that version of the software.
Most of the graphic variables used in the Wizard V9.0 and V9.1 are also used in the Wizard V10.0.
Existing LANSA for the Web System earlier than V8.0 -EPC538
If you have LANSA Web applications created before Release 8.0 and EPC538 were installed, changes made with the Web Functions Wizard will have some impact on your existing functions.
Graphic variable changes made using the Web Functions Wizard will immediately impact your existing applications without any recompilation. The Wizard simply provides an alternate interface for changing the graphic variables you have used in your functions. Any changes made to specific browse list variables, process specific variables or system wide variables will immediately impact your Web functions.
Menu component and presentation layout changes made using the Web Functions Wizard will only impact functions which are compiled or recompiled after the LANSA for the Web system was upgraded for the Web Functions Wizard. The HTML pages for your functions must include a new set of RDML tags such as <RDML LAYOUT> in order to use the Wizard changes. These tags will not exist in your older functions until they have been recompiled.
When you recompile an older function, it may be updated to use the new layouts and components if you have specified process specific or system wide default layout changes.
If you are recompiling existing functions in a partition using the Wizard and you do not wish to have the Wizard change the presentation layout (colors, menu components, etc.) of your existing function, then you have several options:
1. Do not create any system wide default layouts. The RDML LAYOUT tags are still used in your HTML pages when recompiled, but no components will have been defined. Your existing functions will continue to execute without change.
2. Do not create any process specific layouts for a process which already exists, i.e., do not create a layout for the process unless you want it to adopt the new layouts.
3. If you have created system wide default layouts but do not want them to impact specific processes, then you can create a process specific Web skeleton which does not include the RDML LAYOUT and other new RDML tags. For more technical details, refer to Customizing a Presentation Layout – Technically Speaking.
When you import any functions into your system, you should be aware of these points so that you can properly handle the impact of the Wizard on your application.
On IBM i, If you have created your own skeletons in file DC@W22 and you wish to use the Web Functions Wizard for these existing functions, you may need to modify your skeletons according to the changes made in the default shipped skeleton (WEBSKEL in file DC@F28 in the LANSA data library).