The StayLinked solution downloads webpage includes an installation guide for each of the typical server platforms used to host a StayLinked instance. We typically recommend that the StayLinked server process is installed on the telnet server for reliability and security reasons. Once the server process is installed, you can move on to the Administrator and Client installations.
As of Server version v16.0 build 222 the Server process defaults to the use following ports for incoming connections:
- TCP 3006 thru 3019 (Administrator Connections)
- UDP 3006 thru 3999 (Client Connections)
Confirming the Server is running
Before moving on, you may want to confirm that the StayLinked server process is up and running. The best method depends on the server platform:
iSeries – Also known as IBMi and AS/400, the StayLinked server process should appear under a WRKACTJOB SBS(StayLinked) as a subsystem with four active jobs. The QP0ZSPWT job will typically be at a TIMW, TIMA or SELW status when the server is ready for incoming connections.
Unix/Linux – Using the command ps -ef | grep staylinked you should see the StayLinked server process running. The StayLinked server process must run against a valid Java runtime on the server. This Java path is specified in the strserver.sh startup script.
Windows – Windows systems will display the StayLinked Server services in the list of running services. If the service does not appear, it means that the option to ‘run as a service’ was not selected or there is a Windows C# distributable patch that needs to be applied correcting the ‘side-by-side’ error found in the Application Event Viewer.
Netstat – The StayLinked server process listens for incoming connections on port 3006. This means that the netstat command can be used on most platforms to confirm the UDP port has been opened.
StayLinkedManager.log – During server startup, the StayLinked Server process will write entries to this log file in the logs subdirectory. This file can help confirm if there were any issues with the startup process and will write various server information to a startup banner at the time of the server startup. This includes the server serial number if licensing will be required for this system.
As part of preliminary testing, you may wish to confirm that the StayLinked server can ping the client devices, Administrator PC, and the telnet server addresses. The ICMP ping can help confirm basic connectivity between various devices.
Windows systems may need the Windows firewall disabled or have StayLinked added to the list of trusted applications. More details on the ports and protocols required by StayLinked can be found in the StayLinked Secure Communications Guide in this knowledge base.
Instructional Video: Allowing an App through Windows Firewall
Share the post "Server Installation"