Deployment
Complete the following steps to update the deployment configuration:
 |
For optimum results, we recommend that you adhere to the maximum recommended values.
|
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.
|
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 instruction-based packages, the values of Concurrent Notifications and Max Active Delivery Targets are applicable.
|
Common Timeout Configuration Parameters for File-Based and Instruction-Based Packages
|
|
When a timeout occurs, the operation moves to the Aborted or Retry state.
|
|
Parameter
|
Description
|
Default Value
|
|---|---|---|
|
Pending Timeout (secs)
|
Pending timeout in seconds.
|
86400
|
|
Installation Timeout (secs)
|
Installation timeout in seconds.
|
3600
|
|
Pending Retry Timeout (secs)
|
Pending retry timeout in seconds.
|
3600
|
|
|
While File Transfer is active a Deployment in Installing state will not timeout.
|
Timeout Configuration Parameters for File-Based Packages
|
|
When a timeout occurs, the operation moves to the Aborted or Retry state.
|
|
Parameter
|
Description
|
Default Value (in seconds)
|
|---|---|---|
|
Notification Timeout (secs)
|
Notification timeout.
|
120
|
|
Notified Timeout (secs)
|
Notified timeout for only those delivery targets whose scheduled download dates have passed.
|
60
|
|
Scheduling Timeout (secs)
|
Scheduling timeout.
|
60
|
|
Download Timeout (secs)
|
Download timeout.
|
3600
|
|
Downloaded Timeout (secs)
|
Downloaded timeout for only those delivery targets whose scheduled install dates have passed.
|
120
|
|
|
While File Transfer is active a Deployment in Downloadingstate will not timeout.
|
Configuration Parameters for Instruction-Based Packages
|
|
When a timeout occurs, the operation moves to the Aborted or Retry state.
|
|
Parameter
|
Description
|
Default Value (in sec)
|
||
|---|---|---|---|---|
|
Instructions Received Timeout (secs)
|
Instructions received timeout.
|
3600
|
||
|
Sending Instructions Timeout (secs)
|
Sending instructions timeout .
|
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
|
• When the check box is selected: The package deployment is retried regardless of whether a target asset is connected or not. If the target asset comes online within the time frame determined by the auto-retry rate and the number of configured retry attempts, then the deployment will proceed. Otherwise, the deployment to the asset will time out and be aborted.
• When the check box is not selected: The deployment to the target asset will abort immediately if the asset is disconnected. The retry attempts will not occur.
|
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 count field in the Auto-Retry section on the Create One Time Deployment page.
|
5
|
||||
|
Auto-Retry Rate (secs)
|
The auto-retry timer interval in seconds. The retry process is initiated by this timer, which fires at the rate specified here. For example, the default rate is 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.
You can specify a value between 15 seconds and 1000000 seconds. If you specify an invalid value, then the closest valid value is considered.
|
30
|
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
|