Difference: APPXLoginManagerForUnixLinux (30 vs. 31)

Revision 312007-08-24 - SteveFrizzell

 			 META TOPICPARENT 
			 name="APPXConnectionManager"
- META TOPICPARENT
+ name="APPXConnectionManager"
-<
<
  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.
 The APPX Connection Manager command is used to configure and manage APPX Connection Services.
-<
<
+An APPX Connection Services:  
 Listen for a connection request from a remote APPX Client on the designated TCP/IP port;
  Set the appropriate environment and options
  Initiate an APPX session for the APPX Client that requested a connection.
->
>
+An APPX Connection Service listens for and processes connection requests from various types of APPX clients.
-<
<
+APPX Conection Services process connection requests for the following types of remote APPX clients:
->
>
+The following types of remote APPX clients are supported:
  APPX GUI Client (Java)
  Windows Client (Win32)
  Character mode client (Unix/Linux Curses)
 Used with -install option to specify the type of operating system that the service script is to be created for. If this option is not specified, appxdsvc will determine which type of service script to install.
 Options - Session Identity/Permissions 
-ImpersonateUID={true, false}
-<
<
+If this value is set to false, an APPX session which is initiated by the connection service will run as the user of the connection service.  Set this value to true if you want the APPX session to run with the permissions of a user (impersonate) other than the user of the connection service.  If this value is set to true, then the ImpersonateUser option determines which user the APPX session should impersonate.
->
>
+If this value is set to false, an APPX session which is initiated by the connection service will run as the user of the connection ServiceOwner.  Set this value to true if you want the APPX session to run with the permissions of a user (impersonate) other than the user of the connection service.  If this value is set to true, then the ImpersonateUser option determines which user the APPX session should impersonate.
 -ImpersonateUser={LogonUser, NamedUser(USERID), ServiceOwner} 
This option determines which O/S user the APPX session should impersonate (run as). 

If LogonUser is specified, the user ID of the APPX session will be set to the user ID that was provided by the client login.  This user ID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the LogonUser option is specified.
-<
<
+If NamedUser is specifed, the user ID of the APPX session will be set to the specified USERID.  This USERID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the NamedUser option is specified.
->
>
+If NamedUser is specified, the user ID of the APPX session will be set to the specified USERID.  This USERID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the NamedUser option is specified.
 If ServiceOwner is specified, the user ID of the APPX session will be the user ID that the connection service is running as.

-ImpersonateGID={true, false}
->
>
+If this value is set to false, an APPX session which is initiated by the connection service will run with the group permissions of the connection ServiceOwner.  Set this value to true if you want the APPX session to have group permissions based on the ImpersonateGroup option.

-ImpersonateGroup={User, LogonUser, LogonGroup, NamedGroup(GROUPNAME), ServiceOwner, ServiceGroup} 
This option determines which group permissions the APPX session should run with. 

If User is specified, the APPX session will run with the group permissions of the user that the session is running as (impersonating). 

If LogonUser or LogonGroup is specified, the APPX session will run with the group permissions of the user ID that the client provided in conjunction with the connection request.  The user ID must be a valid O/S user. 

If NamedGroup is specified, the group permissions of the APPX session will be set to the specified GROUPNAME.  This GROUPNAME must be a valid O/S group.
-<
<
+-ImpersonateGroup={User, LogonUser, LogonGroup, NamedGroup(groupname), ServiceOwner, ServiceGroup}
->
>
+If ServiceOwner or ServiceGroup is specified.
 -Umask=FILECREATIONMASK 
When a file is created, the default permissions set by Unix/Linux are 666 (-rw-rw-rw-). When a directory is created, the default permissions set by Unix/Linux are 777 (drwxrwxrwx). If the umask option is specified, the FILECREATIONMASK value will modify the default permissions of files or directories that are created by the APPX session. The value of FILECREATIONMASK must be a decimal, hex, or octal number whose bits will be used to mask or turn off the corresonding bits of the default file creation permissions. For example, if you want files to be created with permissions of 644, the appropriate FILECREATIONMASK value would be 022 (octal). If you want files to be created with the default permissions of 666, the appropriate FILECREATIONMASK value would be 000 (octal). For more information on umask values, please refer to your Unix/Linux system documentation.
 Set this option to true if you want the APPX sessions which are initiated by the connection service to inherit the environment of the connection service.
 Options - Startup Process 
-ServiceEnableCmds={true, false}
-<
<
+Set this option to true if you want to allow the client to specify a startup process. Set this option to false if you do not want to allow the client to specify a startup process. If set to  true , then any APPX startup process that may have been specified by the client will be invoked when the connection with the APPX session is established. If set to true, then any startup process that is specified by the client will take precedence over any startup process that may have been specified in the connection service configuration. If the option is not specified, the default value is true.
->
>
+Set this option to true if you want to allow the client to specify a startup process. Set this option to false if you do not want to allow the client to specify a startup process. If set to true, then any APPX startup process that may have been specified by the client will be invoked when the connection with the APPX session is established. If set to true, then any startup process that is specified by the client will take precedence over any startup process that may have been specified in the connection service configuration. If the option is not specified, the default value is true.
 -AppxDatabase=DATABASEID 
This option must be specified if the connection service is being configured to invoke a specific startup process when a client session is initiated.  If specified, the DATABASEID must be valid, i.e. it must be defined in the Databases file in APPX System Administration.
 This option is used to tune the network performance of the APPX session.  When set to true, TCP will send partially filled packets of data rather than wait for a packet to fill before sending it.  This can result in improved interactive response time for the APPX session but will likely increase the number of data packets being transmitted over the network. 

-TCPEnableKeepAlive={true, false}
-<
<
+Set this option to true if you want an APPX session to be able to detect that the connection between an APPX session and an APPX client has been lost.  If this option is set to true and there is no activity between the APPX session and the APPX client for the length of time specified by TCPKeepIdle, then the APPX session will attempt to contact the APPX client to see if it can still be reached.  If the APPX client cannot be contacted, then the APPX session will attempt to contact the APPX client every TCPKeepInterval seconds up to TCPKeepCount times.  After TCPKeepCount attemps, if the APPX client is unable to be contacted, then the APPX session terminates.
->
>
+Set this option to true if you want an APPX session to be able to detect that the connection between an APPX session and an APPX client has been lost.  If this option is set to true and an APPX session has been waiting for a response from an APPX client for the length of time specified by TCPKeepIdle, then the APPX session will attempt to contact the APPX client to see if it can still be reached.  If the APPX client cannot be contacted, then the APPX session will attempt to contact the APPX client every TCPKeepInterval seconds up to TCPKeepCount times.  After TCPKeepCount attempts, if the APPX client is unable to be contacted, then the APPX session terminates.
 -TCPKeepIdle={300, SECONDS}
->
>
+This option is used to set the number of seconds that an APPX session is to wait for a response from an APPX client before checking to see if the client can still be contacted.
 -TCPKeepCount={8, COUNT}
->
>
+This option is used to set the number of times that an APPX session is to attempt to contact a non-responsive APPX client before the APPX session should terminate.
 -TCPKeepInterval={60, SECONDS}
->
>
+This option is used to set the number of seconds that an APPX session is to wait between attemps to contact a non-responsive APPX client.
  Options - SSL
-<
<
+-SSLMode={optional, required, disabled}
-<
<
+-RequireSSL={true, false}
->
>
+-SSLMode={optional, required, disabled} 
This option is used to control whether or not APPX clients must use SSL connections. 
optional - APPX clients may request either an SSL connection or a plain text connection 

required - APPX clients must request an SSL connection 

disabled - APPX clients may only request a plain text connection
-<
<
+-RequireSSLClientCertificates={true, false}
->
>
+-TrustedCAFile=CAFILENAME 
This option idenfies the pathname of the file that identifies which client certificates to trust.
-<
<
+-ServerCertificateFile=CERTFILENAME
->
>
+-ServerCertificateFile=CERTFILENAME 
This option identifies the pathname of the server's X509 certificate (leave blank for anonymous connections).
-<
<
+-ServerPrivateKeyFile=KEYFILENAME
->
>
+-ServerPrivateKeyFile=KEYFILENAME 
This option idenfies the pathname of server's private key file (unlocks the ServerCertificateFile).
-<
<
+-ServerPrivateKeyPassphrase=PASSPHRASE
->
>
+-RequireSSL={true, false} 
This option is not needed and has not been implemented.
-<
<
+-TrustedCAFile=CAFILENAME
->
>
+-RequireSSLClientCertificates={true, false} 
This option is not needed and has not been implemented.

-ServerPrivateKeyPassphrase=PASSPHRASE 
This option is not needed and has not been implemented.
  Configuration - Environment Variables 
VARIABLE=VALUE 
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.
 APPX_KEYMAP = WINDOWS
-<
<
+ The Log File (log)
->
>
+ The Log File (log)
 When an APPX Connection Service is started, a log file is created in the specified LogDirectory. If a LogDirectory was not specified, then the log file is created in the /tmp directory.
-<
<
+The name of the status file is the concatenation of the service name and ".log".  For example, if the service name is "appxd-8430", the name of the log file will be "appxd-8430.log".
->
>
+The name of the log file is the concatenation of the service name and ".log". For example, if the service name is "appxd-8430", the name of the log file will be "appxd-8430.log".
 When the connection service is started, the log file is initialized with the configuration of the connection service.  The configuration information is followed by a dialog of messages relating to actions performed by the connection service.  Each time the connection service processes a connection request, messages relating to the connection request are appended to the log file.

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