SCM Upload Instructions
The eMessage Connector supports SCM packages with Upload instructions. This functionality is similar to that of Axeda Platform. This functionality is added to Things through a Data Shape on Thing Templates for eMessage Agents., called SCM.API.DataShape.Instruction.Upload.
 |
The ThingWorx SCM Upload instruction does not support absolute paths. Keep this in mind when specifying paths for an Upload instruction.
|
The following table lists and briefly describes the parameters for an Upload instruction that are defined in this Data Shape. Note that all of these parameters are required for an Upload instruction.
|
Parameter
|
Description
|
Example
|
|---|---|---|
|
RepositoryName
|
Specifies the name of the repository on the ThingWorx Platform to which the file will be uploaded. This parameter is of ThingWorx Base Type STRING. There is no default value.
|
SystemRepository
|
|
DestinationPath
|
Specifies where to store the uploaded file within the repository. The file will be placed in a Thing-specific directory under this path. This parameter is of Base Type STRING and its default setting is /.
Do NOT use an absolute path.
|
/
|
|
SourceFiles
|
Specifies one or more file entries in an INFOTABLE. There is no default setting.
|
Refer to the section, Setting the SourceFiles Parameter.
|
Setting the SourceFiles Parameter
The SourceFiles parameter uses the GenericStringList Data Shape, which has a single required field, item.
The following table explains this parameter:
|
Parameter
|
Description
|
Example
|
|---|---|---|
|
item
|
Relative path and name of each file to be uploaded. Note that wild card characters (*,?) are allowed for Linux agents. For agents running on Windows, the ? character has the same effect as the * character. Do NOT use an absolute path.
|
..\logs*.log
|