In this chapter:
Enterprise Pack is a framework for extending Parasoft DTP functionality. The primary application in Enterprise Pack is Extension Designer, which enables you to create custom extensions for DTP, as well as deploy Parasoft's pre-made extensions, to perform additional post-analysis analysis. Extensions can produce custom reports for compliance initiatives, trigger processes in third-party systems, and anything else you need in order to deliver software that meets your business objectives.
Enterprise Pack is installed with Parasoft DTP. Refer to New DTP Installations for details.
Depending on the version you are upgrading from, the DTP installer will automatically back up and restore DTP Enterprise Pack as part of the upgrade process. Refer to the Upgrading section for details.
Choose Extension Designer from the settings menu (gear icon) to access Extension Designer interfaces.
Alternatively, you can enter the host and port number in a browser address bar to open Enterprise Pack applications:
http://<host>:8314
If SSL is enabled, the protocol will be https. The actual port number depends on the availability of the port. See Requirements and Support.
The installation process automatically connects Enterprise Pack to DTP using default port settings, but you can manually configure Extension Designer for use within your DTP environment, including:
From Extension Designer, choose Settings from the gear icon menu to access the configuration page.
See DTP Enterprise Pack Configuration for details.
The following terms describe components and concepts associated with DTP Enterprise Pack.
In the context of this technology, a service is a group of one or more flows or artifacts that can perform specialized tasks. Services can provide custom REST endpoints, custom widgets for DTP, trigger actions in third-party system, etc.
Services in DTP Enterprise Pack should not be confused with web services or components that are more generally described as services.
Flows are one or more nodes that can perform specialized tasks. Flows can be grouped into services to more evenly distribute data processing across endpoints, which results in more stable execution.
Nodes are the basic building blocks for creating flows and services that can perform specialized tasks.
Artifacts are complete services or flows that can be downloaded and installed from the Parasoft customer portal. See Downloading and Installing Artifacts.
If you want to perform custom calculations within the context of a flows or services, you can create a model, which defines the template for the data used to perform the specific type of calculation. Specific instances of a model are called profiles, which can be used in a flow to carry out the custom calculation. See Working with Model Profiles for additional information.
Each instance of a model is a profile. Profiles must be paired with flows that can consume the data associated with the specific type of calculation. See Working with Model Profiles for additional information.
The following configuration options are also available.
You can configure the DTP Enterprise Pack database to archive log files, which eases system administration resources. The DTP Enterprise Pack startup process enables the ability to rotate database logs, but your system administrator must perform additional tasks for the database to begin archiving logs. In addition, the process is specific to the operating system running Enterprise Pack.
The logrotate
command configures and starts log rotation using a configuration file. The following snippet is an example configuration file–your actual configuration file should be written according to your organization's needs:
"<DTP_DATA_DIR>/logs/mongodb.log" { size 5M missingok rotate 5 compress delaycompress } |
logrotate -v --state ~/parasoft/dtpservices/logs/status.tmp ~<path to your configuration file>
status.tmp
is not required; you can point to any location where you have write permission. The logrotate
command is not native on Windows. You can download a utility that provides this functionality (e.g., LogRotateWin from https://sourceforge.net/projects/logrotatewin/). A configuration file is also required to configure and start rotation. The following snippet is an example configuration file–your actual configuration file should be written according to your organization's needs:
"<DTP_DATA_DIR>/logs/mongodb.log" { size 5M missingok rotate 5 compress delaycompress postrotate "<DTP_INSTALL>\dtpservices\mongodb\bin\mongo.exe" --port 8316 --eval "db.runCommand('logRotate')" admin endscript } |
LogRotateWin
.C:\Program Files (x86)\Ken Salter\LogRotate>logrotate.exe -v --state "C:\temp\status.tmp" <path to your configuration file>
status.tmp
is not required; you can point to any location where you have write permission. You can add a custom logo to the Enterprise Pack header. To add a custom logo, replace the png at /public/lib/custom-logo.png with your company logo.
The image file must be named "custom-logo.png". The dimensions of the image container is 300px by 35px.