When a user copies an item in SystemWeaver, a SystemWeaver URL link is placed on their clipboard. The URL references the server and port used by the user as well as the item's xID. Such links can be used by anyone who has access to the item to redirect to it using the swExplorerLauncher application. This feature includes support for multi-server installations as well. This article describes how to configure the swExplorerLauncher for use in multi-server installations, and also the logic behind it. 


Prerequisites

  • Client application installation includes the following files:
    • swExplorerLauncher.conf
    • swExplorerLauncher.exe
  • SystemWeaver URL protocol has been registered.


Configuring Support for Multiple IPs

To enable the solution, the swExplorerLauncher.conf configuration file for the swExplorerLauncher must be defined and placed on the client machines in the same location as the swExplorerLauncher executable. 


Example Configuration

<Servers>
  <Server ip="213.115.2.231" port="443">
    <Alt ip="SYS7" port="1345"/>
    <Alt ip="mirror2" port="222"/>
    <Alt ip="ipv4" port="333"/>
    <Alt ip="ipv6" port="444"/>
  </Server>
  <Server ip="sys7" port="1349">
    <Alt ip="172.23.23.100" port="1349"/>
  </Server>
</Servers>


Explanation of the Configuration Elements

<Servers> builds the structure of the configuration and can contain one or more <Server> elements. 


The <Server> tag requires the ip attribute which identifies the IP of one of the servers in the installation. The port attribute defines the port used for the server. 


Each <Alt> tag inside a <Server> defines a valid alternative server in the installation by ip and port.


There is no logic tied to the order of the servers in the configuration file. 


In the above example configuration, one installation has five IP options:  one (1) <Server> and four (4) <Alt> (Alternatives), and another installation has two IP options. Typically, there will be only one installation in the configuration. 


Recommendation

As noted in SystemWeaver Server - Software and Hardware Requirements, we recommend the use if server aliases.

Logic

If an installation includes one or more mirror servers used by users in different geographical locations to decrease latency, those users will ideally want to be redirected to their mirror server when clicking on a SystemWeaver URL link rather than being redirected to the main server or other mirror server in a different location. The logic of the swExplorerLauncher's configuration is as follows: 



Open instance of swExplorer clientNo open swExplorer client
Click on link that includes your preferred IP.Redirects to the open client.Opens client and presents login screen with server and port pre-populated per the URL.
Click on link that includes another IP which you prefer not to use due to, e.g., latency.Redirects to the open client.Opens client and presents login screen with server and port pre-populated per the URL. To use your preferred IP, modify the server and port before logging in.