MirrorSync for Hosting Providers
From 360Works Product Documentation Wiki
(Difference between revisions)
(Added better examples and added clarification about JkFmMount instructions) |
(Corrected locations for 12/11/mac/win) |
||
Line 4: | Line 4: | ||
* You may install the first instance of MirrorSync normally. For subsequent instances, follow these instructions: | * 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. | + | * First, download the MirrorSync Installer from [http://360works.com/filemaker-sync 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. | + | * Rename the .war file to something descriptive of the second installation. For example, rename the .war file to MirrorSync2. |
* Copy the .war file to the FileMaker Tomcat web applications directory, located in | * Copy the .war file to the FileMaker Tomcat web applications directory, located in | ||
Line 23: | Line 23: | ||
::FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/conf/Catalina/localhost/ | ::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 | + | * Back out to FileMaker Server/Admin/admin-helper/WEB-INF/conf/ and open the configuration file. This file may be called: |
+ | **''FileMaker 11 on OS X'': mod_jk.conf | ||
+ | **''FileMaker 12 on OS X'': mod_jk_paths.conf | ||
+ | **''Windows'': uriworkermap.properties | ||
* If you've already installed one instance, you should see: | * If you've already installed one instance, you should see: | ||
− | ::''For FileMaker 11'':<br> | + | ::''For FileMaker 11 on OS X'':<br> |
::JkFmMount /MirrorSync cwpe | ::JkFmMount /MirrorSync cwpe | ||
::JkFmMount /MirrorSync/* cwpe | ::JkFmMount /MirrorSync/* cwpe | ||
− | ::''For FileMaker 12'':<br> | + | ::''For FileMaker 12 on OS X'':<br> |
+ | ::ProxyPass /MirrorSync ajp://127.0.0.1:16021/MirrorSync | ||
+ | ::ProxyPassReverse /MirrorSync ajp://127.0.0.1:16021/MirrorSync | ||
+ | |||
+ | ::''For FileMaker 11 and Windows'':<br> | ||
+ | ::/MirrorSync=cwpc | ||
+ | ::/MirrorSync/*=cwpc | ||
+ | |||
+ | ::''For FileMaker 12 and Windows'':<br> | ||
::/MirrorSync=jwpc | ::/MirrorSync=jwpc | ||
::/MirrorSync/*=jwpc | ::/MirrorSync/*=jwpc | ||
− | ::Add another two lines to the end, using the same format. Replace MirrorSync with the custom name you used on the .war file. For example, if the .war file was renamed to MirrorSync2, on a FileMaker 11 installation, the lines would read: | + | ::Add another two lines to the end, using the same format. Replace MirrorSync with the custom name you used on the .war file. For example, if the .war file was renamed to MirrorSync2, on a FileMaker 11/OS X installation, the lines would read: |
::JkFmMount /MirrorSync cwpe | ::JkFmMount /MirrorSync cwpe |
Latest revision as of 22:01, 2 January 2013
[edit] Installation
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. For example, rename the .war file to MirrorSync2.
- 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 11:
- For FileMaker 12:
- Filemaker Server/Web Publishing/publishing-engine/jwpc-tomcat/
- For FileMaker 12:
- 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 the XML file here:
- For FileMaker 11:
- FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/conf/Catalina/localhost/
- For FileMaker 11:
- For FileMaker 12:
- FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/conf/Catalina/localhost/
- For FileMaker 12:
- Back out to FileMaker Server/Admin/admin-helper/WEB-INF/conf/ and open the configuration file. This file may be called:
- FileMaker 11 on OS X: mod_jk.conf
- FileMaker 12 on OS X: mod_jk_paths.conf
- Windows: uriworkermap.properties
- If you've already installed one instance, you should see:
- For FileMaker 11 on OS X:
- JkFmMount /MirrorSync cwpe
- JkFmMount /MirrorSync/* cwpe
- For FileMaker 11 on OS X:
- For FileMaker 12 on OS X:
- ProxyPass /MirrorSync ajp://127.0.0.1:16021/MirrorSync
- ProxyPassReverse /MirrorSync ajp://127.0.0.1:16021/MirrorSync
- For FileMaker 12 on OS X:
- For FileMaker 11 and Windows:
- /MirrorSync=cwpc
- /MirrorSync/*=cwpc
- For FileMaker 11 and Windows:
- For FileMaker 12 and Windows:
- /MirrorSync=jwpc
- /MirrorSync/*=jwpc
- For FileMaker 12 and Windows:
- Add another two lines to the end, using the same format. Replace MirrorSync with the custom name you used on the .war file. For example, if the .war file was renamed to MirrorSync2, on a FileMaker 11/OS X installation, the lines would read:
- JkFmMount /MirrorSync cwpe
- JkFmMount /MirrorSync/* cwpe
- JkFmMount /MirrorSync2 cwpe
- JkFmMount /MirrorSync2/* cwpe
- 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. Using the example name, it would be located at yourserver.com/MirrorSync2
[edit] Upgrading
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.
[edit] Troubleshooting
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.