Difference: AppxHTMLClient (2 vs. 3)

Revision 32014-11-11 - JeanNeron

Line: 1 to 1
 

APPX HTML Client

This page gives an overview of and installation instructions for 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. In this release, you can only run the applications, you cannot design them. Specifically, the ILF editor and Image Editor are not supported. You may be able to work in Application Design so long as you avoid those 2 editors.

Line: 13 to 13
 The Appx HTML client consists of two modules:

  • Web Server Files. These are the javascipt libraries and style sheets that make up the HTML client. These must be installed in your web server's document directory. These files are platform independant.
Changed:
<
<
  • APPX Server connector. This is a small javascript library that connects the web server to the actual Appx engine. There is a Server Connector for each platform on which Appx runs.
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 maxium flexibility in configuring your installation.
>
>
  • APPX Server connector. This is a small javascript library that connects the client running in your browser to the actual Appx engine. The Appx Server Connector is platform specific, you will need the one that matches the O/S under which your web server is running.
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 maxium 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.

Requirements

Changed:
<
<		You will need a web server, either Linux or Windows based. If you are going to use the Apache web server, 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. 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: 28 to 28
  First 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 it's own folder within the web server documents, i.e., /var/www/html/appx.
Changed:
<
<		Next, extract the Appx Server Connector to a location of your choice. This is the software that will connect your web server to the Appx Login Manager. A folder in the /opt directory would be a good choice on a Linux server. Once the software is extracted, you must manually start the connector running. For example, if you installed the connector in /opt/appxConnector, then you would (as root):
>
>		Next, extract the Appx Server Connector to a location of your choice. This is the software that will connect your browser client to the Appx Login Manager. A folder in the /opt directory would be a good choice on a Linux server. Once the software is extracted, you must manually start the connector running. For example, if you installed the connector in /opt/appxConnector, then you would (as root):
  # cd /opt/appxConnector
# nohup ./node appxConnector.js &
Line: 46 to 46
  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:3014

Tunneling

>
>		http://192.168.0.15/appx/client.html
 
Changed:
<
<		If you do not want to open port 3014 and would rather use port 80, you can use web sockets instead. For example, to configure Apache 2.4 you would do the following:
>
>		You must open port 3014 on your web server for this connection to work. If you do not want to open any new ports on your web server, see the next section 'Tunneling'.

Tunneling/Forwarding

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:

 

  • 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

  • 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”

Line: 76 to 78
 

Known Issues

Changed:
<
<		The following are the known probelms with the HTML client. These are being worked and may be addressed by the final release.
>
>		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.
 
Changed:
<
<		Comments:
>
>

Comments:

  Read what other users have said about this page or add your own comments.
Changed:
<
<
<--/commentPlugin-->
>
>
<--/commentPlugin-->
  -- JeanNeron - 2014-11-10
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