Running Zulu 2 On a dedicated machine

From 360Works Product Documentation Wiki
Jump to: navigation, search

Running Zulu 2 on its own dedicated machine apart from FileMaker Server is a relatively common practice and can provide the benefit of distributing server load. In order to do so, the Zulu 2 context descriptor file must be modified to reflect the hostname or IP address where the FileMaker Server resides.

Using the Zulu_2_Context_Descriptor_Customization page of our docs, locate and edit your context descriptor file. Change the value of the "" parameter from '' to whatever hostname or IP address points to the machine where FileMaker Server's Web Publishing Engine is running.

Once you have edited the context descriptor file, paste it back into its source directory and use the 360Works Admin tool bundled with Zulu (in the 360Works directory) to stop and restart Tomcat. This will apply the change.

Personal tools

Plug-in Products
Other Products