Only ONE PARTapplicationServer is installed and all clients - regardless of their location - connect to this one PARTapplicationServer.

For distributed installations (client-server and multi-site installations), we recommend setting up the PARTapplicationServer as a separate server or virtual machine.^[2]

Special reasons for this are:

The recommended procedure of software installation is to locally copy $CADENAS - the same as with any client.

The use of a 64-bit system is recommended.

The user account requires corresponding rights to $CADENAS, etc.

Communication with the AppServer takes place via the two ports 9020 + 9021 (see also Fig. „Architecture of a Multi-Site Installation with PARTapplicationServer“). (For communication via https, corresponding certificates are also required)

The AppServer requires a connection to the database. The database should be accessible on the server or from it via a fast connection.

The environment variable $CADENAS _DATA controls which data directory is used. You can easily see which directory this points to under Server status dialog page, Environment tab page. See Section 1.3.5.9, “ PARTapplicationServer Dashboard ” in PARTsolutions Administration - Manual for this.

%temp% should have enough space, because there, during Lucene index generation, the index is buffered. Required space size depends on size of installed catalogs and number of roles. Recommendation: Minimum 100-200 GB.

On the server, the same space is needed once again for the index caching. In case of doubt better include more than less.

The PARTapplicationServer (PAPPSERVER) is started as service. The service has to be able to access the CADENAS directories and to connect to the license server. Also see Section 4.5.3.2, “Set up PARTapplicationServer as a service ”.