Install Megaladata Server for Windows

MSI installation

The installer filenames are:

• For the Team edition: MegaladataTeam_7.x.x.msi
• For the Standard edition: MegaladataStandard_7.x.x.msi
• For the Enterprise edition: MegaladataEnterprise_7.x.x.msi

where 7.x.x indicates the version and release numbers of the program.

A web server is required to use Megaladata Studio (the web interface for Megaladata Server). The supported options are:

• Apache: included in the distribution kit for standard installation.
• Microsoft IIS: not included; install and configure it separately.

The Megaladata Server installation process varies depending on whether you use Apache or Microsoft IIS. By default, Megaladata Studio operates via the Apache web server.

Graphical user interface

Running the installer

To install with custom parameters, click Custom in the Installation type dialog.

Selecting components for installation

Choose from the following components:

• Megaladata Server: Required for installation.
• Megaladata Studio: Installs the web interface.
• Documentation: Adds a help section to the web interface.
• Web server: Installs the built-in Apache Httpd web server. Disable this component if you plan to use a third-party web server.

Note: The installer selects all components by default.

Megaladata server parameters

This dialog appears only when installing the Megaladata Server component.

Configure the following parameters:

• Server port: Set the port number for Megaladata Integrator and BatchLauncher connections.
• WS port: Set the port number for Megaladata Studio connections via the WebSocket (ws) protocol.
• Use WebSocket Secure: Enable SSL configuration for WebSocket:
  • WSS port: Set the port number for Megaladata Studio connections via the WebSocket Secure (wss) protocol.
  • SSL certificate: Specify the full path to the SSL certificate PEM file.
  • SSL key: Specify the full path to the SSL key PEM file.
• Install Guardant x64 drivers: Enable this to automatically install the drivers for the electronic security key.

Apache Httpd web server parameters

This dialog appears only when installing the Web Server component.

Configure the following parameters:

• HTTP port: Set the web server's HTTP port number.
• Use WebSocket proxy: Enable proxying for WebSocket connections.
• Use HTTPS: Enable SSL parameter configuration for HTTP:
  • HTTPS port: Set the web server's HTTPS port number.
  • SSL certificate: Specify the full path to the SSL certificate PEM file.
  • SSL key: Specify the full path to the SSL key PEM file.

Megaladata Studio parameters

This dialog appears when installing the Megaladata Studio component without the Web Server component. Set the following parameters:

• Web application catalog: Indicate the preferred location.
• Web application URL: Enter the URL parameters.
• Megaladata Server connection: Parameters for generating the Megaladata Studio configuration file:
  • Host: The value of the host parameter. If this field matches the host in the web application URL, the configuration file specifies host: null.
  • WS port: The ws port value.
  • WSS port: The wss port value.
• Always use secure connection: Enables the secure parameter.
• Use WebSocket proxy: Enables the wsproxy parameter.
• Proxy URI: The path parameter.

Command line

msiexec /i "path_to_msi_file" msi_keys Megaladata_parameters

where:

• msi_keys: Valid values are available by running msiexec /? in the command line. Useful options include:
  • /l* "%TEMP%\Megaladata.msi.log": Enables installation logging.
  • /qn: Performs a "silent" installation without displaying the graphical interface.

:: Silent installation of Megaladata without a web server
msiexec /i ".\MegaladataEnterprise.msi" /qn ADDLOCAL=Server,Studio,Help

:: Silent installation with custom ports
msiexec /i ".\MegaladataEnterprise.msi" /qn WEBSRV_PORT=9080 SERVER_WS_PORT=9081 SERVER_PORT=9082

:: Silent installation with WebSocket SSL enabled
msiexec /i ".\MegaladataEnterprise.msi" /qn SERVER_USE_SSL=1 SERVER_KEY_PATH="%ALLUSERSPROFILE%\ssl.key" SERVER_CRT_PATH="%ALLUSERSPROFILE%\ssl.crt"

Licenses

To start the MegaladataServer service, you must configure licensing keys (see License keys).

If using a network key server, create a file in the directory "C:\ProgramData\Megaladata\Server".

Starting the services

The MegaladataServer and MegaladataHttpd services do not start automatically after installation.

During installation, Start Megaladata Server and Start Web Server shortcuts are added to the Windows Start menu.

To start the services using a shortcut:

1. Right-click the shortcut.
2. Select Run as administrator from the context menu.

Upon successful startup, the message Service "MegaladataServer" started successfully appears in the console window.

To start services from the command line as an administrator, run:

• To start the MegaladataServer service: net start Megaladata
• To start the MegaladataHttpd service: net start httpd_Megaladata

Note: Avoid running the Megaladata Server service under a system account. Instead, create a separate account to customize specific access rights.

Firewall

The host running Megaladata Server must allow the following connections:

• Inbound on TCP port 8080|8443 (WebSocket) for client hosts (browsers):
  • If using a WebSocket proxy, allow connections only for the web server host.
• Inbound on TCP port 4580 for hosts running Megaladata Integrator or BatchLauncher.
• When using Guardant network keys: Allow connections to TCP/UDP ports 3186 and 3187 of the network key server host.

The web server host must allow the following connections:

• On TCP port 80|443 (HTTP(S)) for client hosts (browsers).

Ensure that installed antiviruses and firewalls permit these connections.

netsh advfirewall firewall add rule name="Allow HTTP" dir=in action=allow protocol=TCP localport=80

netsh advfirewall firewall add rule name="Allow Megaladata WebSocket" dir=in action=allow protocol=TCP localport=8080

netsh advfirewall firewall add rule name="Allow Megaladata Port" dir=in action=allow protocol=TCP localport=4850 remoteip=%mgi_host_ip%

netsh advfirewall firewall add rule name="Allow Guardant Net" dir=out action=allow protocol=TCP remoteport=3186-3187 remoteip=%guardant_net_host_ip%

User accounts

During Megaladata Server installation, the following user accounts are created:

• user, with an empty password: Account for operating Megaladata workflows. This account has Workflow design and View reports roles and package publication rights.
• admin, with password admin: Account for Megaladata server administration.
• service, with password service: Account for connecting external applications (such as Integrator and BatchLauncher).

Note: You must change the administrator account (admin) password after completing the installation.

Checking the functionality

To verify the installation:

1. Launch the Megaladata Studio web client:
   • Use the shortcut All Programs\Megaladata\Studio\Megaladata Studio in the Windows Start menu.
   • Or open a browser (Chrome recommended) and navigate to: http://localhost/app/. If you changed the web server port, use: http://localhost:<HTTP Port>/app/.
2. Log in with the user account and an empty password.

• Microsoft IIS