4.
Installing 2X ThinClientServer on Linux
System
requirements
Before you install 2X
ThinClientServer, please ensure that you meet all the following
requirements
- RPM-based
or Debian-based Linux distribution
- 256
MB of RAM or more
- 800
MHz processor or higher
- Approximately
120MB of free space for each 2X ThinClientOS you plan to
upload.
Step 1: Dependencies
|
Distributions
|
Dependency
Packages
|
|
OpenSuSE
11.0
|
compat-openssl097g
|
|
compat-expat1
|
|
CentOS
5.2
|
compat-libstdc++
|
|
Fedora
Core 9
|
compat-libstdc6++-33.i386
|
|
compat-libstdc++
|
|
All
Debian based
|
libstdc++5
(>= 1:3.3.4-1)
|
Table 1: Dependencies
Please ensure that the
dependencies, as outlined in the above table, are met before trying to install
2X ThinClientServer.
Step 2: (RPM) Install the
package
Download the RPM from the 2X
download site and open a terminal as root (super user). Change directory to the
location where you downloaded the RPM and run the following command:
rpm
-Uvh thinclientserver-x-y.i386.rpm
Step 2: (DEB) Install the
package
Open a terminal as root (super
user). Change directory to the location where you downloaded the DEB from the 2X
download site. Run the following command:
dpkg
-i thinclientserver-x-y.i386.deb
Step 3: Configure server
after installation
It is required to configure
the 2X ThinClientServer before the service is started up. Open a terminal as
root (super user). Run the following command:
2Xthinclientserver_conf.sh
Screenshot 10: Auto detection and licence review
In the first part, the
configuration script detects whether all necessary tools are present on the
system. Then it backs the current configuration files for safe keeping. You can
then review the license agreement and accept to continue.
Next, the network and security
setup is probed. You are then shown the total number of network interfaces
installed on the machine. If you have only one interface (localhost is ommitted
here) installed then the script will automatically detect the best
configuration. On the other hand if, as in the figure above, you have multiple
interfaces, you have the choice of manually choosing which interface you wish
your services to bind to. We recommend that you allow the configuration utility
to auto detect the network configuration.
Screenshot 11: Master or Slave Menu
The setup then will then ask
you to either configure this installation as a master server,
i.e.
to create a farm, or join this installation, as a slave, in a farm. Please
choose accordingly.
Screenshot 12: Master details
If you are configuring a
master server, you are prompted for a username and password to connect to the
local MySQL database. You are also asked for the following information:
Master server host name or IP:
This is used by the slave servers, if any, to communicate with the master
server. Please note that hostnames should be resolvable by all slaves.
Internal IP address, as seen
by the thin clients: This IP is used by the thin clients to communicate with the
server.
Screenshot 13: Slave details
If, on the other hand, you are
configuring a slave, you are prompted for the following information:
- Local
MySQL database credentials. These, as in the master configuration, are using to
connect to the local database.
- Master
server management console credentials. These credentials are used during the
synchronization of the slave with the master server.
- IP
of master server.
- The
master console secure port. This, by default, is port 943.
- The
IP address or host name of the slave server. This information will enable the
master server to communicate with the slave server during the synchronization as
well as when pushing updates.
- The
slave console secure port.
- Internal
IP address, as seen by the thin clients: This IP is used by the thin clients to
communicate with the server.
Screenshot 14: Review information
After entering all the
information, you can review all details before porceeding with the
configuration. If you are not satisfied, select
No to go back and input the information
again. Enter Yes if you agree.
Screenshot 15: Services configuration and startup
After you agree with all the
settings, each individual service is configured. When this has finished, the
Apache and MySQL services are started and the installation configured as either
master or slave. Please note that this task can take a while to complete,
especially during a slave server configuration. Finally all services are
started and the script exits.
Distributions with
SELinux
If SELinux has been configured
in enforcing mode, the script will test whether the 2X ThinClientServer services
will start correctly. If not, the script will also suggest SELinux policy
modifications. You need to accept these modifications before these are
configured inside the policy.
Distributions with
AppArmor
2X ThinClientServer comes with
a set of AppArmor profiles to add another security layer. These profiles are
installed, when AppArmor is enabled, and encapsulate all 2X ThinClientServer
services. Thus confined, the services have limited file system access and
cannot execute arbitrary utilities and programs.
Step 4: Open Management
Console
You must now connect to the 2X
ThinClientServer Management Console to configure the initial parameters for 2X
ThinClientServer by starting a web browser and entering the name of the machine
on which 2X ThinClientServer is installed on port 980 (for example:
http://thinserver.2x.com:980)
Please refer to Chapter 5 for
detailed initial configuration information.
You may launch the Management
Console at any time for further configuration by starting a web browser and
entering the name of the machine on which 2X ThinClientServer is installed on
port 980.
Firewall
Issues:
Please
note that for a 2X ThinClientServer Management Console to function, it will be
necessary to ensure that TCP connections on port 980 to the 2X ThinClientServer
can be established.
Please
note that for a DHCP Server to provide TCP/IP settings to the Thin Client
successfully, it will be necessary to ensure that:
- UDP
connections on port 67 to the DHCP Server can be established.
- UDP
connections on port 68 to the Thin Client can be established.
- UDP
connections on port 67 to the 2X ThinClientServer can be established for the 2X
DHCP Helper Service.
- UDP
connections on port 69 to the 2X ThinClientServer can be established for the 2X
TFTP Service.
