Use Case: Software Content Management
Complete the following steps to create, publish, and deploy a package:
1. In ThingWorx Software Content Management, under Packages, click > .
2. Select the root directory in the
Directory Structure (/), and then click
.
3. Click Choose File, and navigate to the your ThingWorxStorage folder and select sample_package.zip. Click Upload.
4. Enter the following information for the package:
◦ Package Name—sample
◦ Version—1.0
◦ Description—sample description
◦ Asset Type—Select the asset type for the package creation.
5. Select a ZIP file and enter sample.lua in the Instruction File Name in Zip File field. Click Save.
6. The Create Test Deployment page appears. You can continue with the test deployment or publish the package by selecting > .
7. Review the information, and click Publish. When prompted to confirm, click Yes.
8. Under Deployments, select > .
9. Select sample from the Packages table and click Next.
10. On the > page, enter a deployment name description and priority for the deployment. If auto-retry for deployments is disabled, no other field is available. However, if auto-retry is enabled, you will see the section, Auto Retry Settings. Enter the settings you want to use for auto retry. Then, click Next.
11. Under
Included Assets, select an asset search from the drop-down menu and click
.
12. Click Next.
13. On the Notify page, select the Enable error notification and Notify people below when deployment to all assets has finished check boxes.
14. In the
Notify User and
Notify User Groups sections, select users or user groups by searching for users, selecting them and clicking
.
15. In the
Notify These Email Addresses section, enter your email and click
. Click
Next.
16. On the Deploy page, review all of the deployment information, make any edits if necessary, and click Deploy.
17. The Track Deployment By Package page appears; from here, you can monitor the status of the deployment.
18. Click Home to view the deployments dashboard.
19. Under
Compliance, purge the deployment. For more information, see
Compliance.