Difference: APPXLoginManagerForUnixLinux (7 vs. 8)

Revision 82007-07-23 - SteveFrizzell

 			 META TOPICPARENT 
			 name="APPXConnectionManager" 
		
 APPX Connection Manager For Unix/Linux
- META TOPICPARENT
+ name="APPXConnectionManager"
-<
<
+This page describes how to install, configure, and manage the APPX Connection Manager on Unix/Linux systems.
->
>
+This page describes how to install the APPX Connection Manager command and how to use it to configure and manage APPX Connection Services on Unix/Linux systems.
   APPX Login Manager For Unix/Linux 
  Installing the APPX Login Manager Command ( appxLoginMgr)
   Creating and Configuring an APPX Connection Service 
  Creating a Connection Service 
  The Name of the Service
   TCP/IP Port Number
 
   Changing a Connection Service 
  Method 1 - The APPX Login Manager Command (appxLoginMgr)
   Method 2 - Text Editor
 
 
   Managing an APPX Login Manager Daemon 
  Method 1 - appxLoginMgr command
   Method 2 - O/S Services
 
   Usage (appxLoginMgr) 
  Synopsis - Service Configuration 
  Configuration - Commands
   Configuration - Options 
  Options - General
   Options - Session Identity/Permissions
   Options - Startup Process
   Options - TCP/IP
   Options - SSL
 
   Configuration - Environment Variables
 
   Synopsis - Service Management
 
   The Configuration File (ini)
   The Environment File (env)
   The Status File (stat)
   The Log File (log)
   Red Hat service command. 
  Usage (service) 
  Synopsis - service Command
 
 
   Examples: 
  How to create private/public-keys without passphrase for server
   How to create public SSL certificate for server
 
   Warnings: 
  "the engine that you named has the setuid bit enabled"
 
   
 
   Reconnect Feature (5.3 & up) 
  Overview:
   Usage:
   Reconnecting to a session
 
   PAM Capable (5.3 & Up)
   Reconnect Revisited (5.4.4) 
  Issues:
   Comments:
-<
<
+When and instance of the APPX Connection Manager service is started, a daemon is spawned which waits for and processes connection requests from the various types of APPX clients.
->
>
+The APPX Connection Manager command is used to configure and manage APPX Connection Services.
-<
<
+The APPX Connection Manager daemon:  
 Waits for a connection request by an APPX Client;
  Validates the user ID and the password provided by the APPX Client;
  Initiates an APPX session for the user who requested a connection.
->
>
+An APPX Connection Service:  
 Waits for a connection request from an 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 (uappxd)
->
>
+ Installing the APPX Connection Manager Command (appxdsvc)
-<
<
+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 service before any client connections may be established.
->
>
+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.
-<
<
+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 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 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.
->
>
+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.
-<
<
+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.
->
>
+In the event that it is necessary to reset the permissions on the appxdsvc command, the following commands can be run by the root user to set the necessary owner and permissions for the appxdsvc command.
 cd /usr/local/appx/tools
-<
<
+chown root uappxd
chmod 775 uappxd
chmod u+s uappxd
->
>
+chown root appxdsvc
chmod 775 appxdsvc
chmod u+s appxdsvc
-<
<
+You can check the permissions of the uappxd command by running the following command:
->
>
+You can check the permissions of the appxdsvc command by running the following command:
-<
<
+ls -l uappxd
->
>
+ls -l appxdsvc
 The correct permissions should be as follows:
-<
<
+-rwsrwxr-x 1 root root    636843 Jul 11 07:31 uappxd
->
>
+-rwsrwxr-x 1 root root    636843 Jul 11 07:31 appxdsvc
-<
<
+ Configuring an Instance of the APPX Connection Manager
->
>
+ Creating an APPX Connection Service
-<
<
+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.
->
>
+On Unix/Linux systems, an instance of the APPX Connection Service is initially created and configured by running the "appxdsvc" command. 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
-<
<
+When the install option is used to configure and instance of the APPX Configuration Manager, the following steps are performed:  
 A service is installed
  An environment (.env) file is created
  An initialization (.ini) file is created
->
>
+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 configuration files are created(ini and env)
  The O/S service is created,
  The service is started
 # Appx connection manager environment variables
 $SSL_TYPE=PLAINTEXT
-<
<
+Before clients can connect to an APPX system, at least one instance of the APPX Connection Manager must be configured and started.
->
>
+Before clients can connect to an APPX system, at least one instance of the APPX Connection Service must be configured and started.
  Configuration Changes
-<
<
+ Managing the APPX Connection Manager 

 Managing As a Service 
 Managing With the uappxd Command
->
>
+ Managing APPX Connection Services 
 Managing With the appxdsvc Command 
 Managing As an O/S Service
  Usage 
NAME
uappxd
-<
<
+SYNOPSIS
uappxd -install -port=PORT [options]... [VARIABLE=VALUE]...
uappxd -modify -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
uappxd -remove {SERVICENAME | -serviceName=SERVICENAME}
->
>
+SYNOPSIS (Configuration)
appxdsvc -install -port=PORT [options]... [VARIABLE=VALUE]...
appxdsvc -modify -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
appxdsvc -remove {SERVICENAME | -serviceName=SERVICENAME}
-<
<
+uappxd [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}
->
>
+SYNOPSIS (Management)
appxdsvc [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}
 DESCRIPTION
-<
<
+uappxd is used to configure and manage instances of the APPX Connection Manager service.
->
>
+appxdsvc is used to configure and manage instances of the APPX Connection Service.
 To create a log monitor process, include --serviceType=logmonitor on the command-line
The optional -AM argument determines the authentication method
 use that as the display name. (The display name appears in the
Services control panel)
-<
<
+SERVICE MANAGEMENT OPTIONS
   -start | <_blank_>
      Start an instance of the Connection Manager service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files.

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

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

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

SERVICE CONFIGURATION OPTIONS
->
>
+OPTIONS (Configuration)
    -install [options]... [VARIABLE=VALUE]...
      Configure and start a new Connection Manager service.  The options which follow are used in conjunction with the -install option:
       VARIABLE=VALUE
         [Optional] You can include a space-separated list of environment variables at the end of the command line when you use the -install option.  These environment variables will be saved in the .env file that is created and will be given to the environment of the appx sessions that are started by the Connection Manager.
->
>
+OPTIONS (Management)
   -start | <blank>
      Start an instance of the Connection Manager service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files.

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

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

   -status
      Report the status of the instance of the Connection Manager that was started with the SERVICENAME.ini file.
 EXAMPLES
Configure and start a new instance of the Connection Manager that will listen for connection requests on port 8060:
          Environment written to:    appxd-8060.env
         Service script written to: /etc/rc.d/init.d/appxd-8060
-<
<
+   uappxd -install -port=8060 -name=appx8060 -displayName="Appx-Production(8060)" -engine=/usr/local/appx/appx APPXPATH=c:\appx\data APPX_KEYMAP=Windows
->
>
+   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:

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