Software Content Management
From Software Content Management, you can create software packages for immediate deployment, or for deployment at a scheduled future time. You can also test packages and deployments before making them available in production. Search and auditing tools for packages and deployments are provided as well.
For more information, see ThingWorx Software Content Management in the ThingWorx Utilities Help Center.
 | The Software Content Management tile is visible only with an Enterprise license. |
Add the Software Content Management Tile to the Console
To add the Software Content Management tile to the ThingWorx Apps console, import the optional ThingWorx-Software-Content-Management-<version> extension. For more information, see Import Optional Extensions.
Adding Permissions to View the Software Content Management Tile
To enable the users who belong to the Controls Engineer, Maintenance Manager, and Maintenance Engineer roles to use Software Content Management, complete the following steps:
1. In ThingWorx Composer, open the TW.UTL.UtilSetupHelper resource.
2. Under Services, execute the AdjustUtilitiesVisibility service with the following value for the orgOrOrgUnit input parameter: PTC.Factory.MachineVisibility:AssetPerformance. The service has completed successfully when "No results" displays in the service output pane.
3. Navigate to > in the left pane.
◦ Add the Controls Engineer user group to the TW.RSM.Admin user group for administrative access.
◦ Add the Maintenance Manager and Maintenance Engineer user groups to the TW.RSM.RemoteServices user group so they can access the remote access actions such as File Transfer, Deployments, and Remote Connections.
Configure Assets for Use in Software Content Management
For an asset to be available in Software Content Management, complete the following steps:
1. In ThingWorx Composer, navigate to and edit the asset. The asset can be either an Asset or KEPServerEX-Based Asset, or a custom equipment type that is configured to appear in Asset Advisor.
2. Under General Information, add the following Implemented Shapes:
◦ PTC.Asset.ManagedAsset
◦ TW.RSM.SFW.ThingShape.Updateable
◦ PTC.Resource.Asset.SCMResourceThingShape
3. Add PTC:AssetType to Tags.
4. Click Save.
For more information on using your configured assets in Software Content Management, see Create a File-based Package in the ThingWorx Utilities Help Center.
Configuring the File Transfer History Stream
The ThingWorx Apps use the stream PTC.SCA.SCO.AssetRemoting.FileTransferHistoryStream to record file transfer events, while Software Content Management uses TW.RSM.FileTransferHistoryStream. To ensure that file transfer events are properly captured in ThingWorx Apps, complete the following steps in ThingWorx Composer:
• Edit the TW.RSM.FileTransferHelper Thing. Under Configuration, set the File History Stream Thing to PTC.SCA.SCO.AssetRemoting.FileTransferHistoryStream. Click Save.
• Copy the data from the TW.RSM.FileTransferHistoryStream Thing to the PTC.SCA.SCO.AssetRemoting.FileTransferHistoryStream Thing.
◦ If you have less than fifty thousand rows of data, refer to the instructions found at the following URL: How to copy entries from one Stream to other Stream.
◦ If you have more than fifty thousand rows of data, use a native SQL script appropriate for your ThingWorx database, similar to the following example. Back up your ThingWorx database before running the script.
INSERT INTO stream (entity_id,source_id,time,field_values,location,source_type,tags)
SELECT 'PTC.SCA.SCO.AssetRemoting.FileTransferHistoryStream',source_id,time,field_values,location,source_type,tags
FROM <your_thingworx_schema_name>.stream
WHERE entity_id= 'TW.RSM.FileTransferHistoryStream'
SELECT 'PTC.SCA.SCO.AssetRemoting.FileTransferHistoryStream',source_id,time,field_values,location,source_type,tags
FROM <your_thingworx_schema_name>.stream
WHERE entity_id= 'TW.RSM.FileTransferHistoryStream'