5. Connecting to the Installation : Installing the Client
Share this page                  
Installing the Client
The client was installed when you installed VectorH on the master node.
If other machines in the environment (such as edge nodes) require connection to the cluster then the Actian client software must be installed on those machines.
The client software is provided for Linux and Windows. (Note that the .NET driver is provided as a separate install.) See http://esd.actian.com/product/drivers/Client_Runtime.
If the client needs to connect through a firewall then refer to Configuring Firewall Ports in the Evaluation Guide for details about which ports to open.
A client installation acts as an instance (without a database server) with the instance ID CL. As such, a client installation is administered similarly to the database instance and responds to commands such as ingstart, ingstop, ingstatus, and can be set up to run as a service. The environment setup script for the client on Linux is called .ingCLsh.
To install on Windows use the setup program.
To install on Linux, use either the RPM or ingbuild distribution. If using the RPM distribution, root or sudo access is required. If you want to install without root or sudo then use ingbuild. Examples follow.
RPM package:
To install the client with the default instance CL and default location of /opt/Actian/Vector_Client using sudo, issue:
sudo ./client_install.sh
To install the client as user actian in a location other than the default, issue a command similar to:
# As user actian
./install.sh ‑express -noroot /home/actian/Vector_Client
After installing the client, the Name Server and Communications Server will be running:
Actian Vector CL name server (iigcn) - running
Actian Vector CL Net server (iigcc) - 1 running
Actian Vector CL Data Access server (iigcd) - not active
If you need to start the DAS server, run ingstart –iigcd.