Rule wizard - Agent Command Status

Each time the Axeda® Platform receives a status message from an asset, it reads the execution status contained in the message and determines if there are any rules configured for that status: if there are, the rule evaluates to true and any associated actions are executed.

In the Axeda® Service application, Asset dashboard Rules module, you can view and enable or disable the rules configured for a specific asset.

Procedures from this page

From this page, you select or change the Agent commands for this rule for the selected assets, asset groups, and models.

How to select Agent command status messages

Select the type(s) of status message(s) sent from the Agent for which you want the Platform to evaluate and execute actions, as follows:

§         Successful - the Agent successfully processed an action or command sent from the Platform.

§         Error - the Agent could not process an action or command sent from the Platform.

§         Inhibited by Agent - custom functionality in the Agent prevented the Agent from uploading files specified in Upload instruction; however, Agent continued processing with next instruction.

§         Not Retrieved by Agent - The agent did not retrieve the queued command.

§         Not Processed by Agent - The agent did not process the command.

§         Permission Denied - the action or command sent to the Agent was denied based on the permission policies set on that Agent.

§         Permission Denied (Timed out) - the action or command sent to the Agent was denied because it did not receive approval from the Axeda® Policy Server for that Agent within the specified timeout period.

§         Unsupported - the Platform sent an action or command to the Agent that the Agent does not support.

Axeda Policy Server-related statuses:

§         Agent Asking Permission - the action or command to the Agent was sent to the Axeda Policy Server for that Agent, and is actively awaiting its permission.

§         Permission Denied - the action or command to the Agent was sent to the Axeda Policy Server for that Agent, and was denied permission.

§         Permission Granted - the action or command to the Agent was sent to the Axeda Policy Server for that Agent, and was granted permission to be performed.

§         Permission Denied: APM Offline - the action or command to the Agent was denied because the Axeda® Policy Server (APS) for that Agent was offline.

Script-related statuses:

§         Script in Bad State - a script is in a bad state on the asset

§         Script is running - a script is currently running on the asset

§         Sequence file was not found - the Agent cannot find the sequence file for the script it tried to run.

§         Script was not found - the Agent cannot locate the script it tried to run

§         Duplicate script names are not allowed - the Agent attempted to register a script using a script name already registered.

§         Script is not running - the Agent is currently not running the script.

§         Script contained invalid commands - the Agent tried to run a script that contains an invalid command

§         Invalid script configuration file - the Agent tried to run a script that contains improperly formatted XML commands.

§         Script has an empty name - the Agent tried to run a script defined without a script name

§         Script is waiting - the Agent is waiting to run a script

§         Script is disabled - the script to run is disabled on the Agent

§         Script is scheduled to the trigger already - the Agent tried to register a schedule for a script that already has a schedule.

§         Script is not scheduled to the trigger - the Agent has a script defined without a schedule

§         Script is not dynamic - the Agent tried to run a script that does not have an associated dynamic timer.

§         Script finished with errors - the Agent ran a script and that script finished unsuccessfully (in error).

§         Duplicate Script Name (Hidden) - the Agent tried to run two scripts of the same name

§         Error - the Agent generated an error while trying to run scripts

§         Invalid Parameters - the Agent tried to run a script that contains invalid parameters

§         Error Opening the file - the Agent generated an error while trying to open script file

§         Error Reading the file - the Agent generated an error while trying to read a script file

§         Bad file format - the script file contained an invalid format

§         Not Implemented - The agent tried to run an action that is not implemented

§         Operation timed out - The command timed out on the Agent.

§         Item is read only - The agent item is read only and cannot be written to.

§         Handle Open error - The agent generated a handle open error.

§         Conversion error - The agent determined a data conversion didn't work.

§         Type mismatch - The agent determined that a data item type was mismatched.

§         Object not found - The object specified in the agent command could not be found.

§         Invalid handle - The handle specified in the agent command was incorrect.

§         Invalid Name - The name specified in the agent command is incorrect.

§         Already Exists - The object specified by the agent command already exists.

§         Bad Quality - The agent object has bad quality (for example, no data)

§         Out of range - The values to be written to the Agent items are not within the supported value range

§         Unknown method - The Agent script contains a method not supported for the agent

§         Bad Soap Format - The command sent to the Agent was formatted incorrectly

§         Bad XML Format - The command sent to the Agent was formatted incorrectly

§         Data Item Not Found - The data item specified in the script is not found.

§         Agent is authenticating the request - The agent is awaiting asset-side authentication before performing an action.

§         Asset-side authentication failed: provider unavailable - The agent did not receive authentication as the provider (that is, RADIUS) was unavailable as the underlying authentication provider could not be contacted successfully.

§         Asset-side authentication failed: provider unknown - The agent did not receive authentication as the provider was unknown.

§         Asset-side authentication failed: access denied - The agent did not receive authentication because the authentication provider (that is, RADIUS) rejected user credentials.

§         Asset-side authentication required - The authentication provider requires that the user enter the proper username.

 

When you are finished, click Next to configure the actions for the rule, or click Finish if you are done modifying the rule. If you click Cancel and continue canceling, all information configured in this wizard is removed and a list of rules appears.