1.3.5.8.  PARTapplicationServer - Configuration
1.3.5.8.2.  AppServer Client: Configuration
Prev  Next
1.3.5.8.2.  AppServer Client: Configuration
1.3.5.8.2.1. Setting options for catalogs, search and database via AppServer | Catalogs and search via AppServer | Search via AppServer
1.3.5.8.2.2. The corresponding keys and values of the configuration file
1.3.5.8.2.3. Key combination and values of the individual GUI options
1.3.5.8.2.4. Caching on client side or at secondary locations
1.3.5.8.2.5. Precondition for Single Sign-on

The AppServer Client configuration can be made in PARTadmin -> AppServer Client [AppServer client] category. [11]

Connection to the AppServer [AppServer connection]: Here you can define how clients should access the AppServer, i.e. via which ports, whether a local AppServer should be used, e.g. whether the AppServer should only be used for searching or also for catalog browsing, etc.

The following list explains the settings in detail:

  • Catalogs, search and database via AppServer [Catalog browsing, search and database with AppServer] and Catalogs and search via AppServer [Catalog browsing and search with AppServer]

    PARTadmin > Category "AppServer Client [AppServer client]" > Selection "Catalogs, search and database via AppServer [Catalog browsing, search and database with AppServer]"

    PARTadmin > Category "AppServer Client [AppServer client]" > Selection "Catalogs, search and database via AppServer [Catalog browsing, search and database with AppServer]"

    There is only one central data directory for multiple installations.

    All accesses (catalog browsing and search [and for catalogs, search and database via AppServer [Catalog browsing, search and database with AppServer] also to the LinkDB]) - no matter from which location - run via the PARTapplicationServer.

    Select one of these two settings if you use PARTsolutions remote without synchronization of the catalog data.

    [Note]Note

    A specific license is required for this. See Section 1.3.5.5, “Licenses for the PARTapplicationServer ”.

    [Note]Note

    The use of the API requires an additional license. This allows third-party systems to access the PARTapplicationServer.

    [Note]Note

    With the option Catalogs, search and database via AppServer [Catalog browsing, search and database with AppServer], connections between the client and LinkDB are not made directly, but also via the AppServer.

  • Search via AppServer [Search with AppServer]

    Only the search runs via the AppServer.

    [Note]Note

    No extra license is required for this.

  • Use local AppServer (default)

    -> All other setting options are deactivated (grayed out).

    Use local AppServer

    Use local AppServer

    The Using the local AppServer offers advantages over pdatamgr.exe . This one is running to 64bit, which avoids possible memory problems.

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

    The AppServer is automatically started and stopped with the PARTdataManager. If Seamless is also started, Seamless uses the application that is already running.

  • Do not use an AppServer [Do not use AppServer]

    -> All other setting options are deactivated (grayed out).

    All processes run via PARTdataManager.



[11] The For the AppServer Client configuration configuration file, see under $CADENAS_SETUP/pappclient.cfg.

Prev Up Next
1.3.5.8.1.4.  Rights " tab page  Home 1.3.5.8.2.1. Setting options for catalogs, search and database via AppServer | Catalogs and search via AppServer | Search via AppServer