Homepage | About EASA | Contact
This page explains how to configure and share the folder easa-share in a multi-server environment.
There are two ways to configure the remote share on windows.
This option includes creating a user account for the EASA Service to use and identical user accounts on all the other machines as well.
The following steps detail how to configure remote access:
User = EASA Password = <password>
The user accounts must have administrator rights. Please choose the password in a way that it can be entered on all machines later (e.g. only include special characters present on all the machines / keyboards).
easa-share
folder must be shared between these computers:EasaServerData
folder on the Main EASA Server machineNow the shared folder is ready to use by a Windows installation of remote JSF, Excel or EASA Web Service.
We will grant access specifically to the LocalSystem and NetworkService accounts in the remote machine which runs JSF, Excel or EASA Web Service.
Since 5.4 we have a new way to configure a remote server (Usually JSF/Excel pair) to be able to access a database directly without need to go through EASA Server as it was before. For that, we created a new folder called easa-share which will contain drivers and xmls to access databases and email configuration too. Basically, we would need to configure a network path to make the remote server able to access that folder over the network. That can be done following the EASA-Share Folder Configuration for Cluster Server Installations guide in wiki:
If that network folder is not configured, then we have a fallback to make it work out of the box; EASA Server will send the needed files to the remote server. When you run EASA in application mode you will see a test on this network path, if it's well configured then it will show test network path: works: true. If it's not configured or it has any issue accessing the folder then it will show test network path: works: false
Follow these steps to configure remote access:
EasaServerData
folder on the Main EASA Server machineNow the shared folder is ready to use by a Windows installation of remote JSF, Excel or EASA Web Service.
There are multiple ways to configure the remote share on UNIX systems. In this article we will use a free software package called Samba to share the folder with both Windows and UNIX. This allows mixing of Windows and UNIX servers in a multi-server environment.
The following configuration should be made only if the main EASA Server machine is running on a UNIX based OS. If the shared folder has to be used by a UNIX machine then follow Mount easa-share in UNIX.
/root/EasaServerData/easa-share
folder exists (by default it installs under the /root
folder)sudo apt-get update sudo apt-get install samba
/home
folder):sudo cp /etc/samba/smb.conf ~ sudo gedit /etc/samba/smb.conf
[easa-share] path = /root/EasaServerData/easa-share browseable = yes writable = yes read only = no public = yes guest ok = yes create mask = 0755 directory mask = 0755 force user = root
sudo service smbd restart
Now the shared folder is ready to use by a Windows installation of remote JSF, Excel or EASA Web Service.
This configuration will be needed only if you need to access a remote share from a UNIX machine. The following steps explain how to mount the easa-share at bootup time and use the mount folder as shared folder.
Skip the step about network path to easa-share when using the installer to install a remote JSF or EASA-WS, because for this case it wil be set manually.
sudo apt-get install cifs-utils
/mnt
but any path can be used):sudo mkdir /mnt/easa-share
/etc/fstab
file to set the mount at bootupsudo gedit /etc/fstab
//<Hostname OR IP>/easa-share /mnt/easa-share cifs guest,_netdev,uid=<USER> 0 0
sudo mount -a
We need to set manually the recently mounted easa-share as shared folder for the EASA installation. For that, we have to go to the EASAServerData folder, with root privileges if it is installed as default. To do it execute the following commands:
su cd / cd root/EasaServerData
shared.properties
file (use sudo if the root privileges were dropped in the meantime):gedit shared.properties
shared.path=/mnt/easa-share
In case that IP is used to point to the EASA server machine in shared.properties
, make sure that the remote machine can ping the EASA server using that same IP address.