Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX Login Manager For Unix/Linux | ||||||||
Line: 44 to 44 | ||||||||
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. | ||||||||
Added: | ||||||||
> > | ||||||||
cd /usr/local/appx/tools chown root appxLoginMgr chgrp appxgrp appxLoginMgr chmod 4775 appxLoginMgr | ||||||||
Added: | ||||||||
> > | ||||||||
You can check the permissions of the appxLoginMgr command by running the following command: | ||||||||
Added: | ||||||||
> > | ||||||||
ls -l appxLoginMgr | ||||||||
Added: | ||||||||
> > | ||||||||
The recommended permissions should be as follows: | ||||||||
Added: | ||||||||
> > | ||||||||
-rwsrwxr-x 1 root root 636843 Jul 11 07:31 appxLoginMgr | ||||||||
Added: | ||||||||
> > | ||||||||
Creating and Configuring an APPX Connection ServiceOn Unix/Linux systems, an instance of the APPX Connection Service is initially created, configured, and started by running the appxLoginMgr 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 | ||||||||
Line: 96 to 102 | ||||||||
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 | ||||||||
Changed: | ||||||||
< < | 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* Warning - the engine that you named has the setuid bit enabled, | ||||||||
Line: 107 to 113 | ||||||||
[root@tubes tools]# | ||||||||
Deleted: | ||||||||
< < | ||||||||
Usage (appxLoginMgr)
| ||||||||
Line: 123 to 128 | ||||||||
Configuration - Commands | ||||||||
Changed: | ||||||||
< < | -install -name=SERVICENAME [options]... [VARIABLE=VALUE]... | |||||||
> > | -install -name=SERVICENAME [options]... [VARIABLE=VALUE]... | |||||||
Changed: | ||||||||
< < | -install -port=PORT [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. 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. | ||||||||
Changed: | ||||||||
< < | 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 specified 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]... | ||||||||
Changed: | ||||||||
< < | 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. Note that when specifying variables on the command line, you must prefix them with a dash if you are referring to settings such as SSLmode, or without a dash if you are referring to environment variables, such as APPX_KEYMAP. | |||||||
> > | 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. Note that when specifying variables on the command line, you must prefix them with a dash if you are referring to settings such as SSLmode, or without a dash if you are referring to environment variables, such as APPX_KEYMAP. Note that the -modify command updates the service configuration file and the environment configuration file by removing the old files and creating new files with the updated options and environment variables. Any comments that may have been manually added to these configuration files are not preserved. | |||||||
-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. Note that when specifying variables on the command line, you must prefix them with a dash if you are referring to settings such as SSLmode, or without a dash if you are referring to environment variables, such as APPX_KEYMAP. | ||||||||
Line: 530 to 541 | ||||||||
handleClients - waiting | ||||||||
Deleted: | ||||||||
< < | appxLoginMgr behavior to keep in mindThe 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. Would not change behavior of the service but could be a surprise to someone that had input documentation remarks (via the # symbol).012) (Error) Red Hat's service wrapper command.Usage: appxd-8060 {start|stop|status|reload|restart}startworks without issuestopdoes seem to remove the running process; however, it produces errors. Further, it fails to remove the PID from the (/var/run/appxd-8060.pid) /etc/init.d/appxd-8060: line 39: success: command not found /etc/init.d/appxd-8060: line 39: failure: command not found /etc/init.d/appxd-8060: line 43: failure: command not foundstatusseems to work without issue.reload | |||||||
Changed: | ||||||||
< < | does not appear to do anything. | |||||||
> > |
Red Hat service command. | |||||||
Changed: | ||||||||
< < | restart | |||||||
> > | Usage: service appxd-8060 {start|stop|status|reload|restart} | |||||||
Changed: | ||||||||
< < | which is a stop followed by a start, suffers from the problem of stop documented earlier.
013) (Cosmetic) Redundant redundant redundant | |||||||
> > | 013) (Cosmetic) Redundant redundant redundant | |||||||
data data data. A minimal install produces three warning statements as documented below: | ||||||||
Line: 623 to 604 | ||||||||
[root@APPX4.30TestBox tools]# | ||||||||
Changed: | ||||||||
< < | 014) (Suggestion) Warn users not to move | |||||||
> > | 014) (Suggestion) Warn users not to move | |||||||
configuration files.
We should probably warn via screen notice on service creation, and document inside the .ini and .env files that if the .ini, .env and appxLoginMgr/appxAuditLogger are move or renamed, then the /etc/init.d system startup script will fail to work. The /etc/inid.d/appxd-8060 startup script references by name and path the .ini, .env, and appxLoginMgr/appxAuditLogger files.
Suggested Behavior changes:
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Line: 650 to 629 | ||||||||
| ||||||||
Changed: | ||||||||
< < | Bugs: | |||||||
> > | Issues:
| |||||||
Changed: | ||||||||
< < |
| |||||||
> > | /etc/init.d/appxd-8060: line 43: failure: command not found | |||||||
Deleted: | ||||||||
< < | ||||||||
RequireSSL - Not Implemented. Do not Use.
| ||||||||
Line: 681 to 664 | ||||||||
*openssl req -new -days 365 -key tubes.internal.appx.com.private.key -x509 -out tubes.internal.appx.com.crt* | ||||||||
Added: | ||||||||
> > | Limitations: | |||||||
Comments:Read what other users have said about this page or add your own comments. |