How do I configure mingle to save attachments to a different location than the working dir?

• 

  Badri Janakiraman October 19, 2010 02:17

  Ian -
  
  Just to clarify, Mingle does not store its attachments in the installation directory. All data files - such as user icons, attachments etc. - are stored in a directory known as the mingle data directory. The mingle data directory *should* be configured to be external to the Mingle installation directory.
  
  It is possible to also set your data directory to a network share. You may pay a small overhead for the cost of access to all data in this location, but it should not be significant. You may want to confirm with your network adminstrator that this is indeed the case.
  
  The data directory is to be set differently on Windows & Unix platforms.
  
  On Windows
  
  

  
  

  
  
  •     Create a shared folder named mingleData on a server named, say, your.file.server.
  
  
  •     You should be able to access this share as \\your.file.server\mingleData from Windows Explorer
  
  
  •     You MUST ensure that the service account used by the Mingle service has full read/write access to this folder. To verify this, log in as the service account user on the machine that runs Mingle and attempt to create a test file on the share at \\your.file.server\mingleData
  
  
  •     If you have data in an existing mingle data directory, make sure you copy it (using rsync or some such tool) over to the remote location so as to replicate the structure on the remote share
  
  
  •     Open Windows Service Manager
  
  
  •     Locate the Mingle service. It will be called MingleServer_x_y - where x_y represents the Mingle release name. For Mingle 3.2 the service name should be called MingleServer_3_2.
  
  
  •     Stop this service
  
  
  •     Navigate to your Mingle installation directory, lets call this MINGLE_HOME
  
  
  •     Locate the file named MingleServer.vmoptions under MINGLE_HOME
  
  
  •     Open the file for edit in your favorite text editor
  
  
  •     Edit the value of the key for mingle.dataDir in there. To set your mingle.dataDir to your share, set -Dmingle.dataDir=\\\\your.file.server\mingleData (Note the four backslashes as opposed to two)
  
  
  •    Open Windows Service Manager and locate the MingleServer_x_y service
  
  
  •    Right-click the service name and select "Properties"
  
  
  •    Navigate to the "Log On" tab
  
  
  •    Change the "Log on as:" user from the "Local System Account" to "This account"
  
  
  •    Set the value of the account to be the name of the service account. e.g. If the name of the service account is "mingleuser", set the value to be ".\mingleuser"
  
  
  •    Set the password and confirmation fields appropriately
  
  
  •    Hit "Apply" to save the values you just entered.
  
  
  •    Restart the Mingle service from the "General" tab by hitting the "Start" button
  
  
  •    Ensure that Mingle started successfully by monitoring the Mingle logs, especially stderr.log and mingle.log
  
  

  
  

  
  On Unix
  
  

  
  

  
  
  •     Create a NFS mount of a remote directory on your remote server.
  
  
  •     You MUST ensure that the service account used to run the Mingle service has full read/write access to this folder
  
  
  •     If you have data in an existing mingle data directory, make sure you copy it (using rsync) over to the remote location so as to replicate the structure on the remote share
  
  
  •     Lets say the mount is accessed as /mnt/mingleData from the machine that runs your Mingle service
  
  
  •     Navigate to your Mingle installation directory, lets call this MINGLE_HOME
  
  
  •     Shut down Mingle by executing "./MingleServer stop" from the command line
  
  
  •     Start Mingle, but this time, specify the "/mnt/mingleData" as the mingle data directory to the startup script. Your startup command line will look something like
  
  

  
  

                 > MingleServer --mingle.dataDir=/mnt/mingleData start

  
  

  
  
  •    Ensure that Mingle started successfully by monitoring the Mingle logs, especially stderr.log and mingle.log
  
  

  
  

      Hope this helps.

  0

  Permalink

Please sign in to leave a comment.