Client/Server and Generic applications fall into legacy application type and can be quite complicated. These types of applications tend not to be web friendly by nature and require additional components to communicate between client and server outside of the browser. A similar example for this type of application is VPN and end-to-end tunneling to define IP/Port to pass along the data.
TAC has great flexibility in publishing generic client/server applications using its unique client/server application template. This template allows publishing a wide variety of client server applications. Regardless of whether it is custom or standard, TAC treats all of them in the same way. This single template is able to handle multiple backend servers and multiple IP/Port ranges. Publishing client/server applications is straightforward.
To publish your Client/Server application, do the following:
Click Add in Application section of your site.
Select Generic client/server application from Client/Server dropdown menu; click Next
Enter Application name, click Next.
Enter server application properties. Enter list of servers that should be accessible on client devices. The entries must be in one of the following formats:
: Port (Server1.corp.com: 1234)
: – (Server1.corp.com: 1200 – 2000)
IP: Port (10.1.1.5:3389)
IP: – ( 10.1.1.5: 1200-2000)
IP/Subnet: port ( 10.0.0.0/255.255.255.0: 3389)
IP/Subnet: – (10.0.0.0/255.255.255.0: 1200-2000)
Enter the executable and executable path when the application starts on client device. You have to enter x86 or x64 field based on the executable type.
Select Authorization and Access Policy under Security, click Next.
Configure and verify portal link settings, click Next.
Remember to apply configuration in TAC to take effective changes. When you try to access the site using your client browser, you may be prompted to download TAC Client Service component and you have to install it in order to work Client/Server, VPN applications.
To work Client/Server and Generic Applications, users require to install TAC Client Services on their end-points. When they initialize the application for the first time the TAC site will prompt to install TAC Client Component (TAC CS) on their endpoints. When there is TAC CS involved the endpoint must have valid trusted system certificate for proper communication.
VPN and other generic applications are tunneling the traffic securely to the TAC Gateway and beyond. TAC will make the connection secure by trusting the certificate installed on user endpoints. If you use self-signed (certificate issued by custom CA) certificates for TAC sites, CA that issued cert has to be added to Trusted Root CA under Local Computer on end-point in order to work TAC CS properly.