3. AppServer V12 - Client Server
3.7.  Automatic login
Prev  Next

3.7.  Automatic login

[Note]Note

The option Enable automatic login (plinkcommon.cfg -> Block [Login] -> Key "AUTOLOGIN") does not exist anymore.

An (automatic) login runs as follows:

  1. At first there is a check if the user has been logged in once before. Information on this is stored in $CADENAS_USER, in token.db.

  2. If information about the last login can be found there, it will be taken.

  3. Otherwise the application attempts to log in via Windows login, however, only if under Rights administration > User databases, the login method Windows is activated.

  4. Otherwise a login dialog with the activated login methods is displayed.

  5. Independently of this you can call the User authentication dialog from PARTdataManager / 3Dfindit anytime.

    • PARTdataManager

    • 3Dfindit

Evaluation of pappclient.cfg

The key applications does not exist anymore. It has been removed, because more and more applications pull the SiteSetup via Appserver, so that is does not make sense to state single applications for this. Either a computer can directly access the directories (CADENAS_DATA, CADENAS_SETUP, CADENAS_SITESETUP, etc.) or not. Mostly only one (Admin) computer is required, in order to make settings or install catalogs. In this case it makes sense to deactivate the RemoteFilesystem, the RemoteIndex and the RemoteDatabase via Variable CADENAS_APPSERVER. The setting options (parameters) about CADENAS_APPSERVER are described in Section 3.3, “PARTsolutions Client”.

The evaluation of the pappclient.cfg runs as follows:

  1. At first there is a check if a variable CADENAS_APPSERVER is set. If yes, then pappclient.cfg is not evaluated, but all settings are taken from the variable CADENAS_APPSERVER.

  2. Then there is a check what should run via Appserver:

    • remoteFileSystem: CADENAS_DATA is pulled via Appserver

    • remoteSetup or remoteSiteSetup: CADENAS_SETUP or CADENAS_SITESETUP run via Appserver

    • remoteDB: Database access via Appserver

    • remotepool: CADENAS_DATA/pool accessed via Appserver

  3. Differentiation between local mode and remote mode (key clientmode )

    • local

      In the local mode the Appserver is started from the client, if it is not running. In this mode the key LocalApplications is evaluated. All applications stated there start or connect to AppServer. Also PARTadmin starts an AppServer. The applications use the AppServer for searching.

      In local mode, PARTadmin always directly accesses the file system and the database. That means above settings are ignored.

    • remote

      In remote mode, all applications always access the AppServer.

      If the client application runs on the same computer as the AppServer, the following rule applies:

      • For PARTadmin: All settings (remoteFileSystem, remoteSetup, remoteSiteSetup, remoteDB ) are ignored. Access is always direct.

      • All other applications: remoteFileSystem is ignored Reason: Appserver starts applications like the psolupdater, which have write access to CADENAS_DATA.

    [Note]Note

    If catalogs are installed with PARTadmin on a client, you can activate direct access to the data via variable CADENAS_APPSERVER (by deactivating remoteSetup, remoteSiteSetup).

    You can also achieve appropriate settings via Installation type "Software Local, data and setup from an existing server ".

    Software Local, data and setup from an existing server

    Software Local, data and setup from an existing server

Prev Up Next
3.6. Setup ERP environment (V12.6)  Home 3.8. CAD Client Configuration