Editing DAQ Setup with AlmaLinux9.4 (section)

===Downloading & Preparing CODA===

====STEP 1: Downloading CODA====

i.	Make sure that you are a user in tcsh

ii.	Go to the jlab’s CODA wiki and download CODA 2.6.2

iii.	<span style="color:green">'''Link:''' https://coda.jlab.org/wiki/index.php/CODA_2.6.2_Downloads</span>  

iv.	Open a new shell (terminal)

v.	$ su

vi.	$ <root password>

vii.	# mkdir /usr/local/coda

viii.	# mv /home/<username>/Downloads/coda_2.6.2.tar.gz /usr/local/coda

ix.	# cd /usr/local/coda

x.	# tar –xf coda_2.6.2.tar.gz

xi.	# exit

====STEP 2: Making Directories for CODA====

i.	Open a new shell (terminal)

ii.	$ mkdir /home/<codauser>/bin

iii.	$ mkdir /home/<codauser>/msql

iv.	$ mkdir  /home/<codauser>/CODA

v.	$ mkdir /home/<codauser>/CODA/cool

vi.	$ mkdir /home/<codauser>/CODA/data

====STEP 3: Setting Up Environment Variables====

i.	Edit an example setup file to set up the environment variables (dosetupcoda262) 

<span style="color:green">'''Link:''' [[Setup Files#Environment Variables (dosetupcoda262)|Environment Variables (dosetupcoda262)]]</span>

ii.	Put dosetupcoda262 in the coda user’s home directory

iii.	Edit dosetupcoda262 with the following:

    1.	Variables that need editing:
     a.	MSQL_TCP_HOST <hostname>
     b.	MSQL_HOME /home/<codauser>/msql
     c.	EXPID <PCSE>
     d.	SESSION <Luter345>
     e.	CODA_DIRECTORY /home/<codauser>/CODA
     f.	CODADATA /home/<codauser>/CODA/data

iv.	Create a .tcshrc file in the home directory that sources dossetupcoda262

<span style="color:green">'''Link:''' [[Setup Files#.tcshrc|.tcshrc]]</span>

    1.	$ vi ~/.tcshrc
    2.	Include the following line in the file:
    3.	LIST WHAT GOES IN THIS
    4.	source {$HOME}/dosetupcoda262
    5.	<span style="color:blue">'''Hint:''' .tcshrc is a hidden file, to list it: $ ls -a </span>
    6.	To test if the sourcing worked properly, open a new shell to see if coda and AFECS is listed at the top of the window

====STEP 4: MSQL Setup====

i.	Starting the msql database

    1.	<span style="color:blue">'''Hint:''' The database must be running at all times. If the program is disrupted, the port that it is using will be left open. </span>
         <span style="color:blue">If this occurs, kill the msql process and re-launch the database.</span> 
    2.	Open a new shell (terminal) 
    3.	$ msqld
    4.	Rename the window ''msql'' for clarity

====STEP 5: Changing Soft Link for Problem Library (cedit)==== 

i.	Open new shell (terminal) 

    1.	$ su
    2.	$ <root password>
    3.	# cd /usr/lib
    4.	# ln –s libXm.so.4 libXm.so.3
    5.	This will create a soft link for the particular library that we need. (Previously used library: libXm.so.3.0.2)

====STEP 6: Cedit (GUI for database; Must be running msqld)====

i.	Open a new shell (terminal)

ii.	$ cedit

<span style="color:red">'''Possible Issue:''' If cedit does not open and throws an error: check if the database is running, the proper directories were made with the correct ownership, and that there are no missing libraries/links. </span>

iii.	Click: File->New Database

iv.	Name the database <database name>

v.	Create a new configuration

vi.	Click: File->New

vii.	Name the configuration <config name>

viii.	Create a basic setup: ROC, EB, ER, and a data file

ix.	See working example. 

<span style="color:green">'''Link:''' [[ADCTDC Configuration#CEDIT|CEDIT]]</span>

====STEP 7: Dbedit (text version of the database)====

i.	Open a new shell (terminal)

ii.	$ dbedit

iii.	Select local host from dropdown

iv.	Select <database name> from dropdown

v.	Compare all sections against a working example

<span style="color:green">'''Link:''' [[ADCTDC Configuration#DBEDIT|DBEDIT]]</span>

====STEP 8: NFS (Export the file systems from jlabdaq to jlabvme)====

i.	Open a new shell (terminal)

ii.	$ su

iii.	$ <root password>

iv.	# vi /etc/exports

<span style="color:green">'''Link:''' [[Setup Files#Exports File|Exports File]]</span>

<span style="color:blue">'''Hint:''' This is a CNU network configuration.</span> 

v.	Edit this file by adding these lines:

    1.	/home 137.155.2.0/255.255.255.0(rw,sync,no_root_squash)
    2.	/usr/local/coda 137.155.2.0/255.255.255.0(rw,sync,no_root_squash)
    3.	/usr/lib/jvm 137.155.2.0/255.255.255.0(rw,sync,no_root_squash)

vi.	Save and exit the file

vii.	<span style="color:blue">'''Hint:''' start NFS while super user</span> 

viii.	# /sbin/chkconfig --levels 345 nfs on

ix.	Check if NFS is on: # /sbin/chkconfig --list nfs status

x.	# /etc/init.d/nfs start

xi.	# exit

xii.	ssh into jlabvme: $ ssh root@jlabvme

xiii.	# vi /etc/fstab

<span style="color:green">'''Link:''' [[Setup Files#fstab File|fstab File]]</span>

xiv.	Add these lines in preparation for mounting

    1.    jlabdaq:/home                 /daqhome           nfs            rw,sync       0 0
    2.    jlabdaq:/usr/local/coda      /usr/local/coda    nfs            defaults       0 0
    3.    jlabdaq:/usr/lib/jvm       /usr/lib/jvm         nfs            defaults       0 0

xv.	Make the directories that were specified above

    1.    # mkdir /daqhome
    2.    # mkdir /usr/local/coda
    3.    # mkdir /usr/lib/jvm

xvi.	# mount –a

xvii.	Proper sourcing in jlabvme

    1.    Create a new environment variable file on jlabvme that has the NFS mounted directories. (We named ours coda_Luter345)  
    2.    <span style="color:green">'''Link:''' [[Setup Files#Environment Variables On jlabvme (coda_Luter345)|Environment Variables On jlabvme (coda_Luter345)]]</span>
    3.    Once the the environment variables are set, they must be sourced
    4.    Create a new script that sources coda_Luter345 (We named ours setLuter345.sh)
    5.    <span style="color:green">'''Link:''' [[Setup Files#setLuter345.sh|setLuter345.sh]]</span>