Extreme API with Python

Extreme API with Python
Page | 70
Part no.9036931-00 Rev AA February 2021
workflowUpdatedBy
workflowexecutionId
workflowUpdatedDateTime
workflowDescription
workflowTimeout
workflowNosIds
workflowCreatedBy
workflowName
workflowVersion
activityMessage
activityDescription
activityCustomId
activityName
activityNosIds
scriptOwner
scriptName
scriptAssignment
scriptTimeout
scriptType
abort_on_error
javax.script.name
javax.script.engine_version
javax.script.language
javax.script.engine
output
STATUS
auditLogEnabled
failFast
extreme.hideLegacyDesktopApps
status
ports
USE_IPV6
jboss.http.port
jboss.bind.address.management
jboss.server.log.dir
jboss.bind.address
jboss.HTTPS.port
As shown, there are more keys in the emc_vars dictionary. Using a Python script, you can see the
differences between the two environments, using as XMC 8.4.4 as a reference:
There are 46 entries in emc_vars in Scripting Engine
There are 72 entries in emc_vars in Workflow Engine
emc_vars not in Workflow Engine:
Not found: deviceId
Not found: managementPorts
Not found: accessPorts