Difference: APPXLoginManagerForUnixLinux (21 vs. 22)

Revision 222007-08-15 - SteveFrizzell

 			 META TOPICPARENT 
			 name="APPXConnectionManager" 
		

 APPX Connection Manager For Unix/Linux
- META TOPICPARENT
+ name="APPXConnectionManager"
 appxdsvc -remove -serviceName=SERVICENAME 
 Configuration - Commands
-<
<
+ -install -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
->
>
+-install -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
 -install  -port=PORT [options]... [VARIABLE=VALUE]... 
The install command is used to configure and start a new instance of an APPX Connection Service. Either form of the install command may be used.
 -remove -servicename=SERVICENAME 
The remove command is used to remove an existing Connection Service. The remove command will remove the configuration files (ini and env) and the corresponding operating system service.
 Configuration - Options
-<
<
+ -port, -SockPort [Required with -install option] 
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.
->
>
+ Options - Session Identity/Permissions 

-ImpersonateGID={true, false} 

-ImpersonateGroup={LogonUser, NamedGroup(groupname), ServiceOwner} 

-ImpersonateUID={true, false} 

-ImpersonateUser={LogonUser, NamedUser(username), ServiceOwner} 

-Umask=FILECREATIONMASK 

-IncludeSystemEnv={true, false}
  Options - General
-<
<
+-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".
->
>
+-name, -ServiceName=SERVICENAME 
The specified SERVICENAME will 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".
-<
<
+-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)
->
>
+-DisplayName=DISPLAYNAME 
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)
-<
<
+-engine, -AppxExecutable=PATHNAME [Optional]
->
>
+-engine, -AppxExecutable=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
-<
<
+-AM, -AuthenticationMethod={OS-User | Appx-User | HT-User(filename)}  [Optional]
->
>
+-LogDirectory={/tmp, LOGDIR} 

-AM, -AuthenticationMethod={OS-User | Appx-User | HT-User(filename)}
 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 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.
-<
<
+-ServiceType=Login [Optional]
->
>
+-ServiceType=Login
 The only valid value when configuring a Connection Service is "Login".  If this option is not specified, the default value is Login.
-<
<
+-initScript={lsb, RedHat } [Optional]
->
>
+-ServiceDisable={true, false} 

-ServiceDisableLogin={true, false} 

-ServiceDisableFMS={true, false} 

-ServiceDisableAppxKeys={true, false} 

-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 - Startup Process
-<
<
+-ServiceEnableCmds={true, false} [Optional]
->
>
+-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.
-<
<
+-AppxDatabase=DATABASEID [Optional]
->
>
+-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.
-<
<
+-AppxApplication=APPLICATIONID [Optional]
->
>
+-AppxApplication=APPLICATIONID
 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 APPLICATIONID must be valid, i.e. it must be defined in the Applications file in APPX System Administration.  The specified APPLICATIONID must also be identified in APPX System Administration as a related application for the specified DATABASEID.
-<
<
+-AppxProcessType={Menu, Job, Input, Output, Update, Action, Inquiry, Query, Status, Subroutine} [Optional]
->
>
+-AppxProcessType={Menu, Job, Input, Output, Update, Action, Inquiry, Query, Status, Subroutine}
 This option must be specified if the connection service is being configured to invoke a specific startup process when a client session is initiated.  This option identifies the type of process that is to be invoked when a client session is initiated.
-<
<
+-AppxProcessName=PROCESSNAME [Optional]
->
>
+-AppxProcessName=PROCESSNAME
 This option must be specified if the connection service is being configured to invoke a specific startup process when a client session is initiated.  This option identifies the name of the process that is to be invoked when a client session is initiated.  The PROCESSNAME must be of the type specified and must be defined in the specified APPX Application.
->
>
+ Options - TCP/IP 

-port, -SockPort={8060, PORT} 
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.

-TCPNoDelay={true, false} 

-TCPEnableKeepAlive={true, false} 

-TCPKeepIdle={300, SECONDS} 

-TCPKeepCount={8, COUNT} 

-TCPKeepInterval={60, SECONDS}
  Options - SSL
-<
<
+*-SSLMode={optional, required, disabled, forcedOn, forcedOff} [Optional]
->
>
+-SSLMode={optional, required, disabled}
-<
<
+-RequireSSL={true, false} [Optional]
->
>
+-RequireSSL={true, false}
-<
<
+-RequireSSLClientCertificates={true, false} [Optional]
->
>
+-RequireSSLClientCertificates={true, false}
 -ServerCertificateFile=CERTFILENAME
 -ServerPrivateKeyPassphrase=PASSPHRASE
-<
<
+-TrustedCAFile=CAFILENAME
->
>
+-TrustedCAFile=CAFILENAME
  Configuration - Environment Variables
-<
<
+VARIABLE=VALUE [Optional]
->
>
+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. 

 Synopsis - Service Management

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