Current Version: v.0.1 (Pilot)
Installation and Minimum Hardware Requirements
Minimum Hardware Requirements
Before installing the Secure Agent, ensure your system meets the following minimum hardware requirements:
For Windows:
Operating System: Windows 10 or later (64-bit)
Processor: Quad-core CPU (Intel or AMD) with a clock speed of 2.5 GHz or higher
Memory: 16 GB RAM
Disk Space: 50 GB of free disk space
Network: High-speed internet connection
Java: JDK 11 or later
For Linux:
Operating System: CentOS 7 or later, Ubuntu 18.04 or later (64-bit)
Processor: Quad-core CPU (Intel or AMD) with a clock speed of 2.5 GHz or higher
Memory: 16 GB RAM
Disk Space: 50 GB of free disk space
Network: High-speed internet connection
Java: JDK 11 or later
Installation Instructions
Follow these steps to install the Secure Agent on your system.
Prerequisites (Install JDK)
For Windows:
Download JDK:
Download the latest JDK from the official Oracle or OpenJDK Website
Install JDK:
Run the installer and follow the on-screen instructions to install the JDK.
Set JAVA_HOME Environment Variable:
Open the Start menu and search for "Environment Variables".
Click on "Edit the system environment variables".
In the System Properties window, click on the "Environment Variables" button.
Under "System variables", click "New" and set the variable name to
JAVA_HOME
and the variable value to the JDK installation path (e.g.,C:\Program Files\Java\jdk-11
).Find the
Path
variable in the "System variables" section, select it, and click "Edit".Click "New" and add
%JAVA_HOME%\bin
to the list.Click "OK" to close all dialogs.
For Linux:
Install JDK:
For Ubuntu/Debian-based distributions:
sudo apt update sudo apt install openjdk-11-jdk
For CentOS/RHEL-based distributions:
sudo yum install java-11-openjdk-devel
Set JAVA_HOME Environment Variable:
Open your
.bashrc
or.profile
file in a text editor:nano ~/.bashrc
Add the following lines at the end of the file:
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 export PATH=$JAVA_HOME/bin:$PATH
Copy code
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 export PATH=$JAVA_HOME/bin:$PATH
Save the file and reload it:
source ~/.bashrc
Downloading the Eazydi Agent
Login to EazyDI Application and navigate to the Environments tab and click New Agent button
Click on Generate New Token and copy it, or optionally download the new token as a text file
Choose the platform and click Download Secure Agent to download the latest build of the Eazydi Agent
Setting up the Eazydi Agent
app.ini
The app.ini
file is a critical configuration file for the Secure Agent, dictating how it connects to the cloud service. Below is a detailed breakdown of the sections and key parameters within the app.ini
file
base_socket_url
Description: The URL used by the Secure Agent to establish a connection with the EazyDi platform.
Purpose: This is a crucial setting that should not be altered. It specifies the endpoint for all communication between the agent and the cloud service.
username
Description: The username associated with your EazyDi account.
Purpose: This parameter is used for authenticating the Agent with the EazyDi platform. It ensures that the agent operates under the correct user context.
Example:
username=myusername@eazydi.com
token
Description: The authentication token provided by EazyDi.
Purpose: This token is used in conjunction with the username to authenticate the Secure Agent. It is essential for secure and authorized access to the platform.
Example:
token=320af1e1-5786-4779-bf20-1ecadb92c900
spark_memory
Description: The amount of memory allocated to Apache Spark.
Purpose: This setting determines how much memory is available for Spark jobs executed by the Agent. Adequate memory allocation is crucial for performance, especially when handling large datasets.
Example:
spark_memory=6g
spark_master
Description: The Spark master URL.
Purpose: This specifies the master node for the Spark cluster. In a standalone or local mode, it indicates that Spark jobs should run on the local machine.
Example:
spark_master=local
spark_cores
Description: The number of CPU cores allocated to Spark.
Purpose: This parameter sets the number of CPU cores available for Spark processing tasks. More cores can improve performance by allowing more parallel processing.
Example:
spark_cores=2
For Windows
Unzip the downloaded file and open
app.ini
[app] base_socket_url=<the url for the connection of the agent to eazydi,do not change> username=myusername@eazydi.com token=320af1e1-5786-4779-bf20-1ecadb92c900 spark_memory=6g spark_master=local spark_cores=2
Fill up
username
andtoken
Double click on the
eazydi agent.exe
to runNotice in Environments Tab your machine will be registered and shows status as up
Notice the agent receiving a message after registering the machine
Using the Eazydi Agent
Create Connections which support the Eazydi Agent and assign the environment to your Agent
In Creating Pipelines using the Eazydi Agent, the Source and Target connections should be the same environment
Running Jobs make sure that the Agent is up and running. Notice the agent will receive requests for jobs in the logs
Once Job is complete it will reflect in Eazydi’s Monitor → Archived Listings
For Linux
Run the command to extract tar.gz file
mkdir linux_eazydi_agent tar -xzvf eazydi-agent-linux-v0.1.tar.gz -C linux_eazydi_agent cd linux_eazydi_agent chmod +x eazydi_agent
Update the
app.ini
using your preferred Linux editor
[app] base_socket_url=<the url for the connection of the agent to eazydi,do not change> username=myusername@eazydi.com token=320af1e1-5786-4779-bf20-1ecadb92c900 spark_memory=6g spark_master=local spark_cores=2
Fill up
username
andtoken
Run
./eazydi_agent
Notice in Environments Tab your machine will be registered and shows status as up
Notice the agent receiving a message after registering the machine
Using the Eazydi Agent
Create Connections which support the Eazydi Agent and assign the environment to your Agent
In Creating Pipelines using the Eazydi Agent, the Source and Target connections should be the same environment
Running Jobs make sure that the Agent is up and running. Notice the agent will receive requests for jobs in the logs
Once Job is complete it will reflect in Eazydi’s Monitor → Archived Listings