PeerLink Help > Getting Started > Installation and Initial Configuration

PeerLink can be installed in numerous ways based on your needs and environment. The PeerLink installation consist of two separate installers, both of which are available for download from our website:

1.	PeerLink installer, containing the PeerLink Hub and PeerLink Broker

2.	PeerLink Agent installer

PeerLink Hub & PeerLink Broker Installation

Both the PeerLink Hub and PeerLink Broker are packaged with the main PeerLink installer and by default, will be installed on the same server.

Basic Requirements

See the Requirements section for more detailed requirements.

Software Installation & Launching

1.	Run the PL-Hub_Installer.exe or PL-Hub_Installer64.exe installer and follow all instructions.

After the installation finishes, both the PeerLink Hub and PeerLink Broker will be installed. The PeerLink Broker will automatically be installed as a running Windows service and set to auto-start. The PeerLink Hub is installed in three parts: a Windows service that is set to auto-start, a web service for granting access to the Windows service via web browsers, and a rich client for interacting with the Windows service. The rich client is started as a normal Windows application.

Start the PeerLink Hub Client by launching the PL-Hub.exe executable located in the base installation directory. If the both the PeerLink Broker and PeerLink Hub Service are up and running as background services, then the PeerLink Hub should successfully start. If not, please make sure that both the PeerLink Broker and PeerLink Hub Service are running as Windows services via the Windows Service Panel (services.msc).

Secure Encrypted TLS Connections

By default, the PeerLink Hub and PeerLink Broker will be installed on the same host machine which does not require secure SSL communication between each other. To enable a secure SSL connection between the PeerLink Hub and PeerLink Broker, first stop the PeerLink Hub Service via the Windows Service Panel (services.msc). Once stopped, navigate to the directory, 'Hub\workspace\prefs', relative to the installation directory. Within this directory, open the com.ci.pl.hub.runtime.prefs file in a text editor. If the file does not contain a line starting with "hub.jms.providerURL", then add the following line in it's entirety:

hub.jms.providerURL=failover\:(ssl\://localhost\:61617)?jms.alwaysSyncSend\=true

Otherwise, making the following changes to the line starting with "hub.jms.providerURL" (changes are bold and underlined):

From: hub.jms.providerURL=failover\:(tcp\://localhost\:61616)?jms.alwaysSyncSend\=true

To: hub.jms.providerURL=failover\:(ssl\://localhost\:61617)?jms.alwaysSyncSend\=true

Once these changes are complete, save the file, then restart the PeerLink Hub Service.

Uninstalling

PeerLink ships with an uninstaller for the environment it is running in. Please use the standard platform specific method for removing programs/applications to uninstall PeerLink.

PeerLink Agent Installation

You will need to install a PeerLink Agent on each server you plan to include in any of your file collaboration sessions.

Basic Requirements

See the Requirements section for more detailed requirements.

Software Installation & Launching

1.	Run the PL-Agent_windows.exe installer on the target server and follow all instructions.

2.	During installation you will need to specify the PeerLink Broker Host Name (computer name, fully qualified domain name, or IP Address) of the server where the PeerLink Broker is running, as well as the configured TCP/IP port number (the default port for TLS communication is 61617).

After the installation finishes, the PeerLink Agent will be installed as a Windows service. You will need to verify that the PeerLink Agent is running, and that it was able to successfully connect to the PeerLink Broker. You can do this by opening Windows Service Panel (services.msc) and making sure that the "PeerLink Agent Service" is started.

4.	Make sure that the PeerLink Agent was able to successfully connect to the PeerLink Broker by going to the PeerLink Agent installation folder, opening the output.log text file, and making sure that "Ready" is displayed on the first line.

Secure Encrypted TLS Connections

By default, the PeerLink Agent is installed with TLS encryption enabled, where the PeerLink Agent connects to the PeerLink Broker through a secure, encrypted connection. If you are running PeerLink on a secure LAN or via a corporate VPN, you might want to disable TLS to boost performance. For more details on disabling or enabling encryption for the PeerLink Agent, please see the broker page of the Central Agent Configuration section.

If AES-256 support is required, please contact support@peersoftware.com to obtain the necessary installers.

Uninstalling

PeerLink Agent ships with an uninstaller for the environment it is running in. Please use the standard platform specific method for removing programs/applications to uninstall the PeerLink Agent.