AS setup with the database driver running on the AS

This setup is recommended.

The installation procedure is the same as described in AS setup with database driver running on the MAS.

In comparison to the setup, where the database driver runs on the AS, you can run a Convert to Runtime in the Tables by Database (ttaad4111m000) session on the AS.

  1. Install a database client or ODBC driver for your database on the Application Server.
  2. Go to the MAS system.
  3. Ensure the AS is registered in the Systems (ttaad0550m000) session.
  4. Add your admin user and password and AS system to the Remote User data (ttaad2501m000) session.
  5. Convert the changes to runtime and restart LN UI.
  6. Start the Database Definitions (ttaad4510m000) session.
    Ensure the Parameter field points to the correct LN server and database instance.
  7. Start the Tables by Database (ttaad4111m000) session to distribute the tabledef6.2 file from the MAS to the AS.
  8. Select the Convert to Runtime option to start the Create Runtime Database Definitions (Tabledef) session. Only select the (Other) Workstation check box and the Workstation (AS).
  9. Click Create.
  10. Set up an Audit Host. Audit servers can only run on the MAS:
    1. Start the Audit Hosts (ttaud3130m000) session.
    2. Add the Master Application Server.
    3. On the Actions menu, select Create Runtime Audit Definitions.
    4. Select the Audit Hosts check box and click Create.
  11. Optionally, add the users to the Remote User Data (ttaad2501m000) session who must be connected to the new AS. Convert these changes to runtime.
  12. Copy all created $BSE/lib/r<users> files from the MAS server to the same directory on the AS server.
    Note: This new entry must be based on the system name of the MAS server.
  13. Go to the AS server.
  14. Remove the $BSE/lib/datecurr file. These settings are automatically retrieved from the MAS during logon.
  15. If available ensure the settings in $BSE/lib/defaults/all and $BSE/lib/defaults/db_resource files are matching the settings located on the MAS.
  16. To use the shared memory data that is configured on the MAS, remove the $BSE\lib\srdd_tab6.2 file that is located on the AS.
  17. Stop and restart shared memory.
    With the first logon the srdd_tab6.2 objects that are configured on the MAS are automatically retrieved and placed in the shared memory on the AS. You cannot convert shared memory to runtime on an AS.