1.4.5.5.3. Requirements

For this deployment, two servers are required:

  1. A central app server.

  2. A separate cache server on which pappcache.exe installed .

The cache server is connected to the central AppServer via the CADENAS_APPSERVER environment variable and then configured in PARTadmin.

Before beginning the installation, the following prerequisites must be met:

  • A running and functional 3Dfindit Enterprise installation (AppServer).

  • Properly configured and functioning authentication in this environment.

  • A user who has been assigned the appserver-admin profile in the rights management system. This user is required for remote configuration via PARTadmin .

  • A Windows server (Windows Server 2016 or later, 64-bit) for running the cache service.

  • Sufficient hard disk space for the RFS2 cache—at least the planned cache size.

System Requirements in Detail:

RequirementDetails
Operating SystemWindows Server 2016 or later (64 bits)
Runtime environmentPARTsolutions 12.0 or later
BackendA running AppServer service ( pappserver )
Certificate StoreWindows Certificate Store (for SSL/TLS)
Configuration pappcache.cfg in $CADENAS_SITESETUP
Hard Drive StorageAt least the configured cache size (default: 10 GB)

[Note]Note

Requirements and Notes:

  • A true edge server is required:

    • => The AllowProxy settings must be set to the IP address of this Edge server

    • => The edge server is assigned its own hostname, B.server.com (if the main server is A.server.com)

    • => Your own certificate and everything you need ...

    • => B.server.com must then be added to the Allowed-CORS header list

    • => In addition, for OpenID, the URLs for B.server.com must also be added to the list of allowed redirect-uris .

More information:

  • => Because SSL is used, standard proxies such as (Squid, Nginx, Caddy, etc.) will NO LONGER work ...

  • => Client-side caching is the method of choice. Caching proxies only work over HTTP, which is insecure ...