Requirements
This section describes the prerequisites to set up the Apex Service Automation application.
License
Apex Service Automation / Service Automation Engine
Apex Service Automation / Service Automation Execution Pack
Hardware and Software Requirements with Deployment Options
The table below outlines the deployment environment (either On-Cloud or On-Premise) for each component. For On-Cloud deployment, only Proxy needs to be installed in the Customer Environment, while the other components will be hosted On-Cloud.
Serial No | Application Components | Deployment Option 1 | Deployment Option 2 | Deployment Option 3 | Deployment Option 4 |
|---|---|---|---|---|---|
1 | SA Application (UI) | Server 1 | Server 1 | Server 1 | Server 1 |
2 | SA API | ||||
3 | Erlang & RabbitMQ | Server 2 | |||
4 | Event Listener Service | ||||
5 | DB | Server 3 | Server 2 | ||
6 | Proxy or Execution Service | Server 4 | Server 3 | Server 2 |
Deployment Option 1
Server | Software Requirement | Minimum Hardware Requirement |
|---|---|---|
OS | Windows 2012 R2 onwards only | |
Server 1 (Application Server) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent 4GB of RAM 100 GB Hard Disk | |
IIS 7.0 or above (Web Server) | ||
Server 2 ( ELS & RabbitMQ Server) | ||
Erlang OTP 22 or higher (32-bit or 64-bit, Recommended 64-bit for better performance | Intel Xeon Quad-Core processor or equivalent | |
RabbitMQ Server 3.8.2 or higher | ||
Dot Net Framework version 4.6.2 and above | ||
Server 3 (DB Server) | ||
Microsoft SQL Server 2012 | Intel Xeon Quad-Core processor or equivalent | |
Server 4 (Proxy Server) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent | |
PowerShell 5.1 or later/ Python 3.5 or later | ||
Deployment Option 2
Server | Software Requirement | Minimum Hardware Requirement |
|---|---|---|
OS | Windows 2012 R2 onwards only | |
Server 1 (Application Server , RabbitMQ & ELS) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent | |
IIS 7.0 or above (Web Server) | ||
Erlang OTP 22 or higher (32-bit or 64-bit, Recommended 64-bit for better performance | ||
RabbitMQ Server 3.8.2 or higher | ||
Server 2 (DB Server) | ||
Microsoft SQL Server 2012 | Intel Xeon Quad-Core processor or equivalent | |
Server 3 (Proxy Server) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent | |
PowerShell 5.1 or later/ Python 3.5 or later | ||
Deployment Option 3
Server | Software Requirement | Minimum Hardware Requirement |
|---|---|---|
OS | Windows 2012 R2 onwards only | |
Server 1 (Application Server , RabbitMQ , ELS & DB) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent | |
IIS 7.0 or above (Web Server) | ||
Erlang OTP 22 or higher (32-bit or 64-bit, Recommended 64-bit for better performance | ||
RabbitMQ Server 3.8.2 or higher | ||
Microsoft SQL Server 2012 | ||
Server 2 (Proxy Server) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent | |
PowerShell 5.1 or later/ Python 3.5 or later | ||
Deployment Option 4
Server | Software Requirement | Minimum Hardware Requirement |
|---|---|---|
OS | Windows 2012 R2 onwards only | |
Server 1 (Application Server , RabbitMQ , ELS , DB & Proxy) | ||
Dot Net Framework version 4.6.2 and above | Intel Xeon Quad-Core processor or equivalent | |
IIS 7.0 or above (Web Server) | ||
Erlang OTP 22 or higher (32-bit or 64-bit, Recommended 64-bit for better performance | ||
RabbitMQ Server 3.8.2 or higher | ||
Microsoft SQL Server 2012 | ||
PowerShell 5.1 or later/ Python 3.5 or later | ||
Privileges Required
This will be shared during the implementation phase.
Port Requirements
Source IP | Destination IP | Port Number | Direction |
|---|---|---|---|
Apex Application Server IP | Rabbit MQ Server IP | 5671(Required SSL) or 5672(http Port) | Unidirectional |
Event Listener Service IP (Proxy Server IP) | Rabbit MQ Server IP | 5671(Required SSL) or 5672(http Port) | Unidirectional |
Execution Service IP (Proxy Server IP) | Application IP | 443 or 80 | Unidirectional |
Execution Service IP (Proxy Server IP) | Mail Service | Mail Service Port | Unidirectional |
Execution Service IP (Proxy Server IP) | Any External Webservice / AP | Relevant port (usually 443) | Unidirectional |
Exact requirements will be shared during the implementation phase.
Apex User / Analyst License
SymphonyAI Service Automation may require an Analyst License of Apex ITSM. This depends on the requirement. Refer the below details.
Usually, SymphonyAI Service Automation owns the ticket logged for Service Automation, updates the tickets with output and resolves the ticket. In this scenario, an analyst license is needed and can be handled with two options.
Option 1: Dedicated analyst license for Service Automation.
Option 2: Share analyst license of one Resolver/Engineer. Drawback of this option is: All the updates the ticket carry the Resolver/Engineer’s name even though it’s updated by Service Automation.
Note
The analyst should be part of all the Workgroups where Service Automation involvement is required.
One API User is required for Service Automation to consume web services of SymphonyAI.
Other Requirements
Internet access is required to install the required PowerShell modules.
Connectivity should be available from the Proxy server to the Local Active Directory, Microsoft O365, and Azure AD.
VPN access is required to Application server, Database server and proxy server perform the installation/configuration of the Service Automation Application, Event Listener, and Execution Service.
Monitoring Account/Service Account is used for executing Service Automation script.
All the required CIs to be added into CMDB.
SMTP or Mail Service to send notifications.