Tags:
view all tags
---+ APPX HTML Client _This page gives an overview of and installation instructions for the Appx HTML client._ <br /><span data-mce-mark="1">%TOC%</span> ---++ 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. 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 it's own built in AES encryption so your data is still protected. 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 independent. * 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. ---+++ LocalConnector Because of the tighter security in web browsers, it is not possible for HTML 5/javascript to seamlessly upload, download or open files 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. By default, the HTML client will check to see if this helper program is installed when the user logs in. If it is not installed, 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, it means the LocalConnector 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 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. ---++ Requirements 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. We have tested the HTML client on current versions of IE, Chrome and Safari. ---++ Installation 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. 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<br /># nohup ./node appxConnector.js & If you are running on Windows, then extract the Appx Server Connector to a folder of your choice and invoke it. For example, if you installed it a folder called "C:\AppxConnector", then you would: cd \appxConnector<br />node appxConnector.js 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. At some point we will automate this step, 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: <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. 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: <span data-mce-mark="1">http://192.168.0.15/appx/client.html</span> 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/Forwarding'. ---+++ LocalConnector As mentioned above, you can suppress the requirement for the LocalConnector by changing the following line in /var/www/html/appx/client.html: <meta name="appx-local-required" content="true" > ---++ 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: * <p>In /etc/httpd/conf.modules.d/00-proxy.conf, add (if not already loaded):<br />LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so</p> * <p>Create the /etc/httpd/conf.d/appx.conf file with the following lines (or just add these to httpd.conf)<br /> ProxyPass /appxws/ ws://localhost:3014<br /> ProxyPass /appxwss/ wss://localhost:3014</p> * <p>Change /var/www/html/appx/client.html settings to:</p> <p>appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11)<br /> appx-proxy-port = “80" <br /> appx-proxy-path = /appxws/ <br /> appx-encryption = “aes”</p> * <p>Restart your web server</p> ---++ SSL If you are running a secure web server (https), you can configure the Appx HTML client to use your SSL connection. Change your /var/www/html/appx/client.html settings as follows: appx-proxy-host = hostname of httpd server (i.e., 192.168.1.11)<br />appx-proxy-port = “443" <br />appx-proxy-path = /appxwss/ <br />appx-encryption = “ssl” Then change the sslEnabled setting in 'appxConnector.js': var sslEnabled = *true*; ---++ 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. ---++ Troubleshooting * <span data-mce-mark="1" style="background-color: transparent;">If the client login dialog box does not display, check your web server error logs for any error messages & correct as required.</span> * <span data-mce-mark="1" style="background-color: transparent;">If you are getting "[proxy:error] [pid xxxx] (13)Permission denied:" errors, you might have a selinux security issue that prevents apache from initiating any outgoing network connections to the web socket server port. In that case, try the following command:</span><br /> <span data-mce-mark="1" style="background-color: transparent;"># setsebool -P httpd_can_network_connect 1</span> * <span data-mce-mark="1" style="background-color: transparent;">Some browsers (like IE) will not run the client successfully if you double click the 'client.html' file. You should always access the web page via http://servername/client.html, even if the page is installed on your local system.</span> * <span style="background-color: transparent;">Check to make sure your </span><span style="background-color: transparent;">Appx Server Connector is still running. If not, restart it via '</span><span style="background-color: transparent;">nohup ./node appxConnector.js &' for Linux or '</span><span style="background-color: transparent;">node appxConnector.js' for Windows. </span> ---++ Known Issues 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. * Tab Order and Tab Groups are not functional * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3064][$newsession does not honour startup arguments]] (#3064) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3070][Em Building messages don't display]] (#3070) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3073][Review Preferences]] (#3073) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3081][Client does not double buffer]] (#3081) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3108][Monitor Screen has some garbage in scrolling area]] (#3108) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3109][Widget Font Size smaller than Java Client]] (#3109) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3125][No Em building indicator]] (#3125) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3147][Reconnect doesn't ever time out?]] (#3147) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3156][Some buttons are trimmed]] (#3156) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3166][Some missplacement of items in WorkFLow screen]] (#3166) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3183][Key Pause not firing]] (#3183) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3187][Scrolling screens missing column separators]] (#3187) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3188][Alert Box in MDI app on krokus looks different than Java Client]] (#3188) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3189][MDI HTML widget on notes doesn't look right for both Java and HTML5 client]] (#3189) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3190][Final Action Inquiry Button not aligned(text)]] (#3190) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3191][Application Journal Button text alignment wrong]] (#3191) * [[http://bugtracker.appx.com/view_bug.jsp?bugid=3195][no scroll bar on scroll screens]] (#3195) ---++ Comments: _Read what other users have said about this page or add your own comments._ --- <br /><span data-mce-mark="1">%COMMENT%</span> -- Main.JeanNeron - 2014-11-10
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r18
|
r8
<
r7
<
r6
<
r5
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r6 - 2014-11-12
-
JeanNeron
Home
Site map
Main web
MedicaidBilling web
Sandbox web
TWiki web
Main Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
Copyright © 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