Written By: |
Jeremy Boilard and Jim Reilly |
---|---|
Manufacturer: |
intlx Solutions |
Product: |
Alarmtraq |
Version: |
11 and older |
Patch Information: |
|
Ticket Number(s): |
Description:
This article provides general installation instructions. Each environment and deployment may be different based on customer requirements. SQL installation will need to be completed prior to the installation of the Alarmtraq installation package.
Requirements
Processor
- Minimum: x64 Processor: 1.4GHz
- Recommended: 2GHz or faster
Memory
- Minimum: 2 GB RAM
- Recommended: 8 GB RAM or greater
Available Disk Space
- Minimum: 80GB
- Recommended: 400GB or greater
Display and Peripherals
- Super VGA (1024 x 768) or higher-resolution monitor
- Keyboard and compatible pointing device
Operating System
- Microsoft Windows Server 2022 (x64)
- Microsoft Windows Server 2019 (x64)
- Microsoft Windows Server 2016 (x64)
- Microsoft Windows Server 2012 (x64)
Port Matrix
Network Protocol | Protocol | Direction | Source | Destination | Purpose |
443 | TCP | ingress | Alarmtraq | HTTPS Webpage | |
80 | TCP | ingress | Alarmtraq | HTTP Webpage | |
162 | UDP | ingress | monitored application | Alarmtraq | SNMP |
22 | TCP | egress | Alarmtraq | monitored application | SSH (Auto Remediation) |
3389 | TCP | ingress | Alarmtraq | Remote Desktop | |
1433 | TCP | Alarmtraq | SQL | SQL |
Installation Paths
Directory | Description |
C:\Program Files (x86)\Alarmtraq | Default installation path of Alarmtraq software |
C:\Program Files (x86)\Alarmtraq\Backup | Alarmtraq Backups |
C:\Program Files (x86)\Alarmtraq\crystal | Reporting |
C:\Program Files (x86)\Alarmtraq\Logs | Troubleshooting Logs |
C:\Program Files (x86)\Alarmtraq\MIB | Product MIBS |
C:\Program Files (x86)\Alarmtraq\Reports | Processed Reports |
C:\Program Files (x86)\Alarmtraq\Sounds | Wave files for desktop app |
C:\Program Files (x86)\Alarmtraq\Templates | Email and API templates |
C:\Program Files (x86)\Alarmtraq\Tools | SQL templates |
Alarmtraq Application Installation
Summary:
- Install Operating System
- Install .NET Framework 4.5 or higher.
- Install SQL Database
- Install Alarmtraq
- Crystal Reports Ver 13.0.21
- Microsoft Interrupt Form Tools V2.0.51727
Step 1:
- Install the latest operating system and .NET Framework 4.5 or higher.
- Next, install the latest version of SQL Server.
- Download the Alarmtraq installation package (Alarmtraq.zip) from the Support Site. A login will need to be created if an account is not already created.
Release 11.0.88 MD5sum = 8a08546536afc3378e4b8eed10c92830
Step 2: Installing Alarmtraq
- Create a temporary directory on the Alarmtraq server called ATinstall.
- Unzip the Alarmtraq.zip file into the ATInstall folder. Open the folder after unzipping the installer package.
- Right-click on the setup.exe file and choose Run as Administrator.
Step 3:
- A license agreement will appear on the screen.
- Press Accept to install the latest version of the Crystal Reports Runtime. This will take several minutes to complete.
Step 4:
- Read and agree to the software license agreement, click Next.
Step 5:
- Select the installation folder and click Next.
Step 6:
- Confirm the installation and click Next.
Step 7:
- Wait while Alarmtraq is installed on your server, this could take several minutes.
Step 8:
- When the installation has completed, click Close.
Step 9:
- Before we can start the Alarmtraq application a database will need to be created.
- To create the database in the SQL server, open the SQL Server Management Studio.
- Click File → Open → File.
- Select the appropriate script file to match your version of SQL Server from the Alarmtraq tools folder C:\Program Files\Alarmtraq\Tools and click open.
Step 10:
- Verify the path located on lines 5 and 7 match your current installation of SQL Server (edit if necessary)
Step 11:
- On the toolbar, click Execute. After a few seconds, a blank Alarmtraq database is created in SQL.
Step 12:
- Navigate to the server Desktop and click on the new Alarmtraq icon.
- A SQL connection window will appear. Select the SQL server you will use.
- Select the Authentication Type: With Integrated Windows authentication.
- Enter the SQL Login ID (Default: sa) and the password you assigned when you installed SQL server.
Step 13:
- Click the Test Connection button to verify your access to the Alarmtraq database.
Step 14:
- If the test is successful click OK and OK to write the connection string to the registry. Alarmtraq will use this connection string when accessing the database.
Step 15:
- Rebuild the SQL Stored Procedures and Functions
- Double-click the new Alarmtraq shortcut on your desktop to launch Alarmtraq.
- The first time you run Alarmtraq, several tables will be populated with working data and may take a few minutes to load.
- When completed, the main form will be visible.
Clustering
A cluster is a group of independent Alarmtraq servers working together as a single system to ensure that mission-critical resources such as modems and IP ports are as highly available as possible. The group is managed as a single system, and is specifically designed to tolerate component failures, and to support the addition or removal of components in a way that's transparent to your organization.
To increase the scalability and to maintain performance, your organization might use a cluster to increase the number of ports in your Alarmtraq cluster to up to 24 modems. The following example adds three servers to the Alarmtraq cluster to create a 24 port load-balanced cluster, which spreads server tasks across three servers.
As you may already be aware, there is one way to help boost your Alarmtraq Server’s uptime, and that is by clustering Alarmtraq Servers. This way should one Alarmtraq Server fail in the cluster, another clustered server will automatically take over, keeping downtime to minutes, instead of hours or more.
Clustered systems have several advantages: fault-tolerance, high-availability, scalability, simplified management, and support for rolling upgrades, to name a few.
Management
- You can assign each server any or all roles to be performed. Click on Edit > Server Roles
Primary Server Only one server should be assigned as the Primary Controller. The Primary controller houses the web server, SNMP manager and dispatcher module. The Primary controller is also responsible for running the maintenance routines.
Manufacturer Release notes:
Disclaimer: intlx Solutions Knowledge Base
The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.
Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.
Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.
Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.
Thank you for your understanding.