Differences between revisions 1 and 12 (spanning 11 versions)
Revision 1 as of 2010-03-29 08:10:42
Size: 429
Editor: root
Comment:
Revision 12 as of 2010-03-29 08:38:58
Size: 3338
Editor: root
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 [default: /home/emen2/emen2 ]
Line 5: Line 6:
3. Create a directory for the Database Environment, [default: /home/emen2/db ]
=== 1. Download ===

Download the latest EMEN2 source code release and untar

http://ncmi.bcm.edu/ncmi/software/software_details?selected_software=EMEN2

{{{
cd /home/emen2
tar -xvzf emen2.03.28.2010.tar.gz
cd emen2
}}}

If there is an existing source tree installed, you may want to rename it in case you want to revert to the previous version, e.g. mv emen2 emen2.old.03.20.2010.

If you have an existing database environment, I strongly recommend taking an additional tar backup of that directory before proceeding, in addition to normal backup procedures (log archive, db hot backup) in case you need to revert without the difficulty of performing a full recovery from archives.



=== 2. Create Database Environment ===

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. Create Configuration ===

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. Initial $DB_HOME setup ===

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 ===

You may want to import the parameter and protocol definitions from the EMEN2 installation at the NCMI. In the future, these will be published in an open format, and made available by default.

{{{
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
}}}

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

Download the latest EMEN2 source code release and untar

http://ncmi.bcm.edu/ncmi/software/software_details?selected_software=EMEN2

cd /home/emen2
tar -xvzf emen2.03.28.2010.tar.gz
cd emen2

If there is an existing source tree installed, you may want to rename it in case you want to revert to the previous version, e.g. mv emen2 emen2.old.03.20.2010.

If you have an existing database environment, I strongly recommend taking an additional tar backup of that directory before proceeding, in addition to normal backup procedures (log archive, db hot backup) in case you need to revert without the difficulty of performing a full recovery from archives.

2. Create Database Environment

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. Create Configuration

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. Initial $DB_HOME setup

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

You may want to import the parameter and protocol definitions from the EMEN2 installation at the NCMI. In the future, these will be published in an open format, and made available by default.

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

EMEN2/Install (last edited 2013-06-27 06:59:34 by IanRees)