APPX Connection Manager For Unix/Linux

When the APPX Connection Manager is started, a daemon is spawned which processes connection requests from the various types of APPX clients.

The APPX Connection Manager daemon:

1. Waits for a connection request by an APPX Client;
2. Validates the user ID and the password provided by the APPX Client;
3. Initiates an APPX session for the user who requested a connection.

Installing the APPX Connection Manager Command ( uappxd)

The APPX Connection Manager command ( uappxd) is installed automatically when you install APPX on your system. The installer sets the necessary owner and permissions on the uappxd command.  So, there is nothing additional that you need to do to install the APPX Connection Manager command. However, after you install APPX, you will need to run the uappxd command to configure and start at least one instance of the APPX Connection Manager before any client connections may be established.

The uappxd command is installed into the "tools" subdirectory of the directory where you installed APPX. So, if you installed APPX in "/usr/local/appx", the full pathname to run the uappxd command will be "/usr/local/appx/tools/uappxd".

The uappxd command must run with the permissions of the root user.  Therefore, the owner of the uappxd command should be the root user and the SUID bit should be set so that the uappxd command can be run by users other than root but still be run with the permissions of root.

In the event that it is necessary to reset the permissions on the uappxd command, the following commands can be run by the root user to set the necessary owner and permissions on the uappxd command.

cd /usr/local/appx/tools
chown root uappxd
chmod 775 uappxd
chmod u+s uappxd

You can check the permissions of the uappxd command by running the following command:

ls -l uappxd

The correct permissions should be as follows:

-rwsrwxr-x 1 root root    636843 Jul 11 07:31 uappxd

Configuring the APPX Connection Manager

On Unix/Linux systems, an instance of the APPX Connection Manager initially configured by running the "uappxd" command. At least one instance of the APPX Connection Manager must be configured and started before an APPX Client can initiate an APPX session. You may configure and start as many instances of the APPX Connection Manager as you desire. However, each concurrently running instance must be configured to listen for connection requests on a different TCP/IP port.

Initial Configuration

When the install option is used to configure and instance of the APPX Configuration Manager, the following steps are performed:

1. A service is installed
2. An environment (.env) file is created
3. An initialization (.ini) file is created

Usage:
./uappxd serviceName
./uappxd -install -name=name -displayName=name -port=port -engine=path -AM=method
./uappxd -status serviceName
./uappxd -start [serviceName]
./uappxd -stop [serviceName]
To create a log monitor process, include --serviceType=logmonitor on the command-line
The optional -AM argument determines the authentication method
  Acceptable values are 'OS-User', 'Appx-User', and 'HT-User(filename)'
  With 'Appx-User' authentication, passwords are validated against
  the Appx user file
  With 'OS-User' authentication, passwords are validated by Windows
  With 'HT-User(filename)' authentication, passwords are validated against
  the named file (which you can maintain the Apache's htpasswd utility
  If you choose 'Appx-User' authentication, you do not need a separate OS user
  account for each Appx user
Note that you can include a space-separated list of envirnoment
variables at the end of the command line when you install a new
service.  Those environment variables will be given to the Appx
engines spawned by this service
The -displayName is optional - if you don't supply a display name
we will append the port number to the end of the service name and
use that as the display name. (The display name appears in the
Services control panel)
Examples:
./uappxd -install -name=Appx8090 -displayName="Appx-Production(8090)"
     -port=8090 -engine=/usr/local/appx/appx
     APPXPATH=c:\appx\data APPX_KEYMAP=Windows
Compile Date Jul 10 2007
If that went by too fast, try ./uappxd | more

# Appx connection manager environment variables
#
#   The entries in this file will become
#   environment variables in the engines
#   spawned by this service
#
#   blank lines are ignored
#
#   anything following a '#' is treated as a comment
#
#   letter case IS important in this file
# --------------------------------------------------
APPX_KEYMAP=WINDOWS
$SSL_TYPE=PLAINTEXT

Before clients can connect to an APPX system, at least one instance of the APPX Connection Manger must be configured and started.

Configuration Changes

Managing the APPX Connection Manager

Managing As a Service

Managing With the uappxd Command

Comments: