EPM engine machine setup

Hardware prerequisites

Network connection : preferably 1000 Mbit/sec.

Memory requirements: if L is the number of (hybrid) links in millions, then the memory (in Mb) needed tu run the epm engine is roughly:

50 L + 15

For instance, 800 000 links require 55 Mb, which easily fits into the small memory of a Raspberry pi SBC.

Software Prerequisites

Linux (ubuntu preferably)

JRE (or JDK), for instance OpenJdk 7

gcc compiler

NFS client

NFS server

Step 1

Runs on a source machine (which is a "full Assothink machine", according to Matscape's standards (MMU (or MMV or MMM))).

Uses directory /media/server.Alex.MMU/epm/ (the 'epm reference dir', refdir)

The script is epm preinstall .

It creates several system files under directory $refdir/install/  .

This has to be done just once if many machines have to be installed.

Step 2

On the target machine:

• set host name
• define a user (standard name and password)
  
• set IP address and check network accessibility
  
• NFS export $HOME directory
  
• NFS mount /media/server.Alex.MMU/
  
• replicate /etc/hosts file (from refdir/install), check the hosts pingability
  
• replicate /etc/fstab.matscape.local file, replicate it at the end of fstab
  
• check the auto mounting of /media/server.Alex.MMU/ /media/MMU/ and /media/MMM/ at least
  
• run script /media/MMU/epm install (it replicates into target machine .bashrc, .alex, Scripts dir, assothink.epm dir...)
• restart new bash instance
• check clock network synchro
• setup and check accessibility of target machine through "Remote Desktop Viewer"
• check generic things
• check epm java engine process (epm java engine mainly) (epm J)
  
• compile C version of epm (epm gcc), check epm C engine (epm C)
  
• launch epm daemon (epm d)

Step 3

On the source machine:

• check NFS access to target machine
• check access to remote machine using rsh
  
• check access to remote machine through "Remote Desktop Viewer"
  
• launch epm controller
• check performance of new machine(java and C)