Difference: APPXLoginManagerForUnixLinux (27 vs. 28)

Revision 282007-08-22 - SteveFrizzell

 			 META TOPICPARENT 
			 name="APPXConnectionManager" 
		

 APPX Connection Manager For Unix/Linux
- META TOPICPARENT
+ name="APPXConnectionManager"
 -DisplayName=DISPLAYNAME 
The DisplayName is a "user-friendly" descriptive name for a connection service.  The DISPLAYNAME value will appear in your system's Services control panel and will be displayed by the ps command.  If you don't specify a DISPLAYNAME when a connection service is being created, the connection service will be created with a DISPLAYNAME based on the SERVICENAME.
-<
<
+-engine, -AppxExecutable={../appx, PATHNAME} 
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
->
>
+-engine, -AppxExecutable={../appx, PATHNAME} 
This option identifies the PATHNAME of the APPX engine that is to 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.  If this option is not specified, the default PATHNAME of "../appx" is used to initiate an APPX session.
 -LogDirectory={/tmp, LOGDIR}
-<
<
+When the service is started, two log files are created in the LOGDIR directory - a log file (.log) and a status file (.stat).  Both log files have the same name as the  ServiceName  but one has a file extension of .log and the other has a file extension of .stat.  If the LogDirectory option is not specified, the log files are created in the /tmp directory.
->
>
+When the service is started, two log files are created in the LOGDIR directory - a log file (.log) and a status file (.stat). Both log files have the same name as the ServiceName but one has a file extension of .log and the other has a file extension of .stat. If the LogDirectory option is not specified, the log files are created in the /tmp directory.
 -AM, -AuthenticationMethod={OS-User, Appx-User, HT-User(HTFILENAME)}
-<
<
+Acceptable values are 'OS-User', 'Appx-User', and 'HT-User(HTFILENAME)'. With 'Appx-User' authentication, passwords are validated against the Appx user file With 'OS-User' authentication, passwords are validated by the operating system. 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.  If this option is not specified, the default value is OS-User.
->
>
+This option identifies the method by which the user ID and the password are to be validated when a connection request is received.  If 'OS-User' authentication is specified, the user ID and the password are validated by the connection service using the operating system's authentication service. If 'Appx-User' authentication is specified, the user ID and the password are validated by APPX using the user file which is maintained in APPX System Administration. If 'HT-User(HTFILENAME)' authentication is specified, the user ID and the password are validated by the connection service using the HTFILENAME file is maintained with the htpasswd utility. If you specify 'Appx-User' authentication or HT-User authentication, the user being validated does not need an OS user account.  If no authentication method is specified, the default authentication method is OS-User.
 -ServiceType=Login 
The only valid value when configuring a Connection Service is "Login".  If this option is not specified, the default value is Login.

-ServiceDisable={true, false}
->
>
+This option can be used to temporarily disable or "turn off" the connection service.  If set to true, the connection service will still run but it will not accept login requests.
 -ServiceDisableLogin={true, false}
->
>
+This option can be used to disable or "turn off" processing of login requests from interactive clients.  If set to true, login requests from interactive clients will not be processed.
 -ServiceDisableFMS={true, false}
->
>
+This option can be used to disable or "turn off" processing of connection requests from APPX/Net connections including the Windows APPX/ODBC driver.  If set to true, connection requests from APPX/Net clients will not be processed.
 -ServiceDisableAppxKeys={true, false}
->
>
+This option can be used to disable the ability to define an APPX keymap.  If set to true, those interactive clients which support the ability to define an APPX keymap will not be allowed to do so.
 -initScript={lsb, RedHat} 
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 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.
 -ImpersonateUser={LogonUser, NamedUser(USERID), ServiceOwner} 
This option determines which O/S user the APPX session should impersonate (run as).

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