Difference: AppxHTMLClient543 (13 vs. 14)

Revision 142016-03-31 - JeanNeron

Line: 1 to 1
 

APPX HTML Client 5.4.3/5.4.4

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

Changed:
<
<
>
>
 

Overview

The 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: 82 to 82
 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'.

Changed:
<
<

LocalConnector

>
>

LocalConnector

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

Changed:
<
<

LocalConnector Installation

>
>

LocalConnector Installation

  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:
  • Windows: Once the download is complete, run the installer. The local connector will be installed, started and Windows will be configured to automatically start on a reboot. No further action is required.
Line: 105 to 105
  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

Changed:
<
<

  • In Releases prior to 5.4.4, 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

  • In Releases to 5.4.4 and greater, 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:3014"
    ProxyPassReverse "/appxhttps/" "https://localhost:3014"
    ProxyPass "/appxhttp/" "http://localhost:3014"
    ProxyPassReverse "/appxhttp/" "http://localhost:3014"

>
>

  • In Releases prior to 5.4.4, 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"

  • In Releases to 5.4.4 and greater, 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:3014"
    ProxyPassReverse "/appxhttps" "https://localhost:3014"
    ProxyPass "/appxhttp" "http://localhost:3014"
    ProxyPassReverse "/appxhttp" "http://localhost:3014"

 

  • 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

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

 

SSL

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.

Line: 162 to 165
 Read what other users have said about this page or add your own comments.
Changed:
<
<
<--/commentPlugin-->
>
>
<--/commentPlugin-->
  -- JeanNeron - 2015-12-18
View topic | History: r19 < r18 < r17 < r16 | 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