| |
| META TOPICPARENT |
name="APPXConnectionManager" |
APPX Connection Manager For Unix/Linux |
| |
The Name of the Service |
|
<
< | Each instance of an APPX Connection Service must have a unique name. When creating an instance of a service, the -name option may be used to specify the name that you want the service to have. If you do not specify a name, a name will be assigned for you. |
>
> | Each instance of an APPX Connection Service must have a unique name. When creating an instance of a service, the -name option may be used to specify the name that you want the service to have. If you do not specify a name, a name will be assigned for you. |
| | TCP/IP Port Number |
|
<
< | When creating an instance of an APPX Connection Service, the -port option must be used to specify the TCP/IP port number on which the service is to listen for connection requests. Any available TCP/IP port number may be specified when installing an instance of the APPX Connection Manager Service. However, as a matter of convention, most APPX administrators configure the APPX Connection Service to listen for connections on port 8060. If additional intances of the APPX Connection Manager are configured, each instance is typically assigned the next available port number after 8060. |
>
> | When creating an instance of an APPX Connection Service, the -port option must be used to specify the TCP/IP port number on which the service is to listen for connection requests. Any available TCP/IP port number may be specified when installing an instance of the APPX Connection Manager Service. However, as a matter of convention, most APPX administrators configure the APPX Connection Service to listen for connections on port 8060. If additional intances of the APPX Connection Manager are configured, each instance is typically assigned the next available port number after 8060. |
| | Changing a Connection Service
Two methods are available for modifying an existing instance of an APPX Connection Service.
Method 1 - The Connection Manager Command (appxdsvc) |
|
<
< | The -modify option of the appxdsvc command can be used to replace a previously configured instance of the APPX Connection Service. This option replaces the existing APPX Connection Service configuration files (ini and env) with two new files configured as specified. |
>
> | The -modify option of the appxdsvc command can be used to replace a previously configured instance of the APPX Connection Service. This option replaces the existing APPX Connection Service configuration files (ini and env) with two new files configured as specified. |
| | Method 2 - Text Editor
A text editor can be used to directly edit the APPX Connection Service configuration files (ini and env). The configuration files include comments to help you make the desired changes.
Managing an APPX Connection Service |
| | -install -name=SERVICENAME [options]... [VARIABLE=VALUE]...
-install -port=PORT [options]... [VARIABLE=VALUE]... |
|
<
< | 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 -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 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. |
>
> | 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. |
| | |
|
<
< | Both forms of the install command allow additional configuration options to be specified. The configuration options are stored in the service configuration file (ini). |
>
> | Both forms of the -install command allow additional configuration options to be specified. The configuration options are stored in the service configuration file (ini). |
| | |
|
<
< | 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. |
>
> | 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. |
| | |
|
<
< | 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. |
>
> | 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. |
| | |
|
<
< | 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. |
>
> | 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]... |
|
<
< | 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. |
>
> | The -replace command is used to replace an existing Connection Service with a new Connection Service with the same name. The -replace command is effectively the same as a -remove command followed by an -install command. After updating the configuration files, the -replace command restarts the 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. |
>
> | 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
Options - General
-name, -ServiceName=SERVICENAME |
|
<
< | The ServiceName uniquely identifies an APPX connection service. When creating (installing) a connection service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when a connection service is being created, the connection service will be created with a default ServiceName based on the TCP/IP port number that was specified: "appxd" followed by a "-" and the specified port number, e.g "appxd-8060". |
>
> | The ServiceName uniquely identifies an APPX connection service. When creating (installing) a connection service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when a connection service is being created, the connection service will be created with a default ServiceName based on the following template: "appxd-" followed by the specified TCP/IP port number, e.g "appxd-8060". |
| |
-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. |
>
> | 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} |
|
<
< | 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. |
>
> | 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 directory in which the service configuration file (ini) for the connection service is located. 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 connection service 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)}
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. |
| |
-TCPNoDelay={true, false} |
|
>
> | 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 TCP to be able to detect that the connection between an APPX session and an APPX client has been lost. |
| | -TCPKeepIdle={300, SECONDS}
-TCPKeepCount={8, COUNT} |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.