Difference: APPXLoginManagerForUnixLinux (13 vs. 14)

Revision 142007-08-06 - SteveFrizzell

Line: 1 to 1

META TOPICPARENT	name="APPXConnectionManager"

Added:

>
>

APPX Connection Manager For Unix/Linux

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

Line: 8 to 9

The APPX Connection Manager command is used to configure and manage APPX Connection Services.

An APPX Connection Service:

Changed:

<
<

Waits for a connection request from an APPX Client;

>
>

Waits for a connection request from a remote APPX Client;

Validates the user ID and the password provided by the APPX Client;
Initiates an APPX session for the APPX Client that requested a connection.

Installing the APPX Connection Manager Command ( appxdsvc)

Changed:

<
<

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

>
>

Changed:

<
<

The appxdsvc 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 appxdsvc command will be "/usr/local/appx/tools/appxdsvc".

>
>

The appxdsvc 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 of the appxdsvc command will be "/usr/local/appx/tools/appxdsvc".

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

Line: 34 to 35

ls -l appxdsvc

Changed:

<
<

The correct permissions should be as follows:

>
>

The recommended permissions should be as follows:

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

Creating and Configuring an APPX Connection Service

Changed:

<
<

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

Initial Configuration

The -install option of the appxdsvc command is used to initially create, configure, and start an instance of the APPX Connection Service. The following steps are performed:

>
>

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

Creating a Configuration

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

The -install option of the appxdsvc command is used to initially create, configure, and start an instance of the APPX Connection Service. The following steps are performed:

The APPX Connection Service configuration files are created(ini and env)
The O/S service is created
The service is started

Added:

>
>

Location of the Configuration Files
The two configuration files may be located in any existing directory on your systerm. However, the appxdsvc command does not have an option to directly specify where the two configuration files should be located. The -install option of the appxdsvc command creates the two configuration files in your current directory. Therefore, before you run the appxdsvc commad, you must first change to the directory where you want the two configuration files to reside. For example, if you want the two configuration files to be created in the APPX tools directory, you should change to the tools directory before you run the appxdsvc command.
Assignment of a TCP/IP Port Number
Any available TCP/IP port number may be specified when installing an instance of the APPX Connection Manager Service. However, as a matter of convention, most APPX administrators configure the APPX Connection Service to listen for connections on port 8060. If additional intances of the APPX Connection Manager are configured, each instance is typically assigned the next available port number after 8060.

Changed:

<
<

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

Configuration Changes

>
>

Changing a Configuration

Two methods are available for modifying an existing instance of the APPX Connection Service.

Method 1 - appxdsvc command

Line: 105 to 114

-name, -ServiceName [Optional]

The specified SERVICENAME wiil be the name assigned to the Connection Manager service script that is created and to the related configuration files. The configuration file will have a file extension of "ini". If this option is omitted, the default SERVICENAME will be "appxd" followed by a "-" and the specified port number, e.g "appxd-8060".

Changed:

<
<

-DisplayName=DISPLAYNAME [Optional]

>
>

-DisplayName=DISPLAYNAME [Optional]

If you don't supply a DISPLAYNAME appxdsvc will append the port number to the end of the SERVICENAME and use that as the DISPLAYNAME. (The DISPLAYNAME will appear in the Services control panel and will be displayed by the ps command)

Changed:

<
<

-engine, -AppxExecutable=PATHNAME [Optional]

>
>

-engine, -AppxExecutable=PATHNAME [Optional]

The APPX engine at the specified PATHNAME will be run when initiating an APPX session. The specified PATHNAME may be alsolute or it may be relative to the location of the appxdsvc command

Line: 179 to 188

appxdsvc -start appx8060

Added:

>
>

Example ini File

Added:

>
>

# Appx connection manager configuration file
#

Line: 232 to 243

# TrustedCAFile = #determines which client certificates to trust # Umask = #umask (file creation mask) given to spawned engines

Added:

>
>

Example env File

Added:

>
>

# Appx connection manager environment variables
#

Line: 249 to 262

APPX_KEYMAP=WINDOWS

Added:

>
>

Comments:

Added:

>
>

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

Added:

>
>

Added:

>
>

<--/commentPlugin-->

Added:

>
>

Changed:

<
<

-- Page added by: Steve - 17 Jul 2007

>
>

-- Page added by: Steve - 17 Jul 2007

META TOPICMOVED	by="SteveFrizzell" date="1184694066" from="Main.APPXConectionManagerForUnix-Linux" to="Main.APPXConnectionManagerForUnixLinux"

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