In this scenario the database is installed on the server and the clients are installed as "fat" clients with the application DLLs installed locally.
To support this scenario, create two Deployment Tool applications:
The following Settings should be considered and reviewed:
The following Options and details should also be considered and reviewed:
Communication Administration file (lroute.dat) and listener (listen.dat) will need to be included to facilitate connection to the data server.
DBMS Type (DBUT). An appropriate server database type should be nominated, for example, Oracle or MS SQL Server.
Database Source Name (DBII).
| Using SuperServer Built-In Functions is the recommended approach for establishing a connection to a remote system. For details on installing a Client application which utilizes SuperServer Built-In Functions refer to Superserver Application using Built-In Functions to connect to server. |
The following Settings should be considered and reviewed:
Deploy to Client without local database
Deploy System definition
Deploy Partition definition
Deploy Execution Add-ons
Deploy with Component Support
Deploy LANSA Communications
The following Options and details should also be considered and reviewed:
Process/Function/Form to Execute - Specify the executable to be used to start the application once installed
Install Listener
The Communication Administration file (lroute.dat) and listener (listen.dat) will need to be included to facilitate connection to the data server.
Server Type (DBID)
Server Name (PSLU)
User for Server (PSUS)
Password for Server (PSPW)Divert Locks (PSDL)
Server Exception Arguments (PSEA) (for example DBID, DBII, DBIT, DBUT, DBUS, PSWD, RPTH, TPTH)
DBMS Type (DBUT). Typically set as NONE (that is, no local database)