System
| System Requirements | |
|---|---|
| Memory | 4GB minimum, 8GB recommended |
| Processor Cores | 2 minimum, 4 recommended |
| Hard Disk Space | 100GB minimum |
| Network Interface | GigE |
If deploying in an AWS environment, we recommend using a M5.xlarge EC2 general purpose instance with general purpose SSD (gp2) EBS volume type. Perspectium has tested using the M5.xlarge instance type though any system meeting the system requirements should be able to run the application.
For other cloud platforms, it is recommended to use the equivalent services to the aforementioned AWS services:
| AWS | Microsoft Azure | |
|---|---|---|
| Virtual Machine | m5.xlarge | Standard_D4_v3 (Dv3 and Dsv3-series) or Standard_D4_v4 (Dv4 and Dsv4-series) |
| Storage | general purpose SSD (gp2) | Standard SSD Managed Disks |
Network
Meshlets requires outbound access to the Perspectium Integration Mesh and its MBS cloud service. The target application being integrated will also need access which may include both inbound (to receive incoming webhook calls if applicable) and outbound access (to make requests to get and post data) depending on the integration type. Contact Perspectium Support for more information.
Your firewall settings will need to allow this traffic in order for the meshlet to connect to our cloud service and your target application to properly read and send data. Check with your IT administrator to verify that firewall settings allow application and protocol access for the meshlet to connect to the Mesh and target application as indicated below.
The following ports are used by the meshlet:
| Network Requirements | |
|---|---|
| AMQPS Protocol on Outbound Port | TCP/5671 outbound to your Perspectium MBS (amqps://example.perspectium.net) |
| or | |
| AMQP Protocol on Outbound Port | TCP/5672 outbound to your Perspectium MBS (amqp://example.perspectium.net) |
| HTTPS Protocol on Port(s) | TBD based on your target application being integrated |
Java
Java is required to be installed to run a meshlet. Newer versions may also be able to run the meshlet but have not been tested or verified. We typically provide support for the latest version of Java with a major release after the Java version's general release date and when we have completed testing to ensure compatibility.
| Perspectium Version | Java 7 & earlier | Java 8 | Java 9 | Java 10 | Java 11 | Java 12 | Java 13 | Java 14 | Java 15 | Java 16 | Java 17 | Java 18 | Java 19 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Helium |  |  | | | | | | | | | | | |
| Iodine | | | | | | | | | | | | ^ | ^ |
Starting with the Iodine 7.0.0 release, Meshlets will run with at minimum Java 11.
^Only supported with Iodine 7.0.1 and newer.
Supported Operating Systems
The following operating systems are supported by meshlets:
| OS | Version |
|---|---|
| Windows | Professional/Home 7+ |
| Server 2012+ | |
| Linux* | Red Hat 6+ |
| Ubuntu 14.04+ | |
| CentOS 6+ |
*Linux requires superuser access (sudo) to install the meshlet and run it as a service.
The versions of Linux specified above have been tested to work with meshlets. Other versions with equivalent Linux kernel and meeting the other requirements above (System, Java, etc.) may also be able to run meshlets. Please contact Perspectium Suppport for more information.
ServiceNow and Target Systems
Integration User
During the implementation phase where the Professional Services team onboards you to the Perspectium service, the team will work with you to determine what user shows as doing the updates in ServiceNow (creating incidents, adding comments, etc.) and the target system as part of the integration.
For ServiceNow, the user is mapped in the table maps and transform maps. The user in ServiceNow can show as follows:
| User | Description |
|---|---|
| System | If no user is designated, updates will show as done by the System user.
|
| Integration User | A user is designated as the Integration User so all updates are show as done by them. This user can be one that already exists in ServiceNow or one that you have created specifically for this integration. The user should have access to be able to create and update records on the ServiceNow tables being integrated (such as the incident table if integrating the Incident process). |
| Actual User | The actual user that is doing the update. So if Jane Doe is updating it in the target system (such as Jira or another ServiceNow instance), the update will show as Jane Doe in ServiceNow.
|
For target systems that are not ServiceNow, the user is configured in the ServiceNow outbound table maps or the meshlet's configuration file. The user in the target system can show as follows:
| User | Description |
|---|---|
| Integration User | A user is designated as the Integration User so all updates are show as done by them. This user can be one that already exists in the system or one that you have created specifically for this integration. The user should have access to be able to create and update records on the object/tables being integrated (such as the incident table if integrating the Incident process). |