Difference: APPXLoginManagerForUnixLinux (3 vs. 4)

Revision 42007-07-19 - SteveFrizzell

Line: 1 to 1

META TOPICPARENT	name="APPXConnectionManager"

Deleted:

<
<

APPX Connection Manager For Unix/Linux

This page describes how to install, configure, and manage the APPX Connection Manager on Unix/Linux systems.

Line: 41 to 40

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

Changed:

<
<

Configuring the APPX Connection Manager

>
>

Configuring an Instance of the APPX Connection Manager

Changed:

<
<

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.

>
>

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:

Line: 51 to 50

An environment (.env) file is created
An initialization (.ini) file is created

Changed:

<
<

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
#

Line: 100 to 68

$SSL_TYPE=PLAINTEXT

Changed:

<
<

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

>
>

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

Added:

>
>

Usage

NAME
uappxd

SYNOPSIS
uappxd -install -port=PORT [options]... [VARIABLE=VALUE]...
uappxd INIFILE | -start INIFILE
uappxd -status INIFILE
uappxd -stop INIFILE
uappxd -restart INIFILE

DESCRIPTION
uappxd 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)

OPTIONS
-start INIFILE | INIFILE
Start an instance of the Connection Manager using the configuration stored in the INIFILE.ini file.

-stop INIFILE
Stop the instance of the Connection Manager that was started with the INIFILE.ini file.

-restart INIFILE
Restart (stop and then start) the instance of the Connection Manager that was started with the INIFILE.ini file.

-status INIFILE
Report the status of the instance of the Connection Manager that was started with the INIFILE.ini file.

-install [options]... [VARIABLE=VALUE]...
Configure and start a new Connection Manager service. The options which follow are used in conjunction with the -install option:

-port=PORT
[Required] Configure the service to listen for connection requests on the specified TCP/IP PORT number. This option is required with the -install option. You may choose any TCP/IP PORT number that is not reserved or already being used on your system.

-name=NAME
[Optional] The specified NAME 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

EXAMPLES
Configure and start a new instance of the Connection Manager:

uappxd -install -port=8060 -name=appx8060 -displayName="Appx-Production(8060)" -engine=/usr/local/appx/appx APPXPATH=c:\appx\data APPX_KEYMAP=Windows

Display the status of an instance of the Connection Manager:

uappxd -status appx8060

Shutdown a running instance of the Connection Manager:

uappxd -stop appx8060

Start a previously configured instance of the Connection Manager:

uappxd -start appx8060

uappxd -install -name=name -displayName=name -port=port -engine=path -AM=method

Comments:

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

View topic | History: r68 < r67 < r66 < r65 | More topic actions...