| |
| META TOPICPARENT |
name="APPX545Installation" |
APPX HTML Client 5.4.5 |
| |
The Local Connector only runs on Windows, OS/X or Linux based desktops or tablets. |
|
<
< | 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 with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off via metas["appx-local-required"]["value"] = "false"; in the your 'appx-client-settings.js file (see 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 with a "+", it means the local connector is installed & running. Red means the connector is not installed. You can click the 'Local' sign to manually download and install the connector. If the 'Local' icon is blue, it means the requirement for a local connector has been turned off via metas["appx-local-required"]["value"] = "false"; in the your 'appx-client-settings.js' file (see below). |
| | Web Browser |
|
<
< | 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. |
>
> | 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 display 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. |
| |
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. |
| | [root@localhost js]# mv appx-client-settingsTemplate.js appx-client-settings.js
|
|
>
> | This file is where you will configure your site specific settings, similar to 'appx.env' in an APPX server installation. |
| | 3) If this is a new installation you must set the name of the host running the Appx Server Connector in the 'appx-client-settings.js' file you just renamed:
metas["appx-proxy-host"]["value"] = "localhost";
Change locahost to the name or IP address of the server running the Appx Server Connector. Do not use localhost unless you plan to run the HTML client on the same server as the Appx Server Connector, i.e., a testing/evaluation environment. |
|
<
< | You can also set any other meta tags that are unique to your installation. The 'appx-client-settings.js' file will never be replaced during an update, so the settings will remain until you change them. |
>
> | You can also set any other meta tags that are unique to your installation. The 'appx-client-settings.js' file will never be replaced during an update, so the settings will remain until you change them. For example, you can set the name and login port of the APPX server, the default rows & columns, whether to use the Local Connector or not, etc. Consult the 'appx-client-settings.js' file for the full list of meta tags that can be set. |
| | Installation - APPX Server Connector Component
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. |
| |
Installation |
|
<
< | 1) If you are upgrading from a prior release, you must uninstall the old Server Connector first by running 'appxConnector-uninstall.js'. You must do this before installing the new connector. This should be run as 'root' on Linux/Unix systems, and as an Administrator on Windows systems. To run the script, open a terminal or DOS window and navigate to the folder where you installed the Appx Server Connector, then invoke the script via 'node': |
>
> | 1) If you are upgrading from a prior release, you must uninstall the old Server Connector first by running 'appxConnector-uninstall.js'. You must do this before installing the new connector. This should be run as 'root' on Linux/Unix systems, and as an Administrator on Windows systems. To run the script, open a terminal or DOS window and navigate to the folder where you installed the Appx Server Connector, then invoke the script via 'node': |
| | [root@localhost appxConnector]# node appxConnector-uninstall.js
Using default mode: systemd
Uninstall complete.
|
| |
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.
|
|
<
< |
- 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. 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.
|
| |
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]
Examples: |
| |
- create sub folders for each of the different style sheets you want to use.
- Edit your appx-client-settings.js file, changing 'appx-client-root' to point to the parent folder, i.e.:
- metas["appx-client-root"]["value"] = "../";
|
|
<
< |
- Copy the appx-client-settings.js file to each js folde.
|
>
> |
- Copy the appx-client-settings.js file to each js folder.
|
| |
- Create a 'css' folder in each subfolder, and put each unique CUSTOM.css file in that folder
Troubleshooting
- If you have created your own login page based on 'client.html', make sure you update it with any changes to the standard 'client.html' when upgrading the HTML client.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.