powered by CADENAS

Manual

Manual

4.5.10.2.  Example 1: Database connection via AppServer and manual user login

The following example shows the settings for manual database login when starting PARTdataManager and client database connection via AppServer (=using the option Catalog browsing, search and database with AppServer).

Catalog browsing, search and database with AppServer

Catalog browsing, search and database with AppServer

In this case a Database login dialog shall be displayed when starting PARTdataManager.

The following settings have to be performed on the AppServer:

  1. Deactivation of automatic login

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

    If al login dialog shall be displayed when starting PARTdataManager, please make sure that the option Enable automatic login is disabled.

  2. Create users

    Change into the category ERP environment -> User.

    Under User-Role assignment, left under User create the desired PARTsolutions users (here exemplified the users "ecat" and "location") by clicking on New and on the right side, activate the desired roles, which should be available for the respective user.

    In the database, create the desired users (here exemplified dbo (sa) and erpuser).

    [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.

  3. Specify passwords

    [Note] Note

    When using a manual user login the password entered by the user is compared with the one under Login-Dialog. Then it is checked whether the user is allowed to access the Appserver.

    With automatic login no password has to be entered under Login-Dialog, because the user identification already happened via Windows login name (compare example 2).

    The database connect happens with the password under Automatic login. The most efficient approach is to create as little database users as possible in order to get as little database connects as possible. Normally two database users are sufficient. One for Standard users which shall be able to execute database queries and to add new datasets to the link database and one for Admins which shall be able to add and delete columns in PARTlinkManager. The respective settings have to be made in the database itself.

    Automatic login:

    Under Automatic login, enter User and Password for the database login.

    A standard installation of the PLINKDB creates an Admin user and a Standard user.

    • Login Admin user

      • User: sa

      • Password: (according to the password given during the database creation)

    • Login Standard user

      • User: erpuser

      • Password: erpuser

    Login-Dialog:

    Here, enter the password which has to be entered in the login dialog when starting PARTdataManager.

    [Note] Note

    The password under Login-Dialog is displayed with only one placeholder, regardless of its actual length (becomes visible when changing the user once).

    [Note] Note

    The passwords (both from Login-Dialog and from Automatic login) are saved in $CADENAS_SETUP/plinkusers.cfg in encrypted form.

    Example:

    [location]
    GROUPS="LOC1","LOC2","LOC3"
    GROUPORDER="DUMMY","ECAT1","ECAT2",...
    DBUSER=location
    DBPASS=cb9bd5394bd75b9b
    PWD=#18cb2237d0679ca88db6464eac60da96345513964
    

Result: When starting PARTdataManager the Database login dialog opens.

[Note] Note

Please regard the following:

  • This is not a local database connection, but a connection to the central database via PARTapplicationServer. You can recognize it at the attached string REMOTE under Driver.

  • Password in PARTdataManager, in the client connection Database login dialog is that password which has been stated in PARTadmin under Login-Dialog, NOT the one under Automatic login.

    If no login dialog shall be displayed on the client then use "Automatic login". See example 2.