ThingWorx Software Content Management

ThingWorx Software Content Management allows you to deploy packages (ZIP and Lua scripts and other arbitrary files) to connected assets using the ThingWorx Websocket-based Edge MicroServer (WSEMS) or instruction files to connected Axeda assets using the eMessage Connector.

You can test packages and deployments before making them available in production. Search and auditing tools for packages and deployments are provided as well. For deployments, you can enable automatic retries when a deployment fails.

You can also schedule a deployment in future. There is no time limit to that schedule and the administrators could schedule to deploy an hour or two weeks from now.

Terms Used

Term	Definition
Asset/Delivery target	A remote thing (for example, a device) connected to ThingWorx that is set up to exchange data over the internet.
Package	A set of instructions sent to devices for execution.
Deployment	A process that downloads and subsequently installs or executes the contents of the package, that is, script files or instruction files, on an asset.
Event	A change in state of the value of a property defined in thing shapes, thing templates, and things.
Service	Represents the behavior of the actual thing or process that you are modeling. Services are used to create connections, define a custom action, or automate a process defined in thing shapes, thing templates, and things.

Was this helpful?