| |
| META TOPICPARENT |
name="APPX500Features" |
APPX Login Manager For Unix/Linux |
| |
-
- Service configuration
- Client request
|
|
<
< | Installing the APPX Connection Manager Command ( appxLoginMgr) |
>
> | Installing the APPX Login Manager Command ( appxLoginMgr) |
| | The APPX Login Manager ( appxLoginMgr) command is installed automatically when you install APPX on your system. The installer sets the necessary owner and group permissions for the appxLoginMgr command. So, there is nothing additional that you need to do to install the appxLoginMgr command. However, after you install APPX, you will need to run the appxLoginMgr command to configure and start an instance of the APPX Connection Service before any remote client connections may be established.
The appxLoginMgr 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 appxLoginMgr command will be "/usr/local/appx/tools/appxLoginMgr". |
| |
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 for example, appxd-8060.
TCP/IP Port Number |
|
<
< | When creating an instance of an APPX Connection Service, the -SockPort 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 instances 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 -SockPort 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 Login 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 instances of the APPX Login 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.
|
| | 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. Note that when specifying variables on the command line, you do not prefix them with a dash if you are referring to environment variables. |
>
> | 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 Login Manager. Note that when specifying variables on the command line, you do not prefix them with a dash if you are referring to environment variables. |
| | Synopsis - Service Management
appxLoginMgr [-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 Login 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 Login 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 Login 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 Login Manager that was started with the SERVICENAME.ini file. |
| |
EXAMPLES |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.