Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.3/5.4.4This page gives installation instructions and an overview of the Appx HTML client. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
OverviewThe Appx HTML client is designed to allow you to connect to an Appx server and run Appx applications using a browser, either on the desktop, a tablet or a smartphone. When running the client in a browser, no software is required on the desktop, tablet or smart phone. When the user logs on, the necessary code is downloaded to their device as required. | ||||||||
Line: 60 to 60 | ||||||||
All releases of the APPX Server Connector require the 'nodejs' package from https://nodejs.org/. For rpm based Linux systems, you can install it via (as root): | ||||||||
Changed: | ||||||||
< < | curl --silent --location https://rpm.nodesource.com/setup | bash -yum install nodejs | |||||||
> > | curl --silent --location https://rpm.nodesource.com/setup | bash -yum install nodejs | |||||||
Changed: | ||||||||
< < | To install on Windows, go to https://nodejs.org and download the Windows installer (msi) file and simply run the installer. | |||||||
> > | To install on Windows, go to https://nodejs.org and download the Windows installer (msi) file and simply run the installer. | |||||||
As of Release 5.4.4 the APPX Server Connector also requires the MongoDB Database for caching images and other items. Instructions for downloading and configuring the database can be found at https://docs.mongodb.org/manual/tutorial/
Installation | ||||||||
Line: 77 to 77 | ||||||||
Assuming the web server to which we installed the client is 192.168.0.15, and that we installed everything into an 'appx' folder on the web server, then we should be able to get a client login dialog box via: | ||||||||
Changed: | ||||||||
< < | http://192.168.0.15/appx/client.html | |||||||
> > | http://192.168.0.15/appx/client.html | |||||||
You must open port 3014 on the server running the APPX Server Connector for this connection to work. If you do not want to open any new ports on your firewall, see the section on 'Tunneling/Forwarding'. | ||||||||
Added: | ||||||||
> > | Upgrading an existing HTML client installationIf you are upgrading an existing HTML client installation, the procedure is similar to installation except:
| |||||||
LocalConnectorAs mentioned above, you can suppress the requirement for the LocalConnector by changing the following line in "client.html": | ||||||||
Line: 122 to 128 | ||||||||
var sslEnabled = true; | ||||||||
Changed: | ||||||||
< < | For Unix/Linux hosts | |||||||
> > | For Unix/Linux hosts | |||||||
var sslPrivateKey = "/etc/pki/tls/private/example.key"; var sslCertificate = "/etc/pki/tls/certs/example.com.crt"; | ||||||||
Changed: | ||||||||
< < | var sslCertAuthority = "/etc/pki/tls/certs/gd_bundle.crt"; For Windows hosts var sslPrivateKey = "c:\\appx\\SSL\\example.key"; var sslCertificate = "c:\\appx\\SSL\\example.crt"; var sslCertAuthority = "c:\\appx\\SSL\\gd_bundle.crt" | |||||||
> > | var sslCertAuthority = "/etc/pki/tls/certs/gd_bundle.crt"; For Windows hosts var sslPrivateKey = "c:\\appx\\SSL\\example.key"; var sslCertificate = "c:\\appx\\SSL\\example.crt"; var sslCertAuthority = "c:\\appx\\SSL\\gd_bundle.crt" | |||||||
The SSL key values above are examples, you will need to change the file paths to point to your own SSL certificates. | ||||||||
Line: 165 to 171 | ||||||||
Troubleshooting | ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | Comments | |||||||
> > | Comments | |||||||
Changed: | ||||||||
< < | Read what other users have said about this page or add your own comments. | |||||||
> > | Read what other users have said about this page or add your own comments. | |||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
-- JeanNeron - 2015-12-18 |