Supported Operating Systems
PortX & XpoLog Supported Operating Systems

Windows Server (32 bit and 64 bit for all editions)

• Windows Server 2008 R2
• Windows Server 2012 and 2012 R2
• Windows Server 2016
• Windows Server 2019

Windows Workstation

• Windows 8
• Windows 8.1
• Windows 10

Any Linux distribution with kernel versions 2.6.x and later (32-bit and 64-bit)

Mac OS

• OSX 10.11
• OSX 10.12
• OSX 10.13

PortX & XpoLog can also run as an application hosted on popular Java servers:

• Apache Tomcat 6 and above
• Oracle WebLogic 9 and above
• IBM WebSphere 6 and above
• RedHat JBoss 5 and above

Any of these versions can be downloaded from the download page.

XPLG Hardware Requirements
PortX & XpoLog Hardware Requirements

As a best practice, a Portx/XpoLog node should have the following resources:

•  Any modern CPU with 8 cores (3 GHz per core).
• 16 to 32 GB of RAM, but not more than 64 GB.
• SSD disk system, preferably with high IOPs.
  The disk size will depend on a number of factors such as the volume of logs collected, retention period, and so on. You can also choose to host the collected logs in a mounted share.
• Java 1.8 and above
  The XPLG Product Suite installer comes with an embedded Java runtime, so users don’t have to install Java separately.
• However, there is also a generic installer package that comes without Java. This is so that users who have specific Java distribution requirements can install their choice of Java 1.8 distribution separately.
• During installation, PortX/XpoLog will prompt for the Java location.
• Fast network (10 or 100 Gbps)
  All nodes should be located in the same subnet or data center for optimal network performance

Ports
Requierd Ports for PortX/Xpolog 

A number of ports need to be open for different systems. More information can be found in PortX/XpoLog System Requirements.

Deployment Modes

XPLG Product Suite, PortX & XpoLog can be deployed in two different methods:

• Standalone mode
• Cluster mode

PortX / XpoLog Standalone configuration

Only one server is used for collecting, processing, indexing, and storing logs from target systems.

It also runs the web UI for the XPLG Product Suite.

Logs collected from different systems can be saved in a local drive or a mounted share.

This deployment model is suitable for small networks.

PortX / XpoLog Clustered mode

PortX/ XpoLog can run in two configurations:

• Single node cluster
• Multi-node cluster

In clustered operation, PortX/XpoLog processes run separately, unlike the standalone mode, where everything is included in one process.

The clustered operation involves two distinct types of processes:

• Processes related to the web UI
• Processes related to backend work such as indexing, analysis, monitoring, or alerting

A cluster of nodes can separate these two types of tasks.

Some nodes can run UI processes while others can take care of backend operations.

In a single-node cluster, the two different types of processes are running on the same host.

This mode is useful for proof-of-concept, testing, or demonstration purposes.

In a multi-node cluster setup, PortX/XpoLog processes are running on separate groups of machines.

An array of machines can be responsible for user interface interactions while another array of nodes can be running the backend processes.

Each type of machine would interface with a centralized storage pool like a SAN or a cloud-hosted storage volume.

It is also possible to run PortX/ XpoLog clusters in high availability (HA) mode and to expand the cluster for capturing logs from large, distributed networks.

For advanced cluster setup architecture, refer to XPLG Products Suite Documentation.

Demo Server

This quick setup guide will show you how to install, configure, and use a single node, standalone PortX/XpoLog server running on an Amazon EC2 instance.