Difference: APPXLoginManagerForUnixLinux (33 vs. 34)

Revision 342008-04-17 - JoeOrtagus

 			 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.
- META TOPICPARENT
+ name="APPXConnectionManager"
  Client request
 
 

 Installing the APPX Connection Manager Command ( appxdsvc)
-<
<
+The APPX Connection Manager ( appxdsvc) command is installed automatically when you install APPX on your system. The installer sets the necessary owner and group permissions for the appxdsvc command.  So, there is nothing additional that you need to do to install the appxdsvc command. However, after you install APPX, you will need to run the appxdsvc command to configure and start an instance of the APPX Connection Service before any remote client connections may be established.
->
>
+The APPX Connection Manager ( appxdsvc) command is installed automatically when you install APPX on your system. The installer sets the necessary owner and group permissions for the appxdsvc command.  So, there is nothing additional that you need to do to install the appxdsvc command. However, after you install APPX, you will need to run the appxdsvc command to configure and start an instance of the APPX Connection Service before any remote client connections may be established.
 The appxdsvc command is installed into the "tools" subdirectory of the directory where you installed APPX. So, if you installed APPX in "/usr/local/appx", the full pathname of the appxdsvc command will be "/usr/local/appx/tools/appxdsvc".
-<
<
+The appxdsvc command must run with the permissions of the root user.  Therefore, the owner of the appxdsvc command should be the root user and the SUID bit should be set so that the appxdsvc command can be run by users other than root but still be run with the permissions of root.
->
>
+The appxdsvc command must run with the permissions of the root user.  Therefore, the owner of the appxdsvc command should be the root user and the SUID bit should be set so that the appxdsvc command can be run by users other than root but still be run with the permissions of root.
-<
<
+In the event that it is necessary to reset the permissions on the appxdsvc command, the following commands can be run by the root user to set the necessary owner and group permissions for the appxdsvc command.
->
>
+In the event that it is necessary to reset the permissions on the appxdsvc command, the following commands can be run by the root user to set the necessary owner and group permissions for the appxdsvc command.
 cd /usr/local/appx/tools
 -rwsrwxr-x 1 root root    636843 Jul 11 07:31 appxdsvc
-<
<
+ Creating and Configuring an APPX Connection Service
->
>
+ Creating and Configuring an APPX Connection Service
 On Unix/Linux systems, an instance of the APPX Connection Service is initially created, configured, and started by running the appxdsvc command with the -install option. At least one appropriately configured instance of the APPX Connection Service must be created, configured, and started before a remote APPX Client can initiate an APPX session. You may create, configure, and start as many different instances of the APPX Connection Service as you desire. However, each concurrently running instance must be configured to listen for connection requests on a different TCP/IP port.
-<
<
+ Creating a Connection Service
->
>
+ Creating a Connection Service
-<
<
+Before remote clients can connect to an APPX system, at least one instance of an APPX Connection Service must be configured and started.
->
>
+Before remote clients can connect to an APPX system, at least one instance of an APPX Connection Service must be configured and started.
 The -install option of the appxdsvc command is used to initially create, configure, and start an instance of the APPX Connection Service. The following steps are performed:  
 A configuration file (ini) is created
  A service is created
  The service is started
-<
<
+For compete information on using the -install option of the appxdsvc command, please refer to the usage section of this page.
->
>
+For compete information on using the -install option of the appxdsvc command, please refer to the usage section of this page.
  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. 
 Changing a Connection Service  
Two methods are available for modifying an existing instance of an APPX Connection Service.
->
>
+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  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.
->
>
+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.  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.
->
>
+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.
-<
<
->
>
  Method 1 - appxdsvc command
-<
<
+The appxdsvc command can be used to manage an instance of the APPX Connection Service. The appxdsvc command can be used to start, stop, restart, or display the status of an instance of an APPX Connection Service.
->
>
+The appxdsvc command can be used to manage an instance of the APPX Connection Service. The appxdsvc command can be used to start, stop, restart, or display the status of an instance of an APPX Connection Service.
  Method 2 - O/S Services 

Your operating system includes commands or programs that can be used to manage services. APPX Connection Services can be managed with these tools. The actual commands and programs vary depending on your operating system. 
 Usage (appxdsvc)
-<
<
->
>
  Synopsis - Service Configuration
-<
<
+The appxdsvc service configuration commands are used to create, configure, and remove an instance of an APPX Connection Service.
->
>
+The appxdsvc service configuration commands are used to create, configure, and remove an instance of an APPX Connection Service.
 appxdsvc -install -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
 appxdsvc -replace -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]... 

appxdsvc -remove -serviceName=SERVICENAME
-<
<
+ Configuration - Commands
->
>
+ Configuration - Commands
 -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.
->
>
+-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 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. 

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.
->
>
+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 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.
->
>
+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 following template: "appxd-" followed by the specified TCP/IP 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 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.
->
>
+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 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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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 ServiceOwner.  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 ServiceOwner.  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).
->
>
+This option determines which O/S user the APPX session should impersonate (run as).
-<
<
+If LogonUser is specified, the user ID of the APPX session will be set to the user ID that was provided by the client login.  This user ID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the LogonUser option is specified.
->
>
+If LogonUser is specified, the user ID of the APPX session will be set to the user ID that was provided by the client login.  This user ID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the LogonUser option is specified.
-<
<
+If NamedUser is specified, the user ID of the APPX session will be set to the specified USERID.  This USERID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the NamedUser option is specified.
->
>
+If NamedUser is specified, the user ID of the APPX session will be set to the specified USERID.  This USERID must be a valid O/S user.  The connection service must be running with the permissions of the root user if the NamedUser option is specified.
-<
<
+If ServiceOwner is specified, the user ID of the APPX session will be the user ID that the connection service is running as.
->
>
+If ServiceOwner is specified, the user ID of the APPX session will be the user ID that the connection service is running as.
 -ImpersonateGID={true, false}
-<
<
+If this value is set to false, an APPX session which is initiated by the connection service will run with the group permissions of the connection ServiceOwner.  Set this value to true if you want the APPX session to have group permissions based on the ImpersonateGroup option.
->
>
+If this value is set to false, an APPX session which is initiated by the connection service will run with the group permissions of the connection ServiceOwner.  Set this value to true if you want the APPX session to have group permissions based on the ImpersonateGroup option.
 -ImpersonateGroup={User, LogonUser, LogonGroup, NamedGroup(GROUPNAME), ServiceOwner, ServiceGroup}
-<
<
+This option determines which group permissions the APPX session should run with.
->
>
+This option determines which group permissions the APPX session should run with.
 If User is specified, the APPX session will run with the group permissions of the user that the session is running as (impersonating).
-<
<
+If LogonUser or LogonGroup is specified, the APPX session will run with the group permissions of the user ID that the client provided in conjunction with the connection request.  The user ID must be a valid O/S user.
->
>
+If LogonUser or LogonGroup is specified, the APPX session will run with the group permissions of the user ID that the client provided in conjunction with the connection request.  The user ID must be a valid O/S user.
-<
<
+If NamedGroup is specified, the group permissions of the APPX session will be set to the specified GROUPNAME.  This GROUPNAME must be a valid O/S group.
->
>
+If NamedGroup is specified, the group permissions of the APPX session will be set to the specified GROUPNAME.  This GROUPNAME must be a valid O/S group.
 If ServiceOwner or ServiceGroup is specified.

-Umask=FILECREATIONMASK
-<
<
+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.
->
>
+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.
 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.
->
>
+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}
-<
<
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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.
->
>
+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 an APPX session to be able to detect that the connection between an APPX session and an APPX client has been lost.  If this option is set to true and an APPX session has been waiting for a response from an APPX client for the length of time specified by TCPKeepIdle, then the APPX session will attempt to contact the APPX client to see if it can still be reached.  If the APPX client cannot be contacted, then the APPX session will attempt to contact the APPX client every TCPKeepInterval seconds up to TCPKeepCount times.  After TCPKeepCount attempts, if the APPX client is unable to be contacted, then the APPX session terminates.
->
>
+Set this option to true if you want an APPX session to be able to detect that the connection between an APPX session and an APPX client has been lost.  If this option is set to true and an APPX session has been waiting for a response from an APPX client for the length of time specified by TCPKeepIdle, then the APPX session will attempt to contact the APPX client to see if it can still be reached.  If the APPX client cannot be contacted, then the APPX session will attempt to contact the APPX client every TCPKeepInterval seconds up to TCPKeepCount times.  After TCPKeepCount attempts, if the APPX client is unable to be contacted, then the APPX session terminates.
 -TCPKeepIdle={300, SECONDS}
-<
<
+This option is used to set the number of seconds that an APPX session is to wait for a response from an APPX client before checking to see if the client can still be contacted.
->
>
+This option is used to set the number of seconds that an APPX session is to wait for a response from an APPX client before checking to see if the client can still be contacted.
 -TCPKeepCount={8, COUNT}
-<
<
+This option is used to set the number of times that an APPX session is to attempt to contact a non-responsive APPX client before the APPX session should terminate.
->
>
+This option is used to set the number of times that an APPX session is to attempt to contact a non-responsive APPX client before the APPX session should terminate.
 -TCPKeepInterval={60, SECONDS}
-<
<
+This option is used to set the number of seconds that an APPX session is to wait between attemps to contact a non-responsive APPX client.
->
>
+This option is used to set the number of seconds that an APPX session is to wait between attemps to contact a non-responsive APPX client.
  Options - SSL 

-SSLMode={optional, required, disabled}
-<
<
+This option is used to control whether or not APPX clients must use SSL connections. 
optional - APPX clients may request either an SSL connection or a plain text connection
->
>
+This option is used to control whether or not APPX clients must use SSL connections. 
optional - APPX clients may request either an SSL connection or a plain text connection
 required - APPX clients must request an SSL connection 

disabled - APPX clients may only request a plain text connection

-TrustedCAFile=CAFILENAME
-<
<
+This option identifies 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).
->
>
+This option identifies the pathname of the server's X509 certificate (leave blank for anonymous connections).
 -ServerPrivateKeyFile=KEYFILENAME
-<
<
+This option idenfies the pathname of server's private key file (unlocks the ServerCertificateFile).
->
>
+This option idenfies the pathname of server's private key file (unlocks the ServerCertificateFile).
 -RequireSSL={true, false}
-<
<
+This option is not needed and has not been implemented.
->
>
+This option is not needed and has not been implemented.
 -RequireSSLClientCertificates={true, false}
-<
<
+This option is not needed and has not been implemented.
->
>
+This option is not needed and has not been implemented.
 -ServerPrivateKeyPassphrase=PASSPHRASE
-<
<
+This option is not needed and has not been implemented.
->
>
+This option is not needed and has not been implemented.
  Configuration - Environment Variables
-<
<
+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.
->
>
+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 | < blank > 
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 

Example 1: Configure and start a new instance of the Connection Service that will listen for connection requests on port 8060: 

appxdsvc -install -port=8060
-<
<
->
>
 Warning - the engine that you named has the setuid bit enabled
you may not want that bit set for the authentication method that you have chosen (OS-User)
 appxdsvc -start appx8060
-<
<
+ The Configuration File (ini) 
Each instance of an APPX Connection Service has a configuration file that is used to store the various parameters relating to that specific instance of the connection service.
->
>
+ The Configuration File (ini) 
Each instance of an APPX Connection Service has a configuration file that is used to store the various parameters relating to that specific instance of the connection service.
 The -install option of the appxdsvc command creates the configuration file when the service is created.
-<
<
+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 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.
->
>
+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.
-<
<
+The name of the configuration file and the location of the configuration file should not be changed.  The service that is created will not work correctly if the name or the location of the configuration file is changed.
->
>
+The name of the configuration file and the location of the configuration file should not be changed.  The service that is created will not work correctly if the name or the location of the configuration file is changed.
 # Appx connection manager configuration file
#
  The Environment File (env)
-<
<
+Each instance of an APPX Connection Service has an environment file that is used to store the environment variables relating to that specific instance of the connection service.  The environment variables in the environment file are inherited by each APPX session that is started by the APPX Connection Service.
->
>
+Each instance of an APPX Connection Service has an environment file that is used to store the environment variables relating to that specific instance of the connection service.  The environment variables in the environment file are inherited by each APPX session that is started by the APPX Connection Service.
-<
<
+The -install option of the appxdsvc command creates the environment file when the service is created.
->
>
+The -install option of the appxdsvc command creates the environment file when the service is created.
-<
<
+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 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.
->
>
+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.
-<
<
+The name of the environment file and the location of the environment file should not be changed.  The service that is created will not work correctly if the name or the location of the environment file is changed.
->
>
+The name of the environment file and the location of the environment file should not be changed.  The service that is created will not work correctly if the name or the location of the environment file is changed.
 # Appx connection manager environment variables
#
  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.
->
>
+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 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.
->
>
+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
->
>
+Real User ID      0
 Configuration values follow
*Daemonize = true
*DontForkEngine = false
  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.
->
>
+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 log 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".
-<
<
+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.
->
>
+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

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