powered by CADENAS

Manual

Manual

4.5.10.4. Example 3: Direct database connection and manual user login

The following example shows the settings for manual database login at PARTdataManager start and direct client database connection (= using the options Catalog browsing and search with AppServer or Search with AppServer ).

Preconditions

  • Setup ODBC on client

    When using the setting option Catalog browsing and search with AppServer or Search with AppServer the connection between client and link database is directly established. Meaning ODBC has to be set up on the client.

    [Note] Note

    In contrast, when using the option Catalog browsing, search and database with AppServer this is not necessary on client side, because the connection to link database is established via AppServer.

    The name used for setting up the ODBC connection has to be identic with the entry under PARTlinkManager -> Extras menu -> Configure ERP environment -> tabbed page Database -> Name.

  • Set environment variable CADENAS_DATA on the client

    The environment variable $CADENAS_DATA has to be set and point to the data directory (on the server).

    [Note] Note

    In contrary, this is not necessary when the option Catalog browsing, search and database with AppServer is used because then the connection to $CADENAS_DATA is established via AppServer.

The following settings have to be made on the AppServer:

  1. Disable automatic login

    PARTadmin -> category ERP environment -> Database login -> Enable automatic login

    If a login dialog for user authentication shall be displayed at PARTdataManager start, please make sure that the option Enable automatic login is disabled.

  2. Create users

    Change to the category ERP environment -> User.

    Under User-Role assignment on the left side under User, click on New and create the required PARTsolutions users (here exemplified the users "ecat" and "location") and on the right side, enable the desired roles which shall be available to the respective user.

    Create the same users in the database.

    [Note] Note

    There is a distinction to be made between PARTsolutions users and database users:

    • The connect to the database happens by using a database user.

    • PARTsolutions users are mapped to database users. In the following figure, see dialog area Database user and dialog area User.

      On the right side, users get roles assigned.

    ALL database users have to be created both in the PARTsolutions configuration files and in the database as well.

    In comparison: If the database connection is established via AppServer then principally two database users are sufficient because different user configurations can use the same database connect. See example 1.

  3. The input fields under Login-Dialog and Automatic login can remain empty because the authentication data is entered in the login dialog at PARTdataManager start and is checked directly at the database.

Result: At PARTdataManager start the Database login dialog opens.