| |
| META TOPICPARENT |
name="APPXConnectionManager" |
APPX Connection Manager For Unix/Linux |
| |
- Validates the user ID and the password provided by the APPX Client;
- Initiates an APPX session for the APPX Client that requested a connection.
|
|
>
> | An APPX Conection Service supports connection requests for the following clients:
- APPX Desktop Client (Java GUI)
- Windows Client (Windows Desktop)
- Character mode client (Unix/Linux Desktops)
- APPX ODBC connections (Windows Desktop)
- APPX/Net connections (all servers)
|
| | Installing the APPX Connection Manager Command ( appxdsvc)
The APPX Connection Manager ( appxdsvc) command is installed automatically when you install APPX on your system. The installer sets the necessary owner and permissions for the appxdsvc command. So, there is nothing additional that you need to do to install the appxdsvc command. However, after you install APPX, you will need to run the appxdsvc command to configure and start an instance of the APPX Connection Service before any remote client connections may be established. |
| |
Creating and Configuring an APPX Connection Service
On Unix/Linux systems, an instance of the APPX Connection Service is initially created, configured, and started by running the appxdsvc command with the -install option. At least one 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 Configuration |
>
> | Creating a Connection Service |
| | |
|
<
< | Before remote clients can connect to an APPX system, at least one instance of the APPX Connection Service must be configured and started. |
>
> | Before remote clients can connect to an APPX system, at least one instance of an APPX Connection Service must be configured and started. |
| |
The -install option of the appxdsvc command is used to initially create, configure, and start an instance of the APPX Connection Service. The following steps are performed: |
|
<
< |
- The APPX Connection Service configuration files are created(ini and env)
- The O/S service is created
|
>
> |
- A configuration file (ini) is created
- An environment file (env) is created
- A service is created
|
| |
- The service is started
|
|
<
< |
Location of the Configuration Files
The two configuration files may be located in any existing directory on your systerm. However, the appxdsvc command does not have an option to directly specify where the two configuration files should be located. The -install option of the appxdsvc command creates the two configuration files in your current directory. Therefore, before you run the appxdsvc commad, you must first change to the directory where you want the two configuration files to reside. For example, if you want the two configuration files to be created in the APPX tools directory, you should change to the tools directory before you run the appxdsvc command.
Assignment of a TCP/IP Port Number
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. |
| | |
|
<
< |
Changing a Configuration
Two methods are available for modifying an existing instance of the APPX Connection Service. |
>
> | For compete information on using the -install option of the appxdsvc command, please refer to the usage section of this page. |
| | |
|
<
< | Method 1 - appxdsvc command |
>
> | The Name of the Service |
| | |
|
>
> | 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.
TCP/IP Port Number
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.
Changing a Connection Service
Two methods are available for modifying an existing instance of an APPX Connection Service.
Method 1 - The Connection Manager Command (appxdsvc) |
| | The -modify option of the appxdsvc command can be used to replace a previously configured instance of the APPX Connection Service. This option replaces the existing APPX Connection Service configuration files (ini and env) with two new files configured as specified.
Method 2 - Text Editor |
|
<
< | |
| | A text editor can be used to directly edit the APPX Connection Service configuration files (ini and env). The configuration files include comments to help you make the desired changes.
Managing an APPX Connection Service
Two methods are available for managing an existing instance of the APPX Connection Service. |
| | appxdsvc -start appx8060
|
|
<
< | Example ini File |
>
> | 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 name of the configuration file is the concatenation of the service name and ".ini". For example, if the service name is "appxd-8060", the name of the configuration file will be "appxd-8060.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 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. |
| |
# Appx connection manager configuration file
|
| | # Umask = #umask (file creation mask) given to spawned engines
|
|
<
< | Example env File |
>
> | 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 name of the environment file is the concatenation of the service name and ".env". For example, if the service name is "appxd-8060", the name of the environment file will be "appxd-8060.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 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. |
| |
# Appx connection manager environment variables
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.