Difference: APPXLoginManagerForUnixLinux (23 vs. 24)

Revision 242007-08-16 - SteveFrizzell

Line: 1 to 1

META TOPICPARENT	name="APPXConnectionManager"

APPX Connection Manager For Unix/Linux

Line: 139 to 139

The remove command is used to remove an existing Connection Service. The remove command will remove the configuration files (ini and env) and the corresponding operating system service.

Configuration - Options

Changed:

<
<

Options - Session Identity/Permissions

>
>

Options - General

-name, -ServiceName=SERVICENAME

The ServiceName uniquely identifies an APPX connection service. When creating (installing) a connection service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when a connection service is being created, the connection service will be created with a default ServiceName based on the TCP/IP port number that was specified: "appxd" followed by a "-" and the specified port number, e.g "appxd-8060".

-DisplayName=DISPLAYNAME

The DisplayName is a "user-friendly" descriptive name for a connection service. The DISPLAYNAME value will appear in your system's Services control panel and will be displayed by the ps command. If you don't specify a DISPLAYNAME when a connection service is being created, the connection service will be created with a DISPLAYNAME based on the SERVICENAME.

-engine, -AppxExecutable={../appx, PATHNAME}

The APPX engine at the specified PATHNAME will be run when initiating an APPX session. The specified PATHNAME may be alsolute or it may be relative to the location of the appxdsvc command

-LogDirectory={/tmp, LOGDIR}

-AM, -AuthenticationMethod={OS-User, Appx-User, HT-User(HTFILENAME)}

Acceptable values are 'OS-User', 'Appx-User', and 'HT-User(HTFILENAME)'. 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. If this option is not specified, the default value is OS-User.

-ServiceType=Login

The only valid value when configuring a Connection Service is "Login". If this option is not specified, the default value is Login.

-ServiceDisable={true, false}

Added:

>
>

-ServiceDisableLogin={true, false}

-ServiceDisableFMS={true, false}

-ServiceDisableAppxKeys={true, false}

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

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 service. 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.

Line: 162 to 189

-IncludeSystemEnv={true, false}

Set this option to true if you want the APPX sessions which are initiated by the connection service to inherit the environment of the connection service.

Deleted:

<
<

Options - General

-name, -ServiceName=SERVICENAME

The specified SERVICENAME will be the name assigned to the Connection Manager service script that is created and to the related configuration files. The configuration file will have a file extension of "ini". If this option is omitted, the default SERVICENAME will be "appxd" followed by a "-" and the specified port number, e.g "appxd-8060".

-DisplayName=DISPLAYNAME

If you don't supply a DISPLAYNAME appxdsvc will append the port number to the end of the SERVICENAME and use that as the DISPLAYNAME. (The DISPLAYNAME will appear in the Services control panel and will be displayed by the ps command)

-engine, -AppxExecutable=PATHNAME

The APPX engine at the specified PATHNAME will be run when initiating an APPX session. The specified PATHNAME may be alsolute or it may be relative to the location of the appxdsvc command

-LogDirectory={/tmp, LOGDIR}

-AM, -AuthenticationMethod={OS-User | Appx-User | HT-User(filename)}

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. If this option is not specified, the default value is OS-User.

-ServiceType=Login

The only valid value when configuring a Connection Service is "Login". If this option is not specified, the default value is Login.

-ServiceDisable={true, false}

-ServiceDisableLogin={true, false}

-ServiceDisableFMS={true, false}

-ServiceDisableAppxKeys={true, false}

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

Options - Startup Process

Deleted:

<
<

-ServiceEnableCmds={true, false}

Set this option to true if you want to allow the client to specify a startup process. Set this option to false if you do not want to allow the client to specify a startup process. If set to true , then any APPX startup process that may have been specified by the client will be invoked when the connection with the APPX session is established. If set to true, then any startup process that is specified by the client will take precedence over any startup process that may have been specified in the connection service configuration. If the option is not specified, the default value is true.

Line: 239 to 231

-ServerPrivateKeyPassphrase=PASSPHRASE

-TrustedCAFile=CAFILENAME

Deleted:

<
<

Configuration - Environment Variables

Changed:

<
<

VARIABLE=VALUE

>
>

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.

Deleted:

<
<

Synopsis - Service Management

appxdsvc [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}

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