In this scenario the database is installed on an IBM i server and the clients are installed as "fat" clients with the application DLLs installed locally.
To support this scenario, create a single Deployment Tool application to be installed on each client. This will include the application's forms, processes and functions much the same as when connecting to a Windows or Linux client.
The IBM i portion of the application must be deployed using the LANSA for i Export and Import facilities. This will include the system variables, files (including message files) and their OAMs.
Client Package
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
- Omit Object Definitions
- Deploy with Component Support
- Deploy LANSA Communications
The following Options and details should also be considered and reviewed:
- LANSA User in the Execution Parameters list.
- Process/Function/Form to Execute - Specify the executable to be used to start the application once installed
- Install Listener
- Communication Administration file (lroute.dat) and listener (listen.dat) will need to be included to facilitate connection to the data server.
- DBMS Type. Typically set as NONE (that is, no local database).
- SuperServer options:
- Server Type (DBID)
- Server Name (PSLU)
- User for Server (PSUS)
- Password for Server (PSPW)
- Divert Locks (PSDL)
- Use Commitment Control (PSCC)
- DBCS Capable (PSDB)
- Client to Server (PSCT) and Server to Client (PSST)