Difference: AppxHTMLClient545 (12 vs. 13)

Revision 132016-11-04 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="Main.Appx545Installation"

APPX HTML Client 5.4.5

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: 47 to 47

When uploading files, the web browser uploads the file into the Mongo database and returns a file path to your APPX process. You can use this path with .CLIENT UPLOAD FILE to transfer the file out of Mongo to the final destination. Note that using this method means you will not get the original path and file name as it existed on the user's computer. If you need this information, then you will have to use the Local Connector method. Files will stay in the Mongo database until the session ends, then they will be removed.

The Web Browser option does NOT allow you to invoke programs on the user's device (see .CLIENT LOAD URL). If you need this capability, you will have to use the Local Connector option.

Added:

>
>

NOTE: This option only works if you are connecting to an APPX server running Release 5.4.5 or higher.

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: 122 to 124

There are various reasons why you would want to do this:

You have development, model and production installations of APPX all on the same server. In this case, you would install a matching server connector in 3 different folders and configure each one to use a different set of ports. When a new release is available, you could install it in the test folder without affecting the model or production versions.

Changed:

<
<

Load balancing. You could install multiple connectors as above and configure multiple ports and have different users connect on different ports by setting up different 'appx-client-settings.js' files. For example, all users in a certain department use a settings file that uses ports 3014/3015, another department might use use a settings file that uses 3020/3021, etc.

>
>

Load balancing. You could install multiple connectors as above and configure multiple ports and have different users connect on different ports by setting up different 'appx-client-settings.js' files on the web server. In this case, you would install the web server component multiple times into different folders then customize the 'appx-client-settings.js' file in each folder. For example, all users in a certain department use a settings file that uses ports 3014/3015, another department might use use a settings file that uses 3020/3021, etc. Each department woudl have it's own login page on the web server.

By default the installer will install a server connector on port 3014 and a mongo connector on port 3015. The installer accepts the following arguments: node appxConnector-install [appx | mongo] [appxport] [mongoport]

Line: 240 to 242

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

Changed:

<
<

<--/commentPlugin-->

>
>

<--/commentPlugin-->

-- JeanNeron - 2015-12-18

View topic | History: r17 < r16 < r15 < r14 | More topic actions...