Difference: APPXLoginManagerForUnixLinux (47 vs. 48)

Revision 482008-07-29 - JeanNeron

 			 META TOPICPARENT 
			 name="APPXConnectionManager"
- META TOPICPARENT
+ name="APPXConnectionManager"
->
>
  APPX Login Manager For Unix/Linux 
This page describes how to install the APPX Login Manager command and how to use it to install, configure, and manage APPX Login Services on Unix/Linux systems.
 In the event that it is necessary to reset the permissions on the appxLoginMgr command, the following commands can be run by the root user to set the necessary owner and group permissions for the appxLoginMgr command.
-<
<
+ cd /usr/local/appx/tools
chown root appxLoginMgr
chgrp appxgrp appxLoginMgr
chmod 4775 appxLoginMgr
->
>
+ cd /usr/local/appx/tools
chown root appxLoginMgr
chgrp appxgrp appxLoginMgr
chmod 4775 appxLoginMgr
 You can check the permissions of the appxLoginMgr command by running the following command:
-<
<
+ls -l appxLoginMgr
->
>
+ls -l appxLoginMgr
 The recommended permissions should be as follows:
 The appxLoginMgr command can be used to manage an instance of the APPX Connection Service. The appxLoginMgr 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.  Red Hat uses the command line tool service.
->
>
+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.  Red Hat uses the command line tool service.
-<
<
+[root@tubes tools]# service appxd-8060 status
->
>
+[root@tubes tools]# service appxd-8060 status
 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)
-<
<
+ Usage (appxdsvc)
->
>
+ Usage (appxLoginMgr)
  Synopsis - Service Configuration 
The appxLoginMgr service configuration commands are used to create, configure, and remove an instance of an APPX Connection Service.
 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, appxLoginMgr 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.
 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}
->
>
+  appxLoginMgr [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}
 MANAGEMENT OPTIONS 
 -start | < blank >
 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
->
>
+appxLoginMgr -install -port=8060
 Warning - the engine that you named has the setuid bit enabled
 ../appx Configuration written to: appxd-8060.ini
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
->
>
+appxLoginMgr -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:
-<
<
+appxdsvc -status appx8060
->
>
+ appxLoginMgr
-status appx8060
 Shutdown a running instance of the Connection Service:
-<
<
+appxdsvc -stop appx8060
->
>
+appxLoginMgr -stop appx8060
 Start a previously configured instance of the Connection Service:
-<
<
+appxdsvc -start appx8060
->
>
+appxLoginMgr -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 -install option of the appxdsvc command creates the configuration file when the service is created.
->
>
+The -install option of the appxLoginMgr 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 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 appxLoginMgr command is run to create the service. Therefore, before you run the appxLoginMgr 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 appxLoginMgr 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 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.
-<
<
+The -install option of the appxdsvc command creates the environment file when the service is created.
->
>
+The -install option of the appxLoginMgr 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 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 appxLoginMgr command is run to create the service. Therefore, before you run the appxLoginMgr 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 appxLoginMgr 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.
  appxLoginMgr behavior to keep in mind
-<
<
+ The appxLoginMgr -modify argument will maintain existing values,
->
>
+ The appxLoginMgr -modify argument will maintain existing values,
 but will actually remove and create new .env and .ini files with the
new values specified.  This combination action of remove and
recreation will change (remove) any existing non default comments.
  To match the Windows platform, he following should be valid syntax: "appxLoginMgr -install".  It should default to port 8060, or the Windows platform should not default to port 8060.
  To clarify the purpose of the file, consider renaming uappxd/appxdsvc to appxLoginMgr on all platforms.
  To clarify the purpose of the file, consider renaming uappxd/appxdsvc to appxAuditLogger
-<
<
+ In an effort to make appxdsvc and uappxd (appxLoginMgr) as similar as possible, consider allowing -status as a single argument that would list all appxLoginMgr daemons.  (Perhaps this isn't practical on Unix platforms)
  APPX_KEYMAP environment variable should be initialized upon default install options.  Currently "appxLoginMgr -install -SockPort=8060" does not place APPX_KEYMAP into appxLoginMgr-8060.env.
->
>
+ In an effort to make appxdsvc and uappxd (appxLoginMgr) as similar as possible, consider allowing -status as a single argument that would list all appxLoginMgr daemons.  (Perhaps this isn't practical on Unix platforms)
  APPX_KEYMAP environment variable should be initialized upon default install options.  Currently "appxLoginMgr -install -SockPort=8060" does not place APPX_KEYMAP into appxLoginMgr-8060.env.
  appxLoginMgr should create .ini and .env files in the tools subdirectory, and not in the current working directory.
  The appxLoginMgr -replace argument should require the -ServiceName option, and not assume ServiceName=appxd-8060.
-<
<
+ The requirements for use of -name argument seem inconsistant.  Below are examples where + works, and - does not.
->
>
+ The requirements for use of -name argument seem inconsistant.  Below are examples where + works, and - does not.
   (-) ./appxLoginMgr -modify appxd-8060 -TCPNodelay=false
  (+) ./appxLoginMgr -modify -name=appxd-8060 -TCPNodelay=false
  (-)./appxLoginMgr -status

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