ThingWorx Utilities Administration > Resource Provider and Asset Configuration
Resource Provider and Asset Configuration
Resource Providers
Resource providers are used to find assets in the asset searches for ThingWorx Software Content Management. However, a resource provider can be used to search for other resources that you do not want to show up in the searches. The Role:Ownables and Role:Operatable tags are used to search for resources/assets in ThingWorx Software Content Management.
You will also want to consider which resource providers to associate with your assets. This association is done using a resource thing shape that is configured on the resource provider and then added to either a thing or a thing template for a collection of things.
* 
It is recommended that an asset only be assigned to one resource provider to avoid duplication in the search results.
If you are only using thing-based assets, use PTC.Resource.Asset.SCMResourceProvider for ThingWorx Software Content Management assets. It is configured with the PTC.Resource.Asset.SCMResourceThingShape resource thing shape. It has both the Role:Ownables and Role:Operatable tags, and the assets can be searched for in ThingWorx Software Content Management.
If you plan to use the out-of-the-box resource providers, several things should be taken into consideration to help you best configure your assets:
Selecting the appropriate resource thing shape: If you intend to use ThingWorx Software Content Management to deploy software to your assets, then use PTC.Resource.Asset.SCMResourceThingShape
Where to configure the resource thing shape: Is there a possibility of reassigning an asset to a different resource provider?
* 
This is important because the migration cost of moving things from one resource provider to another could be significant depending on the number of assets.
If yes, add the resource thing shape to your assets (things).
If no, add the resource thing shape to your asset types (thing templates).
Assets
A non-administrator user can deploy packages to only those assets (things) for which he has visibility permissions in ThingWorx.
Was this helpful?