Difference: AppxHTMLClient545 (5 vs. 6)

Revision 62016-10-21 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPX545Installation"

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 Clients

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.

Line: 108 to 108

If you are upgrading an existing HTML client installation, then you should check the following:

If you have customized 'client.html' you will have to re-do your customizations as it will be replaced when the new files are installed.
If you have created your own login page based on the standard 'client.html', compare your page and the standard 'client.html' for any changes that might be required.

Added:

>
>

Installing Multiple Server Connectors

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:

node appxConnector-install [appx | mongo] [appxport] [mongoport]

Examples:

node appxConnector-install appx 3020

Installs a server connector listening on port 3020

node appxConnector-install mongo 3021

Installs a mongo connector listening on port 3021

node appxConnector-install 3020 3030

Installs 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 Configuration

As 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:

In /etc/httpd/conf.modules.d/00-proxy.conf, add (if not already loaded):

LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
Create the /etc/httpd/conf.d/appx.conf file with the following lines (or just add these to httpd.conf):

ProxyPass "/appxwss" "wss://localhost:3014"
ProxyPassReverse "/appxwss" "wss://localhost:3014"
ProxyPass "/appxws" "ws://localhost:3014"
ProxyPassReverse "/appxws" "ws://localhost:3014"

ProxyPass "/appxhttps" "https://localhost:3015"
ProxyPassReverse "/appxhttps" "https://localhost:3015"
ProxyPass "/appxhttp" "http://localhost:3015"
ProxyPassReverse "/appxhttp" "http://localhost:3015"

Changed:

<
<

Change 'client.html' settings to:

appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11)
appx-proxy-port = “80"
appx-mongo-port = “80"
appx-proxy-path = /appxws/
appx-encryption = “aes”

>
>

Change 'client.html' settings to:

appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11)
appx-proxy-port = “80"
appx-mongo-port = “80"
appx-proxy-path = /appxws/

Restart your web server

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.

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:

<
<

You still use 'http://' to connect to the client page. The client will switch to the SSL connection once the page is loaded.
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.

>
>

You still use 'http://' to connect to the client page. The client will switch to the SSL connection once the page is loaded.
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.

Styles

Many 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.

View topic | History: r17 < r16 < r15 < r14 | More topic actions...