Installing Zulu 2
Installing Zulu 2 on your server
Servlet rather than a "plugin"
Zulu 1 was introduced as both a traditional server-side plugin and as a standalone server running alongside FileMaker Server. Zulu 2 is only available as a standalone server because of the flexibility offered by separating from FileMaker Server. The Zulu plugin is deprecated and no longer supported. If you are currently running Zulu as a plugin, please uninstall the plugin and download the latest version of Zulu 2 from the 360Works store 360Works Zulu
To install the standalone server application, simply run the Windows Installer or Mac Installer that came packaged with your Zulu download and open the Zulu2SampleData example file.
Standard Installation
Prerequisites
- Check your Java version to make sure you are running at least Java 6
- Be sure FileMaker Server is installed and running with XML Custom Web Publishing enabled. (FMS does not need to necessarily run on the same machine as Zulu, but is required for Zulu to function.)
Installation Steps
- Unzip the package downloaded from the Zulu product page.
- Run the installer provided in the package.
- Follow the installer prompts, entering a username and password when prompted. (this is your sync admin password, write it down!)
Installer Hangs
- If the installer hangs during the installation, please follow the instructions here to remedy this.
Post Installation
- Register Zulu when the Welcome Page launches. (if you're using other 360Works products, and would like to try the demo license, simply restart the Tomcat Application Server using the 360Works Admin tool. For more detailed instructions, check out the Troubleshooting section.
Custom Installation
Users who need a more customized solution may choose to perform a manual installation of the Zulu 2 software. Zulu 2 runs on your server as an Apache Tomcat application, so you will need to download and install the Apache Tomcat server application for your operating system. (this may involve setting Tomcat up to start automatically with your system, as well as configuring your web server to forward traffic for Zulu to port 80). Installing Zulu inside the FileMaker Server Web Publishing Engine is no longer supported.
Prerequisites
- Check your Java version to make sure you are running at least Java 6
- Be sure FileMaker Server is installed and running with XML Custom Web Publishing enabled. (FMS does not need to necessarily run on the same machine as Zulu, but is required for Zulu to function.)
- Download and install Apache Tomcat 6.x or 7.x from http://tomcat.apache.org, for Windows make sure to download the installer
- Follow Tomcat documentation for running Tomcat as server, for Windows make to make the service selection during installation
- Start up Tomcat (this usually happens automatically when using the installer, otherwise you will need to run the Catalina shell script with a 'start' command).
Installing Zulu 2
- Copy the Zulu.war file from the Installer Data folder into the
$TOMCAT_HOME/webapps
folder in your Tomcat instance. - (Tomcat 6) Modify the
zulu.xml
file located in the$TOMCAT_HOME/conf/Catalina/localhost/
folder. - (Tomcat 7) Modify the
context.xml
file located in the$TOMCAT_HOME/webapps/zulu/META-INF/
folder.- Specify your username and password on these two lines of the
zulu.xml
file:<Parameter name="zulu.adminUsername" value="" override="false" />
<Parameter name="zulu.adminPassword" value="" override="false" />
- Specify your username and password on these two lines of the
- If necessary for your configuration, set up URL forwarding from IIS / Apache to your Tomcat connectors. See Tomcat documentation on how to do this.
Important notes about using Zulu 2 with FileMaker Server 11 or 14
Zulu 2 utilizes FileMaker Server's native AJP connector port for communication with FileMaker Server. This port is unavailable on FileMaker Server 11 and FileMaker Server 14. Please follow these instructions to correct the host port number in order to use Zulu 2.
Navigate to:
- Windows: C:\Program Files\360Works\Application\webapps\Zulu\META-INF\context.xml
- Mac: Library/360Works/Application/webapps/Zulu/META-INF/context.xml
Copy the context.xml file to your desktop, leaving a copy inside the META-INF folder (This is important. if there is no context.xml file in this location, Tomcat does not react well, and may require reinstallation). In the desktop copy of the context.xml, remove the port number from this line:
- Parameter name="jdbc.host" value="127.0.0.1:16020" overide="false"
So that it reads:
- Parameter name="jdbc.host" value="127.0.0.1" overide="false"
Now, drop the context.xml file back into the META-INF directory, use the "Replace" option to replace the old context.xml then try and publish to confirm the issue is fixed.
Next Steps
Serve the Sample File
Confirm your installation and see Zulu at work by serving the Zulu Sample File on your server. You'll want to do this before adding Zulu to your own file.