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: 40 to 41 | ||||||||
-rwsrwxr-x 1 root root 636843 Jul 11 07:31 appxdsvc
Creating and Configuring an APPX Connection Service | ||||||||
Changed: | ||||||||
< < | 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 instance of the APPX Connection Service must be created, configured, and started before an 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. | |||||||
> > | 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 instance of the APPX Connection Service must be created, configured, and started before an 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. | |||||||
Initial ConfigurationThe -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:
| ||||||||
Line: 53 to 54 | ||||||||
| ||||||||
Changed: | ||||||||
< < | The -modify option of the appxdsvc command is 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 | ||||||||
Changed: | ||||||||
< < | Instead of using the -modify option of the appxdsvc command, you may also change a previously configured instance of the APPX Connection Service by directly editing the APPX Connection Service configuration files with the text editor of your choice. 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. | |||||||
Managing an APPX Connection ServiceTwo methods are available for managing an existing instance of the APPX Connection Service. | ||||||||
Line: 81 to 82 | ||||||||
appxdsvc [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}DESCRIPTION | ||||||||
Changed: | ||||||||
< < | The appxdsvc command is used to configure and manage instances of the APPX Connection Service. | |||||||
> > | The appxdsvc command is used to create, configure, and manage instances of the APPX Connection Service. | |||||||
Changed: | ||||||||
< < | OPTIONS (Configuration) | |||||||
> > | CONFIGURATION OPTIONS | |||||||
-install -port=PORT [options]... [VARIABLE=VALUE]...Configure and start a new Connection Service. | ||||||||
Line: 105 to 106 | ||||||||
-engine, -AppxExecutable | ||||||||
Changed: | ||||||||
< < | -AM, -AuthenticationMethod [Optional] | |||||||
> > | -AM, -AuthenticationMethod={OS-User | Appx-User | HT-User(filename)} [Optional] | |||||||
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. | ||||||||
Changed: | ||||||||
< < | -serviceType, -ServiceType [Optional] | |||||||
> > | -serviceType, -ServiceType=Login [Optional] | |||||||
The only valid value when configuring a Connection Service is "Login". | ||||||||
Changed: | ||||||||
< < | -initScript | |||||||
> > | -initScript=SYSTEMTYPE [Optional]
Used with -install option to specify the type of system that the service script is to be created for [lsb | RedHat ]. If not specified, appxdsvc will determine which type of service script to install. | |||||||
VARIABLE=VALUE [Optional]
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. | ||||||||
Changed: | ||||||||
< < | OPTIONS (Management) | |||||||
> > | 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. | ||||||||
Line: 134 to 136 | ||||||||
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 | ||||||||
Changed: | ||||||||
< < | Warning - the engine that you named has the setuid bit enabled | |||||||
> > | 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) To turn off the setuid bit, chmod u-s ../appx Configuration written to: appxd-8060.ini Environment written to: appxd-8060.env | ||||||||
Changed: | ||||||||
< < | Service script written to: /etc/rc.d/init.d/appxd-8060 | |||||||
> > | Service script written 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 Display the status of an instance of the Connection Service: | ||||||||
Line: 229 to 234 | ||||||||
Changed: | ||||||||
< < | -- Page added by: Steve - 17 Jul 2007 | |||||||
> > | -- Page added by: Steve - 17 Jul 2007 | |||||||
|