Tags:
view all tags
---+ APPX Connection Manager For Unix/Linux _This page describes how to install, configure, and manage the APPX Connection Manager on Unix/Linux systems._ %TOC% 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; 1 Validates the user ID and the password provided by the APPX Client; 1 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. <pre> cd /usr/local/appx/tools chown root uappxd chmod 775 uappxd chmod u+s uappxd </pre> You can check the permissions of the uappxd command by running the following command: <pre> ls -l uappxd </pre> The correct permissions should be as follows: <pre> -rwsrwxr-x 1 root root 636843 Jul 11 07:31 uappxd </pre> ---++ Configuring an Instance of the APPX Connection Manager On Unix/Linux systems, an instance of the APPX Connection Manager is 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 1 An environment (.env) file is created 1 An initialization (.ini) file is created <pre> # 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 </pre> Before clients can connect to an APPX system, at least one instance of the APPX Connection Manager must be configured and started. ---+++ Configuration Changes ---++ Managing the APPX Connection Manager ---+++ Managing As a Service ---+++ Managing With the uappxd Command ---++Usage <pre> <b>NAME</b> uappxd <b>SYNOPSIS</b> <b>uappxd</b> -install -port=<u>PORT</u> [<u>options</u>]... [<u>VARIABLE</u>=<u>VALUE</u>]... <b>uappxd</b> <u>INIFILE</u> | -start <u>INIFILE</u> <b>uappxd</b> -status <u>INIFILE</u> <b>uappxd</b> -stop <u>INIFILE</u> <b>uappxd</b> -restart <u>INIFILE</u> <b>DESCRIPTION</b> <b>uappxd</b> is used to configure and manage instances of the APPX Connection Manager service. 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 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) <b>OPTIONS</b> <b>-start</b> <u>INIFILE</u> | <u>INIFILE</u> Start an instance of the Connection Manager using the configuration stored in the <u>INIFILE</u>.ini file. <b>-stop</b> <u>INIFILE</u> Stop the instance of the Connection Manager that was started with the <u>INIFILE</u>.ini file. <b>-restart</b> <u>INIFILE</u> Restart (stop and then start) the instance of the Connection Manager that was started with the <u>INIFILE</u>.ini file. <b>-status</b> <u>INIFILE</u> Report the status of the instance of the Connection Manager that was started with the <u>INIFILE</u>.ini file. <b>-install</b> [<u>options</u>]... [<u>VARIABLE</u>=<u>VALUE</u>]... Configure and start a new Connection Manager service. The <u>options</u> which follow are used in conjunction with the <b>-install</b> option: <b>-port</b>=<u>PORT</u> [Required] Configure the service to listen for connection requests on the specified TCP/IP <u>PORT</u> number. This option is required with the <b>-install</b> option. You may choose any TCP/IP <u>PORT</u> number that is not reserved or already being used on your system. <b>-name</b>=<u>NAME</u> [Optional] The specified <u>NAME</u> wiil be the name assigned to the Connection Manager service that is being configured. If this option is omitted, the 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 <b>EXAMPLES</b> Configure and start a new instance of the Connection Manager: <b>uappxd -install -port=8060 -name=appx8060 -displayName="Appx-Production(8060)" -engine=/usr/local/appx/appx APPXPATH=c:\appx\data APPX_KEYMAP=Windows</b> Display the status of an instance of the Connection Manager: <b>uappxd -status appx8060</b> Shutdown a running instance of the Connection Manager: <b>uappxd -stop appx8060</b> Start a previously configured instance of the Connection Manager: <b>uappxd -start appx8060</b> uappxd -install -name=name -displayName=name -port=port -engine=path -AM=method </pre> ---++ Comments: _Read what other users have said about this page or add your own comments._ --- %COMMENT% --- -- Page added by: [[SteveFrizzell][Steve]] - 17 Jul 2007
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r71
|
r6
<
r5
<
r4
<
r3
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r4 - 2007-07-19
-
SteveFrizzell
Home
Site map
Main web
MedicaidBilling web
Sandbox web
TWiki web
Main Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
Copyright © 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