| |
| 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. |
| | 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 command and the - replace command of the appxdsvc connection manager can be used to modify or replace a previously configured instance of the APPX Connection Service. These options update the existing APPX Connection Service configuration files (ini and env) with the options 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. |
>
> | 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. If you use this method to modify an existing configuration, you should exercise care to ensure that the syntax is correct. The preferred method for modifying a connection service is with Medhod 1 above. |
| | Managing an APPX Connection Service
Two methods are available for managing an existing instance of the APPX Connection Service.
|
| | -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
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. |
>
> | -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
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. |
>
> | -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}
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
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. |
>
> | -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. |
>
> | 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}
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. |
| | disabled - APPX clients may only request a plain text connection
-TrustedCAFile=CAFILENAME |
|
<
< | This option idenfies the pathname of the file that identifies which client certificates to trust. |
>
> | This option identifies the pathname of the file that identifies which client certificates to trust. |
| |
-ServerCertificateFile=CERTFILENAME
This option identifies the pathname of the server's X509 certificate (leave blank for anonymous connections). |
| | 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 |
|
<
< | appxdsvc [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME} |
>
> | appxdsvc [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME} |
| |
MANAGEMENT OPTIONS
-start | < blank > |
|
<
< | Start an instance of the Connection Manager service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files. |
>
> | Start an instance of the Connection Manager service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files. |
| |
-stop |
|
<
< | Stop the instance of the Connection Manager service that was started with the SERVICENAME.ini file. |
>
> | Stop the instance of the Connection Manager service that was started with the SERVICENAME.ini file. |
| |
-restart |
|
<
< | Restart (stop and then start) the instance of the Connection Manager that was started with the SERVICENAME.ini file. |
>
> | Restart (stop and then start) the instance of the Connection Manager that was started with the SERVICENAME.ini file. |
| |
-status |
|
<
< | Report the status of the instance of the Connection Manager that was started with the SERVICENAME.ini file. |
>
> | Report the status of the instance of the Connection Manager that was started with the SERVICENAME.ini file. |
| |
EXAMPLES |
| | you may not want that bit set for the authentication method that you have chosen (OS-User)
To turn off the setuid bit, chmod u-s
../appx Configuration written to: appxd-8060.ini |
|
<
< | Environment written to: appxd-8060.env
Service script written to: /etc/rc.d/init.d/appxd-8060 |
>
> | Environment written to: appxd-8060.envtten to: /etc/rc.d/init.d/appxd-8060 |
| |
appxdsvc -install -port=8060 -name=appx8060 -displayName="Appx-Production(8060)" -engine=/usr/local/appx/appx APPXPATH=c:\appx\data APPX_KEYMAP=WINDOWS |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.