Prerequisites: Instruction-Based Packages
Instruction-based packages allow you to create packages that define a set of instructions that the asset should perform. The eMessage Connector has built-in support for instruction-based packages. For more information, see What is the eMessage Connector? in the ThingWorx Axeda Compatibility Package Help Center.
The following list describes the prerequisites for creating an instruction-based package on an eMessage asset:
1. Set up the eMessage Connector to communicate with ThingWorx and the eMessage agents to communicate with the eMessage Connector. For more information, see the Getting Started with eMessage Connector and eMessage Agents in the ThingWorx Axeda Compatibility Package Help Center.
 |
If you are a PTC Cloud Services customer, you can work with your support representative to set up the eMessage Connector and ThingWorx.
|
2. If you migrated your asset from the Axeda Platform to ThingWorx, a Thing was automatically created for the asset in ThingWorx. This Thing represents the asset that is running the agent.
If you did not migrate your asset from the Axeda Platform to ThingWorx, create a Thing that represents the asset running the agent. For more information, see the Creating New Axeda eMessage Entities Using ThingWorx Composer in the ThingWorx Axeda Compatibility Package Help Center.
3. Ensure that the Thing that represents the asset running the agent inherits the PTC.Resource.Asset.SCMResourceThingShape and TW.RSM.SFW.ThingShape.UpdateableWithInstructions Thing Shapes. For more information, see Things and Thing Shapes in the ThingWorx Platform Help Center.
4. On the General Information tab for the Thing, in the Tags field, search for and select the PTC:Asset model tag.
5. Provide visibility permissions to the TW.RSM.RemoteServices organization by completing the following steps:
1. On the Thing, view the Permissions page. The Visibility tab is displayed by default.
2. In the Search Organizations field above the Org or Org Unit table, click 
.
.3. Select the TW.RSM.RemoteServices organization from the dropdown list.
4. Click Save, then click Done.