Difference: APPXLoginManagerForUnixLinux (42 vs. 43)

Revision 432008-06-27 - JoeOrtagus

Line: 1 to 1
 
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.
Line: 39 to 39
  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".
Changed:
<
<		The appxloginmgr command must run with the permissions of the root user. Therefore, the owner of the appxloginmgr command should be the root user and the SUID bit should be set so that the appxloginmgr command can be run by users other than root but still be run with the permissions of root.
>
>		The appxloginmgr command must run with the permissions of the root user because it will be spawning appx processes running as each logged in user. Therefore, the owner of the appxloginmgr command should be the root user and the SUID bit should be set so that the appxloginmgr 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 appxloginmgr command, the following commands can be run by the root user to set the necessary owner and group permissions for the appxloginmgr command.
Changed:
<
<

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:
Changed:
<
<		ls -l appxloginmgr
>
>		ls -l appxloginmgr
 

The recommended permissions should be as follows:

Line: 70 to 70
 The -install option of the appxloginmgr command is used to initially create, configure, and start an instance of the APPX Connection Service. The following steps are performed:
  1. A configuration file (ini) is created
  2. An environment file (env) is created
Changed:
<
<
  1. A service is created
>
>
  1. A service is created, including required init files and links. ( On Red Hat, /etc/init.d/ )
 
  1. The service is started

For compete information on using the -install option of the appxloginmgr command, please refer to the usage section of this page.

The Name of the Service

Changed:
<
<		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 for example, appxd-8060.
 

TCP/IP Port Number

Changed:
<
<		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.
>
>		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.
 

Changing a Connection Service

Two methods are available for modifying an existing instance of an APPX Connection Service.
Line: 90 to 90
 

Managing an APPX Connection Service

Two methods are available for managing an existing instance of the APPX Connection Service.
Changed:
<
<

Method 1 - appxdsvc command

>
>

Method 1 - appxLoginMgr command

 
Changed:
<
<		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 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.
>
>		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,
          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
up and running (process 13893 servicing port 8060)
[root@tubes tools]#

 

Usage (appxdsvc)

Synopsis - Service Configuration

Changed:
<
<
The appxdsvc service configuration commands are used to create, configure, and remove an instance of an APPX Connection Service.

appxloginmgr -install -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...

>
>
The appxLoginMgr service configuration commands are used to create, configure, and remove an instance of an APPX Connection Service.
 
Changed:
<
<		appxloginmgr -install -port=PORT [options]... [VARIABLE=VALUE]...
>
>		appxloginmgr -install -SockPort=[TCP-Port] [options]... [VARIABLE=VALUE]...
 
Changed:
<
<		appxloginmgr -modify -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
>
>		appxloginmgr -modify -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
 
Changed:
<
<		appxloginmgr -replace -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
>
>		appxloginmgr -replace -serviceName=SERVICENAME [options]... [VARIABLE=VALUE]...
 
Changed:
<
<		appxloginmgr -remove -serviceName=SERVICENAME
>
>		appxloginmgr -remove -serviceName=SERVICENAME
 

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.

View topic | History: r68 < r67 < r66 < r65 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback