- make sure that user ssh login keys are setup and work for both 127.0.0.1
interface, as well as for the short/full installation machine name
- installing DM support software and deploying test system should not
require elevated privileges
- instructions below assume that user's git ssh keys have been setup
Installing DM Support
=============
======================
1) mkdir -p DM_INSTALL_DIR && cd DM_INSTALL_DIR
2) svn co https://subversion.xray.aps.anl.gov/DataManagement/support
2) git clone git@git.aps.anl.gov:DM/dm-support support
3) cd support
4) ./sbin/install_support_all.sh
- you will need to enter two passwords of your choice for glassfish (master and admin password); each password needs to be entered only once, as expect scripts handle repeated requests
- you will need to enter two passwords of your choice for glassfish
(master and admin password)
- each password needs to be entered only once, as expect scripts handle
repeated requests
Deploying Test System
==============
======================
1) cd DM_INSTALL_DIR
2) svn co https://subversion.xray.aps.anl.gov/DataManagement/trunk dev
3) cd dev
2) git clone git@git.aps.anl.gov:DM/dm
3) cd dm
4) ./sbin/dm_deploy_test_system.sh
- passwords needed:
* postgres admin password (your choice)
...
...
@@ -28,9 +32,11 @@ Deploying Test System
* dmadmin LDAP password (existing)
* dmadmin BSS login password (existing)
* dmadmin ESAF DB password (existing)
- scripts also require entry for the data storage directory (e.g, DM_INSTALL_DIR/data), etc; for most of those entries the defaults, if given, are fine
- scripts also require entry for the data storage directory
(e.g, DM_INSTALL_DIR/data), etc
- for most of the required entries the defaults, if given, are fine
