Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Added: | ||||||||
> > | ||||||||
APPX Connection Manager For Unix/LinuxThis 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: 117 to 118 | ||||||||
Configuration - Commands | ||||||||
Changed: | ||||||||
< < | -install -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]... | |||||||
> > | -install -name=SERVICENAME [options]... [VARIABLE=VALUE]... | |||||||
-install -port=PORT [options]... [VARIABLE=VALUE]... | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | The install command is used to configure a new instance of an APPX Connection Service. Either form of the install command may be used. The first form of the install command requires only that a service name be specified. All other options are optional including the TCP/IP port. Any option not specified will be configured with an appropriate default value. The second form of the install command requires only that a TCP/IP port be specified. All other options are optional including the ServiceName. Any option not specified will be configured with an appropriate default value. | |||||||
Changed: | ||||||||
< < | The first form of the install command requires only that a service name be specified. | |||||||
> > | Both forms of the install command allow additional configuration options to be specified. The configuration options are stored in the service configuration file (ini). | |||||||
Changed: | ||||||||
< < | The second form of the install command requires only that a TCP/IP port be specified. | |||||||
> > | Both forms of the install command optionally allow values to be specified for environment variables. If specified, the environment variables and their values are stored in the environment configuration file (env). The environment variables in the environment configuration file will be set for any APPX sessions which are started by the connection service. | |||||||
Changed: | ||||||||
< < | Both forms of the install command allow for configuration options to be specified. If specified, the configuration options are stored in the service configuration file (ini). Default values will be used for any configuration options that are not specified including the service name. | |||||||
> > | In addition to creating the service configuration file and the environment configuration file, the install command also creates an operating system service that will be automatically started when the computer system is started. | |||||||
Changed: | ||||||||
< < | Both forms of the install command optionally allow values to be specified for environment variables. If specified, the environment variables and their values are stored in the environment configuration file (env). The environment variables in the environment configuration file will be set for any APPX sessions which are started by the connection service. -modify -name=SERVICENAME [options]... [VARIABLE=VALUE]...
The modify command is used to modify the configuration of an existing Connection Service. The specified options will be updated in the service configuration files. Any options not specified will not be changed. | |||||||
> > | After creating the configuration files and the operating system service, the install command starts the service. -modify -name=SERVICENAME [options]... [VARIABLE=VALUE]...
The modify command is used to modify the configuration of an existing Connection Service. The specified options will be updated in the service configuration files. Any options not specified will not be changed. After updating the configuration files, the modify command restarts the service. | |||||||
-replace -name=SERVICENAME [options]... [VARIABLE=VALUE]... | ||||||||
Changed: | ||||||||
< < | The replace command is used to replace an existing Connection Service with a new Connection Service with the same name. The replace option is effectively the same as a remove command followed by an install command. | |||||||
> > | The replace command is used to replace an existing Connection Service with a new Connection Service with the same name. The replace option is effectively the same as a remove command followed by an install command. After updating the configuration files, the replace command restarts the service. | |||||||
Changed: | ||||||||
< < | -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. | |||||||
> > | -remove -name=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. If the service is running when the remove command is executed, the remove command will first stop the service and then remove the service. | |||||||
Configuration - Options
| ||||||||
Line: 149 to 154 | ||||||||
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-LogDirectory={/tmp, LOGDIR} | ||||||||
Added: | ||||||||
> > | 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. | ||||||||
Line: 184 to 190 | ||||||||
-ImpersonateGroup={User, LogonUser, LogonGroup, NamedGroup(groupname), ServiceOwner, ServiceGroup} -Umask=FILECREATIONMASK | ||||||||
Changed: | ||||||||
< < | 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 specified, the FILECREATIONMASK will modify the default permissions of files or directories that are created by the APPX session. The value of FILECREATIONMASK should be an 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. If you want files to be created with the default permissions of 666, the appropriate FILECREATIONMASK value would be 000. For more information on umask values, please refer to your Unix/Linux system documentation. | |||||||
> > | 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. | |||||||
Changed: | ||||||||
< < | If the umask option is not set, files and directories that are created by the APPX session will be given the default permissions of the Service Owner. -IncludeSystemEnv={true, false} | |||||||
> > | If the umask option is not set, files and directories that are created by the APPX session will be given the default permissions of the Service Owner. -IncludeSystemEnv={true, false} | |||||||
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} | ||||||||
Line: 285 to 289 | ||||||||
The -install option of the appxdsvc command creates the configuration file when the service is created. | ||||||||
Changed: | ||||||||
< < | The name of the configuration file is the concatenation of the service name and ".ini". For example, if the service name is "appxd-8060", the name of the configuration file will be "appxd-8060.ini". | |||||||
> > | The name of the configuration file is the concatenation of the service name and ".ini". For example, if the service name is "appxd-8430", the name of the configuration file will be "appxd-8430.ini". | |||||||
The configuration file is created in whichever directory is your current directory at the time that the appxdsvc command is run to create the service. Therefore, before you run the appxdsvc command to create a service, you must first change to the directory where you want the configuration file to reside. For example, if you want the configuration file to be created in the APPX tools directory, you should change to the tools directory before you run the appxdsvc command. | ||||||||
Line: 350 to 353 | ||||||||
The -install option of the appxdsvc command creates the environment file when the service is created. | ||||||||
Changed: | ||||||||
< < | The name of the environment file is the concatenation of the service name and ".env". For example, if the service name is "appxd-8060", the name of the environment file will be "appxd-8060.env". | |||||||
> > | The name of the environment file is the concatenation of the service name and ".env". For example, if the service name is "appxd-8430", the name of the environment file will be "appxd-8430.env". | |||||||
The environment file is created in whichever directory is your current directory at the time that the appxdsvc command is run to create the service. Therefore, before you run the appxdsvc command to create a service, you must first change to the directory where you want the environment file to reside. For example, if you want the environment file to be created in the APPX tools directory, you should change to the tools directory before you run the appxdsvc command. | ||||||||
Line: 371 to 374 | ||||||||
# -------------------------------------------------- APPX_KEYMAP=WINDOWS | ||||||||
Added: | ||||||||
> > |
The Status File (stat)When an APPX Connection Service is started, a status file is created in the specified LogDirectory. If a LogDirectory was not specified, then the status file is created in the /tmp directory. The name of the status file is the concatenation of the service name and ".stat". For example, if the service name is "appxd-8430", the name of the status file will be "appxd-8430.stat". The status file can be viewed to see the actual context within which the service is running.appxd-8430 running as process 28192 Effective User ID 0 Real User ID 0 Configuration values follow *Daemonize = true *DontForkEngine = false *InitScriptStyle = *SleepAfterFork = AppxApplication = AppxDatabase = AppxExecutable = ../appx AppxProcessName = AppxProcessType = AuthenticationMethod = OS-User DisplayName = appxd-8430 ImpersonateGID = true ImpersonateGroup = User ImpersonateUID = true ImpersonateUser = LogonUser IncludeSystemEnv = true LogDirectory = /tmp LogNamePattern = /tmp/appxlog%N.xml LogRotationInterval = 86400 LogRotationSize = 1G RequireSSL = false RequireSSLClientCertificates = false ServerCertificateFile = ServerPrivateKeyFile = ServerPrivateKeyPassphrase = ServiceDisable = false ServiceDisableAppxKeys = false ServiceDisableFMS = false ServiceDisableLogins = false ServiceDisableODBC = ServiceEnableCmds = true ServiceName = appxd-8430 ServiceType = login SockPort = 8430 SSLMode = Optional TCPEnableKeepAlive = true TCPKeepCount = 8 TCPKeepIdle = 300 TCPKeepInterval = 60 TCPNoDelay = true TrustedCAFile = Umask = Environment variables follow APPX_KEYMAP = WINDOWS 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". | |||||||
Added: | ||||||||
> > | 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.
*Daemonize = true *DontForkEngine = false *InitScriptStyle = *SleepAfterFork = AppxApplication = AppxDatabase = AppxExecutable = ../appx AppxProcessName = AppxProcessType = AuthenticationMethod = OS-User DisplayName = appxd-8430 ImpersonateGID = true ImpersonateGroup = User ImpersonateUID = true ImpersonateUser = LogonUser IncludeSystemEnv = true LogDirectory = /tmp LogNamePattern = /tmp/appxlog%N.xml LogRotationInterval = 86400 LogRotationSize = 1G RequireSSL = false RequireSSLClientCertificates = false ServerCertificateFile = ServerPrivateKeyFile = ServerPrivateKeyPassphrase = ServiceDisable = false ServiceDisableAppxKeys = false ServiceDisableFMS = false ServiceDisableLogins = false ServiceDisableODBC = ServiceEnableCmds = true ServiceName = appxd-8430 ServiceType = login SockPort = 8430 SSLMode = Optional TCPEnableKeepAlive = true TCPKeepCount = 8 TCPKeepIdle = 300 TCPKeepInterval = 60 TCPNoDelay = true TrustedCAFile = Umask = createListener complete - listening on port 8430 CAppxD::Run starting handleClients - starting handleClients - waiting | |||||||
Comments: | ||||||||
Deleted: | ||||||||
< < | ||||||||
Read what other users have said about this page or add your own comments.
|