|
Size: 2131
Comment:
|
Size: 2563
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Installing and configuring EMEN2 = |
|
| Line 3: | Line 5: |
| 1. Download the latest EMEN2 source code release and untar | |
| Line 5: | Line 6: |
| 2. Create a directory for the Database Environment (referred to as $DB_HOME going forward. Reasonable default is /home/emen2/db/ ) | |
| Line 7: | Line 7: |
| Recommended: Set the $DB_HOME environment variable to this path for convenience | === 1. Download the latest EMEN2 source code release and untar === |
| Line 9: | Line 9: |
| 3. Copy emen2/config.sample.yml to $DB_HOME/config.yml | {{{ cd /home/emen2 tar -xvzf emen2.03.28.2010.tar.gz cd emen2 }}} === 2. Create a directory for the Database Environment === (referred to as $DB_HOME going forward. Reasonable default is /home/emen2/db/ ) {{{ mkdir /home/emen2/db cp config/config.sample.yml /home/emen2/db/config.yml }}} Recommended: Set the $DB_HOME environment variable to this path for convenience. Place this in your .bash_profile or similar. {{{ export DB_HOME=/home/emen2/db }}} === 3. Copy emen2/config.sample.yml to $DB_HOME/config.yml === |
| Line 13: | Line 38: |
| {{{ | |
| Line 15: | Line 41: |
| }}} | |
| Line 16: | Line 43: |
| 4. After config.yml is to your liking, run | |
| Line 18: | Line 44: |
=== 4. After config.yml is to your liking, run === {{{ |
|
| Line 19: | Line 49: |
| }}} | |
| Line 22: | Line 53: |
| 5. Test web server | |
| Line 24: | Line 54: |
=== 5. Test web server === {{{ |
|
| Line 25: | Line 59: |
| }}} | |
| Line 28: | Line 63: |
| 6. Optional: Import Parameter/Protocol definitions from the NCMI Database. | |
| Line 30: | Line 64: |
=== 6. Optional: Import Parameter/Protocol definitions from the NCMI Database. === {{{ |
|
| Line 31: | Line 69: |
| }}} | |
| Line 36: | Line 75: |
| 6. Daemon | === 7. Run as daemon === |
| Line 40: | Line 79: |
| {{{ | |
| Line 41: | Line 81: |
| }}} |
Installing and configuring EMEN2
Generally, you will want to create a user account for running emen2, e.g. 'emen2.' This has the benefit of working well with the default config file. Running as any other user also works fine, you will just have to change one or two paths in config.yml.
1. Download the latest EMEN2 source code release and untar
cd /home/emen2 tar -xvzf emen2.03.28.2010.tar.gz cd emen2
2. Create a directory for the Database Environment
(referred to as $DB_HOME going forward. Reasonable default is /home/emen2/db/ )
mkdir /home/emen2/db cp config/config.sample.yml /home/emen2/db/config.yml
Recommended: Set the $DB_HOME environment variable to this path for convenience. Place this in your .bash_profile or similar.
export DB_HOME=/home/emen2/db
3. Copy emen2/config.sample.yml to $DB_HOME/config.yml
Edit the various settings in config.yml. See EMEN2/config.yml. Primarily, you will want to check the path and network settings. A simple configuration will have most EMEN2 directories (db, applog, archive, db_hotbackup, emen2files, etc.) placed under the path specified by the "&root" element, which is /home/emen2/ by default.
root: &root
/home/emen2/
4. After config.yml is to your liking, run
python ./setup.py
The rest of the $DB_HOME environment will be created, skeleton parameter/protocol definitions will be installed, and a root user created. You will be prompted on the shell for a root password.
5. Test web server
python ./TwistSupport.py
You should be able to connect to this web server instance once it is "listening..." The default port is 8080. You may login with the root password you specified previously.
6. Optional: Import Parameter/Protocol definitions from the NCMI Database.
python ./clients/clone.py -- --defs
Note: the first "--" is intentional and required at the moment. Command arguments for the local database go before "--", arguments to the cloning script go after ("--defs")
You will be prompted for two sets of credentials. First, an NCMI DB account, and second, the root password for the local database. If you do not have an NCMI DB account, you may specify "anonymous" as the username, and your email address as the password.
7. Run as daemon
After you are satisfied with your setup, you can run EMEN2 in the background
python ./emen2control.py --start