Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
Sometimes M2M Assets should poll the platform on demand, such as in the case of avoiding excessive data charges from chatty assets. A mechanism was developed that instructs the Asset to contact (poll) the platform for actions that the Asset needs to act on such as File Uploads, Set DataItem, etc.
The Shoulder Tap SMS message is the platform’s way of contacting the Asset – tapping it on the shoulder to let it know there’s a message waiting for it. The Asset responds by polling for the waiting message. This implementation in the platform provides a way to configure the Model Profile that is responsible for sending an SMS Shoulder Tap message to an M2M Asset. The Model Profile contains model-wide instructions for how and when a Shoulder Tap message should be sent.
How does it work?
The M2M asset is set not to poll the Axeda Platform for a long period, but the Enterprise user has some actions that the Asset needs to act upon such as FOTA (Firmware Over-the-Air).
How do you make Shoulder Tap work for your M2M Assets?
import com.axeda.platform.sdk.v1.services.ServiceFactory;
final ServiceFactory sFact = new ServiceFactory()
def assetId = (Long)parameters.get("assetId")
def stapService = ServiceFactory.getShoulderTapService()
stapService.sendShoulderTap( assetId )
See Extending the Axeda Platform UI - Custom Tabs and Modules for more about creating and configuring Extended UI Modules.
What about Retries?
Retry Count and Interval are configured in the Model Profile Custom Object like so:
final DeliveryMethodDescriptor dmd = new DeliveryMethodDescriptor();
fdmd.setMaxRetryCount(2);
fdmd.setRetryInterval(60);