Manage the PDM server

 

 

 

 

 

 

IT IS IMPERATIVE TO REGULARLY BACKUP THE DATABASE, VAULT AND WORKSPACES OF EACH CLIENT STATION ( if they are not centralized). ALL BACKUP INFORMATION IS INDICATED IN THE INSTALLATION GUIDE (DATA/BACKUP PROCEDURE CHAPTER ).

FOR SECURITY REASONS, THESE BACKUPS HAVE TO BE SAVED ON ANOTHER DISK OR BETTER, ON ANOTHER SERVER.

 

 

This dialog allows to start the PDM server. It also allows to know the status of this service and to configure it (select the SQL server, the name of the database to connect on, define the vault location, ...)

It is composed of several sections:

 

 

 

This section allows to know the status of the PDM service and gives some informations in case of troubles.

 

The icon is situated beside the Windows clock and provides information on the service state.

 

The service is started and is operational.

The service is starting.

There is a problem. The service is not operational. Check information in the status section.

The service is stopped.

 

This service can also be accessed from the Windows services console (services.msc command in the Windows Run menu).

After the installation of TopSolid'Pdm Server, an icon is displayed on the desktop. It allows to run the TopSolid'Pdm Server Service Administration application.

After the installation of TopSolid, for a use in Local Pdm server mode, this application is ran when TopSolid is started, or can be started independently by double-clicking on c:\Program Files\TOPSOLID\TopSolid 7\bin\TopSolid.Pdm.ServerServiceAdmin.exe.

 

 

This service must be launched to be able to use TopSolid in client/server mode.

 

 

 

 

 

This section allows to select the Pdm server execution mode:

 

  • SQL server: It is the classic mode for a use in client/server mode on a local network.

 

 

  • Primary Pdm Server: This Pdm server is the primary Pdm server in the case of a multisite usage with replication. An installation of at least a SQL 2014 Standard edition is required. The SQL replication functionality has to be activated, and so on. For all information, (utility, how it works, installation, ...) please refer to the installation guide, chapter multisite.

 

 

An additional specific license is required.

 

 

 

  • Secondary Pdm Server: This Pdm server is the secondary Pdm server in the case of a multisite usage with replication. It is a pdm server installed on a distant site. For all information, (utility, how it works, installation, ...) please refer to the installation guide, chapter multisite.

 

 

An additional specific license is required.

 

 

 

  • Files server only: It is possible to install the TopSolid'Pdm server on two different servers. One will be used as Pdm Server, and the other as File server. In this case, on the server PDM (with the database) you will to add the Pdm Files server, by using the Add, Modify or Remove the Files server by entering its ip address or its name and its listening port.

 

 

 

This section allows to select the SQL instance to use (except for the TopSolid'pdm Local Server which can only be .\SQLTOPSOLID) and the database.

For the primary Pdm server, you will have to select a snapshot folder, when for the secondary one, you will have to fill the primary server.

 

 

Pdm Server mode:

 

  • SQLServer:  (Not available for TopSolid'pdm Local Server). Select in the drop down list, the SQL server and its instance to use. By default, it is .\SQLTOSPOLID for a client/server or a local server installation.

It is also possible to select another SQL server by clicking Browse... in the drop-down list. In this case, the SQL server has to be set as explained in the Installation guide (Chapter: SQL server is not on the same server than TopSolid'Pdm Server).

After having selected the SQL server, click Apply...

  • Database: Select in the drop down list, the database to use. By default, it is PdmServer for a client/server or LocalPdmServer for a local server installation.

If the database doesn't exist, it will be automatically created during the first start of the service. If it exists, TopSolid'Pdm server will use it.

After having selected the database, click Apply...

 

 

Primary Pdm Server mode:

 

  • SQL Server: Select in the drop down list, the SQL server and its instance to use. By default, it is .\SQLTOSPOLID. It is also possible to select another SQL server by clicking Browse... in the drop-down list. In this case, the SQL server has to be set as explained in the Installation guide (Chapter: SQL server is not on the same server than TopSolid'Pdm Server).

After having selected the SQL server, click Apply...

 

 

The installed SQL server edition must be at least SQL 2014 Standard or higher. The SQL Replication has to be activated. its installation has to be done by following the multisite documentation information.

 

 

  • Database: Select in the drop down list, the database to use. By default, it is PrimaryPdmServer for a client/server or LocalPdmServer for a local server installation.

If the database doesn't exist, it will be automatically created during the first start of the service. If it exists, TopSolid'Pdm server will use it.

After having selected the database, click Apply...

 

  • Snapshot folder: This folder contains temporary files to be able to create the first database replication.

 

 

Secondary Pdm Server mode:

 

  • Primary server: Allows to enter the primary connection information.

    • Address: Enter the primary server ip address.

    • Port: Enter the port of the primary server. (8086 by default).

 

  • Secondary server:

    • SQL Server: Select in the drop down list, the SQL server and its instance to use. By default, it is .\SQLTOSPOLID. It is also possible to select another SQL server by clicking Browse... in the drop-down list. In this case, the SQL server has to be set as explained in the Installation guide (Chapter: SQL server is not on the same server than TopSolid'Pdm Server).

After having selected the SQL server, click Apply...

 

    • Database: Select in the drop down list, the database to use. By default, it is SecondaryPdmServer. If the database doesn't exist, it will be automatically created during the first start of the service. If it exists, TopSolid'Pdm server will use it.

After having selected the database, click Apply...

 

  • File cache: This folder allows to avoid to download several times same files from the primary site. When a TopSolid client has downloaded it for the first time, all other users will use this file from the local cache.

 

  

 

The only way to create a database is to start the TopSolid'Pdm Server service.

 

 

 

 

 

This section allows to Add, Modify or Remove vaults, which can be with the TCP or the FTP protocol. (With TopSolid'Pdm Local Server, only the vault path on a local disk can be defined).

 

Defined vaults are listed and their location indicated.

 

 

Vaults can only be configured if the service is started.

 

 

 

 

 

This section displays all secondary servers of this primary server. On the right, each secondary server indicates its status. (started, stopped, ....)

 

 

 

This section allows to Start, Restart and Stop the TopSolid'Pdm server service or to access to the Advanced management.

 

  • Start:

This command allows you to startup the PDM server.

 

  • Stop:

This command allows you to stop the PDM server.

 

  • Restart:

This command allows you to stop and restart the PDM server. After the restart, the icon's check mark is green.

 

Listening ports:

When using the PDM in client/server mode, the communication between clients and server is done through the network via listening ports. These ports have to be opened inlet and outlet on each server and clients.

 

8086: The PDM server's main listening port. It is on this port that the client connects to the server. If it is changed, it must be on the server and on each client. This port is also used by the file server.

 

In the case of the TopSolid'Pdm Local Server use, the listening port by default is 8006.

 

 

  • It is important to leave this port defined above open in the firewall.

  • When the service is first started up, the database is created depending on the connection string settings.