Understanding Modules
Understanding Modules
Resolve Actions Express modules are used for communication, remote execution, and systems integration with external services. Each module serves as an interface to its equivalent service - a mail service, telecommunication, or command executor. Each module is configured individually according to its parameters. Multiple instances of the same module can be defined by using the module instance table in the module configuration window, allowing for high availability and redundancy.
Each module is subject to the license agreement.
When switching between the modules, the related service must be restarted. The following table describes a sample of Module types:
| Module | Description |
|---|---|
| Caller Modules | Dial-up servers for incoming and outgoing phone calls. Caller Modules are responsible for performing all IVR and telephone related workflow activities. |
| Email Modules | Email components that perform email related workflow activities such as sending and receiving emails. Similar to MS Outlook or MS Outlook Express accounts. |
| Everbridge | Integrates Actions Express with Everbridge. |
| MS Operations Manager | Integrates Actions Express with MS Operations Manager. |
| HP Service Manager | Integrates Actions Express with HP Service Manager. |
| IBM Tivoli Omnibus | Integrates Actions Express with IBM Tivoli OMNIbus. |
| Text Message Modules | Cellular components that send text messages to Actions Express recipients. |
| Executor | Runs any type of command, batch file, or .exe file on a local or remote machine. note The executor module may be installed locally or separately on each machine from which commands are executed. note The communication between the Actions Express Server and the executor module is unidirectional and is encrypted by 3DES using port 11006. |
| SYSLOG | A connector to SYSLOG Daemon. |
| Message Queue Modules | Connectors to a Microsoft/IBM MQ components (used to manage queues of messages and requests). |
| ServiceNow | Integrates Actions Express with ServiceNow. |
| SNMP Modules | Receives SNMP traps sent from external devices to Actions Express. |
| Event Gateway | Provides a RESTful API to receive events from external sources. |
Choose Configuration > Modules and open the Core Components or Integrations lists. A window similar to the following is displayed:
Creating new core components is not supported in Actions Express. Although it is technically possible to create a new one from the + icon in the top right of the Core Components table, it would not be working.