Difference between revisions of "Retain Linux Install"

Revision as of 15:17, 18 April 2016

Prerequisites for Retain 3.5:

1. Create disks for best practices
   • OS
   • ARCHIVE
   • INDEX
   • LOGS
   • DATA
2. Install http server (apache2) from YaST
3. If connecting to Exchange:
   1. Set DNS to Exchange server, in YaST/Network Settings
4. Create MySQL download directory
   1. • md /software/mysql directory and change to it
   2. download MySQL Community Server 5.5.42 [1] direct? [2] to that mysql directory
      • wget "http://dev.mysql.com/get/archives/mysql-5.5/MySQL-5.5.42-1.sles11.x86_64.rpm-bundle.tar"
   3. Extract the MySQL client and MySQL server or just untar the whole thing
      • tar -xf MySQL-5.5.42-1.sles11.x86_64.rpm-bundle.tar
5. Create Retain download directory
   1. • md /software/retain[version] directory and change to it
   2. download the current version of Retain [3] or the beta.
      • wget "http://download.gwava.com/download.php?product=Retain&version=current"
      • wget "http://download.gwava.com/download.php?product=Retain&version=beta"
6. Unzip Retain
   1. • chmod +x *.sh

Install:

1. ./RetainInstall.sh
2. install modules:
   • Retain Server
   • Reporting & Monitoring
   • Worker
3. setup database, using MySQL
   • give it the path from above
   • give mysql root user a password (remember this)
   • create a database, username and password
4. take the defaults
5. If using multiple disks:
   1. Stop tomcat rcretain-tomat7 stop
   2. Change ownership on INDEX and LOGS to chown -R tomcat:tomcat /[volume]
   3. Change permissions on INDEX and LOGS to chmod -R 774 /[volume]
   4. Change ownership on DATA to chown -R mysql:mysql /DATA
   5. Change permissions on DATA to chmod -R 774 /DATA
   6. Change ownership on ARCHIVE to chown -R tomcat:tomcat /ARCHIVE
   7. Change permissions on ARCHIVE to chmod -R 777 /ARCHIVE
      1. Start tomcat rcretain-tomat7 start
6. Otherwise, configure the server.

Server Configuration

1. Browse to [retain server]/RetainServer
2. If using a single disk, take the defaults
3. Otherwise, use advanced options to specify multiple disks.
4. Set DB User to retain
5. Set DB ROOT User to root
6. Set Search engine to Lucene

Retain Configuration

1. Module Configuration and set up a module
   1. GroupWise
      1. Go to GWAdmin
      2. Go to System/Trusted Applications
         1. Create new: Retain
         2. Copy Trusted Application Key (save someplace safe)
      3. Go to Retain/Module Configuration/GroupWise
         1. SOAP:
            1. Copy Trusted Application Key to field
            2. Set POA Host name to IP|domain name of post office
            3. Test Connection
            4. Save Changes

1. Reporting and Monitoring Configuration and set up R&M
   1. Core Settings:
      1. Enable: Disable the disk usage statistics
      2. Enable: Disable the number of messages statistics
   2. Connection:
      1. Set server host names to IP or domain name, not localhost
   3. Save bootstrap
   4. Click on Reporting and install bootstrap

Job Configuration

1. Create Initial Dredge Schedule
   1. Single for Initial Dredge
   2. Save Changes
2. Create Initial Dredge Profile
   1. Scope tab:
      1. All Messages
      2. Try to publish all messages (SLOW)
      3. Enable Retention and Item Store Flag
      4. Save Changes
3. Create Worker
   1. Local Worker is good, if the worker is remote name it after the server it is on.
   2. Polling:
      1. Poll for configuration every 60 minutes is usually enough
   3. Logging:
      1. Diagnostic (so we don't have to try to reproduce the issue, which may take hours)
   4. Module specific
      1. POA Host Name should be blank
   5. Save Changes
      1. Save Bootstrap
      2. Open Worker web page (http://[Workerhost]/RetainWorker
      3. Upload
4. Create Initial Dredge Job
   1. Core Settings:
      1. Set Schedule, Profile and Worker as created above
   2. Mailboxes:
      1. Select Mail Server(s) to dredge
   3. Notification:
      1. Enable Mail when errors occur and Mail summary when job is complete
   4. Save Changes
5. Run Job
   1. Go to Schedules and set the minutes back 1 min.
   2. Go to Worker Web Console and click on "Refresh job cache now"
   3. Go to Status and determine if job is running properly.