MirrorSync for Hosting Providers

From 360Works Product Documentation Wiki
Revision as of 16:40, 30 October 2012 by Jesse (Talk | contribs)

Jump to: navigation, search


To install multiple instances of MirrorSync on a single server, follow the instructions below.

  • You may install the first instance of MirrorSync normally. For subsequent instances, follow these instructions:
  • First, download the MirrorSync Installer from 360works.com. In that download, locate the MirrorSync.war file in the Installer Data.
  • Rename the .war file to something descriptive of the second installation.
  • Copy the .war file to the FileMaker Tomcat web applications directory, located in
For FileMaker 11:
FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/bin/
For FileMaker 12:
FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/bin
  • The .war file will extract itself, creating a new folder. This means the application is deployed.
  • Modify the XML for MirrorSync to set a username and password to administer MirrorSync. Set a value for adminUsername and adminPassword. You can use an MD5 encoded password using adminPasswordHash. Find this XML file here:
For FileMaker 11:
FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/conf/Catalina/localhost/
For FileMaker 12:
FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/conf/Catalina/localhost/
  • Back out to FileMaker Server/Admin/admin-helper/WEB-INF/conf/ and open mod_jk.conf (OS X) or uriworkermap.properties (Windows)
  • If you've already installed one instance, you should see:
JkFmMount /MirrorSync cwpe
JkFmMount /MirrorSync/* cwpe
Add another two lines to the end, using this format. Replace MirrorSync with the custom name you used on the .war file.
  • Restart the Web Server / Apache / IIS
  • Open the new instance of MirrorSync by navigating to your server in a browser, and adding the custom name after a slash. For example, yourserver.com/MirrorSync2


If upgrading to the latest version of MirrorSync, make sure to stop the Web Publishing Engine. Then, use the .war file included in the upgrade download files and install it to the locations above. Make sure to keep your naming consistant.


If users cannot log in, try restarting the Web Publishing Engine. Also make sure the XML files have the correct user names and passwords in each instance.

Personal tools

Plug-in Products
Other Products