Network protocol and ports used by StruxureWare Portal


Transfer protocol





80 (443)

A limited amount of data is transferred between StruxureWare Portal and the various data giving systems like e.g. StruxureWare Power Monitoring Expert, StruxureWare Data Center Operation and StruxureWare Data Center Expert using pull from StruxureWare Portalserver.

Between StruxureWare Portalserver and the web browser/client, the amount of data is also limited and therefore bandwidth requirements very low.

Manually created user and password (default admin/admin).

Authentication server integration support.

Server and client negotiate SSL cipher type and key length

Communication between StruxureWare Portal server and data providing StruxureWare systems.

Communication from webbrowser to StruxureWare Portal server is also using HTTP protocol.

PostgreSQLTCP5432Very limited data is transferred between the database and StruxureWare Portal application-YesDatabase is located and same server as StruxureWare Portal server installation


The StruxureWare Portal server could be placed in a DMZ to achieve access from the internet outside of a company, or accessed through a VPN client. How this could be done depends very much on company policy and network infrastructure. The StruxureWare Portal is based on a standard open source portal and collaboration software which means it is designed and heavily being used in most common access scenarios.

Furthermore, the connected StruxureWare servers can be hardened by enabling e.g. firewall, and iptables trust rules. All web service requests to the StruxureWare servers require credentials, so data is transferred securely.


SSL is not available by default but can be enabled by following this guide.

Authentication servers

Authentication servers/services are found in the StruxureWare Portal right side menu go to->control panel->portal settings->Authentication.

Several authentication servers and services could be used. AD/LDAP is documented here.

Packages used in StruxureWare Portal

The StruxureWare Portalis based on Liferay Portal 6.1 CE GA2 (6.1.1).

Software Vulnerability, Scans and Certifications

The StruxureWare Portalis based on Liferay Portal 6.1 CE GA2 (6.1.1). The general Liferay software vulnerabilities can be seen here.
A software scanning tool is run against every release of the product. The results are investigated and needed action in terms of security updates, etc. taken. The scanning tool used is named  Nessus.  Nessus is a network vulnerability scan utility.  It scans the server as a network device and not just a web server. Please contact us if you need further details.


Antivirus is not included in the StruxureWare Portal installation. The antivirus software must be installed afterwards. Depending on the antivirus product being used, it might be a good idea to not include database installation directory in the scans.


StruxureWare Portallogs activity and failures to various log files are located relative to the installation folder in ..\StruxureWare Portal\tomcat-7.0.27\logs, ..\ StruxureWare Portal\logs, ..\PosgreSQL\9.1\data\pg_log.

Database architecture

Currently the database and server are installed in the same partition by default. The database technology is postgreSQL and cannot be exchanged with any other database type or technology.

Skip to end of metadata
Go to start of metadata
  • No labels