Note that in most production configurations the Windows web server and the Windows application server are two separate machines.
Step | Activity | How to Do It | OK |
|---|
Install Visual LANSA on the application server | If Visual LANSA is not installed on your application server, install it from CD either as an Independent Workstation or Independent Server. During the installation, in the Partition Initialization dialog select:
| Accept default settings. If you need more information, see Install or Upgrade LANSA on Windows Guide and Visual LANSA Framework Guide. There is no need to configure the Visual LANSA Framework - simply import the Framework objects into your Visual LANSA system. |
Install LANSA for the Web on the Windows server from CD | If not already installed on the target Windows server, install:
| Install it to the same directory as Visual LANSA. If you have multiple LANSA systems, use the same LANSA configuration as for the LANSA Web system. Accept default installation settings. If you need more information, see Install or Upgrade LANSA on Windows Guide. |
Ensure you have a Web license | Ensure the target application server has a Web license. | If you need more information, see Licensing at the LANSA Support website. |
Configure LANSA for the Web | 1. Ensure IIS is running by entering this URL into the browser running on the Web Server: http://localhost | Use the iisreset command from a command window if you have problems. | |
2. Make sure Microsoft Windows Script Host (WSH) is installed by locating the file wscript.exe. | |||
3. Configure LANSA Listener on Windows Data/Application Server. | |||
4. Create User on Windows Data/Application Server. | |||
5. Configure Data/Application Server. | |||
6. Verify IIS Plug-in Communications with Data/Application Server. | |||
7. Verify that the Web Server is ready to use. |
Verify that LANSA Web Server is installed and operational on the target system | Make sure the partition is web enabled. |
|
Install the deployment material | Install the package by double-clicking the package .MSI file to the same directory where you have installed the LANSA system (for example C:\Program Files\<LANSA>). | If you encounter problems during the installation, check the MSI*.log file in the end user's defined %TEMP% folder, for example: MSI2ce4c.log. As well as installing the Application, a standard Windows program menu folder will be created for each Application using the Company and Application descriptions as folder names. This means that every Application built with the same Company details and installed on the same PC will be grouped together. |
Execute the Framework application | Execute the VLF-ONE application. | Typically starting URLs are formatted like this: http://<host>/<lansa system>/<partition>/<entry point web page>?Lang=<language code>&FrameworkID=<framework id> For example: http://localhost/MyLansaSystem/PRD/MY_OEXEC.html?Lang=ENG&FrameworkID=MY_VLFONE_SYSTEM |
Instruct your users to create a shortcut for the application. | Usually the best way to launch a VLF-ONE application is from a shortcut. | See Shortcuts for Launching VLF-ONE Applications in the Framework guide. |