LINKDB

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

Detailed information is found under Section 4.2, “Installation Link database ”.

PARTapplicationServer

A separate server or virtual machine is recommended for the PARTapplicationServer.

Special reasons for this are:

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

It makes sense to also install the CADENAS license service on this server. See FLM server installation - Requesting/installing 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 administrators have write access. All other users have read-only rights. $CADENAS_DATA only exists 1x, in fact for all clients and all locations.

$CADENAS on clients (PARTsolutions software and interfaces)

Software distribution / software updates

Advantage: Software updates can be carried out just as easily 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 the CADENAS_DATA index files.

Detailed information on this is found under Section 1.3.5.8.3.7, “ Caching index files of $CADENAS_DATA on PARTapplicationServer ” and Section 1.3.5.4, “Caching methods for data storage and operation ”.

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.

See Section 1.3.5.8.2.4, “Caching on client side or at secondary locations ” and Section 1.3.5.4, “Caching methods for data storage and operation ”.