LINKDB

The PARTsolutions link database (LINKDB) is set up as additional database on an already existing database server. No further software is needed on the database server.

PARTapplicationServer

For the PARTapplicationServer a dedicated server or a virtual machine is recommended.

Special reasons for this are:

ONE dedicated PARTapplicationServer for all locations is sufficient. All clients fetch the detailed data of the search hits from the central $CADENAS_DATA file server.

On this server the CADENAS license server can also be installed. See Section 3.4, “FLM Server Installation - Request/install licenses ”.

File-Server Head Quarter

For the PARTsolutions catalogs and the setup directory a new share on an already existing file server is sufficient. No further software is needed on the file server.

Note Catalog administration has writing permission. All other user have only reading permission. $CADENAS_DATA only exists 1x, in fact for all clients and all locations.

$CADENAS on clients (PARTsolutions software and interfaces)

Software deployment / software updates

Advantage: Software updates can easy be performed later.

File-Server Secondary Location (Setup directory [$CADENAS_SETUP])

Replication of $CADENAS_SETUP

$CADENAS_SETUP can easily be replicated (cyclically or if needed) from the head quarter to the secondary locations (e.g. with Robocopy, Microsoft DFS or similar tools).

Caching of index files

In order for the PARTapplicationServer to work efficiently, we recommend caching of CADENAS_DATA index files.

RFS or SQUID Caching (optionally)

In order for the data flow between client and server to be optimal, often used data (especially project and ZJV files) can be cached. At large assemblies (also at native parts) in this way the performance can be enhanced.