| | 1 | == i2b2 Background Installation Details == |
| | 2 | |
| | 3 | [wiki:i2b2 Return to i2b2 component page] |
| | 4 | |
| | 5 | === The Install Artifacts === |
| | 6 | My feeling (Jeff) is that the install packages should be in a well-known place within the available BRICCS network/resources, eg: in a repo on briccs-2. We could use wget "locally" to download known versions of software within the automated procedures. Or could we just script automated sftp's? Having known versions of software in our own location would be reassuring, quick and easy to script. |
| | 7 | |
| | 8 | This may have to be a private facility to avoid licence implications, so perhaps sftp would be easier for this. Any thoughts? |
| | 9 | |
| | 10 | === Ownership, Groups and Privileges === |
| | 11 | Within a Linux environment, the question of owner and group needs thinking through. |
| | 12 | |
| | 13 | I'm not in favour of running software as root. Should we have specific owners and groups (eg: catissue, jboss) or have a generic group (eg: briccs)? These could be set up during the install process if they did not already exist. |
| | 14 | |
| | 15 | NB: The Oracle-XE install creates user oracle and group dba |
| | 16 | |
| | 17 | === Start and Restart === |
| | 18 | * Should the database and JBoss be started at boot? |
| | 19 | * Should they routinely be restarted each day overnight to reclaim any errant resources? |
