Other Pre-installation Tasks¶
This page describes tasks that you must complete on the server where you are going to install the Solution Manager:
Select a User Account to Install the Solution Manager¶
In the host where you are installing the Denodo Platform:
Designate an existing account to install and launch the Solution Manager components.
Or create a user account to install and launch the Solution Manager components.
Always install and run the Solution Manager components with the same user account. That is because they modify files in the directory where they are installed and the user account needs read and write privileges. If you perform the installation with one user account and run the servers with another, the second user account may not be able to modify the files in the installation.
Check that the Required Ports Are Free¶
The components of the Solution Manager listen for incoming connections on several ports. The appendix Default Ports Used by the Solution Manager Modules lists the default ports.
Make sure these ports are available on your system. If they are not available, select others that are free during the installation process.
You can install the Solution Manager even if these ports are used at that moment but then, the components that use them will not start until these ports are free.
Grant Privileges to This User Account¶
The default installation directory is:
On Linux, grant the write privileges required to this user account to be able to create this folder. On Linux, you have to execute this:
# Create the directory "/opt/denodo" sudo mkdir /opt/denodo # Grant ownership of this directory to the user "ec2-user" of the group "ec2-user" sudo chown ec2-user:ec2-user /opt/denodo
Check the PATH Environment Variable on Windows¶
Ignore this subsection if you are installing the Solution Manager on Linux.
If you are installing the Solution Manager on Windows, check that the PATH environment variable meets these rules:
PATH cannot have double quotes. If it does, the modules of the Solution Manager will not start. E.g. the following PATH is invalid:
If PATH has double quotes, remove them.
PATH cannot end with a backslash (
\). If it does, the modules of the Solution Manager will not start as a Windows service.
If it does, remove the backslash or add a semicolon at the end of the value of the variable.