A Communications or Model Profile provides the communications and capabilities information for M2M models. These models may be assets running an agent written using the Axeda Wireless Protocol (AWP) or they may be devices with their own protocol that communicate with the Axeda® Platform through the Axeda Codec Server. The Axeda® Platform needs the communications information to deliver messages to the devices. The profile contains a DeliveryMethodDescriptor that tells the Axeda® Platform how to deliver a message, including
o The Codec for encoding and decoding messages
o The DeliveryMethod, which specifies how to deliver the message. For example, Queued or ShoulderTap.
o The Transport, which specifies the name of the transport for delivery (TCP, e-mail, UDP, SMS).
o The timeout and ordinal fields for configuring how the Axeda® Platform chooses and uses this DeliveryMethodDescriptor.
For assets running AWP agents, the profile also provides the threshold rules capabilities for the model. The threshold rules capabilities specify the algorithms and actions supported by the asset. The Axeda Platform uses the specified algorithms and actions when constructing the DeviceRuleSet messages for programming the asset-based rules executable on the asset itself. Refer to the Axeda® Platform Web Services Reference for more information on threshold rules.
Notes: For
contactable devices that communicate through the Axeda Codec Server, version
2.0.0.0, threshold rules are not supported.
If a profile does not contain a DeliveryMethodDescriptor or
if no profile exists for an asset, the server uses the default set of
DeliveryMethodDescriptors to deliver messages to the asset. The default
method is to use the eMessage (SOAP) protocol, which is appropriate for
assets running the Axeda Gateway and Connector Agents, Axeda Agent Embedded,
and Axeda IDM Agents.
A model can have at most one profile, but you can associate a single profile
with more than one model.
If a model profile that was deleted by a Web service still appears in the
Applications, it may be that the cache needs to be cleared.
The name of a model profile does not need to match the name of a model,
but the name of the model profile must be unique in the Axeda® Platform.
Using Axeda Web services you can create, update, delete, or find model profiles. You can search by name (exact name search) or by search criteria (wildcard lookup by name). Existing privileges for similar operations on Models determine if a user can perform these operations on model profiles. You can obtain lists of the supported Codecs, Transports, and delivery methods. You can also list the supported threshold algorithm and action capabilities.
For release 2.0.0.0 of the Axeda Codec Server, an example Groovy script is provided with the Axeda Codec Developer's Kit. You can register this Groovy script as a custom object in the Axeda® Platform and then run it to create one or more Model Profiles for the Models that the Axeda Platform will monitor. Refer to the Axeda® Codec Developer's Kit Guide for more information..