English
Deutsch
Español
Français
Hrvatski
Italiano
Polski
Türkçe
Русский
中文
日本語
한국어
Legal notice
powered by CADENAS

Manual

Top Links

Manual

4.2. Installation Link database
4.2.2. Installation von PARTsolutions parts management with PDM/ERP/PLM integration
Prev   Next

4.2.2. Installation von PARTsolutions parts management with PDM/ERP/PLM integration

The following list shows the most important steps of the installation routine:

The complete installation procedure can be found under Section 3.1.1, “Installation of Software ” in Installation Manual.

  1. The basic components for PARTsolutions are installed in the PARTsolutions programs dialog by selecting PARTsolutions parts management.

    PARTsolutions programs

    PARTsolutions programs

    This ensure the installation of the following basic modules:

  2. The modules (with respective directories, scripts, etc.) for Parts Management with ERP,PDM, PLM integration are installed in the dialog PARTsolutions parts management with PDM/ERP/PLM integration.

    PARTsolutions parts management with PDM/ERP/PLM integration

    PARTsolutions parts management with PDM/ERP/PLM integration

    • Parts management productive (without database)

      For productive operation:

      Notes on the complete installation procedure can be found in the chapter in hand Section 4.2, “Installation Link database ”.

    • Parts management demo environment (incl. SQlite)

      For users who want to test Parts Management with PDM/ERP/PLM integration, but do not want to implement it productively. Here the demo data will be installed.

      [Note] Note

      In order to display the demo data, the installation of the standards DIN, EN, ISO, etc., is required.

    • SAP interface (MM/DVS): Module to connect PARTsolutions to SAP MM.

    [Note] Note

    As soon as you have selected parts management with ERP, PDM, PLM integration, you are working with link database connection. In a standard installation without adjustments only the Database login… dialog will show up during the start of the PARTsolutions modules.

    Database login…

    Database login…

    • When using the standard SQL scripts in your installation medium the link database PLINKDB is created with the user "erpuser" (password "erpuser":

    • For the demo database PLDBDEMO, the following users are available:

      • ecat

      • location

      • mechanical

      • plant

      • product_aircraft

      • product_automotive

      • quality

      • supplier

      • release

      Password entry can be left out.

    For each of the above mentioned options PARTlinkManager (Section 4.25, “ PARTlinkManager reference ”) is installed. Furthermore under $CADENAS_SETUP\scripts you can find the directory erp.

  3. Driver for database

    ODBC/JDBC driver (Oracle JDBC, MSSQL ODBC, MSSQL JDBC) can be installed within the installation routine. Therefor, in the dialog box Database connection selection, activate the desired option.

    Database connection selection

    Database connection selection

    [Note] Note

    In a Client Server environment the ODBC driver has to be installed and set up.

    If Parts management demo environment (incl. SQlite) had been selected, you don't have to select any driver here. JDBC is installed by default.

    If Parts management productive (without database) had been selected, the standard selection is MS-SQL Server ODBC driver configuration.

    Detailed information on ODBC and JDBC can be found under Section 4.2.5, “Configure the data-source for ODBC (exemplified by MSSQL) ” and Section 4.2.6, “ JDBC driver ”.

  4. You also have the option of selection EDM/PDM/PLM integrations.

    EDM/PDM/PLM integrations selection

    EDM/PDM/PLM integrations selection

  5. For complex problems, such as for example Part reduction and Article assignment (initial filling of LinkDB) you need:

[Note] Note

More information concerning the setup-routine can be found under PARTsolutions Teilemanagement.

Prev  Up  Next
4.2.1. Hardware requirements   Home  4.2.3. Configuration of the database server connection (exemplified by MSSQL)