Deployment
You can update deployment settings for performance, file-based package time-outs, instruction-based package time-outs, and auto-retry. Complete the following steps to update the deployment configuration:
1. From the left pane in ThingWorx Software Content Management, under the Administration section, navigate to > .
The Deployment Configuration page appears.
2. Under the Performance Configuration, Timeout Configuration, Instruction Based Configuration, Auto-Retry, Upload sections, enter appropriate value in the fields that you want to update, and click Save.
Performance Configuration Parameters for Deployment
|
Parameter
|
Description
|
Default Value
|
|
Concurrent Downloads
|
Maximum number of delivery targets for file-based packages that can download a file simultaneously.
|
|
This parameter does not apply to instruction-based packages. This setting does not have any impact on the downloads started by the Download instruction in instruction-based packages.
|
|
|
The number of concurrent deployments must not exceed the value of the Max Threads Allocated to File Transfer Pool setting on the Configuration page of the FileTransferSubsystem in ThingWorx Composer. It is recommended that you set the value of Max Threads Allocated to File Transfer Pool to 60.
|
|
50
|
|
Concurrent Notifications
|
Maximum number of delivery targets that can transition from the Pending state to the Notifying state for file-based packages and from the Pending state to the Sending Instructions state for instruction-based packages simultaneously.
|
50
|
|
Max Active Delivery Targets
|
Maximum number of delivery targets for all packages that can be allowed in the active state.
The following states are active:
• Notifying
• Notified
• Scheduled
• Downloading
• Downloaded
• Installing
• Sending Instructions
• Instructions Received
|
50
|
|
|
• For file-based packages, the values of Concurrent Downloads, Max Active Delivery Targets and Max Threads Allocated to File Transfer Pool setting of the FileTransferSubsystem subsystem are applicable.
• For instruction-based packages, the values of Concurrent Notifications and Max Active Delivery Targets are applicable.
|
Time-out Configuration Parameters for File-based Packages
|
|
When a time-out occurs, the operation moves to the Aborted state.
|
|
Parameter
|
Description
|
Default Value
|
|
Pending Timeout (secs)
|
Pending time-out in seconds.
|
86400
|
|
Notification Timeout (secs)
|
Notification time-out in seconds.
|
120
|
|
Notified Timeout (secs)
|
Notified time-out in seconds for only those delivery targets whose scheduled download dates have passed.
|
60
|
|
Scheduling Timeout (secs)
|
Scheduling time-out in seconds.
|
60
|
|
Download Timeout (secs)
|
Download time-out in seconds.
|
3600
|
|
Downloaded Timeout (secs)
|
Downloaded time-out for only those delivery targets whose scheduled install dates have passed.
|
120
|
|
Installation Timeout (secs)
|
Installation time-out in seconds.
|
3600
|
|
Pending Retry Timeout (secs)
|
Pending retry time-out in seconds.
|
60
|
Configuration Parameters for Instruction-based Packages
|
|
When a time-out occurs, the operation moves to the Aborted state.
|
|
Parameter
|
Description
|
Default Value
|
|
Instructions Received Timeout (secs)
|
Instructions received time-out in seconds.
|
3600
|
|
Sending Instructions Timeout (secs)
|
Sending instructions time-out in seconds.
|
|
The value of the Sending Instructions Timeout (secs) parameter must be greater than the time required for an asset to go missing; that is, the value of the isReporting property to be equal to false.
|
|
86400
|
|
Download Target Repository
|
Configure a default repository for instruction-based package downloads. Specify any ThingWorx repository that implements the FileRepository Thing Template.
|
TW.RSM.Thing.FileRepository
|
Configuration Parameters for Auto-Retry
|
Parameter
|
Description
|
Default Value
|
|
Enabled
|
Select this check box to enable automatic retries of package deployment. To disable this feature, clear the check box.
|
true
|
|
Auto-Retry For Disconnected Targets
|
Select this check box if you want the package deployment to be retried without checking whether a target asset is connected.
If you clear this check box, the auto-retry mechanism checks whether a target asset is connected. If the target asset is disconnected, the deployment is not retried for that particular asset.
|
true
|
|
Max Auto-Retries Per Interval
|
The maximum number of retry delivery targets (assets) when auto-retry begins. If this maximum is set too high, performance can be adversely affected.
|
500
|
|
Default Max Auto-Retries
|
The global default value used by the ThingWorx Utilities user interface to display a default maximum number of retries for a deployment.
For example, this value appears in the Auto-Retry Count field on the Create One Time Deployment page.
|
5
|
|
Auto-Retry Rate (ms)
|
The number of milliseconds for the interval of the Auto-Retry timer. The retry process is initiated by this timer, which fires at the rate specified here. For example, the default rate is every 30,000 ms, or every 30 seconds. This means that the timer triggers the auto-retry process to retry eligible deployments for eligible delivery targets (assets) every 30 seconds.
|
30000
|
Configuration Parameter for Upload
|
Parameter
|
Description
|
Default Value
|
|
Overall Upload Checksum Required
|
Specifies whether the platform should validate the checksum of the uploaded file.
|
false
|
