MirrorSync advanced topics From 360Works Product Documentation Wiki Welcome to the advanced section of the MirrorSync documentation! This guide will help you customize MirrorSync to suit your development needs, and provide detailed instructions for various situations. If you would like a good general overview of the software, please read through the basic set up documentation first!
Contents 1 Deployment questions 1.1 How do I uninstall MirrorSync? 1.2 Installation for hosting providers 1.3 Using a FileMaker sub-admin account 1.4 Split server deployments 1.5 How do I install MirrorSync on Linux? 1.6 Does MirrorSync work with runtime versions of FileMaker Pro? 1.7 What if I need to redeploy FileMaker Server? 1.8 I am running MirrorSync 2. What do I need to do to upgrade to 3? 1.9 Installing without a network connection 1.10 How do I migrate MirrorSync from one server to another? 2 Networking questions 2.1 Can MirrorSync send encrypted appBase="webapps" unpackWARs="true" autoDeploy="true" startStopThreads="30"> For installation on Mac or Windows, we recommend you use the installer. We at 360Works use the installer for our hosting clients as well, and find it easy to update and manage. If you are curious as to what the installer actually does, it modifies and adds the following: Creates a folder at '/Library/360Works' on Mac or 'C:\Program Files\360Works' on Windows that is readable and writeable. Downloads and installs an instance of Tomcat 7 (http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.55/bin/apache-tomcat-7.0.55.zip) into that folder. (Only one copy of Tomcat is installed, regardless of how many copies of MirrorSync are running) Copies and renames the installer's MirrorSync.war, which deploys the web app, as well as the other supporting material into the folder. Adds a launch daemon in Library/LaunchDaemons in OS X, or creates a Windows Service to automatically start Tomcat. Modifies the http.conf file for Apache to allow for URL redirection. If using Windows with IIS, we create an ISAPI filter or a URL Rewrite rule for the URL redirect. Copies a lightweight Admin Utility JAR file to manage Tomcat to either C:\Program Files\360Works or /Applications. If upgrading from an older version of MirrorSync, we'll remove the URL redirects for the old MirrorSync. If you prefer to skip the installer and manually deploy using your own instance of Tomcat that you've set up, please note and follow these instructions: 1. Create a folder at '/Library/360Works' on Mac or 'C:\Program Files\360Works' on Windows. Make sure that it is readable and writeable to the process that Tomcat is running as. This is where MirrorSync stores its private acceptCount="100" address="127.0.0.1" compressableMimeType="text/html,text/css,text/plain,application/javascript,application/json" compression="on" compressionMinSize="2048" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="5" port="16020" protocol="HTTP/1.1" redirectPort="8443"/>
Remove the part that says address="127.0.0.1", so that it looks like this:
Save this change, then restart the Web Publishing Engine. Test that the WPE is working by using the URL "http://yourServer/fmi/xml/FMPXMLRESULT.xml?-dbnames" - it should show you an XML list of -Dcom.prosc.tomcat=true -Xmx1G
The new memory settings won't take effect until Tomcat is restarted, which can be done using the 360Works Admin.jar, which is in /Applications on OS X and C:\Program Files\360Works\ on Windows. Reading/writing incorrect timestamp values from MySQL MirrorSync uses the timezone configured in the MySQL server. Most of the time, this is fine. However, some applications (such as Magento) may ignore the MySQL configured time zone and instead default to GMT/UTC timezones when writing time values. In that case, MirrorSync may not detect changes made in MySQL and/or it may write incorrect time values to other value="" />
The MirrorSync.xml configuration file is located at C:\Program Files\360Works\Applications\conf\Catalina\localhost\MirrorSync.xml on Windows, /Library/360Works/Applications/conf/Catalina/localhost/MirrorSync.xml on Mac. MirrorSync configuration client 'hangs' This is an issue that we have observed on OS X, where you may get the beachball and the configuration client can lock up / freeze / hang when entering text into a dialog. So far, we have been able to trace all of these occurrences to one of the following 3rd party extensions: Rescue Time BetterSnapTool BetterTouchTool Caffeine QuicKeys If you encounter this issue, check to see if you have any of these applications running, either by looking at the top-right menubar corner or using the Activity Monitor application. Quit them if they are running. If you are experiencing this problem and you do not have one of these applications running, go to your Users & Groups system preference, click the 'Login items' tab, and then use Activity Monitor to quit out of all applications listed as a login item. If that still does not solve the problem, please contact us at
[email protected] and we will help troubleshoot the problem. Error 10 occurs during sync This issue typically occurs when a syncing client opens a connection to the MirrorSync server for a container upload, but takes longer than the connectionTimeout property configured in IIS. This can be solved by making a change to the connectionTimeout Property in the IIS Manager application. From Administrative Tools, open the Internet Information Services Manager application. Choose the top level (server name) node in the tree on the left. Choose the "Configuration Editor" option under the management header (from Features view). Expand the "Section" drop down list and expand the system.applicationHost node, then choose "webLimits" The connectionTimeout property is the first property available, and defaults to 2 minutes. Increase the connectionTimeout from 2 minutes to something more appropriate (30 minutes seems to work well). Be sure to apply the change before closing the IIS manager application.
IIS Manager editing the connectionTimeout property
Handshake alert: unrecognized_name This issue can occur when the host name used to access your SSL enabled FileMaker Server does not match the host name resulting from reverse looking up the Server's IP address. For instance if you have an internal DNS rule providing a CNAME pointing to your FileMaker Server which is available externally by a different primary DNS entry. Typically the host name used to reach the server should match the servers established host name. If it does not, such as in the example above the mechanism performing this validation may be turned off. Access the setenv.bat or setenv.sh file in your 360Works/Applications/bin/ directory, and modify the first CATALINA_OPTS string. add to the end of the string: "Djsse.enableSNIExtension=false" making sure to include a space between the new parameter and the previously last parameter in the string. Restart the 360Works Application Server. Configuring MirrorSync creates gaps in serial numbers This is known and expected behavior. When MirrorSync auto-detects primary keys, modification timestamps, and creation timestamps, it does so by creating a new test record, checking to see which fields are writeable and which ones have auto-enter options on them, and then deletes that test record. This will result in the next number in the serial number sequence to be used up. I forgot my MirrorSync admin password Re-run the MirrorSync installer and you can reset the password to whatever you want. Running the installer will not lose or overwrite any configurations. I'm getting a MySQL error that starts with 'Packet for query is too large' MySQL has a default limit of 4 megabytes for BLOBs, which are basically MySQL's version of a FileMaker container field. You can increase this limit by adding these lines (or something similar, read MySQL documentation for full details) to your MySQL configuration file: max_allowed_packet = 1024M innodb_log_file_size = 1024M Java Security blocks MirrorSync Configuration client from launching Old versions of MirrorSync will have an expired developer certificate so Java will keep the applet from launching. The certificate will not be updated on these versions so in order to launch the configuration client you must add the origin site to the exception list. Typically this will be the host name or IP address of the machine running MirrorSync. The origin site should be listed on the Java security prompt ex:
Once you know the origin site, open the Java Control panel and click on security. Click on "Edit Site List" and then click "add" and enter in your origin site. If you get a warning about using HTTP, click "continue". Once you have added your origin site to the exception list, you should now be able to launch the MirrorSync Configuration client. You may get a security prompt that looks like this:
Make sure to check the box that says "I accept the risk and want to run this application" and then click run. NullPointerException when copying scripts If this occurs, and if you are running MirrorSync on a Linux server, make sure that you have the regular version of Java installed, rather than the headless version.
Retrieved from "http://docs.360works.com/index.php?title=MirrorSync_advanced_topics&oldid=2421" This page was last modified on 3 January 2018, at 16:48. This page has been accessed 257,281 times.