Troubleshooting

Getting the Right Privileges

I can connect to my Web Publishing Engine and FileMaker Server via the Administration Console, but I don't see the databases I expect to see.

Make sure that for every database you want to make available via XML-CWP or XSLT-CWP, you have created an appropriate Extended Privilege ( fmxml or fmxslt ) and attached it to at least one privilege set.

Dealing with Firewalls

My Web requests mysteriously time out, as though something were blocking them.

If you can get to the Administration Console, but your Custom Web Publishing URL requests appear to get no response, you may have a firewall in your way. If you suspect a firewall may be involved, consult your network administrator to explore this question. If it turns out that your machines are set up such that your Web server is on one side of a firewall, and your Web Publishing Engine machine or FileMaker Server machine is on the other, you need to open certain ports in the firewall. The rules are these:

• When the Web server and Administration Console are on one machine, and the Web Publishing Engine on another, traffic must be able to flow between the two machines on ports 16016 and 16018.

• When the Web Publishing Engine is on a different machine from FileMaker Server, traffic must be able to flow between the two machines on port 5003.

Dealing with Spaces

The Web Publishing Engine doesn't seem to see my entire URL . I enter a long URL and the Web server appears to truncate it and reports that the shorter URL can't be found.

If (despite the cautionary notes in this chapter) you have left any of your databases, fields, or layouts with spaces (or indeed any other non- alphanumeric characters ) in their names , your Custom Web Publishing URLs may very well break. If a Web server or browser encounters a space in a URL, it assumes the URL ends there. Other non-alphanumerics have different but equally irritating effects.

If you must work with URLs with spaces in them, you can get by with replacing all spaces with the string %20 whenever you need to write out a URL. Your stylesheet then might generate an HTML page with the following link:

 <a href="http://192.168.101.100/fmi/xsl/process-this.xsl?-db=Too%20Many  %20Spaces&-lay=Spaces%20Here%too&-findall 

If at all possible, we strongly encourage you to use only alphanumeric characters for database, layout, and field names and to avoid the use of whitespace. Extend this caution to script names if you are planning to call scripts from the Web.