Difference: AppxHTMLClient543 (2 vs. 3)

Revision 32015-12-18 - JeanNeron

Line: 1 to 1
 

APPX HTML Client 5.4.3

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: 13 to 13
 The client will support SSL connections if your web server is configured appropriately. If not, the client will use its own built in AES encryption but be aware that this is not sufficient to protect sensitive data.

The Appx HTML client consists of two modules:

Changed:
<
<
  • Web Server Files. These are the javascript 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.
>
>
  • Web Server Files (webhost.zip). These are the javascript 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 (serverConnector.zip). 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 maximum 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.

Line: 47 to 47
  Change HOSTNAME to the name or IP address of the server running the Appx Server Connector. Do not use localhost.
Changed:
<
<
3) Install the 'nodejs' package from https://nodejs.org/ if it is not already installed on your server. For rpm based Linux systems, you can install it via (as root):
>
>
3) Install the 'nodejs' package from https://nodejs.org/ if it is not already installed on your server. For rpm based Linux systems, you can install it via (as root):
 
Changed:
<
<
curl --silent --location https://rpm.nodesource.com/setup | bash -
yum install nodejs
>
>
curl --silent --location https://rpm.nodesource.com/setup | bash -
yum install nodejs
 
Changed:
<
<
To install on Windows, go to https://nodejs.org and download the Windows installer (msi) file and simply run the installer.
>
>
To install on Windows, go to https://nodejs.org and download the Windows installer (msi) file and simply run the installer.
  4) 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, run the appxConnector-install.js script. This should be run as 'root' on Linux/Unix systems, and as an Administrator on Windows systems. This will check your system for the required modules. 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':
Changed:
<
<
[root@localhost ~]# cd /opt/appxConnector543 [root@localhost appxConnector543]# node appxConnector-install.js    Checking for required modules... Module: crypto                    - Installed. Module: fs                        - Installed. Module: hexy                      - Installed. Module: http                      - Installed. Module: https                     - Installed. Module: mongodb                   - Installed. Module: net                       - Installed. Module: node-cryptojs-aes         - Installed. Module: string                    - Missing, please run 'npm install string' to install. Module: string_decoder            - Installed. Module: url                       - Installed. Module: ws                        - Installed.   Missing modules.  Please install required modules and run again.
>
>
[root@localhost ~]# cd /opt/appxConnector543
[root@localhost appxConnector543]# node appxConnector-install.js
Checking for required modules...
Module: crypto - Installed.
Module: fs - Installed.
Module: hexy - Installed.
Module: http - Installed.
Module: https - Installed.
Module: mongodb - Installed.
Module: net - Installed.
Module: node-cryptojs-aes - Installed.
Module: string - Missing, please run 'npm install string' to install.
Module: string_decoder - Installed.
Module: url - Installed.
Module: ws - Installed.

Missing modules. Please install required modules and run again.
 
Changed:
<
<
Notice in this example the module 'string' is missing and the instructions on how to install it are displayed. If any modules are missing on your system, run the appropriate 'npm' command to install them, then re-run the install script. If all modules are now present, the service will be created:
>
>
Notice in this example the module 'string' is missing and the instructions on how to install it are displayed. If any modules are missing on your system, run the appropriate 'npm' command to install them, then re-run the install script. If all modules are present, the service will be created:
 
Changed:
<
<
[root@localhost appxConnector543]# node appxConnector-install.js    Checking for required modules... Module: crypto                    - Installed. Module: fs                        - Installed. Module: hexy                      - Installed. Module: http                      - Installed. Module: https                     - Installed. Module: mongodb                   - Installed. Module: net                       - Installed. Module: node-cryptojs-aes         - Installed. Module: string                    - Installed. Module: string_decoder            - Installed. Module: url                       - Installed. Module: ws                        - Installed.   Installing appxconnector service... Using default mode: systemd Installing service on /etc/systemd/system/appxconnector.service Already installed, restarting appxconnector service... Running systemctl start appxconnector... Done
>
>
[root@localhost appxConnector543]# node appxConnector-install.js  
Checking for required modules...
Module: crypto - Installed.
Module: fs - Installed.
Module: hexy - Installed.
Module: http - Installed.
Module: https - Installed.
Module: mongodb - Installed.
Module: net - Installed.
Module: node-cryptojs-aes - Installed.
Module: string - Installed.
Module: string_decoder - Installed.
Module: url - Installed.
Module: ws - Installed.

Installing appxconnector service...
Using default mode: systemd Installing service on /etc/systemd/system/appxconnector.service
Already installed, restarting appxconnector service...
Running systemctl start appxconnector...
Done
 
Changed:
<
<
5) Confirm the service is running. In Linux you can use 'ps -ef|grep appxConnector.js', and in Windows you can use the 'Services' control panel
>
>
5) Confirm the service is running. In Linux/Unix you can use 'ps -ef|grep appxConnector.js', and in Windows you can use the 'Services' control panel.
  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
>
>
http://192.168.0.15/appx/client.html
  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 section on 'Tunneling/Forwarding'.

LocalConnector

Line: 136 to 136
 

Troubleshooting

  • If the client login dialog box does not display, check your web server error logs for any error messages & correct as required.
  • 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:
    # setsebool -P httpd_can_network_connect 1
Changed:
<
<
  • 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.
>
>
  • 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.
 
  • Check to make sure your Appx Server Connector is still running. If not, restart it.
Deleted:
<
<
  • Comments:
 
Changed:
<
<
Read what other users have said about this page or add your own comments.
>
>

Comments

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

 
Changed:
<
<

<--/commentPlugin-->
>
>

<--/commentPlugin-->
 
Changed:
<
<
-- JeanNeron - 2014-11-10
>
>
-- JeanNeron - 2015-12-18
 
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