Chapter 29. V9.08 SP1
29.5. Global and local PARTapplicationServer settings
Prev  Next

29.5. Global and local PARTapplicationServer settings

Please perform the AppServer Client configuration in PARTadmin -> category AppServer client.[145]

Here, you can define how clients should access the AppServer, meaning via which ports, whether a local AppServer should be used, whether the AppServer has only to be used for searching or for catalog browsing as well.

PARTadmin -> "AppServer Client" category

PARTadmin -> "AppServer Client" category

The following listing explains the settings in particular:

  • Catalog browsing and search with AppServer

    As of PARTsolutions V9.08 there is only ONE central data directory for multi-installations as well.

    All access (catalog browsing and search) is processed via PARTapplicationServer - regardless from which location.

    Thus select this option, if PARTsolutions is used remotely without synchronization of catalog data.

    Therefor a specific license is needed.

    [Note]Note

    Using the API requires another license. Thereby third party systems can access the PARTapplicationServer.

    [Note]Note

    With this option there is no write access to $CADENAS_DATA.

  • Search with AppServer

    Only the search runs on the AppServer.

    Therefor no extra license is needed.

  • Use local AppServer (default)

    Using the local AppServer is advantageous compared to pdatamgr.exe. This is running on 64Bit, whereby possible memory problems are avoided.

    The local AppServer is only used for searching, not for catalog browsing.

    The AppServer is automatically started and exited together with PARTdataManager. If Seamless is also started, then Seamless uses the already running application.

  • Do not use AppServer

    All processes are running via PARTdataManager.

Enter server address and ports: (only active with the options Catalog browsing and search with AppServer and Search with AppServer)

  • Server address: Here please enter the server address

  • HTTP port: 9020 (default) [used for the file system]

  • Service port: 9021 (default) [used for index and search]

  • Don't use proxy server:

The respective keys and values of the configuration file

Clientmode can assume the following values:

  • Remote: Connection with RemoteServer

  • Local: A local AppServer is started, when PARTdataManager is started

  • Noserver: No access on AppServer

remoteFileSystem: The key controls, whether the Remote File System shall be used, meaning whether the catalogs shall be fetched via AppServer.

The key can assume the following values:

  • YES

    In this case there is no write access possible to CADENAS_DATA.

  • NO

Key combinations and values of the single GUI options

  • Catalog browsing and search with AppServer 

    [Common]
clientmode=remote
remoteFileSystem=YES

  • Search with AppServer 

    [Common]
clientmode=remote
remoteFileSystem=NO

  • Use local AppServer 

    [Common]
clientmode=local
remoteFileSystem=NO

  • Do not use AppServer 

    [Common]
clientmode=noserver
remoteFileSystem=NO

The key applications controls, which applications shall use the PARTapplicationServer and which not.

Global and local specification of the settings

[Note]Note

The usage of the PARTapplicationServer may be specified globally and locally.

First of all the file $CADENAS_SETUP/pappclient.cfg applies globally for all users.

However, in the file $CADENAS_USER/partsolu.cfg, for single clients certain keys can be overridden locally. If nothing is set, then the settings from pappclient.cfg apply.

Example:

Configuration file: $CADENAS_SETUP/pappclient.cfg:

[COMMON] 
clientmode=remote 
remoteFileSystem=YES

applications=pdatamgr,pseamless

applications=pdatamgr,pseamless (default): PARTdataManager and Seamless fetch their data from AppServer.

clientmode=remote: Connect with RemoteServer

remoteFileSystem=YES: The Remote File System shall be used, meaning the catalogs shall be fetched via AppServer.

In this case, if a normal user tries to perform a NativeCheckin, an error message is displayed:

No write access possible because the access to the catalogs is done by the AppServer. To be able to perform the check-in, you must enable the direct access to the server for this client

Reason:

  1. The global configuration file defines, that PARTdataManager (thereover the interface function NativeCheckin runs) uses the PARTapplicationServer.

    (applications=pdatamgr,pseamless)

  2. Furthermore the Remote File System shall be used via AppServer.

    (remoteFileSystem=YES)

So when in the local configuration file, for example at an Admin working place, the key remoteFileSystem is overridden, NativeCheckin should be possible.

Configuration file: $CADENAS_USER/partsolu.cfg:

[COMMON] 
remoteFileSystem=NO

Now access to $CADENAS_DATA does not happen via AppServer anymore (which does not have write access). Now $CADENAS_DATA can be accessed via UNC or network drive.

[Note]Note

For Admin computers, please set the environment variable $CADENAS_DATA respectively.

The DATA path via which the PARTapplicationServer accesses the catalogs, is displayed in the dialog box Server state.

In order to see the path, in PARTadmin -> category AppServer client, click on the button Show server state.

On the tabbed page Environment, you can find the line CADENAS_DATA.



[145] The configuration file for the AppServer client configuration is found under $CADENAS_SETUP/pappclient.cfg.

Prev Up Next
29.4.  PARTdataManager: Suppress note at missing search indexes Home 29.6. SharedIndex on $CADENAS_USER