Overview

DS2 and Python programs that are published to SAS Micro Analytic Service, whether user-written or generated by SAS analytical solutions, are known as modules. This term reflects the language-neutral nature of SAS Micro Analytic Service interfaces.
A module is a collection of methods. For DS2, a module represents one DS2 package and its methods. For Python, a module is a collection of Python functions.
Module methods can be used to process events in a SAS Event Stream Processing continuous query. The results of such processing create derived events that flow to downstream components in the continuous query. In addition to generating derived events, module methods can influence SAS Event Stream Processing by interrogating and setting event opcodes and flags. Event opcodes and flags are covered in more detail in the DS2 and Python programming chapters that follow. Also, for more information about SAS Event Stream Processing, see the Documentation in the Knowledge Base, at http://support.sas.com.
SAS Micro Analytic Service uses two internal component types to manage the modules that are published to it. These are the module context and the revision. A third component, the user context, provides execution environments containing sets of module contexts. SAS Micro Analytic Service automatically manages user contexts for SAS Event Stream Processing by maintaining one user context per dfESPproject object. Therefore, unlike previous versions of SAS Micro Analytic Service, user contexts do not appear in the user interfaces.
Note: If you plan to write DS2 modules to deploy to SAS Micro Analytic Service, follow the programming guidelines described in DS2 Programming for Event Stream Processing with SAS Micro Analytic Service. If you plan to write Python modules to deploy to SAS Micro Analytic Service, follow the programming guidelines described in Python Programming for SAS Event Stream Processing with SAS Micro Analytic Service.
Last updated: March 2, 2017