2.1.  Software components

Basically the software is made up of the 5 components listed below. All components, central or local, can be individually installed.

  1. Software

    One PARTsolutions installation per location. There is a master installation at one location that is synchronized cyclically with the other locations. All updates are installed at this master location. If there are performance problems at one location, one installation can theoretically also be kept per department, whereby the maintenance and replication effort increases.

  2. Catalogs

    All catalogs are stored centrally for each location. Process as for software.

  3. LinkDB

    One central LinkDB. The LinkDB can be installed at a central location which can be easily reached by all other locations. Should the network performance not suffice, the LinkDB can be installed at every location and replicated per database mechanism. The LinkDB is independent of the database used in the company. Of course the existing database may be used for the LinkDB as well. Experience has been made with, among others, MS SQL Server, Oracle, SAPDB, mySQL.

    [Note]Note

    Please note the information under Section 2.5, “ LinkDB”.

    [Note]Note

    The LinkDB is an optional component and is always required for the operation of PARTsolutions with ERP/PDM integration.

  4. Fingerprints

    The fingerprints are usually found with the catalog state and are thus also replicated with a catalog update.

    [Note]Note

    To speed up the search, the PARTapplicationServer should be used for a client-server installation. See Section 4.5.3, “ PARTapplicationServer installation.

  5. License server

    The license server is a tool which runs on a specific port on a server. All clients must have access to this computer/port. The license server can be installed in any locations. When updating licenses, a new license file must of course be imported at every location.

    Normally, a local installation of the software and catalogs demonstrates the best performance. The LinkDB should be, in so far as the network speed allows, centrally available in order to avoid possible complicated replication configurations at the database level.

    There are no special hardware requirements for the server nor the client. If a CAD system works on a client, PARTsolutions should also work without a problem. Regarding system and hardware requirements, please see the following information.

    The server is a pure " file server " on which only files are transferred to the client and executed on the client side. The file sizes can be found in the following table. The server should be designed in such a way that it can provide the files for the clients quickly even at peak times (in the morning).