Difference: AppxHTMLClient546 (4 vs. 5)

Revision 52018-04-27 - JeanNeron

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

APPX HTML Client 5.4.6 & Higher

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: 87 to 86
  The server that will run the APPX Server Connector requires some additional software:
Changed:
<
<
  • The 'nodejs' package (https://nodejs.org/).

    For rpm based Linux systems, you can install it via (as root):
    curl --silent --location https://rpm.nodesource.com/setup | bash -yum install nodejs

    To install on Windows, go to https://nodejs.org and download the Windows installer (msi) file and simply run the installer.

>
>
 
  • The Mongo Database (https://www.mongodb.org/). Instructions for downloading and configuring the database can be found at https://docs.mongodb.org/manual/tutorial/
  • If the server is running Windows, you also need to install .NET Framework 3.5. Quick install instructions:

    Press the Windows key on your keyboard, type Windows Features, and press Enter. This brings up the Turn Windows features on or off dialog box. ...
    Select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) check box, press OK, and reboot your computer if prompted.

Line: 116 to 112
  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 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

Line: 237 to 229
 
    • metas["appx-client-root"]["value"] = "../";
  • 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
Added:
>
>

Anonymous Logins

Starting in Release 6.0, you can configure the client for anonymous logins. This is a login where the user is not presented with a login screen, but is taken directly to the startup process. Note that the user is not really 'anonymous', instead every user who connects via this method will have the same user credentials. You control which user credentials will be used by configuring the server connector.

This is configured in the server connector for better security. Your configuration file will probably include a valid user id/password for your server, so we don't want it in the web server folder.

The settings are in the 'appx-client-anonymousLogin.js' file in your server connector folder. The variables you can change are:

"appx-allow-noLogin" must be set to 'true'. If this is set to false, no matter what variables are provided the HTML Client will not allow anonymous logins.

"appx-allow-specific" can be set to 'true' or 'false'. If this is set to 'true', you can embed the process to run in the URL. If this is set to false, APPX will run the startup process for the specified anonymous user.

"appx-use-noLogin" can be set to 'true' or 'false'. If 'true' this tells the HTML Client that all logins are anonymous login. If 'false', then the login URL must include 'requireLogin=true' to request an anonymous login. The 'false' setting allows you to have both anonymous and normal logins.

"appx-use-specific" can be set to 'true' or 'false'. If "true" APPX will automatically run the process specified by the application related settings below. If 'false', the applications settings can be specified in the URL.

"appx-anon-user" should contain the login user ld

"appx-anon-pswd" should contain the password

"appx-anon-host" should contain the APPX host

"appx-anon-port" should contain the port number for the APPX host

"appx-application" should contain the 3 character APPX application id

"appx-database" should contain the 3 character Database Id to use

"appx-procType" should contain the APPX process type to run (MENU, INPUT, JOB, etc)

"appx-process" should contain the name of the APPX process to run

URL String variables

You can specify the following variables in the URL. These will override the settings in the 'appx-client-anonymousLogin.js' file.

requireLogin ---- true/false value: true = user is required to login, false = you are using anonymous login
specific ---- true/false value: true = you are logging user into a specific process, false = you are using normal login
user ---- Login Id
password ---- Password
host ---- Server
port ---- Port
application ---- application to run
database ---- database to use
procType ---- process type you are running
process ---- process to run


Examples:

Logging in as an anonymous user, using all the settings ithe 'appx-client-anonymousLogin.js' file:

http://<html client server>?requireLogin=false

Logging in as an anonymous user but overriding the startup process:

http://<html client server>?requireLogin=false&specific=true&application=DMO&database=DMO&procType=MENU&process=MAIN%20 MENU

This requires "appx-allow-specific" set to 'true'.

Logging in as a specific user:

http://<html client server>?requireLogin=false&specific=true&user=anon&password=password&host=<host name>&port=<port number>

 

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.
  • 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.
Changed:
<
<
  • If you can't display table data inside a browser and you are running Windows Server 2008R2, you might try installing this HOTFIX from Microsoft. Windows 2008R2 servers without that HOTFIX will sometimes zero-out the MongoDB data. https://support.microsoft.com/en-us/kb/2731284
>
>
  • If you can't display table data inside a browser and you are running Windows Server 2008R2, you might try installing this HOTFIX from Microsoft. Windows 2008R2 servers without that HOTFIX will sometimes zero-out the MongoDB data. https://support.microsoft.com/en-us/kb/2731284
 
  • If you're having trouble with Remote connections, this page has some tips
  • If the client seems to hang while loading images or tables, that its a very good indicator that MongoDB server has stopped. If MongoDB server needs to be started or restarted then make sure you restart the appxConnector service after MongoDB is running.
  • Your mongodb driver may be out of date. Use 'npm install mongodb' as root/Administrator to make sure you have the latest version
Line: 253 to 297
 Read what other users have said about this page or add your own comments.
Changed:
<
<

<--/commentPlugin-->
>
>

<--/commentPlugin-->
  -- JeanNeron - 2017-11-14
 
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