Installing Zulu

From 360Works Product Documentation Wiki
Revision as of 15:27, 20 April 2015 by Martin (talk | contribs) (→‎Mac)
Jump to navigation Jump to search
Zulu  
Getting Setup with Zulu: Installing • Installing as Servlet • Installing the Plugin Version • Zulu Google Setup • Integrating your file • ‎Zulu Sync • ‎Serving the Sample File • Registration • Installing Zulu Manually
About Zulu The big picture • Limitations • Requirements • Differences between servlet and plugin • Hosting • Security
Troubleshooting Troubleshooting • Testing Configurations • Umlauts • URLs Used By Zulu • Updating • Logs
Google Sync with Google • ‎Sharing a Google Calendar • Google Contacts • Google Reset • Appointment Slots
Calendars Repeating Events • Date Ranges • ‎Read Only Calendars • Deleting Events • Invitations • Switching Calendars • Multiple Calendars • Properties • See it in iCal • My site
Contacts Contact Groups • Contacts Integrations • Related Contact Fields • Address Book • Zulu Phone Fax Email
Does Zulu work with... Android • Blackberry • Multiple Machines • Outlook • MobileMe • iPhone
Extra Credit Adding Fields • Time Zones • Duplicating Records • Calc Fields • Access Privledges • Refresh • Filtering • Post Editing Scripts • Alarms and notifications

Installation: Installing the plugin on your FileMaker Server

Servlet rather than a "plugin"

Zulu was introduced as both a traditional server-side plugin and as a small application (a servlet) for FileMaker Server. Newer versions of Zulu are only available as servlets because these offer a lot more configuration options. If you are currently running Zulu as a plugin, please uninstall the plugin and download the latest version of Zulu from the 360Works store 360Works Zulu

To install the servlet, simply run the Windows Installer or Mac Installer that came packaged with your Zulu download.

Standard Installation

Prerequisites
  • Be sure FileMaker Server is installed and running with XML Custom Web Publishing enabled.
Installation Steps

Run the installer downloaded from the Zulu product page

Custom Installation

Manual Installation

Users who need a more customized solution may need to perform a manual installation of the Zulu software. Zulu runs on your server as an Apache Tomcat application; therefore, it will run alongside the Web Publishing engine using the existing Tomcat instance installed by FileMaker Server or you can download and install the Apache Tomcat server application for your operating system to run Zulu in a standalone Tomcat Server (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).

Zulu can be installed into the Web Publishing Engine. This is the easiest installation method to configure, and is easily redirected to port 80. Alternatively, you may install Zulu in a standalone Tomcat server of your choice. This option is available if you do not want to modify the Web Publishing Engine or if you need further customization.

Installing in the FileMaker Server Web Publishing Engine

Prerequisites

  • Be sure FileMaker Server is installed and running with XML Custom Web Publishing enabled.

Installing Zulu

  • Copy the Zulu.war file from the Installer Data folder into the jwpc-tomcat folder located at FileMaker Server/Web Publishing/publishing-engine/jwpc-tomcat/ (a Zulu folder will be created automatically when the .war file is dropped in place).
  • Now you should be able to access the Zulu sync admin splash page by visiting http://localhost:16020/zulu verify that you are able to successfully access this page.
  • (FMS13) Back in the jwpc-tomcat folder, navigate to jwpc-tomcat/zulu/META-INF/ and edit the context.xml
  • (FMS12) Back in the jwpc-tomcat folder, navigate to jwpc-tomcat/conf/Catalina/localhost/ and edit the zulu.xml
    • Specify your username and password on these two lines of the zulu.xml/context.xml file:
      • <Parameter name="zulu.adminUsername" value="" override="false" />
      • <Parameter name="zulu.adminPassword" value="" override="false" />

URL Redirection

NOTE: These instructions apply only to users installing inside the FMS13 Web Publishing Engine.

Windows

FileMaker Server uses the URL Rewrite module of IIS to redirect traffic from the native HTTP Tomcat port 16020 to the standard web traffic port 80

  • Launch the IIS Manager, expand the Sites folder, then click on the FMWebSite site. You will see a collection of modules in the center pane of IIS Manager.
  • Double click the module that reads URL Rewrite.
  • In the right hand pane, click Add Rule(s) at the very top of the list of actions.
  • From here, choose Blank rule and press OK
  • Set up the rule to match the pattern for the requested URL using regular expressions.
  • Set the pattern as ^zulu(.*)
  • Scroll down to the action section and be sure the action type is set to Rewrite
  • Set the Rewrite URL as http://localhost:16020/zulu{R:1}
  • Be sure Append query string and Stop processing of subsequent rules are both checked, then apply the settings.
  • Go to the ARR proxy settings (they're hidden under IIS -> Application Request Routing Cache -> Server Proxy Settings) and uncheck the "Reverse rewrite host in response headers" checkbox.
  • Finally, test the the zulu URL in your browser (http://localhost/zulu)
Mac

If Zulu is installed in it's own instance of Tomcat (Default Installation)

  • Navigate to FileMaker Server/HTTPServer/conf/httpd.conf and open the httpd.conf file with a text editor. You will need elevated permissions to modify this file.
  • Add these lines to the end of the httpd.conf file:
    • ProxyPass /zulu ajp://127.0.0.1:42423/zulu retry=1 timeout=7200
  • Save the file back to its original location.

If Zulu is installed inside the FileMaker Web Publishing Engine

  • Navigate to FileMaker Server/Admin/admin-helper/WEB-INF/conf/ and open the mod_proxy.conf file with a text editor. You will need elevated permissions to modify this file.
  • Add these lines to the end of the mod_proxy.conf file:
    • ProxyPass /zulu ajp://127.0.0.1:16021/zulu retry=1 timeout=7200
  • Save the file back to its original location.


Now Apache needs to be restarted, but we need to be sure to restart Apache with the FMS13 configuration.

  • Open a terminal window and enter cd "/Library/FileMaker Server/HTTPServer/bin" and press return.
  • Enter this command to restart Apache (you will need to enter your system password when prompted): sudo ./httpdctl graceful
  • Test the Zulu URL in your browser (http://localhost/zulu)
Using Filemaker Server 11?

Navigate to:

Mac:

/Library/360Works/Applications/webapps/zulu/META-INF/context.xml

Windows:

/Program Files/360Works/Applications/webapps/zulu/META-INF/context.xml

Find the line that reads:

<Parameter name="jdbc.host" value="127.0.0.1:16020" override="false" />

And remove the port number so it looks like this:

<Parameter name="jdbc.host" value="127.0.0.1" override="false" />

Try and publish your calendars to confirm this fixed the issue.

Alternative - Installing in a standalone Apache Tomcat Server

Prerequisites
  • 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
  • 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" />
  • If necessary for your configuration, set up URL forwarding from IIS / Apache to your Tomcat connectors. See Tomcat documentation on how to do this.

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.

Zulu Serving The Sample File

Retrieved from "http://docs.360works.com/index.php?title=Installing_Zulu&oldid=1397"