You may need to start DTP services after a new installation, migration, or upgrade. In this section:
You can easily use the Windows Start menu to start and stop DTP services:
You can also use Windows Services to start and stop DTP services, as well as change startup from automatic to manual.
See the documentation for your version of Windows for details.
There are a few ways you can start DTP and its related services:
In addition to starting and stopping DTP and its related services, the dtpconsole.sh script provides interactive management capabilities, such as configuring database connections.
After the initial startup and configuration, you can start DTP applications using the dedicated scripts. The scripts are non-interactive and suitable for starting and stopping DTP services in automated environments. Please note that automation scripts are not compatible with crontab functionality. If you are using crontab functionality, use the dtpconsole.sh script to start and stop DTP.
Use the dtp.sh script located in the <DTP_INSTALL>/bin directory. You can specify the following commands:
dtp.sh run | Run the DTP server process in the current window. |
dtp.sh start | Start DTP server as a background process. |
dtp.sh stop | Stop DTP server. |
dtp.sh status | Display the current status of DTP server. |
dtp.sh help | Print the help to the console. |
Use the datacollector.sh script located in the <DTP_INSTALL>/bin directory. You can specify the following commands:
datacollector.sh run | Run the Data Collector process in the current window. |
datacollector.sh start | Start Data Collector as a background process. |
datacollector.sh stop | Stop Data Collector. |
datacollector.sh status | Display the current status of Data Collector. |
datacollector.sh help | Print the help to the console. |
Use the dtpservices.sh script located in the <DTP_INSTALL>/dtpservices directory. You can specify the following commands:
dtpservices.sh run | Run the Enterprise Pack process in the current window. |
dtpservices.sh start | Start Enterprise Pack as a background process. |
dtpservices.sh stop | Stop Enterprise Pack. |
dtpservices.sh status | Display the current status of Enterprise Pack. |
dtpservices.sh reset-server | Reset the DTP server connection settings for Enterprise Pack to the defaults. See Server Settings for information about the server configuration. |
dtpservices.sh help | Print the help to the console. |
In some unexpected instances, you may see the following message when running the "Time out on DTP Enterprise Pack process termination. Please kill all processes manually. (Refer to the documentation)" This message only triggers if any of the children processes of the main DTP Enterprise Pack application (typically one of the service processes) started but was not killed completely. These processes must be terminated before starting DTP Enterprise Pack again.
|
As alternative to using the dtpconsole.sh script, the automation scripts, or crontab to manage DTP, it is possible to configure custom systemd services on Linux systems that support systemd. Before doing this, ensure that the DTP services are not running. Please note that these systemd services are not compatible with crontab functionality. If you are using crontab functionality, use the dtpconsole.sh script to start and stop DTP.
To use systemd services:
<servicefilename>.service
./etc/systemd/system
directory.Below are some sample systemd services for each of the DTP services that can be used in the files you created in the above steps. It is important to ensure that the User and Group for each service is consistent with the DTP installation owner. Additionally, the "ExecStart" and "ExecStop" options should correspond to your DTP installation location.
For DTP Server:
[Unit] Description=Parasoft DTP Server # Wait for the network services to be started first Wants=network.target After=network.target # When the database is MySQL and on the local machine... # Wants=mysql.service # After=mysql.service [Service] # User/Group should be consistent with DTP installation owner User=devtest Group=devtest Type=simple ExecStart=/home/devtest/parasoft/dtp/bin/dtp.sh run ExecStop=/home/devtest/parasoft/dtp/bin/dtp.sh stop # Set maximum file descriptor limit to max LimitNOFILE=65536 SuccessExitStatus=143 SIGKILL Restart=on-failure [Install] WantedBy=multi-user.target |
For DTP Data Collector:
[Unit] Description=Parasoft DTP Data Collector Service # Wait for the network services to be started first Wants=network.target After=network.target # When the database is MySQL and on the local machine... # Wants=mysql.service # After=mysql.service [Service] # User/Group should be consistent with DTP installation owner User=devtest Group=devtest Type=simple ExecStart=/home/devtest/parasoft/dtp/bin/datacollector.sh run ExecStop=/home/devtest/parasoft/dtp/bin/datacollector.sh stop # Set maximum file descriptor limit to max LimitNOFILE=65536 SuccessExitStatus=143 SIGKILL Restart=on-failure [Install] WantedBy=multi-user.target |
For DTP Enterprise Pack (if installed):
[Unit] Description=Parasoft DTP Enterprise Pack Service # Wait for the network services to be started first Wants=network.target After=network.target [Service] # User/Group should be consistent with DTP installation owner User=devtest Group=devtest Type=simple ExecStart=/home/devtest/parasoft/dtp/dtpservices/dtpservices.sh run ExecStop=/home/devtest/parasoft/dtp/dtpservices/dtpservices.sh stop # Set maximum file descriptor limit to max LimitNOFILE=65536 Restart=on-failure [Install] WantedBy=multi-user.target |
After the services have been configured, you can enable them to start automatically when the machine is restarted. For each service file you created, run the following:
sudo systemctl enable <servicefilename> |
Once you have enabled all the services, reload the systemd manager configuration:
sudo systemctl daemon-reload |
Then for each service you created, run the following to start them:
sudo systemctl start <servicefilename> |
To check the status for a service:
sudo systemctl status <servicefilename> |
To stop a service:
sudo systemctl stop <servicefilename> |