ProgramFiles

ProgramData

Software, data and setup locally: The option could be used for a pure single-user installation or a server installation, for example. If necessary, adjust the installation paths of CADENAS DATA, CADENAS SITE SETUP and CADENAS Pool.

Destination Folder (2nd dialog) --- In the figure CADENAS DATA is adapted as an example.

Example the start.env: The path under CADENAS_DATA has been modified.

[ENVIRONS]
CADENAS=%DirOfThisFile%
CADENAS_SETUP=C:\ProgramData\PARTsolutions\setup
CADENAS_DEFAULTUSER=$CADENAS_SETUP\user\default_user
CADENAS_SITESETUP=C:\ProgramData\PARTsolutions\sitesetup
CADENAS_USER=%UserAppData%\PARTsolutions\user
CADENAS_LICENSE=$CADENAS_SITESETUP\lic
CADENAS_POOL=C:\ProgramData\PARTsolutions\pool
CADENAS_DATA=C:\data\

Note The paths from the first and second dialogue will be held in the start.env discarded. Never change paths there, but always via the installation routine, either in the case of a Update or via "Add and remove programs" for the current installation.

Local software, data and setup from an existing server [Software Local, data and setup from an existing server]: If a server installation has been carried out and the directories CADENAS_DATA and CADENAS_SETUP have been released there, a client can be installed where the software is located locally but the other directories are referenced.

Note When installing the client, the server MUST already be running and fully configured.

Destination Folder (2nd dialog)

Local software, data and setup from the app server [Software Local, data and setup from the app server]: Use this option for a client installation.

CADENAS_DATA and CADENAS_SETUP are configured via the app server, so that only the app server URL has to be entered. Adjust the installation path of CADENAS Pool if necessary.

Note It is essential that you observe the above rules or consult the Consulting Team. Cadenas Pool must never be below Cadenas DATA!

Note When installing the client the server MUST already be running and completely be configured.

Destination Folder (2nd dialog)

Applications

Mechanical Integrations

Activate the integrations that you have purchased.

Note CAD systems for which an integration is selected should already be available at this point so that automatic registration works.

Note For a server-client installation, Integrations have ALWAYS to be installed on the server AND on the client, otherwise the required configuration files are missing on the server.

PDM Integrations

Activate the integrations that you have purchased.

Note For a server-client installation, Integrations have ALWAYS to be installed on the server AND on the client, otherwise the required configuration files are missing on the server.

Offline Interfaces

Activate the integrations that you have purchased.

BIM Integrations:

Activate the integrations that you have purchased.

Tools: Contains database scripts required for setting up the ERP environment and vbs files for special tasks.

You can also use the scripts to set different rights for the standard user ("erpuser") and the admin user ("psadmin").

Example from mysql:

CREATE USER IF NOT EXISTS 'erpuser' IDENTIFIED WITH mysql_native_password BY 'erpuser';

GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.ERPTABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.LINKTABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.CLASSFOLDERTABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.CLASSTABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.PRJTABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.PLMTABLE2 to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.PLM_HIERARCHY to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.CNSSEQ to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.TREETABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.LOGTABLE to erpuser;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.EXPORTTABLE to erpuser;

Der Admin muss auch Spalten-Definitionen in der ERPTABLE ändern können.

CREATE USER IF NOT EXISTS 'psadmin' IDENTIFIED WITH mysql_native_password BY 'psadmin';

GRANT ALTER, SELECT, INSERT, UPDATE, DELETE ON partlinkdb.ERPTABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.LINKTABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.CLASSFOLDERTABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.CLASSTABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.PRJTABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.PLMTABLE2 to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.PLM_HIERARCHY to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.CNSSEQ to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.TREETABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.LOGTABLE to psadmin;
GRANT SELECT, INSERT, UPDATE, DELETE ON partlinkdb.EXPORTTABLE to psadmin;

In PARTadmin, under Database connection, the connection can be checked.

Details on all systems can be found in the readme files of the individual directories.

Activate interfaces on the client: The option is activated by default. If you deactivate the option, you have to activate the desired interfaces manually later in PARTadmin under category CAD integration. See also Section 1.3.2, “ CAD integration ” in PARTsolutions Administration - Manual .

Category "CAD integration [CAD integration] "

Batch scripts are available at ...\software\install\scriptsthat can be executed locally at any time to activate/deactivate all interfaces. These can also be used administratively in the course of software distribution with deployment.

After the installation is complete, the corresponding start menu entries are displayed. The Activate Interfaces / Deactivate Interfaces links start the batch scripts mentioned above.

Start menu entries