Difference between revisions of "Retain Linux Install"
From GWAVA Technologies Training
Line 1: | Line 1: | ||
==Retain 3.5== | ==Retain 3.5== | ||
=== Prerequisites for Retain 3.5: === | === Prerequisites for Retain 3.5: === | ||
+ | ====Additional Disks==== | ||
+ | # Create additional disks for Retain best practices | ||
+ | #* Create the disks in the VM software | ||
+ | #* Format the disks in the VM itself using YaST/Partitioner | ||
+ | ##* ARCHIVE | ||
+ | ##* INDEX | ||
+ | ##* LOGS | ||
+ | ##* DATABASE (if local) | ||
− | + | ====Install HTTP Server==== | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
# Install http server (apache2) from YaST | # Install http server (apache2) from YaST | ||
# If connecting to Exchange: | # If connecting to Exchange: | ||
## Set DNS to Exchange server, in YaST/Network Settings | ## Set DNS to Exchange server, in YaST/Network Settings | ||
− | # Create | + | |
+ | ====Install MySQL ==== | ||
+ | ##* Create a directory and download it | ||
##* md /software/mysql directory and change to it | ##* md /software/mysql directory and change to it | ||
## download MySQL Community Server '''5.5.42''' [http://dev.mysql.com/downloads/mysql/] direct? [http://dev.mysql.com/downloads/file.php?id=455557] to that mysql directory | ## download MySQL Community Server '''5.5.42''' [http://dev.mysql.com/downloads/mysql/] direct? [http://dev.mysql.com/downloads/file.php?id=455557] to that mysql directory | ||
Line 17: | Line 22: | ||
## Extract the MySQL client and MySQL server or just untar the whole thing | ## Extract the MySQL client and MySQL server or just untar the whole thing | ||
##* <code>tar -xf MySQL-5.5.42-1.sles11.x86_64.rpm-bundle.tar</code> | ##* <code>tar -xf MySQL-5.5.42-1.sles11.x86_64.rpm-bundle.tar</code> | ||
+ | |||
+ | ====Download Retain==== | ||
# Create Retain download directory | # Create Retain download directory | ||
##* md /software/retain[version] directory and change to it | ##* md /software/retain[version] directory and change to it | ||
Line 25: | Line 32: | ||
##* <code>chmod +x *.sh</code> | ##* <code>chmod +x *.sh</code> | ||
− | === Install | + | ===Install=== |
# <code>./RetainInstall.sh</code> | # <code>./RetainInstall.sh</code> | ||
Line 32: | Line 39: | ||
#* Reporting & Monitoring | #* Reporting & Monitoring | ||
#* Worker | #* Worker | ||
+ | #* Skip Stubbing as very few customers use that functionality | ||
+ | #* Skip the Router as that should be installed on its own server in the network DMZ | ||
# setup database, using MySQL | # setup database, using MySQL | ||
#* give it the path from above | #* give it the path from above | ||
Line 41: | Line 50: | ||
## Change ownership on INDEX and LOGS to <code>chown -R tomcat:tomcat /[volume]</code> | ## Change ownership on INDEX and LOGS to <code>chown -R tomcat:tomcat /[volume]</code> | ||
## Change permissions on INDEX and LOGS to <code>chmod -R 774 /[volume]</code> | ## Change permissions on INDEX and LOGS to <code>chmod -R 774 /[volume]</code> | ||
− | ## Change ownership on | + | ## Change ownership on DATABASE to <code>chown -R mysql:mysql /DATABASE </code> |
− | ## Change permissions on | + | ## Change permissions on DATABASE to <code>chmod -R 774 /DATABASE </code> |
## Change ownership on ARCHIVE to <code>chown -R tomcat:tomcat /ARCHIVE </code> | ## Change ownership on ARCHIVE to <code>chown -R tomcat:tomcat /ARCHIVE </code> | ||
## Change permissions on ARCHIVE to <code>chmod -R 777 /ARCHIVE </code> | ## Change permissions on ARCHIVE to <code>chmod -R 777 /ARCHIVE </code> | ||
Line 57: | Line 66: | ||
# Set Search engine to Lucene | # Set Search engine to Lucene | ||
− | === Retain Configuration === | + | ===Retain Configuration=== |
+ | ====Reporting and Monitoring Configuration==== | ||
+ | # Click on Reporting and Monitoring Configuration | ||
+ | ## Core Settings: | ||
+ | ### Enable: Disable the disk usage statistics | ||
+ | ### Enable: Disable the number of messages statistics | ||
+ | ## Connection: | ||
+ | ### Set server host names to IP or domain name, not localhost | ||
+ | ## Save bootstrap | ||
+ | ## Click on Reporting and install bootstrap | ||
+ | ===Module Configuration=== | ||
# Module Configuration and set up a module | # Module Configuration and set up a module | ||
## GroupWise | ## GroupWise | ||
Line 71: | Line 90: | ||
##### Test Connection | ##### Test Connection | ||
##### Save Changes | ##### Save Changes | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== Job Configuration === | === Job Configuration === |
Revision as of 18:48, 26 April 2016
Contents |
Retain 3.5
Prerequisites for Retain 3.5:
Additional Disks
- Create additional disks for Retain best practices
- Create the disks in the VM software
- Format the disks in the VM itself using YaST/Partitioner
- ARCHIVE
- INDEX
- LOGS
- DATABASE (if local)
Install HTTP Server
- Install http server (apache2) from YaST
- If connecting to Exchange:
- Set DNS to Exchange server, in YaST/Network Settings
Install MySQL
Download Retain
- Create Retain download directory
- md /software/retain[version] directory and change to it
- download the current version of Retain [3] or the beta.
- Unzip Retain
-
chmod +x *.sh
-
Install
-
./RetainInstall.sh
- install modules:
- Retain Server
- Reporting & Monitoring
- Worker
- Skip Stubbing as very few customers use that functionality
- Skip the Router as that should be installed on its own server in the network DMZ
- setup database, using MySQL
- give it the path from above
- give mysql root user a password (remember this)
- create a database, username and password
- take the defaults
- If using multiple disks:
- Stop tomcat
rcretain-tomat7 stop
- Change ownership on INDEX and LOGS to
chown -R tomcat:tomcat /[volume]
- Change permissions on INDEX and LOGS to
chmod -R 774 /[volume]
- Change ownership on DATABASE to
chown -R mysql:mysql /DATABASE
- Change permissions on DATABASE to
chmod -R 774 /DATABASE
- Change ownership on ARCHIVE to
chown -R tomcat:tomcat /ARCHIVE
- Change permissions on ARCHIVE to
chmod -R 777 /ARCHIVE
- Start tomcat
rcretain-tomat7 start
- Start tomcat
- Stop tomcat
- Otherwise, configure the server.
Server Configuration
- Browse to [retain server]/RetainServer
- If using a single disk, take the defaults
- Otherwise, use advanced options to specify multiple disks.
- Set DB User to retain
- Set DB ROOT User to root
- Set Search engine to Lucene
Retain Configuration
Reporting and Monitoring Configuration
- Click on Reporting and Monitoring Configuration
- Core Settings:
- Enable: Disable the disk usage statistics
- Enable: Disable the number of messages statistics
- Connection:
- Set server host names to IP or domain name, not localhost
- Save bootstrap
- Click on Reporting and install bootstrap
- Core Settings:
Module Configuration
- Module Configuration and set up a module
- GroupWise
- Go to GWAdmin
- Go to System/Trusted Applications
- Create new: Retain
- Copy Trusted Application Key (save someplace safe)
- Go to Retain/Module Configuration/GroupWise
- SOAP:
- Copy Trusted Application Key to field
- Set POA Host name to IP|domain name of post office
- Test Connection
- Save Changes
- SOAP:
- GroupWise
Job Configuration
- Create Initial Dredge Schedule
- Single for Initial Dredge
- Save Changes
- Create Initial Dredge Profile
- Scope tab:
- All Messages
- Try to publish all messages (SLOW)
- Enable Retention and Item Store Flag
- Save Changes
- Scope tab:
- Create Worker
- Local Worker is good, if the worker is remote name it after the server it is on.
- Polling:
- Poll for configuration every 60 minutes is usually enough
- Logging:
- Diagnostic (so we don't have to try to reproduce the issue, which may take hours)
- Module specific
- POA Host Name should be blank
- Save Changes
- Save Bootstrap
- Open Worker web page (http://[Workerhost]/RetainWorker
- Upload
- Create Initial Dredge Job
- Core Settings:
- Set Schedule, Profile and Worker as created above
- Mailboxes:
- Select Mail Server(s) to dredge
- Notification:
- Enable Mail when errors occur and Mail summary when job is complete
- Save Changes
- Core Settings:
- Run Job
- Go to Schedules and set the minutes back 1 min.
- Go to Worker Web Console and click on "Refresh job cache now"
- Go to Status and determine if job is running properly.