Difference: AppxHTMLClient545 (2 vs. 3)

Revision 32016-09-30 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPX545Installation"

APPX HTML Client 5.4.5

Line: 42 to 42
  The other option is to use the Web Browser's built in ability to handle files. With this option, the APPX Server Connector stores the file in the Mongo database, then passes a URL to the Web Browser. The Web Browser will either display the file in a new tab if it knows how process that file type, or offer to save the file if it does not know how to display it. This is a better choice if you are planning to deploy your applications on non Windows tablets or smartphones.
Changed:
<
<		The file does not remain in the Mongo Database indefinitely (how long??), so if the user refreshes that tab they will get error 404.
>
>		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.
  can you still drag & drop w/o the local connector?
Line: 56 to 56
  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 connections. Note: 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. Is this an error that prevents it from running, or just an informational message?
>
>		If you plan to use an SSL connection, your web server must be configured to accept both SSL and non-SSL connections. Note: 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. This is just an informational message.
  If you are going to run the APPX Server Connector on a Windows server, make sure all patches have been applied. In particular, https://support.microsoft.com/en-us/kb/2731284 will break tables if it is not applied

Installation - Web Server Component

Line: 71 to 71
 

Installation - APPX Server Connector Component

Changed:
<
<		The APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then port 3015 (the default port) needs to be open between the server connector machine and your HTML clients.
>
>		The APPX Server Connector is the software that connects the HTML clients and the APPX server. This can be installed on the same server as the web server, or the APPX Server, or a completely different machine. If you are not using tunnneling via the web server, then ports 3014/3015 (the default port) needs to be open between the server connector machine and your HTML clients.
 

Prerequisites

The server that will run the APPX Server Connector requires some additional software:

Line: 104 to 103
  http://192.168.0.15/appx/client.html
Changed:
<
<		You must open port 3015 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'.
>
>		You must open ports 3014/3015 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'.
 

Post Installation if upgrading an existing HTML client installation

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

Line: 114 to 113
  As mentioned above, you have a choice on how the HTML client should handle files sent to/from the browser.
Changed:
<
<		By default, the HTML client will try to use the local connector (is this true?). You can suppress the requirement for the Local Connector by changing the following line in "client.html":
>
>		By default, the HTML client will try to use the local connector. You can suppress the requirement for the Local Connector by changing the following line in "client.html":
  <meta name="appx-local-required" content="true" >
Line: 134 to 133
  <meta name="appx-upload-without-local" content="false" >
Changed:
<
<		Change the "true" to "false" to force the HTML client to use the Web Browser to handle files.
>
>		Change the "false" to "true" to force the HTML client to use the Web Browser to handle files.
  The Application Designer can also control this. Each file chooser widget can be individually set to not use the local connector by using the macro: @FULC=F

Tunneling/Forwarding

Changed:
<
<		If you do not want to open port 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:
>
>		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

Changed:
<
<

  • Create the /etc/httpd/conf.d/appx.conf file with the following lines (or just add these to httpd.conf):

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

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

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

  • 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

Changed:
<
<		If you are using Windows IIS for your web sever platform, and do not wish to expose TCP 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.
>
>		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.
 
<?xml version="1.0" encoding="UTF-8"?>
 <configuration>
     <system.webServer>
View topic | History: r17 < r16 < r15 < r14 | 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