A Jet deployment requires the installation of a Signiant SDCX Server, and a storage location at every endpoint.
Once the SDCX Server and storage location are in place, complete Jet configuration by:
All Jet deployment and configuration steps are performed through the Jet management Console.
For more information on Jet architecture, see the Product Overview.
Before deploying Jet to an on-premises network architecture, make sure that the mandatory prerequisites for its implementation are in place:
Deploy and configure SDCX host servers that meet operating system and hardware requirements.
Ensure SDCX host servers have static IP addresses to avoid potential downtime associated with changes to dynamic IP addresses.
Configure network and local server firewalls to allow connections to and from other Signiant SDCX Servers and from the Jet Cloud Services as per network requirements.
Reserve local ports for Signiant SDCX Servers only. (strongly recommended)
Allocate adequate local or network storage.
Allocate and configure either a publicly routable IP address or a custom IP address using NAT if using port forwarding or a private network.
Ensure access to the required external domains.
Once all requirements are complete, you can deploy a Signiant SDCX Server.
Protocol | Direction | Port Range | Change Type | Description |
TCP | Inbound | 49221 | Network Firewall | Used for file transfer |
UDP | Bidirectional | 49221-49421 | Network Firewall | Used for file transfer |
TCP | Bidirectional | 50221 | Network Firewall | Used for file transfer |
TCP | Outbound | 443 | Network Firewall | Used to connect to cloud services: Storage server to Amazon EC2 IP Ranges Storage server to Amazon CloudFront IP Ranges |
The following ports must not be used by any other local processes:
Protocol | Direction | Port Range | Change Type | Description |
HTTPS | Local | 8443 | Local Server | Local connection to storage server |
TCP | Local | 8888 | Local Server | Local connection to storage server |
UDP | Local | 50222-50421 | Local Server | Local connection to storage server |
TCP | Local | 50443 | Local Server | Local connection to storage server |
TCP | Local | 50080 | Local Server | Local connection to storage server |
TCP | Local | 50081 | Local Server | Local connection to storage server |
TCP | Local | 51221-51320 | Local Server | Local connection to storage server |
TCP | Local | 61001-61003 | Local Server | Local connection to storage server |
For more details, see System Requirements.
Signiant SDCX Servers allow Jet endpoints to send and receive files. Once installed on a Linux or Windows server, you can assign an SDCX Server to an endpoint.
Once an SDCX Server is assigned to an endpoint, it can be connected to another local folder on the same system, a shared storage device, another SDCX Server, or connected to a cloud storage endpoint.
Signiant SDCX Server software can be downloaded from the Jet management console or the Signiant Help Center.
To download the Signiant SDCX Server software from the Jet management console:
In your Jet management console, click Endpoints.
Click the SDCX Software download button.
Select the server operating system from the drop-down menu.
Click Download, or click Skip if you have previously downloaded the software.
Copy the registration key to your clipboard.
Installing the SDCX Server software requires the registration key, which is a unique token that associates the server with your account. You must copy a new registration key to install the software on each source or destination server.
After you have downloaded the Signiant SDCX Server software, install it on the source or destination server.
To install the Signiant SDCX Server software:
tar -zxvf Install_Signiant_SDCX_Server_<version>.tar.gz
.sudo ./installer.sh -registration-key=<registration_key>
.For more installation options, use ./installer.sh -help
To install the Signiant SDCX Server software:
To install the Signiant SDCX Server software:
.\<installer-file-name> /S -registration-key=<registration_key>
Invoke-WebRequest -Uri "http://localhost:8080/spring/install" -useBasicParsing -Method 'POST' -Body {installKey=<registration_key>}
During initial Linux installation, all SDCX Server services run as root
. If a distributed file system protocol, like NFS, is used with the root squashing feature enabled, a remote NFS client running as root
will be mapped to a non-root user ( nfsnobody
).
If a service running as root
in this scenario produces access errors when trying to read or write from a network share, configure the NFS server user permissions to match the root squashing user.
During initial Windows installation, all SDCX Server services run as NT-Authority\System
, which allows for unrestricted access to local system resources. Some SDCX Server services must be configured to run under a different account in order to access remote resources like NAS.
To configure a username for shared storage on Windows:
domain\userName
)Note: The NAS server itself may be on a Windows domain. If the server is not associated with a Windows domain, do not enter a domain.
\\server\share\jet-source
)You may need to uninstall the Signiant SDCX Server in order to perform an upgrade from a previous version.
To uninstall the Signiant SDCX Server, run the uninstaller script in your terminal:
sudo /usr/Signiant_Media_Shuttle/bin/siguninstall
The siguninstall
command removes the SDCX Server and all associated applications from your system.
To reinstall the server after removal, follow the installation procedure using a new registration key.
Uninstalling the SDCX Server on Windows requires you to manually uninstall the Signiant SDCX Server software as well as its supporting applications.
To uninstall the Signiant SDCX Server:
To reinstall the server after removal, follow the installation procedure using a new registration key.
You may need to restart Jet services on your local computer after reinstalling SDCX Server software.
To restart services:
Linux: In your terminal, run >./siginit restart
.
Windows: In the Services control panel, right-click on the services and choose Restart.