Versions Compared

Old Version 1

changes.mady.by.user Nadine Hinojosa

Saved on

compared with

New Version 2

changes.mady.by.user Nadine Hinojosa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Show Contents List
You are here:

...

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:
1.    The first application will be installed on the server and includes system variables, files (including message files) and their OAMs.
2.    The second application must be installed on each client and includes the application's forms, processes and functions.
Server Package
The following Settings should be considered and reviewed:

...

  • LANSA User
  • 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.
  • SuperServer options:
  • 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).

...