Difference: AppxHTMLClient (9 vs. 10)

Revision 102014-12-15 - JeanNeron

Line: 1 to 1
 

APPX HTML Client

This page gives an overview of and installation instructions for the Appx HTML client.

Line: 24 to 24
  If your application does not require the ability to upload/download/open files on the desktop, you can turn this off (see Installation below).
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 l ocal connector is installed & runnning. 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.
>
>		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 & runnning. 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 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: 34 to 34
  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 connecions.
>
>		If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections.
  We have tested the HTML client on current versions of IE, Chrome and Safari.

Installation

Line: 51 to 51
  Note that this will appear to 'hang', but it is actually running and waiting for connections. Just minimize the DOS box and leave it running.
Changed:
<
<		We will automate this step, but for now you must manually start the connector upon first installation and after every reboot.
>
>		Eventually this will be a service, but for now you must manually start the connector upon first installation and after every reboot.
  Finally, you need to set the name of the host running the Appx Server Connector in the 'client.html' web page:
Line: 85 to 85
 
    • The user has to manually start the local connector every time they log in, or they can add the script to their programs that start automatically when the log in. The steps vary by Linux distribution, consult your documentation.

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 you would do the following:
>
>		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:
 

  • 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 /appxws/ ws://localhost:3014
    ProxyPass /appxwss/ wss://localhost:3014

Changed:
<
<

  • Change /var/www/html/appx/client.html settings to:

    appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11)
    appx-proxy-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-proxy-path = /appxws/
    appx-encryption = “aes”

 

  • Restart your web server

SSL

Line: 119 to 119
 
  • Check to make sure your Appx Server Connector is still running. If not, restart it via 'nohup ./node appxConnector.js &' for Linux or 'node appxConnector.js' for Windows.

Known Issues

Changed:
<
<		The following are the known problems with the HTML client. These are being worked and we hope to have them addressed by the final release.
>
>		The following are the known problems with the HTML client. We are continuing to enhance the client, watch the download page for updates!
 
Changed:
<
<
>
>
 
Changed:
<
<
>
>
 
Added:
>
>

(Add any from the 'Being Fixed' status!)

 

Comments:

Read what other users have said about this page or add your own comments.

View topic | History: r18 < r17 < r16 < r15 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback