Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 46 to 46 | ||||||||
When uploading files, the web browser uploads the file into the Mongo database and returns a file path to your APPX process. You can use this path with .CLIENT UPLOAD FILE to transfer the file out of Mongo to the final destination. Note that using this method means you will not get the original path and file name as it existed on the user's computer. If you need this information, then you will have to use the Local Connector method. Files will stay in the Mongo database until the session ends, then they will be removed. | ||||||||
Changed: | ||||||||
< < | The Web Browser option does NOT allow you to invoke programs on the user's device (see .CLIENT LOAD URL). If you need this capability, you will have to use the Local Connector option. | |||||||
> > | The Web Browser option does NOT allow you to invoke programs on the user's device (see .CLIENT LOAD URL). If you need this capability, you will have to use the Local Connector option. | |||||||
NOTE: This option only works if you are connecting to an APPX server running Release 5.4.5 or higher.
Differences between ADC and HTML Clients |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 177 to 169 | ||||||||
Remove the leading // to uncomment the line. The '+Local' connector icon will be blue in this case. | ||||||||
Changed: | ||||||||
< < | The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F, however setting "appx-upload-without-local" = true will override this, even if the macro specifies the local connector should be used (@FULC=T). | |||||||
> > | The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F, however setting "appx-upload-without-local" = true will override this, even if the macro specifies the local connector should be used (@FULC=T). | |||||||
Tunneling/ForwardingIf you do not want to open ports 3014/3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 24 to 24 | ||||||||
Prerequisites | ||||||||
Changed: | ||||||||
< < | The server that will run the APPX Server Connector requires some additional software: | |||||||
> > | In addition to a 64 bit Operating System (Windows or Linux), the server that will run the APPX Server Connector requires some additional software: | |||||||
| ||||||||
Line: 54 to 54 | ||||||||
The HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client.
Requirements | ||||||||
Changed: | ||||||||
< < | You will need a web server, either Linux or Windows based. If you are going to use the Apache web server and you want to use a forwarding proxy, it must be version 2.4 or higher. We have tested IIS on Win 7 with success, earlier versions of IIS have not been tested. | |||||||
> > | You will need a web server, either Linux or Windows based (64 bit). If you are going to use the Apache web server and you want to use a forwarding proxy, it must be version 2.4 or higher. We have tested IIS on Win 7 with success, earlier versions of IIS have not been tested. | |||||||
The web server does not have to be on the same server as Appx. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5This 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: 88 to 89 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Installation | ||||||||
Line: 242 to 244 | ||||||||
Read what other users have said about this page or add your own comments.
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
-- JeanNeron - 2015-12-18 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5This 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: 47 to 47 | ||||||||
When uploading files, the web browser uploads the file into the Mongo database and returns a file path to your APPX process. You can use this path with .CLIENT UPLOAD FILE to transfer the file out of Mongo to the final destination. Note that using this method means you will not get the original path and file name as it existed on the user's computer. If you need this information, then you will have to use the Local Connector method. Files will stay in the Mongo database until the session ends, then they will be removed. The Web Browser option does NOT allow you to invoke programs on the user's device (see .CLIENT LOAD URL). If you need this capability, you will have to use the Local Connector option. | ||||||||
Added: | ||||||||
> > | NOTE: This option only works if you are connecting to an APPX server running Release 5.4.5 or higher. | |||||||
Differences between ADC and HTML ClientsThe HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client. | ||||||||
Line: 122 to 124 | ||||||||
There are various reasons why you would want to do this:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
By default the installer will install a server connector on port 3014 and a mongo connector on port 3015. The installer accepts the following arguments: node appxConnector-install [appx | mongo] [appxport] [mongoport] | ||||||||
Line: 240 to 242 | ||||||||
Read what other users have said about this page or add your own comments.
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
-- JeanNeron - 2015-12-18 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
APPX HTML Client 5.4.5This page gives installation instructions and an overview of the Appx HTML client. | ||||||||
Line: 243 to 243 | ||||||||
-- JeanNeron - 2015-12-18 \ No newline at end of file | ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5This 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: 37 to 37 | ||||||||
The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. | ||||||||
Changed: | ||||||||
< < | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off via <meta name="appx-local-required" content="false"> in the client.html page (see below). | |||||||
> > | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off via metas["appx-local-required"]["value"] = "false"; in the your 'appx-client-settings.js file (see below). | |||||||
Web BrowserThe other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones. | ||||||||
Line: 63 to 63 | ||||||||
1) Extract the Web Server File (webhost.zip) into the document folder for your web server. Depending on your web site layout, you may want to put this in its own folder within the web server documents, i.e., /var/www/html/appx. | ||||||||
Changed: | ||||||||
< < | 2) Set the name of the host running the Appx Server Connector in the 'client.html' web page: | |||||||
> > | 2) If this is a new installation, you must rename the appx-client-settingsTemplate.js file to appx-client-settings.js. This file is in the 'js' subdirectory. For example: | |||||||
Changed: | ||||||||
< < | <meta name="appx-proxy-host" content="HOSTNAME"> <!-- Server Connector hostname or web server if tunneling --> | |||||||
> > | [root@localhost]# cd js [root@localhost js]# mv appx-client-settingsTemplate.js appx-client-settings.js | |||||||
Changed: | ||||||||
< < | Change HOSTNAME to the name or IP address of the server running the Appx Server Connector. Do not use localhost unless you plan to run the HTML client on the same server as the Appx Server Connector, i.e., a testing/evaluation environment. | |||||||
> > | 3) If this is a new installation you must set the name of the host running the Appx Server Connector in the 'appx-client-settings.js' file you just renamed: | |||||||
Added: | ||||||||
> > | metas["appx-proxy-host"]["value"] = "localhost"; Change locahost to the name or IP address of the server running the Appx Server Connector. Do not use localhost unless you plan to run the HTML client on the same server as the Appx Server Connector, i.e., a testing/evaluation environment. You can also set any other meta tags that are unique to your installation. The 'appx-client-settings.js' file will never be replaced during an update, so the settings will remain until you change them. | |||||||
Installation - APPX Server Connector ComponentThe APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then ports 3014/3015 (the default port) needs to be open between the server connector machine and your HTML clients.PrerequisitesThe server that will run the APPX Server Connector requires some additional software: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 94 to 103 | ||||||||
[root@localhost ~]# cd /opt/appxConnectorNotice in this example the module 'string' is missing and the instructions on how to install it are displayed. If any modules are missing on your system, run the appropriate 'npm' command to install them, then re-run the install script. If all modules are present, the service will be created: | ||||||||
Changed: | ||||||||
< < | [root@localhost appxConnector]# node appxConnector-install.js | |||||||
> > |
[root@localhost appxConnector545]# node appxConnector-install.js Checking for required modules... | |||||||
4) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appx', and in Windows you can use the 'Services' control panel. 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 ports 3014/3015 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'. Post Installation if upgrading an existing HTML client installation | ||||||||
Line: 114 to 124 | ||||||||
There are various reasons why you would want to do this:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
By default the installer will install a server connector on port 3014 and a mongo connector on port 3015. The installer accepts the following arguments: | ||||||||
Added: | ||||||||
> > | ||||||||
node appxConnector-install [appx | mongo] [appxport] [mongoport] Examples: | ||||||||
Line: 130 to 144 | ||||||||
Installs a server connector on 3020 and a mongo connector on 3030. | ||||||||
Changed: | ||||||||
< < | You can then create different client.html pages using the different ports via setting "appx-proxy-port" and "appx-mongo-port" in each client.html page. If you are using port forwarding, then you'll have to create unique names and use those names in client.html instead (they all would use port 80). | |||||||
> > | You can then create different folders to contain the client.html pages using the different ports via setting "appx-proxy-port" and "appx-mongo-port" in each appx-client-settings.js file in each folder. If you are using port forwarding, then you'll have to create unique names and use those names instead (they all would use port 80). | |||||||
Local Connector or Web Browser ConfigurationAs mentioned above, you have a choice on how the HTML client should handle files sent to/from the browser. | ||||||||
Changed: | ||||||||
< < | By default, the HTML client will try to use the local connector. You can suppress the requirement for the Local Connector by changing the following line in "client.html": | |||||||
> > | By default, the HTML client will try to use the local connector. You can suppress the requirement for the Local Connector by uncommenting the following line in your appx-client-settings.js file: | |||||||
Changed: | ||||||||
< < | <meta name="appx-local-required" content="true" > | |||||||
> > | //metas["appx-local-required"]["value"] = "false"; | |||||||
Changed: | ||||||||
< < | Change the "true" to "false" to supress the requirement. | |||||||
> > | Remove the leading // to uncomment the line. | |||||||
If you do not turn off the Local Connector requirement as above, then when the 'client.html' page is loaded it will check to see if the local connector is running on the users desktop. If not, they will get a dialog box offering to download the local connector. The actual installation of the local connector varies by the O/S on the user's desktop:
| ||||||||
Line: 151 to 165 | ||||||||
| ||||||||
Changed: | ||||||||
< < | If you are going to use the Web Browser to handle files instead of the local connector, then turn off the requirement for a Local Connector as above, and change the following line in "client.html": | |||||||
> > | If you are going to use the Web Browser to handle files instead of the local connector, then turn off the requirement for a Local Connector as above, and uncomment the following line in your appx-client-settings.js file: | |||||||
Changed: | ||||||||
< < | <meta name="appx-upload-without-local" content="false" > | |||||||
> > | //metas["appx-upload-without-local"]["value"] = "true"; | |||||||
Changed: | ||||||||
< < | Change the "false" to "true" to force the HTML client to use the Web Browser to handle files. The '+Local' connector icon will be blue in this case. | |||||||
> > | Remove the leading // to uncomment the line. The '+Local' connector icon will be blue in this case. | |||||||
The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F, however setting "appx-upload-without-local" = true will override this, even if the macro specifies the local connector should be used (@FULC=T).
Tunneling/Forwarding | ||||||||
Line: 163 to 177 | ||||||||
If you do not want to open ports 3014/3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 172 to 186 | ||||||||
If you are running a secure web server (https), you can configure the Appx HTML client to use your SSL connection. Your web server must be configured to accept both SSL (https:) and non-SSL (http:) connections. | ||||||||
Changed: | ||||||||
< < | Change your "client.html" settings as follows (this file is located on your web server): | |||||||
> > | Change the following in your appx-client-settings.js file: | |||||||
appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11) appx-proxy-port = “443" appx-proxy-path = /appxwss/ appx-encryption = “ssl” | ||||||||
Line: 213 to 227 | ||||||||
It is possible to have different CUSTOM.css style sheets. Install the client web server files as normal, then follow these steps:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Troubleshooting
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 232 to 246 | ||||||||
Read what other users have said about this page or add your own comments.
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
-- JeanNeron - 2015-12-18 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 37 to 37 | ||||||||
The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. | ||||||||
Changed: | ||||||||
< < | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means file upload/download will be handled via the Browser and not the Local Connector via setting <meta name="appx-upload-without-local" content="false" > to true in the client.html page (see below). | |||||||
> > | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off via <meta name="appx-local-required" content="false"> in the client.html page (see below). | |||||||
Web BrowserThe other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 37 to 37 | ||||||||
The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. | ||||||||
Changed: | ||||||||
< < | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off completely via setting <meta name="appx-upload-without-local" content="false" > to true in the client.html page (see below). | |||||||
> > | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means file upload/download will be handled via the Browser and not the Local Connector via setting <meta name="appx-upload-without-local" content="false" > to true in the client.html page (see below). | |||||||
Web BrowserThe other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones. | ||||||||
Line: 94 to 96 | ||||||||
[root@localhost ~]# cd /opt/appxConnectorNotice in this example the module 'string' is missing and the instructions on how to install it are displayed. If any modules are missing on your system, run the appropriate 'npm' command to install them, then re-run the install script. If all modules are present, the service will be created: | ||||||||
Added: | ||||||||
> > | ||||||||
[root@localhost appxConnector]# node appxConnector-install.js | ||||||||
Changed: | ||||||||
< < | 4) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appxConnector.js', and in Windows you can use the 'Services' control panel. | |||||||
> > | 4) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appx', and in Windows you can use the 'Services' control panel. | |||||||
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: | ||||||||
Line: 157 to 164 | ||||||||
Change the "false" to "true" to force the HTML client to use the Web Browser to handle files. The '+Local' connector icon will be blue in this case. | ||||||||
Changed: | ||||||||
< < | The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F | |||||||
> > | The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F, however setting "appx-upload-without-local" = true will override this, even if the macro specifies the local connector should be used (@FULC=T). | |||||||
Tunneling/ForwardingIf you do not want to open ports 3014/3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following: | ||||||||
Line: 170 to 177 | ||||||||
# setsebool -P httpd_can_network_connect 1
SSL | ||||||||
Changed: | ||||||||
< < | If you are running a secure web server (https), you can configure the Appx HTML client to use your SSL connection. Your web server must to configured to accept both SSL (https:) and non-SSL (http:) connections. | |||||||
> > | If you are running a secure web server (https), you can configure the Appx HTML client to use your SSL connection. Your web server must be configured to accept both SSL (https:) and non-SSL (http:) connections. | |||||||
Change your "client.html" settings as follows (this file is located on your web server): |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 110 to 110 | ||||||||
Installing Multiple Server Connectors | ||||||||
Changed: | ||||||||
< < | You can install multple server connectors, each listening on different ports. By default the installer will install a server connector on port 3014 and a mongo connector on port 3015. The installer accepts the following arguments: | |||||||
> > | You can install multple server connectors, each listening on different ports. | |||||||
Added: | ||||||||
> > | There are various reasons why you would want to do this:
| |||||||
node appxConnector-install [appx | mongo] [appxport] [mongoport] Examples: | ||||||||
Line: 123 to 126 | ||||||||
node appxConnector-install mongo 3021Installs a mongo connector listening on port 3021 | ||||||||
Deleted: | ||||||||
< < | ||||||||
node appxConnector-install 3020 3030 | ||||||||
Changed: | ||||||||
< < | Installs a server connector on 3020 and an mongo connector on 3030 | |||||||
> > | Installs a server connector on 3020 and a mongo connector on 3030. | |||||||
Changed: | ||||||||
< < | You can then create different client.html pages using the different ports via setting "appx-proxy-port" and "appx-mongo-port" in each client.html page. If you are using port forwarding, then you'll have to create unique names and use those name in client.html. | |||||||
> > | You can then create different client.html pages using the different ports via setting "appx-proxy-port" and "appx-mongo-port" in each client.html page. If you are using port forwarding, then you'll have to create unique names and use those names in client.html instead (they all would use port 80). | |||||||
Local Connector or Web Browser ConfigurationAs mentioned above, you have a choice on how the HTML client should handle files sent to/from the browser. | ||||||||
Line: 163 to 165 | ||||||||
| ||||||||
Deleted: | ||||||||
< < | If you are using Windows IIS for your web sever platform, and do not wish to expose ports 3014/3015 then you'll need IIS 8.0 or greater to support Websockets with IIS ARR installed and the URL Rewrite module enabled. A web.config similar to the following should work.
<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <rewrite> <rules> <rule name="ReverseProxyInboundRule1"> <match url="appxws" /> <action type="Rewrite" url="http://localhost:3014/{R:0}" /> </rule> <rule name="ReverseProxyInboundRule2"> <match url="appxhttp" /> <action type="Rewrite" url="http://localhost:3015/{R:0}" /> </rule> </rules> </rewrite> </system.webServer> </configuration> | |||||||
NOTE: If you are running selinux security on your server, you will have to configure it so that apache can initiate an outgoing network connections to the web socket server port. Use the following command: # setsebool -P httpd_can_network_connect 1 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 30 to 30 | ||||||||
See below for details on installing these packages.
Local Connector vs Web Browser | ||||||||
Changed: | ||||||||
< < | There are 2 ways of uploading/downloading/displaying files with the HTML client. | |||||||
> > | There are 2 ways the HTML client can interact with processes on the APPX Server (uploading/downloading/displaying files, invoking programs on the client). | |||||||
Local Connector | ||||||||
Changed: | ||||||||
< < | The Local Connector is a small 'helper' program that allows you to upload/download and open files on the users desktop, similar to the way it can be done with the APPX Desktop Client. By default, the HTML client will check to see if the local connector program is running when the user logs in. If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. If your application does not require the ability to upload/download/open files on the desktop, or you want to use the Browser based method, you can turn this off (see Installation below). | |||||||
> > | The Local Connector is a small 'helper' program that allows you to upload/download and open files on the users desktop, similar to the way it can be done with the APPX Desktop Client. By default, the HTML client will check to see if the local connector program is running when the user logs in. If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. If your application does not require the ability to upload/download/open files on the users device or invoke programs on the user's device you can turn this off (see Installation below). | |||||||
The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. | ||||||||
Line: 45 to 45 | ||||||||
The file only remains in the Mongo Database for 5 seconds after it is retrieved, so if the user refreshes that tab they will get error 404. When uploading files, the web browser uploads the file into the Mongo database and returns a file path to your APPX process. You can use this path with .CLIENT UPLOAD FILE to transfer the file out of Mongo to the final destination. Note that using this method means you will not get the original path and file name as it existed on the user's computer. If you need this information, then you will have to use the Local Connector method. Files will stay in the Mongo database until the session ends, then they will be removed. | ||||||||
Added: | ||||||||
> > | The Web Browser option does NOT allow you to invoke programs on the user's device (see .CLIENT LOAD URL). If you need this capability, you will have to use the Local Connector option. | |||||||
Differences between ADC and HTML ClientsThe HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client. | ||||||||
Line: 108 to 108 | ||||||||
If you are upgrading an existing HTML client installation, then you should check the following:
| ||||||||
Added: | ||||||||
> > | Installing Multiple Server ConnectorsYou can install multple server connectors, each listening on different ports. By default the installer will install a server connector on port 3014 and a mongo connector on port 3015. The installer accepts the following arguments: node appxConnector-install [appx | mongo] [appxport] [mongoport] Examples:node appxConnector-install appx 3020Installs a server connector listening on port 3020 node appxConnector-install mongo 3021Installs a mongo connector listening on port 3021 node appxConnector-install 3020 3030Installs a server connector on 3020 and an mongo connector on 3030 You can then create different client.html pages using the different ports via setting "appx-proxy-port" and "appx-mongo-port" in each client.html page. If you are using port forwarding, then you'll have to create unique names and use those name in client.html. | |||||||
Local Connector or Web Browser ConfigurationAs mentioned above, you have a choice on how the HTML client should handle files sent to/from the browser. | ||||||||
Line: 140 to 161 | ||||||||
If you do not want to open ports 3014/3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> | ||||||||
Line: 155 to 175 | ||||||||
| ||||||||
Changed: | ||||||||
< < | | |||||||
> > | | |||||||
Line: 184 to 204 | ||||||||
Once you have made the above changes, restart the Server Connector and refresh the Appx Login page in your browser (if it was still loaded when you made these changes). NOTES: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
StylesMany aspects of the presentation of the Appx Client are controlled by the APPX.css style sheet in the 'css' folder. If you are familiar with working with style sheets, feel free to experiment with different settings, however those changes will be lost the next time the client is updated. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 33 to 33 | ||||||||
There are 2 ways of uploading/downloading/displaying files with the HTML client.
Local Connector | ||||||||
Changed: | ||||||||
< < | The Local Connector is a small 'helper' program that allows you to upload/download and open files on the users desktop, similar to the way it can be done with the APPX Desktop Client. By default, the HTML client will check to see if the local connector program is running when the user logs in (is this true?). If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. If your application does not require the ability to upload/download/open files on the desktop, or you want to use the Browser based method, you can turn this off (see Installation below). | |||||||
> > | The Local Connector is a small 'helper' program that allows you to upload/download and open files on the users desktop, similar to the way it can be done with the APPX Desktop Client. By default, the HTML client will check to see if the local connector program is running when the user logs in. If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. If your application does not require the ability to upload/download/open files on the desktop, or you want to use the Browser based method, you can turn this off (see Installation below). | |||||||
The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. | ||||||||
Changed: | ||||||||
< < | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. | |||||||
> > | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off completely via setting <meta name="appx-upload-without-local" content="false" > to true in the client.html page (see below). | |||||||
Web BrowserThe other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones. | ||||||||
Line: 131 to 132 | ||||||||
<meta name="appx-upload-without-local" content="false" > | ||||||||
Changed: | ||||||||
< < | Change the "false" to "true" to force the HTML client to use the Web Browser to handle files. | |||||||
> > | Change the "false" to "true" to force the HTML client to use the Web Browser to handle files. The '+Local' connector icon will be blue in this case. | |||||||
The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F
Tunneling/Forwarding |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 44 to 44 | ||||||||
The file only remains in the Mongo Database for 5 seconds after it is retrieved, so if the user refreshes that tab they will get error 404. | ||||||||
Changed: | ||||||||
< < | can you still drag & drop w/o the local connector? How do uploads work without a local connector? | |||||||
> > | When uploading files, the web browser uploads the file into the Mongo database and returns a file path to your APPX process. You can use this path with .CLIENT UPLOAD FILE to transfer the file out of Mongo to the final destination. Note that using this method means you will not get the original path and file name as it existed on the user's computer. If you need this information, then you will have to use the Local Connector method. Files will stay in the Mongo database until the session ends, then they will be removed. | |||||||
Differences between ADC and HTML ClientsThe HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client. | ||||||||
Line: 141 to 139 | ||||||||
If you do not want to open ports 3014/3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
<?xml version="1.0" encoding="UTF-8"?> |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5 | ||||||||
Line: 42 to 42 | ||||||||
The other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones. | ||||||||
Changed: | ||||||||
< < | The file does not remain in the Mongo Database indefinitely (how long??), so if the user refreshes that tab they will get error 404. | |||||||
> > | The file only remains in the Mongo Database for 5 seconds after it is retrieved, so if the user refreshes that tab they will get error 404. | |||||||
can you still drag & drop w/o the local connector? | ||||||||
Line: 56 to 56 | ||||||||
The web server does not have to be on the same server as Appx. | ||||||||
Changed: | ||||||||
< < | If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections. Note: if you are trying to use SSL with the local connector running you will receive an error saying that part of your connection is not secure. The local connector does not have the functionality to talk to the browser using SSL. Is this an error that prevents it from running, or just an informational message? | |||||||
> > | If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections. Note: if you are trying to use SSL with the local connector running you will receive an error saying that part of your connection is not secure. The local connector does not have the functionality to talk to the browser using SSL. This is just an informational message. | |||||||
If you are going to run the APPX Server Connector on a Windows server, make sure all patches have been applied. In particular, https://support.microsoft.com/en-us/kb/2731284 will break tables if it is not applied
Installation - Web Server Component | ||||||||
Line: 71 to 71 | ||||||||
Installation - APPX Server Connector Component | ||||||||
Changed: | ||||||||
< < | The APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then port 3015 (the default port) needs to be open between the server connector machine and your HTML clients. | |||||||
> > | The APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then ports 3014/3015 (the default port) needs to be open between the server connector machine and your HTML clients. | |||||||
PrerequisitesThe server that will run the APPX Server Connector requires some additional software: | ||||||||
Line: 104 to 103 | ||||||||
http://192.168.0.15/appx/client.html | ||||||||
Changed: | ||||||||
< < | You must open port 3015 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'. | |||||||
> > | You must open ports 3014/3015 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'. | |||||||
Post Installation if upgrading an existing HTML client installationIf you are upgrading an existing HTML client installation, then you should check the following: | ||||||||
Line: 114 to 113 | ||||||||
As mentioned above, you have a choice on how the HTML client should handle files sent to/from the browser. | ||||||||
Changed: | ||||||||
< < | By default, the HTML client will try to use the local connector (is this true?). You can suppress the requirement for the Local Connector by changing the following line in "client.html": | |||||||
> > | By default, the HTML client will try to use the local connector. You can suppress the requirement for the Local Connector by changing the following line in "client.html": | |||||||
<meta name="appx-local-required" content="true" > | ||||||||
Line: 134 to 133 | ||||||||
<meta name="appx-upload-without-local" content="false" > | ||||||||
Changed: | ||||||||
< < | Change the "true" to "false" to force the HTML client to use the Web Browser to handle files. | |||||||
> > | Change the "false" to "true" to force the HTML client to use the Web Browser to handle files. | |||||||
The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F
Tunneling/Forwarding | ||||||||
Changed: | ||||||||
< < | If you do not want to open port 3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following: | |||||||
> > | If you do not want to open ports 3014/3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | If you are using Windows IIS for your web sever platform, and do not wish to expose TCP 3015 then you'll need IIS 8.0 or greater to support Websockets with IIS ARR installed and the URL Rewrite module enabled. A web.config similar to the following should work. | |||||||
> > | If you are using Windows IIS for your web sever platform, and do not wish to expose ports 3014/3015 then you'll need IIS 8.0 or greater to support Websockets with IIS ARR installed and the URL Rewrite module enabled. A web.config similar to the following should work. | |||||||
<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX HTML Client 5.4.5This 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: 14 to 14 | ||||||||
The client will support SSL connections if your web server is configured appropriately. If not, the client will use its own built in AES encryption but be aware that this is not sufficient to protect sensitive data. The Appx HTML client consists of two modules: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Note that Appx does not have to be running on the same server as your web server, and the APPX Server Connector does not have be on the same server as either Appx or your web server. This gives you maximum flexibility in configuring your installation. Once the HTML client is working, you can connect to any Appx 5.4+ server, just as you can with the Appx Desktop Client. Due to the engine changes that were made in 5.4 to support the HTML client, you cannot connect to an earlier Appx engine. | ||||||||
Added: | ||||||||
> > | We have tested the HTML client on current versions of IE, Chrome, Firefox and Safari. | |||||||
Prerequisites | ||||||||
Changed: | ||||||||
< < | The server that will run the APPX Server Connector requires 'nodejs' (https://nodejs.org/). In Release 5.4.4 and higher you also need the Mongo Database (https://www.mongodb.org/). See below for details on installing these packages.
Local Connector | |||||||
> > | The server that will run the APPX Server Connector requires some additional software:
Local Connector vs Web BrowserThere are 2 ways of uploading/downloading/displaying files with the HTML client.Local ConnectorThe Local Connector is a small 'helper' program that allows you to upload/download and open files on the users desktop, similar to the way it can be done with the APPX Desktop Client. By default, the HTML client will check to see if the local connector program is running when the user logs in (is this true?). If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. If your application does not require the ability to upload/download/open files on the desktop, or you want to use the Browser based method, you can turn this off (see Installation below). The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. | |||||||
Changed: | ||||||||
< < | Because of the tighter security in web browsers, it is not possible for HTML 5/javascript to seamlessly upload, download or open files unassisted on the users desktop the way it can be done with the Appx Desktop Client. To address this, the HTML client includes a small 'helper' program that supports this. This is called the 'LocalConnector'. By default, the HTML client will check to see if the local connector program is running when the user logs in. If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. | |||||||
> > | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector.
Web Browser | |||||||
Changed: | ||||||||
< < | If your application does not require the ability to upload/download/open files on the desktop, you can turn this off (see Installation below). | |||||||
> > | The other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones. | |||||||
Changed: | ||||||||
< < | There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. The 'Remote' connector refers to the connection to the Appx Server Connector. This must be green with a "+" for any connection to work. | |||||||
> > | The file does not remain in the Mongo Database indefinitely (how long??), so if the user refreshes that tab they will get error 404. can you still drag & drop w/o the local connector? How do uploads work without a local connector? | |||||||
Differences between ADC and HTML ClientsThe HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client. | ||||||||
Line: 39 to 56 | ||||||||
The web server does not have to be on the same server as Appx. | ||||||||
Changed: | ||||||||
< < | If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections. | |||||||
> > | If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections. Note: if you are trying to use SSL with the local connector running you will receive an error saying that part of your connection is not secure. The local connector does not have the functionality to talk to the browser using SSL. Is this an error that prevents it from running, or just an informational message? | |||||||
If you are going to run the APPX Server Connector on a Windows server, make sure all patches have been applied. In particular, https://support.microsoft.com/en-us/kb/2731284 will break tables if it is not applied | ||||||||
Deleted: | ||||||||
< < | We have tested the HTML client on current versions of IE, Chrome, Firefox and Safari. | |||||||
Installation - Web Server Component1) Extract the Web Server File (webhost.zip) into the document folder for your web server. Depending on your web site layout, you may want to put this in its own folder within the web server documents, i.e., /var/www/html/appx. | ||||||||
Line: 52 to 67 | ||||||||
<meta name="appx-proxy-host" content="HOSTNAME"> <!-- Server Connector hostname or web server if tunneling --> | ||||||||
Changed: | ||||||||
< < | Change HOSTNAME to the name or IP address of the server running the Appx Server Connector. Do not use localhost you plan to run the HTML client on the same server as the Appx Server Connector, i.e., a testing/evaluation environment. | |||||||
> > | Change HOSTNAME to the name or IP address of the server running the Appx Server Connector. Do not use localhost unless you plan to run the HTML client on the same server as the Appx Server Connector, i.e., a testing/evaluation environment. | |||||||
Installation - APPX Server Connector Component | ||||||||
Changed: | ||||||||
< < | The APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then port 3014 (the default port) needs to be open between the server connector machine and your HTML clients. | |||||||
> > | The APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then port 3015 (the default port) needs to be open between the server connector machine and your HTML clients. | |||||||
Prerequisites | ||||||||
Changed: | ||||||||
< < | 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): | |||||||
> > | The server that will run the APPX Server Connector requires some additional software:
| |||||||
Changed: | ||||||||
< < | curl --silent --location https://rpm.nodesource.com/setup | bash -yum install nodejs | |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | 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 | ||||||||
Changed: | ||||||||
< < | 1) Extract the Appx Server Connector to a location of your choice. A folder in the /opt directory would be a good choice on a Linux server. Once the software is extracted, run the appxConnector-install.js script. This should be run as 'root' on Linux/Unix systems, and as an Administrator on Windows systems. This will check your system for the required modules. To run the script, open a terminal or DOS window and navigate to the folder where you installed the Appx Server Connector, then invoke the script via 'node':
[root@localhost ~]# cd /opt/appxConnector543 | |||||||
> > | 1) If you are upgrading from a prior release, you must uninstall the old Server Connector first by running 'appxConnector-uninstall.js'. You must do this before installing the new connector. This should be run as 'root' on Linux/Unix systems, and as an Administrator on Windows systems. To run the script, open a terminal or DOS window and navigate to the folder where you installed the Appx Server Connector, then invoke the script via 'node':
[root@localhost appxConnector]# node appxConnector-uninstall.js Using default mode: systemd Uninstall complete. The service exists: false [root@localhost appxConnector]#2) Extract the 5.4.5 Appx Server Connector to a location of your choice. A folder in the /opt directory would be a good choice on a Linux server. 3) Run the appxConnector-install.js script. This should also be run as 'root' on Linux/Unix systems, or as an Administrator on Windows systems. This will check your system for the required modules. To run the script, open a terminal or DOS window and navigate to the folder where you installed the Appx Server Connector, then invoke the script via 'node': [root@localhost ~]# cd /opt/appxConnector | |||||||
Notice in this example the module 'string' is missing and the instructions on how to install it are displayed. If any modules are missing on your system, run the appropriate 'npm' command to install them, then re-run the install script. If all modules are present, the service will be created: | ||||||||
Deleted: | ||||||||
< < | [root@localhost appxConnector543]# node appxConnector-install.js | |||||||
Changed: | ||||||||
< < | 2) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appxConnector.js', and in Windows you can use the 'Services' control panel. | |||||||
> > | [root@localhost appxConnector]# node appxConnector-install.js4) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appxConnector.js', and in Windows you can use the 'Services' control panel. | |||||||
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 | |||||||
Changed: | ||||||||
< < | 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'. Upgrading an existing HTML client installation | |||||||
> > | You must open port 3015 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'. Post Installation if upgrading an existing HTML client installation | |||||||
Changed: | ||||||||
< < | If you are upgrading an existing HTML client installation, the procedure is similar to installation except:
LocalConnector | |||||||
> > | If you are upgrading an existing HTML client installation, then you should check the following:
Local Connector or Web Browser Configuration | |||||||
Changed: | ||||||||
< < | As mentioned above, you can suppress the requirement for the LocalConnector by changing the following line in "client.html": | |||||||
> > | As mentioned above, you have a choice on how the HTML client should handle files sent to/from the browser. By default, the HTML client will try to use the local connector (is this true?). You can suppress the requirement for the Local Connector by changing the following line in "client.html": | |||||||
<meta name="appx-local-required" content="true" > Change the "true" to "false" to supress the requirement. | ||||||||
Deleted: | ||||||||
< < | LocalConnector Installation | |||||||
Changed: | ||||||||
< < | If you do not turn off the LocalConnector requirement as above, then when the 'client.html' page is loaded it will check to see if the local connector is running on the users desktop. If not, they will get a dialog box offering to download the local connector. The actual installation of the local connector varies by the O/S on the user's desktop: | |||||||
> > | If you do not turn off the Local Connector requirement as above, then when the 'client.html' page is loaded it will check to see if the local connector is running on the users desktop. If not, they will get a dialog box offering to download the local connector. The actual installation of the local connector varies by the O/S on the user's desktop: | |||||||
| ||||||||
Line: 106 to 130 | ||||||||
| ||||||||
Added: | ||||||||
> > | If you are going to use the Web Browser to handle files instead of the local connector, then turn off the requirement for a Local Connector as above, and change the following line in "client.html": <meta name="appx-upload-without-local" content="false" > Change the "true" to "false" to force the HTML client to use the Web Browser to handle files. The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F | |||||||
Tunneling/Forwarding | ||||||||
Changed: | ||||||||
< < | If you do not want to open port 3014 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following: | |||||||
> > | If you do not want to open port 3015 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | If you are using Windows IIS for your web sever platform, and do not wish to expose TCP 3014 then you'll need IIS 8.0 or greater to support Websockets with IIS ARR installed and the URL Rewrite module enabled. A web.config similar to the following should work. | |||||||
> > | If you are using Windows IIS for your web sever platform, and do not wish to expose TCP 3015 then you'll need IIS 8.0 or greater to support Websockets with IIS ARR installed and the URL Rewrite module enabled. A web.config similar to the following should work. | |||||||
<?xml version="1.0" encoding="UTF-8"?> <configuration> | ||||||||
Line: 149 to 179 | ||||||||
var sslEnabled = true; | ||||||||
Changed: | ||||||||
< < | For Unix/Linux hosts var sslPrivateKey = "/etc/pki/tls/private/example.key"; var sslCertificate = "/etc/pki/tls/certs/example.com.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" | |||||||
> > | For Unix/Linux hosts var sslPrivateKey = "/etc/pki/tls/private/example.key"; var sslCertificate = "/etc/pki/tls/certs/example.com.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. Once you have made the above changes, restart the Server Connector and refresh the Appx Login page in your browser (if it was still loaded when you made these changes). | ||||||||
Changed: | ||||||||
< < | NOTE: You still use 'http://' to connect to the client page. The client will switch to the SSL connection once the page is loaded. | |||||||
> > | NOTES:
| |||||||
StylesMany aspects of the presentation of the Appx Client are controlled by the APPX.css style sheet in the 'css' folder. If you are familiar with working with style sheets, feel free to experiment with different settings, however those changes will be lost the next time the client is updated. | ||||||||
Line: 182 to 207 | ||||||||
} This will set the background color of edittable fields to 'pink' and the default background color to 'white'. | ||||||||
Changed: | ||||||||
< < | Styles by website (5.4.4.1 HTML Client & up only) | |||||||
> > | Styles by website | |||||||
It is possible to have different CUSTOM.css style sheets. Install the client web server files as normal, then follow these steps: | ||||||||
Line: 195 to 220 | ||||||||
| ||||||||
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 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
APPX HTML Client 5.4.5This page gives installation instructions and an overview of the Appx HTML client.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. In this release, you can only run the applications, you cannot design them. Specifically, the ILF editor, old ILF Debugger and Image Editor are not supported. You may be able to work in Application Design so long as you avoid those. The client will support SSL connections if your web server is configured appropriately. If not, the client will use its own built in AES encryption but be aware that this is not sufficient to protect sensitive data. The Appx HTML client consists of two modules:
Local ConnectorBecause of the tighter security in web browsers, it is not possible for HTML 5/javascript to seamlessly upload, download or open files unassisted on the users desktop the way it can be done with the Appx Desktop Client. To address this, the HTML client includes a small 'helper' program that supports this. This is called the 'LocalConnector'. By default, the HTML client will check to see if the local connector program is running when the user logs in. If it is not running, it will offer to install it, and if the user cancels they will be nagged the next time they log in. If your application does not require the ability to upload/download/open files on the desktop, you can turn this off (see Installation below). There is a 'Connectivity' indicator in the lower right corner of the browser window with the words 'Remote' and 'Local'. If 'Local' is in green with a "+", it means the local connector is installed & running. Red means the connector is not installed. The 'Remote' connector refers to the connection to the Appx Server Connector. This must be green with a "+" for any connection to work.Differences between ADC and HTML ClientsThe HTML client has a different presentation for most non-Appx elements such as Date Choosers, File Upload/download dialog boxes, Tables, etc. The goal of the HTML client was to replicate the presentation of your screens as accurately as possible as far as the Appx elements are concerned (i.e., the widgets and fields you use in the Image Editor). Since we use different 3rd party tools and runtimes for other elements, they will look different compared to the Appx Desktop Client.RequirementsYou will need a web server, either Linux or Windows based. If you are going to use the Apache web server and you want to use a forwarding proxy, it must be version 2.4 or higher. We have tested IIS on Win 7 with success, earlier versions of IIS have not been tested. The web server does not have to be on the same server as Appx. If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections. If you are going to run the APPX Server Connector on a Windows server, make sure all patches have been applied. In particular, https://support.microsoft.com/en-us/kb/2731284 will break tables if it is not applied We have tested the HTML client on current versions of IE, Chrome, Firefox and Safari.Installation - Web Server Component1) Extract the Web Server File (webhost.zip) into the document folder for your web server. Depending on your web site layout, you may want to put this in its own folder within the web server documents, i.e., /var/www/html/appx. 2) Set the name of the host running the Appx Server Connector in the 'client.html' web page: <meta name="appx-proxy-host" content="HOSTNAME"> <!-- Server Connector hostname or web server if tunneling --> Change HOSTNAME to the name or IP address of the server running the Appx Server Connector. Do not use localhost you plan to run the HTML client on the same server as the Appx Server Connector, i.e., a testing/evaluation environment.Installation - APPX Server Connector ComponentThe APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then port 3014 (the default port) needs to be open between the server connector machine and your HTML clients.PrerequisitesAll 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): curl --silent --location https://rpm.nodesource.com/setup | bash -yum install nodejsTo 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/ Installation1) Extract the Appx Server Connector to a location of your choice. A folder in the /opt directory would be a good choice on a Linux server. Once the software is extracted, run the appxConnector-install.js script. This should be run as 'root' on Linux/Unix systems, and as an Administrator on Windows systems. This will check your system for the required modules. To run the script, open a terminal or DOS window and navigate to the folder where you installed the Appx Server Connector, then invoke the script via 'node':[root@localhost ~]# cd /opt/appxConnector543Notice in this example the module 'string' is missing and the instructions on how to install it are displayed. If any modules are missing on your system, run the appropriate 'npm' command to install them, then re-run the install script. If all modules are present, the service will be created: [root@localhost appxConnector543]# node appxConnector-install.js2) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appxConnector.js', and in Windows you can use the 'Services' control panel. 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: 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'. 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": <meta name="appx-local-required" content="true" > Change the "true" to "false" to supress the requirement.LocalConnector InstallationIf you do not turn off the LocalConnector requirement as above, then when the 'client.html' page is loaded it will check to see if the local connector is running on the users desktop. If not, they will get a dialog box offering to download the local connector. The actual installation of the local connector varies by the O/S on the user's desktop:
Tunneling/ForwardingIf you do not want to open port 3014 and would rather use port 80, you can use forwarding instead. For example, to configure Apache 2.4 on Linux you would do the following:
<?xml version="1.0" encoding="UTF-8"?> <configuration> <system.webServer> <rewrite> <rules> <rule name="ReverseProxyInboundRule1"> <match url="appxws" /> <action type="Rewrite" url="http://localhost:3014/{R:0}" /> </rule> <rule name="ReverseProxyInboundRule2"> <match url="appxhttp" /> <action type="Rewrite" url="http://localhost:3014/{R:0}" /> </rule> </rules> </rewrite> </system.webServer> </configuration>NOTE: If you are running selinux security on your server, you will have to configure it so that apache can initiate an outgoing network connections to the web socket server port. Use the following command: # setsebool -P httpd_can_network_connect 1 SSLIf you are running a secure web server (https), you can configure the Appx HTML client to use your SSL connection. Your web server must to configured to accept both SSL (https:) and non-SSL (http:) connections. Change your "client.html" settings as follows (this file is located on your web server): appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11)appx-proxy-port = “443" appx-proxy-path = /appxwss/ appx-encryption = “ssl” Change your "appxConnector.js" as follows (this file is located on your APPX Server Connector server): var sslEnabled = true; For Unix/Linux hosts var sslPrivateKey = "/etc/pki/tls/private/example.key"; var sslCertificate = "/etc/pki/tls/certs/example.com.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. Once you have made the above changes, restart the Server Connector and refresh the Appx Login page in your browser (if it was still loaded when you made these changes). NOTE: You still use 'http://' to connect to the client page. The client will switch to the SSL connection once the page is loaded. StylesMany aspects of the presentation of the Appx Client are controlled by the APPX.css style sheet in the 'css' folder. If you are familiar with working with style sheets, feel free to experiment with different settings, however those changes will be lost the next time the client is updated. Instead, you can add a CUSTOM.css style sheet with your own settings. This should be located in the same folder as APPX.css and will override the standard settings in the HTML client. For example: input { background-color: pink; } .appxbox { background-color: white; } This will set the background color of edittable fields to 'pink' and the default background color to 'white'.Styles by website (5.4.4.1 HTML Client & up only)It is possible to have different CUSTOM.css style sheets. Install the client web server files as normal, then follow these steps:
Troubleshooting
CommentsRead what other users have said about this page or add your own comments.-- JeanNeron - 2015-12-18 |