11. Deploy LANSA for the Web Applications
Considerations
- The machine where the installation is built must be a fully working example of the application. This is vital as many configuration files are pulled directly from the Build environment.
- LANSA for the Web applications on Windows consist of three logical parts: the Web Server (e.g. IIS), the Data Application server (i.e. LANSA) and the Database Server (e.g. SQL Server). It is most common, even in high transaction environments, to locate the Database Server on a dedicated machine so that as much RAM as possible may be allocated to the database. The Web Server and Data Application Server are then installed together on a separate machine, again the RAM is largely available for the LANSA processes to execute in. In systems with a high throughput, multiple Web Server/App Server machines may be installed with a Load Balancer to share the load between them, or even a simple DNS round-robin multiple IP address setup to load balance between the servers.
- Linux and IBM i servers may also host any part, or all, of LANSA for the Web. Some common scenarios which involve a part of Windows and a part elsewhere are:
- Windows Web Server with IBM i Data Application Server and DB2 i Database Server.
- Linux Web Server with Windows Data Application Server and SQL Server Database Server.
- Windows Web Server and Data Application Server with Linux Oracle Database Server
- IIS must be enabled on the Web Server. Specific settings are not required as the install automatically configures what it requires.
- The User ID for the Web Configuration must be able to log on to the Data Application Server and should be a member of the user group "LANSA Users". This is configured automatically.
- When deploying LANSA shipped weblets (typically the std_* weblets) or external resources (XW* external resources), either as selected objects or a cross-referenced objects, ensure the package has been built in an environment where the appropriate version of these objects has been installed.
- A WAM or WEBEVENT function cannot be automatically launched from a deployed package in a browser.
- A URL shortcut can be created to launch the Web Application using the Files with Special Processing option.
- To request a runtime License for your LANSA web application you must supply the CPU details of the Windows server on which the application is installed. This is achieved using a shipped LANSA utility, called X_CPU. Refer to the LANSA Support web page for further information.
- To review the current licenses on the runtime environment execute the process *LICENSES.
- The LANSA utility X_CPU and the process *LICENSES are included when you deploy the LANSA runtime.
- Template XWAMENB has been created to assist with the deployment of a WAM Application.
- Refer to the Installing LANSA on IBM i Guide or Installing LANSA on Windows Guide for more information on installing the Web Server.
Restrictions
- The web user is not configured to be the partition security officer
Update X46SEC with the web user so that the Web Administrator may connect successfully. E.g. Set it to PCXUSER as the default.
- Default SQL Server Instance MSSQLSERVER is not fully supported
If a default SQL Server instance is used, the web user will not be given permission to login to the database.
- Deploying a large set of files in the Web Images may fail with messages like "too long for an identifier"
The images directory will need to be deployed manually.
- JSM Service must be stopped before building a version which includes Integrator
- Some shortcuts are not removed when the application is uninstalled.
- MSI Install will fail part way through if there is a pending reboot. The install will be rolled back.
Reboot the machine and restart the install.
Also see
11.2 Data Application Server with Windows Application Database