In the second video of our four-part series, you'll learn how to install SAS Event Stream Processing for Edge Computing.
Download Order Assets
- Go to my.sas.com/ to download the certificates, license and SAS Mirror Manager
Create and Populate a Mirror Repository
Execute the following on the Ubuntu machine
cd /home/administrator/Downloads/mirrormgr-linux
chmod +x mirrormgr
chmod +x edge_mirror.sh
./edge_mirror.sh aarch64-ubuntu-linux-16
Install Repositories on Jetson device
In the example below 192.168.68.119 is the IP address of the Jetson device
# Create deploy folder on Jetson device
ssh jetson@192.168.68.119
mkdir deploy
exit
# Move files to the Jetson
cd Downloads/
cd mirrormgr-linux/
scp -r espedge_repos/ jetson@192.168.68.119:/home/jetson/deploy
# Install packages on Jetson
ssh jetson@192.168.68.119
sudo apt install /home/jetson/deploy/espedge_repos/aarch64-ubuntu-linux-16/basic/*
sudo apt install /home/jetson/deploy/espedge_repos/aarch64-ubuntu-linux-16/analytics/*
sudo apt install /home/jetson/deploy/espedge_repos/aarch64-ubuntu-linux-16/astore/*
sudo apt install /home/jetson/deploy/espedge_repos/aarch64-ubuntu-linux-16/textanalytics/*
sudo apt install /home/jetson/deploy/espedge_repos/aarch64-ubuntu-linux-16/gpu/*
Apply the License
SASViyaV4_9CMN6Y_stable_2021.1.6_license_2021-11-15T154936.jwt is the name of our license file in the example below, replace it with the name of your license file.
cd /home/administrator/Downloads/mirrormgr-linux
scp SASViyaV4_9CMN6Y_stable_2021.1.6_license_2021-11-15T154936.jwt jetson@192.168.68.119:/home/jetson/deploy
ssh jetson@192.168.68.119
sudo mv /home/jetson/deploy/SASViyaV4_9CMN6Y_stable_2021.1.6_license_2021-11-15T154936.jwt /opt/sas/viya/home/SASEventStreamProcessingEngine/etc/license/
Start the ESP server
export DFESP_HOME=/opt/sas/viya/home/SASEventStreamProcessingEngine/
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$DFESP_HOME/ssl/lib:$DFESP_HOME/lib:/opt/sas/viya/home/SASFoundation/sasexe:/usr/lib
export PATH=$PATH:$DFESP_HOME/bin
dfesp_xml_server -http 31415 -pubsub 31416
More details about the deployment can be found in the documentation
