Storage and Port Configuration

R2026b

Storage Configuration

  • To ensure optimal data storage performance, use physical drives instead of networked storage solutions.

  • Make sure that you have adequate disk space for the database mount point. For Docker Compose deployments, the database volume path is configured through the PSACCESS_DB_VOLUME variable in the .env file. If you are using admin-docker-agent, the database is stored under polyspaceAccessRoot/appdata/polyspace-access where polyspaceAccessRoot is the folder where you unzip the Polyspace® Access™ installation image.

  • Secure the database mount point with a RAID (Redundant Array of Independent Disks) array and back up the mount point regularly.

  • Allocate this recommended amount of disk space for the mount points of the working directories of the Polyspace Access processes:

    • Temporary upload directory: 10 GB

      Uploaded files are stored in this folder while they are transferred to the web server mount point.

    • Upload directory: 10 GB

      Once the transfer to the web server mount point is complete, files are moved to this directory. The path to this directory must be the same for the extract-transform-load (ETL) and web server services. If the services are on different machines, the paths to this directory must point to the same hard drive.

    • Storage directory: 50 GB

      The ETL (import process) looks for files in the upload directory and stores them in the storage directory. Files that are successfully uploaded to the database are deleted. Files that fail to upload are sent to the invalid results directory.

    • Working directory: 10 GB

      The ETL (import process) uses this directory to process files from the storage directory. Files are treated in the order in which they are received. The data is prepared to be sent to the database. Set the size of this directory to a minimum of twice the size of your largest result file when unzipped.

    • Invalid results directory: 50 GB

      Files that fail to upload are stored in this directory. You can recover and analyze the files to determine why the upload failed. Set up a policy to determine the amount of time after which older data can be deleted. Manually clean this directory regularly.

  • Make sure that all users have read and write permissions for the ETL and temporary upload directories. For Docker Compose deployments, the location of ETL directories is configured through the PSACCESS_ETL_BASEDIR variable in the .env file and each directory is defined in the file common.yaml. If you are using admin-docker-agent, configure these directories in the Cluster Admin settings.

Network Port Configuration

When you configure Polyspace Access, you specify a port number that client machines use to communicate with the Polyspace Access services. To avoid installation errors and to verify that the services are accessible, make sure that the port that you specify is open. To check whether a port portNumber is open, use this command:

netstat -na | grep portNumber
If the output of the command is empty, the port is not in use. If the port is in use, specify a different port or stop the process currently using the port.

If you install Polyspace Access on a single node with a default configuration, check the availability of these ports:

  • 8080 — Default Polyspace Access gateway port for Docker Compose deployments (GATEWAY_PORT in the .env file). If you are using admin-docker-agent, the default port is 9443.

  • 27000 — Inbound port of license manager daemon that is required to manage license checkouts.

  • Make sure that you also check the availability of the vendor daemon (MLM) port. If you did not specify a port for the vendor daemon, check the license manager log file to find the assigned port. To specify a port for the vendor daemon, see step 2 of Configure Polyspace Access License.

If you change the default port values in the .env file, check the availability of all the ports that you specify.

See Also

Topics