jdeDirect Multi-Server Security Guide
In the above example, we have shown a multi-server JDE OneWorld implementation, with environment PY on the DEV system and PD on the PROD system. A PC has a PY Fat Client installed, and a second PC has Thin Client access to the OW system, be that via Citrix, web or any other means.
jdeDirect ODBC drivers may be installed and configured in 3 different ways, the User Id and Password used when using jdeDirect behave differently in each configuration.
1.. Fat Client.
A standard Fat Client install of jdeDirect can be carried out on the PY machine. In this case, the User Id and Password used is authenticated against the PY fat client and therefore must exist in OW PY.
The same user and password is used when connecting to PD, the user id must also exist in PD, the password may be different – but the PY copy of the user id and password are used to authenticate against OW using the PY Fat Client APIs.
2.. Pass Through.
This enables the use of a database User Id and Password, switching off OW user authentication.
This database user id must exist on both systems and the user id must exist in OW for both PY and PD as described above.
The user id and password is authenticated against the database connected to the PY Fat Client when connecting to either PY or PD.
3.. Thin Client.
When using jdeDirect on the Thin Client machine, a Thin Client Service Program needs to be installed on a GATEWAY machine (this runs as a service) to support
Thin Client authentication. The GATEWAY machine services authentication requests coming from Thin Clients that can then be configured to apply Fat Client Security, 1 above, or Pass Through Security, 2 above.
** In all cases, the standard JDE OW row/column security, user preferences, language settings etc. continue to be applied based on the configuration of the DSN setting for System Data Source.