Filemaker FileMaker Server 7 Advanced Installation guide

FileMaker

®

Server 7

Advanced

Web Publishing

Installation Guide

© 2004 FileMaker, Inc . All Rights Reserved.

FileMaker, Inc.

5201 Patrick Henry Drive

Santa Clara, California 95054

FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries, and ScriptMaker and the file folder logo are trademarks of FileMaker, Inc.

FileMaker documentation is copyrighted. You are not authorized to make additional copies or distribute this documentation without written permission from

FileMaker. You may use this documentation solely with a valid licensed copy of FileMaker software.

All persons and companies listed in the examples are purely fictitious and any resemblance to existing persons and companies is purely coincidental.

Credits are listed in the Acknowledgements document provided with this software.

For more information, visit our web site at www.filemaker.com.

Edition: 01

Contents

Chapter 1

Before yo u be gin

Using FileMaker Server documentation

Customer support

About the license key

Hardware and software requirements

Windows requirements for the Web Publishing Engine

Mac OS requirements for the Web Publishing Engin e

W indows requirements for FileMaker Site Assistant and FileMaker CDML Converter tool s

Mac OS requirements for FileMaker Site Assistant and FileMaker CDML Converter tool s

I mportant note about supported operating systems

About the Web Publishing Engine software components

About the tools for developing XSLT stylesheets

Overview of installing, configuring, and using the Web Publishing Engine

Installing the Web Publishing Engine in various host configurations

About the protocols for the Web Publishing Engine

Using SSL and FileMaker Server encryption

Registering the Web Publishing Engine in FileMaker Server

Installing plug-ins for the Web Publishing Engine

Chapter 2

Installing the Web Publishing Engine in Windows

Overview of installation

Installing the Web Publishing Engine software components

About the Web Publishing Engine service s

Installing the Web Publishing Engine from the command line

Setting up authentication for a Windows IIS web site

Uninstalling, modifying, or repairing the Web Publishing Engine

Installing the FileMaker Site Assistant and FileMaker CDML Converter

Where to go from here

23

24

25

26

26

19

20

23

12

13

15

16

10

10

10

11

16

18

9

10

8

8

7

8

8

4 FileMaker Server Advanced Web Publishing Installation Guide

Chapter 3

Installing the Web Publishing Engine in Mac OS X

Overview of installation

Installing the Web Publishing Engine software components

Where files are stored on your hard disk

Uninstalling, modifying, or repairing the Web Publishing Engine

Installing the FileMaker Site Assistant and FileMaker CDML Converter


Chapter 4

Configuring the Web Publishing Engine

About the Web Publishing Engine Administration Console

General steps for configuring the Web Publishing Engine

Configuring the Web Publishing Engine for the first time

Configuring the connection between the Web Publishing Engine and FileMaker Server

Viewing an overview of the Web Publishing Engine configuration

Configuring Instant Web Publishing

Disabling Instant Web Publishing

Disabling Custom Web Publishing with XML

Configuring Custom Web Publishing with XSLT

Setting the Web Publishing Engine mode

Setting server-side XSLT stylesheet caching

C onfiguring the interaction between web sessions and database sessions

C onfiguring access to a mail server for the Web Publishing Engine

S etting the default text encoding for XSLT requests

Disabling Custom Web Publishing with XSLT

Specifying general settings for the Web Publishing Engine

Specifying logging options for the Web Publishing Engine

S etting the session time-out for the Web Publishing Engine

Changing the IP address of the Web Publishing Engine host

Changing the user name and password for the Web Publishing Engine

Restricting access to the Administration Console

Viewing a list of the published databases for FileMaker Server

L ogging out of the Administration Console

43

44

45

45

41

41

41

43

36

38

39

40

31

31

32

48

49

50

51

46

46

47

48

27

28

29

29

29

30

Using th e Web Publishing Engine and Administration Console services

Starting, restarting, or stopping the services in Windows

Starting, restarting, stopping , o r disabling the services in Mac OS X

Changing the user name and password for the Administration Console


Index

Contents 5

51

52

52

53

53

55

6 FileMaker Server Advanced Web Publishing Installation Guide

Chapter 1

Before you begin

Welcome to FileMaker ® Server 7 Advanced, which includes the Web Publishing Engine and support for

Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC). The Web Publishing Engine provides Instant Web Publishing and Custom Web Publishing with XML or XSLT for FileMaker Server. For information on ODBC and JDBC, see the FileMaker ODBC and JDBC Developer’s Guide .

Using FileMaker Server documentation

This FileMaker Server Advanced Web Publishing Installation Guide describes how to install and configure the Web Publishing Engine on Windows and Mac OS X computers.

The FileMaker Server Advanced Custom Web Publishing Guide describes how to develop FileMaker XSLT stylesheets, use the Web Publishing Engine to publish your databases using XML or XSLT, and convert

CDML solutions to FileMaker XSLT.

The FileMaker Instant Web Publishing Guide describes how to make FileMaker Pro databases accessible to web browser users over an intranet or the Internet.

Installing FileMaker ODBC and JDBC Client Drivers describes how to install driver files for using

FileMaker Pro with ODBC and JDBC applications.

The FileMaker ODBC and JDBC Developer’s Guide describes how to use ODBC and JDBC with FileMaker products.

The FileMaker Server Administrator’s Guide and FileMaker Server Admin Help describe how to install and configure FileMaker Server.

The FileMaker Security Guide describes security concerns to keep in mind when using FileMaker products.

Note Portions of this documentation referring to FileMaker Server 7 Advanced features such as web publishing and ODBC/JDBC only apply to FileMaker Server 7 Advanced licensed customers.

I mportant You can download PDFs of FileMaker 7 documentation from www.filemaker.com. Any updates to this document are also available from the web site.

8 FileMaker Server Advanced Web Publishing Installation Guide

Customer support

For information about technical support and customer service, see: www.filemaker.com (North American customers) www.filemaker.com/intl (customers outside North America) or choose Help menu > FileMaker on the Web (Mac OS), or the “FileMaker web resources” topics in

FileMaker Server Help (Windows). At the web site, you will find the service options available to North

American customers, as well as links to FileMaker worldwide sites, answers to frequently asked questions, and access to the TechInfo Knowledge Base. If you do not have access to the web, please refer to the

FileMaker Service Directory included in the software box. North America customers can also call (800)

965-9090 to learn about the service options available.

About the license key

To use the Web Publishing Engine, you must purchase and install a FileMaker Server Advanced license key.

Although you can install the Web Publishing Engine software without a license key, FileMaker Server will not allow the Web Publishing Engine to connect without a FileMaker Server Advanced license key.

If you purchased FileMaker Server Advanced, you can enter the license key during FileMaker Server installation. If you purchased FileMaker Server Option Pack, you must update the license key after FileMaker

Server installation. For information on installing FileMaker Server or updating the FileMaker Server license key, see the FileMaker Server Administrator’s Guide.

Note Only one Web Publishing Engine is allowed with each copy of FileMaker Server.

Hardware and software requirements

To install and use the Web Publishing Engine and associated tools, you need the CD-ROM in the FileMaker

Server package and the following minimum equipment and software:

Windows requirements for the Web Publishing Engine

Minimum requirements for 1-50 clients

1

Intel-compatible PC with a Pentium III 1 GHz processor

1

256 MB of installed RAM

1 hard disk with at least 500 MB of available disk space

1

CD or DVD drive

1

Windows Server 2003 Standard Edition or Windows 2000 Server (with Service Pack 4) operating system

1

Microsoft Internet Information Services (IIS) (5.0 for Windows 2000 Server) (6.0 for Windows Server

2003)

Before you begin 9

1

Java 2 Platform, Standard Edition (J2SE) 1.4.2 Windows (automatically installed with the Web Publishing

Engine)

1 network connectivity to the Internet or an intranet via TCP/IP

Minimum requirements for more than 50 clients

1

Intel-compatible PC with a Pentium 4 2 GHz processor

1

512 MB of installed RAM (1 GB or more recommended)

1 hard disk with at least 1 GB of available disk space

1

CD or DVD drive

1

Windows Server 2003 Standard Edition or Windows 2000 Server (with Service Pack 4) operating system

1

Microsoft Internet Information Services (IIS) (5.0 for Windows 2000 Server) (6.0 for Windows Server

2003)

1

Java 2 Platform, Standard Edition (J2SE) 1.4.2 Windows (automatically installed with the Web Publishing

Engine)


Mac OS requirements for the Web Publishing Engine

Minimum requirements for 1-50 clients

1

Apple G4 500 MHz

1



1

CD or DVD drive

1

Mac OS X or Mac OS X Server 10.2.8 (with Java 1.4.1 Update 1) or 10.3

1

Apache HTTP Server (the version shipped with your operating system), enabled


Minimum requirements for more than 50 clients

Also consider using this set of requirements if you plan to install the Web Publishing Engine and FileMaker

Server on the same computer.

1

Power Mac G4 1 GHz

1

512 MB of installed RAM (1 GB or more recommended)

1 hard disk with at least 1 GB of available disk space

1

CD or DVD drive

1

Mac OS X Server 10.2.8 (with Java 1.4.1 Update 1) or 10.3

1

Apache HTTP Server (the version shipped with your operating system), enabled



Windows requirements for FileMaker Site Assistant and FileMaker CDML Converter tools

1

Intel-compatible PC with a Pentium III 500 MHz processor

1



1

CD or DVD drive

1

Windows 2000 Server (with Service Pack 4), Windows 2000 Professional, Windows XP, Windows Server

2003 Standard Edition

1

Java 2 Platform, Standard Edition (J2SE) 1.4.2 Windows (automatically installed with the tools)

1 for Site Assistant only, network connectivity to the Web Publishing Engine via TCP/IP or installation on the same host as Web Publishing Engine

Mac OS requirements for FileMaker Site Assistant and FileMaker CDML Converter tools

1

Apple G3 or G4 computer, 500 MHz

1



1

CD or DVD drive

1

Mac OS X or Mac OS X Server 10.2.8 (with Java 1.4.1 Update 1) or 10.3

1 for Site Assistant only, network connectivity to the Web Publishing Engine via TCP/IP or installation on the same host as Web Publishing Engine

Important note about supported operating systems

At the time this guide was written, FileMaker, Inc. tested the Web Publishing Engine with the Windows and

Mac OS operating systems listed above. The Web Publishing Engine may or may not work with newer operating system releases. For information on newer operating systems, see www.filemaker.com.

About the Web Publishing Engine software components

The Web Publishing Engine uses the following software components:

1

Web server: The Web Publishing Engine requires an Apache (Mac OS X) or IIS (Windows) web server.

The web server must be installed before you install the Web Server Module and Administration Console.

1

Web Server Module and Administration Console: These two software components are always installed together as a unit on the web server host computer. The Web Server Module enables the Web Publishing

Engine to connect to the web server. You use the Administration Console in a web browser to configure the Web Publishing Engine via the connection through the web server.


1

Web Publishing Engine: The Web Publishing Engine supports Instant Web Publishing and Custom Web

Publishing with XML and XSLT using databases hosted by FileMaker Server. The Web Publishing Engine consists of two software components that are always installed together as a unit:

1

Web Publishing Core: This software component communicates with the web server and FileMaker

Server and can generate Instant Web Publishing pages of hosted databases. It can also generate XML data from databases based on query commands and parameters.

1

Custom Web Publishing Engine: This software component communicates with the web server and

Web Publishing Core. It processes XSLT stylesheets and provides output as HTML, XML, or text to the web server, which then provides the output to a web user’s browser.

1

FileMaker Server: FileMaker Server is required for hosting the databases you want to publish on the web.

Web

Browser

Web Server

Web Server Module

Administration Console

FileMaker Server

Web Publishing Engine

Web Publishing Core

Custom Web Publishing

Engine (CWPE)


Products.fp7

Customers.fp7

Overview of Web Publishing Engine software components

About the tools for developing XSLT stylesheets

FileMaker Server Advanced includes two independent application tools you can use to develop XSLT stylesheets:

1

FileMaker Site Assistant creates basic XSLT stylesheets as a starting point for use with Custom Web

Publishing with XSLT.

1

FileMaker CDML Converter converts existing CDML format files to XSLT stylesheets that are compatible with the Web Publishing Engine.


Overview of installing, configuring, and using the

Web Publishing Engine

Here is a summary of the steps for installing, configuring, and using the Web Publishing Engine:

1.

Do one of the following:

1

If you haven’t already done so, install FileMaker Server. See the FileMaker Server Administrator’s

Guide.

1

If you have already installed FileMaker Server, update the license key with a FileMaker Server

Advanced license key. See FileMaker Server Admin Help.

2.

3.

4.

5.

6.

7.

If you haven’t already done so, install a web server.

For more information, see the instructions for your web server.

Install the Web Publishing Engine.

For background installation information, see the next section, “Installing the Web Publishing Engine in various host configurations.” For details on installing the Web Publishing Engine in Windows, see

chapter 2, “Installing the Web Publishing Engine in Windows.” For details on installing the Web

Publishing Engine in Mac OS X, see chapter 3, “Installing the Web Publishing Engine in Mac OS X.”

Install the tools for developing XSLT stylesheets.

For information on installing the tools in Windows, see “Installing the FileMaker Site Assistant and

FileMaker CDML Converter” on page 26. For information on installing the tools in Mac OS X, see

“Installing the FileMaker Site Assistant and FileMaker CDML Converter” on page 29.

In FileMaker Server Admin, register the Web Publishing Engine in FileMaker Server.

To register the Web Publishing Engine, you specify the Web Publishing Engine identifier and optional passcode for securing the connection between FileMaker Server and the Web Publishing Engine. See

“Registering the Web Publishing Engine in FileMaker Server” on page 16.

In the Web Publishing Engine Administration Console, configure the Web Publishing Engine. See

chapter 4, “Configuring the Web Publishing Engine.”

In FileMaker Pro, enable Custom Web Publishing and Instant Web Publishing in each database you want to publish.

For information on enabling Custom Web Publishing in a database, see the FileMaker Server Advanced

Custom Web Publishing Guide. For information on enabling Instant Web Publishing in a database, see the FileMaker Instant Web Publishing Guide.


8.

Set up a web publishing solution for the database by doing any of the following:

1

Enable Instant Web Publishing for the database. See the FileMaker Instant Web Publishing Guide.

1

Create a custom web site or application to query the database for XML data via a query string in a URL.

See the FileMaker Server Advanced Custom Web Publishing Guide.

1

Create a custom web site or application to query the database via XSLT stylesheets. You can create

XSLT stylesheets by using the CDML Converter to convert existing CDML format files and then enhancing the converted stylesheets, or by creating new XSLT stylesheets. See the FileMaker Server

Advanced Custom Web Publishing Guide.

Installing the Web Publishing Engine in various host configurations

You can install the Web Publishing Engine and its associated software components in the following configurations of one, two, or three host computers. The operating systems of the various computers can be all Windows, all Mac OS X, or any combination of the two. Make sure the ports indicated in the following diagrams are available on each computer (not used by another process), and are not blocked by a firewall.

1

One computer configuration: You can install FileMaker Server, the Web Publishing Engine, and all of the associated software components on the same computer. This is the simplest configuration.

One computer configuration

Web Server







Engine (CWPE)


Ports 5003 and 16008 through 16018 must be available on this computer. Port 5003 must also be open if there is an internal software firewall on the computer.


1

Two computers configuration, variation A: You can install the Web Publishing Engine, web server, Web

Server Module, and Administration Console on one computer, and FileMaker Server on a second computer.

This configuration separates all of the web-publishing related components from FileMaker Server.

Two computers configuration, variation A

Computer 1 Computer 2

Web Server







Engine (CWPE)


Ports 16008 through 16018 must be available on computer 1.

Port 5003 must be open on the firewall.

Port 5003 must be available on computer 2.

1

Two computers configuration, variation B: You can install the web server, Web Server Module, and

Administration Console on one computer, and the Web Publishing Engine and FileMaker Server on a second computer. In this configuration, you can optionally locate the web server host computer on the outside of a firewall, and the Web Publishing Engine and FileMaker Server host computer can be located inside the firewall.

Two computers configuration, variation B


Web Server







Engine (CWPE)


Ports 16010 and 16018 must be available on computer 1.

Ports 16016 and 16018 must be open on the firewall.

Ports 5003 and 16008 through 16018 must be available on computer 2. Port 5003 must also be open if there is an internal software firewall on computer 2.


1

Three computers configuration: You can install the web server, Web Server Module, and Administration

Console on one computer, the Web Publishing Engine on a second computer, and FileMaker Server on a third computer. The web server, Web Server Module, and Administration Console are on a computer that serves as the request gateway, and you can optionally use a firewall to separate them from the components on the other two computers.

Computer 1

Three computers configuration


Web Server







Engine (CWPE)


Ports 16010 and 16018 must be available on computer 1.

Ports 16016 and

16018 must be open on this firewall.

Ports 16008 through 16018 must be available on computer 2.

Port 5003 must be open on this firewall.

Port 5003 must be available on computer 3.

Important To secure your solution, especially on the Internet, consider using a firewall on the public side of the preceding configurations. For more information on setting up security for web published solutions, see the FileMaker Security Guide.

About the protocols for the Web Publishing Engine

To communicate with FileMaker Server and your web server, the Web Publishing Engine uses the following protocols on the ports indicated. If you’re using a firewall, be sure to configure it to allow these particular protocols.

The FileMaker Proprietary Networking protocol on port 5003 is used between FileMaker Server and the Web

Publishing Engine. The AJP protocol is used between the web server and the Web Publishing Engine.

Protocol

FileMaker Proprietary Networking

Apache Jakarta Protocol (AJP) 1.3

Tomcat Control

FileMaker Internal

HTTP

TCP ports

5003

16016, 16018

16010

16008, 16012

16014

For information on other ports used by FileMaker Server, see the FileMaker Server Administrator’s Guide.


Using SSL and FileMaker Server encryption

Depending on your particular host computer configuration, you can use SSL and FileMaker Server encryption for security. You can use SSL between the web server host computer and web user’s browsers. You can also use FileMaker Server encryption between the FileMaker Server host computer and the Web Publishing

Engine host computer. For information on enabling FileMaker Server encryption, see FileMaker Server

Admin Help.

Registering the Web Publishing Engine in FileMaker Server

To enable web publishing in FileMaker Server, you must register the Web Publishing Engine in FileMaker

Server by using FileMaker Server Admin to specify an:

1

Identifier string that identifies the Web Publishing Engine to FileMaker Server.

1

Optional passcode to make sure that your FileMaker Server only connects to your particular Web

Publishing Engine. Passcodes prevent unauthorized users from using other Web Publishing Engines to access the databases hosted by your FileMaker Server.

For information on how to register the Web Publishing Engine in FileMaker Server, see FileMaker Server

Admin Help.

After registering the Web Publishing Engine in FileMaker Server, you must configure the Web Publishing

Engine with the same identifier and passcode. See “Configuring the connection between the Web Publishing

Engine and FileMaker Server” on page 36. To authenticate a connection for web publishing, FileMaker

Server compares the identifier and passcode specified in the Web Publishing Engine with the identifier and passcode specified in FileMaker Server. If the identifiers or passcodes don’t match, FileMaker Server denies the connection.

Here is an example of the information you would need to specify in a three-computer configuration:

Web server host computer

Web Publishing Engine host computer

FileMaker Server host computer (192.168.100.101)

Web Server







Engine (CWPE)

WPE_1

Passcode_1


The Web Publishing Engine is configured with 192.168.100.101 as the IP address of the FileMaker Server host, “WPE_1” as the Web Publishing Engine identifier, and

“Passcode_1” as the passcode.

The Web Publishing Engine is registered in FileMaker Server with

“WPE_1” as the Web Publishing

Engine identifier and “Passcode_1” as the passcode.


If your solution uses relationships between databases that are hosted on multiple FileMaker Servers, then you must register the Web Publishing Engine in each FileMaker Server.

For example, here is a solution in which a Products database hosted by FileMaker Server 1 uses data from a

Catalog database hosted by FileMaker Server 2. To enable the Web Publishing Engine to connect to both

FileMaker Servers, you must register the Web Publishing Engine in each FileMaker Server that specifies the same identifier and optional passcode that is configured in the Web Publishing Engine, such as WPE_1 and

Passcode_1. Although you can only specify the IP address of one FileMaker Server when you configure the

Web Publishing Engine, the connection to the other FileMaker Server occurs automatically.

FileMaker Server 1 host computer (192.168.100.101)

Web server host computer

Web Server



FileMaker Server 1

Web Publishing Engine host computer





Engine (CWPE)

The Web Publishing Engine is configured with 192.168.100.101 as the IP address of

FileMaker Server 1 host, “WPE_1” as the

Web Publishing Engine identifier, and

“Passcode_1” as the passcode.

FileMaker Server 2 is not configured in the Web Publishing Engine.

WPE_1

Passcode_1

Products.fp7

Customers.fp7

FileMaker Server 2 host computer (192.168.100.103)

FileMaker Server 2

Orders.fp7

Catalog.fp7

The Web Publishing Engine is registered in each FileMaker Server with “WPE_1” as the Web Publishing

Engine identifier and “Passcode_1” as the passcode.


Installing plug-ins for the Web Publishing Engine

If you want to use calculation plug-ins with the Web Publishing Engine, you must install the plug-ins in the following folder on the host where the Web Publishing Engine is installed. These folder locations are relative to the installation folder where the Web Publishing Engine is installed (not the root folder):

In Windows:

Web Publishing\publishing-engine\wpc\Plugins

In the Mac OS:

Library/FileMaker Server 7/Web Publishing/publishing-engine/wpc/Plugins

Note You must install the plug-ins for the Web Publishing Engine in addition to any plug-ins you may have installed for FileMaker Server or FileMaker Pro, even if they are the same plug-ins. For additional information about using plug-ins, see the FileMaker Server Administrator’s Guide.

Chapter 2

Installing the Web Publishing Engine in Windows

For late-breaking information about the Web Publishing Engine, browse the contents of the CD and view the

FMS Web Read Me (English).pdf file in the FileMaker Server 7 folder, or visit www.filemaker.com.

Overview of installation

During installation, you can choose to install the following Web Publishing Engine software components:

1

Web Publishing Engine component

1

Web Server Module and Administration Console components (always installed together as a unit on the web server)

You can install the Web Publishing Engine software components on one, two, or three host computer

configurations. See “Installing the Web Publishing Engine in various host configurations” on page 13.

To create the one computer configuration or the two computers configuration, variation A, you can use the

Complete Install option to install the Web Publishing Engine component and the Web Server Module and

Administration Console components on the same host computer.

In the two computers configuration, variation B, or in the three computers configuration, the Web Publishing

Engine component is on a different host computer than the Web Server Module and Administration Console components, which are on the web server host. To create either of these two configurations, you must run the installer on the appropriate host and use the Custom Install option to install the Web Publishing Engine component only. Then run the installer again on the web server host and use the Custom Install option to install the Web Server Module and Administration Console components only.

To install the FileMaker Site Assistant and FileMaker CDML Converter tools, you must use an independent

tools installer. See “Installing the FileMaker Site Assistant and FileMaker CDML Converter” on page 26.


Installing the Web Publishing Engine software components

Before you begin the installation process, review the following notes:

1

Exit other open programs and save your work.

1

Log on to the host computer using Administrator privileges.

1

If your computer is running virus protection software, turn it off prior to installation and then turn it back on afterwards.

To install the Web Publishing Engine software components:

1.

Insert the FileMaker Server 7 Advanced CD into the CD or DVD drive on the host computer where you want to install the Web Publishing Engine software components.

2.

The FileMaker Server Advanced CD window appears.

Click the Install icon.

Install icon

4.

5.

6.

3.

Choose a language and click OK.

The default language selection matches your operating system language. A Complete Install will install the Web Publishing Engine documentation (this FileMaker Server Advanced Web Publishing Installation

Guide and the FileMaker Server Advanced Custom Web Publishing Guide) in the language version you choose. You can install additional language versions of the documentation by choosing Custom Install, and then selecting other language packs from the list of supported languages.

When the InstallShield Wizard for the FileMaker Server Web Publishing Engine appears, click Next.

Read and accept the terms of the license agreement and click Next.

Enter your customer information and click Next.

Installing the Web Publishing Engine in Windows 21

7.

Specify the folder where you want to install the software components and click Next.

By default, the Web Publishing Engine is installed in this folder:

\Program Files\FileMaker\FileMaker Server 7\Web Publishing

The Setup Type screen appears.


8.


1

To install all of the software components on the current host computer (the Web Publishing Engine, the

Web Server Module, and the Administration Console), select Complete and click Next. Proceed to

step 11.

1

To install only some of the software components on the current host computer (either the Web

Publishing Engine, or the Web Server Module and Administration Console), select Custom and click

Next.

If you selected Custom, the Custom Setup screen appears.

9.

Select the items you want to install:

1

To install the Web Publishing Engine only, select Web Publishing Engine and deselect Web Server Module

and Administration Console. Click Next and proceed to step 11.

1 To install the Web Server Module and Administration Console only, select Web Server Module and

Administration Console and deselect Web Publishing Engine. The Web Server Module and Administration

Console are installed together as a unit. Click Next and proceed to step 10.

1

To install additional language versions of the Web Publishing Engine documentation, select the

appropriate language pack. Click Next and proceed to step 11.

10.

If you are installing the Web Server Module and Administration Console on a different host computer than the Web Publishing Engine, enter the IP address of the host computer where the Web Publishing

Engine is installed and click Next.

Otherwise, the installer does not request the IP address and you can skip this step.

11.

Specify whether you want the Web Publishing Engine services (Web Publishing Core service and Custom

Web Publishing Engine service), and/or the Administration Console service to start automatically or manually and click Next.

See the next section, “About the Web Publishing Engine services.”


12.

Click Install.

13.

When the installation is complete, click Finish.

14.

If you installed the Web Server Module and Administration Console, restart the IIS web server.

Note The Web Publishing Engine documentation is installed in the Electronic Documentation folder (inside the English Extras folder).

About the Web Publishing Engine services

If you install this software component

Web Publishing Engine

Administration Console

Web Publishing Engine and Administration

Console installed on same host

These services are also installed

FileMaker Publishing Engine (WPC)

FileMaker Publishing Engine (CWPE)

FileMaker Publishing Engine (CONFIG)

FileMaker Publishing Engine (WPC)

FileMaker Publishing Engine (CWPE & CONFIG)

For information on restarting the services, see “Using the Web Publishing Engine and Administration

Console services” on page 51.

Installing the Web Publishing Engine from the command line

To install the Web Publishing Engine from the command line:

1.


2.

Open a command window and type: msiexec /i <path>\FileMaker Server 7 Web Publishing Engine.msi /qn+ /Lr <log file>.txt

where:

1

<path> is the drive for your CD or DVD drive and this folder path:

\FileMaker Web Publishing Engine

Note If you have copied the FileMaker Server 7 Web Publishing Engine.msi to your hard disk, replace the preceding path with the path to the file’s location on your hard disk.

1

<log file> .txt specifies the path and name of the text log file, such as C:\logfile.txt. You can view the log file with WordPad or a word processing program.

3.

For more information on using msiexec, see Windows help.

Follow the on-screen instructions.


Setting up authentication for a Windows IIS web site

FileMaker Server handles the authentication for password-protected databases. You can choose whether you want to also use IIS web site authentication in addition to FileMaker Server authentication.

You must decide whether you want to use IIS web site authentication and take the appropriate steps before using the Administration Console for the first time to configure the Web Publishing Engine.

You can choose from the following scenarios:

1

Disable IIS authentication. You can disable all IIS authentication methods and use anonymous access to

the IIS site. This is the simplest configuration. See the next section, “Disabling IIS authentication.”

1

Leave IIS authentication enabled and also enable Basic Authentication. You can leave the current IIS authentication methods enabled for use with other web sites, and use Basic Authentication for the Web

Publishing Engine. You must also set up Windows user accounts that exactly match the user accounts for

the Web Publishing Engine and web-published FileMaker databases. See “Enabling IIS authentication” on page 25.

For information on IIS, see the IIS online documentation by entering http://localhost/iisHelp in your web browser.

Disabling IIS authentication

If you disable all IIS authentication methods and use anonymous access to the IIS site, then you don’t need to add any Windows user accounts.

To disable IIS authentication:

1.

In Internet Information Services, select the web site and choose Action menu > Properties.

2.

3.

In the Directory Security properties sheet, click Edit for authentication methods.

In the Authentications Methods dialog box, do the following:

1

Select Anonymous access.

1

Disable all of the authentication methods under Authenticated access.

4.

5.

Click OK to close the Authentications Methods dialog box.

Click OK to close the Directory Security properties sheet.


Enabling IIS authentication

If you enable any of the IIS authentication methods for the IIS web server, you must enable Basic

Authentication for web sites that connect to the Web Publishing Engine. Note that the Web Publishing Engine only uses Basic Authentication and none of the other IIS authentication methods. Other web sites on the web server can use the other IIS authentication methods.

In this scenario, you must also create Windows user accounts on the web server host computer that contain user names and passwords that exactly match the user names and passwords for the following accounts:

1

Web Publishing Engine user name and password, which you create by using the Administration Console.

See “Configuring the Web Publishing Engine for the first time” on page 32.

1 all password-protected accounts defined in all web-published FileMaker databases.

To enable IIS authentication:

1.

In Internet Information Services, select the web site and choose Action menu > Properties.

2.

3.

In the Directory Security properties sheet, click Edit for authentication methods.

In the Authentications Methods dialog box, do the following:

1

Enable Anonymous access.

1

Enable Basic Authentication along with any of the other authentication methods under Authenticated access.

4.

5.

Click OK to close the Authentications Methods dialog box.

Click OK to close the Directory Security properties sheet.

Uninstalling, modifying, or repairing the Web Publishing Engine

You can use the Windows Add or Remove Programs control panel to uninstall the Web Publishing Engine components, replace missing or corrupt files, or to change which features are installed. Before uninstalling,

be sure to stop the Web Publishing Engine services. See “Starting, restarting, or stopping the services in

Windows” on page 52.

Note If you’re running Windows 2000 Server and you uninstall a feature that contains a Web Publishing

Engine service, the installer will prompt you to restart your computer.


Installing the FileMaker Site Assistant and FileMaker CDML Converter

You can install the FileMaker Site Assistant on any computer that has network access to the Web Publishing

Engine, or you can install it on the same computer as the Web Publishing Engine. The Site Assistant needs access to the Web Publishing Engine to operate.

You can install the FileMaker CDML Converter, which does not need access to the Web Publishing Engine, on any computer.

To install the FileMaker Site Assistant and FileMaker CDML Converter tools:

1.

Insert the FileMaker Server 7 Advanced CD into the CD or DVD drive on the host computer where you want to install the tools.

2.

The FileMaker Server Advanced CD window appears.

Click the Browse icon.

3.

4.

Locate and double-click the Setup.exe file in the FileMaker Web Publishing Tools folder.

Follow the on-screen instructions to install either or both tools.

To install the FileMaker Site Assistant and FileMaker CDML Converter tools from the command line:

1.

Insert the FileMaker Server 7 Advanced CD into the CD or DVD drive on the host computer where you want to install the tools.

2.

Open a command window and type: msiexec /i <path>\FileMaker Server 7 Web Publishing Tools.msi /qn+ /Lr <log file>.txt

where:

1

<path> is the drive for your CD or DVD drive and this folder path:

\FileMaker Web Publishing Tools

Note If you have copied the FileMaker Server 7 Web Publishing Engine.msi to your hard disk, replace the preceding path with the path to the file’s location on your hard disk.

1

<log file> .txt specifies the path and name of the text log file, such as C:\logfile.txt. You can view the log file with WordPad or a word processing program.

3.

For more information on using msiexec, see Windows help.

Follow the on-screen instructions.

Where to go from here

After you install the Web Publishing Engine, you must use the Administration Console to configure the Web

Publishing Engine. For more information, see chapter 4, “Configuring the Web Publishing Engine.”

Chapter 3

Installing the Web Publishing Engine in

Mac OS X

For late-breaking information about the Web Publishing Engine, browse the contents of the CD and view the

FMS Web Read Me (English).pdf file in the FileMaker Server 7 folder, or visit www.filemaker.com.

Overview of installation

During installation, you can choose to install the following Web Publishing Engine software components:

1

Web Publishing Engine component

1

Web Server Module and Administration Console components (always installed together as a unit on the web server)

You can install the Web Publishing Engine software components on one, two, or three host computer

configurations. See “Installing the Web Publishing Engine in various host configurations” on page 13.

To create the one computer configuration or the two computers configuration, variation A, you can use the

Easy Install option to install the Web Publishing Engine component and the Web Server Module and

Administration Console components on the same host computer.

In the two computers configuration, variation B, or in the three computers configuration, the Web Publishing

Engine component is on a different host computer than the Web Server Module and Administration Console components, which are on the web server host. To create either of these two configurations, you must run the installer on the appropriate host and use the Custom Install option to install the Web Publishing Engine component only. Then run the installer again on the web server host and use the Custom Install option to install the Web Server Module and Administration Console components only.

To install the FileMaker Site Assistant and FileMaker CDML Converter tools, you must use an independent

tools installer. See “Installing the FileMaker Site Assistant and FileMaker CDML Converter” on page 29.


Installing the Web Publishing Engine software components

Before you begin the installation process, review the following notes:

1

If you are using Mac OS X Server 10.2.8, make sure Java 2 Platform, Standard Edition (J2SE) 1.4.1

Update 1 is installed on the host computer. If it isn’t, use Software Update to install J2SE 1.4.1 before beginning the installation process.

1

Log on to the host computer using Administrator privileges.

1

If your computer is running virus protection software, turn it off prior to installation and then turn it back on afterwards.

To install the Web Publishing Engine software components:

1.


The disc’s window appears on your screen. If you see only the disc icon, double-click the CD icon to open its window.

2.

3.

4.

5.

Double-click the FileMaker Web Publishing Engine installer.

If the installer requests authentication, enter a user name and password for an administrator account.

Read and accept the terms of the license agreement and click Accept.

The Easy Install dialog box appears.


1

To install all of the software components on the current host computer (the Web Publishing Engine, the

Web Server Module, and the Administration Console), choose Easy Install and proceed to step 8.

1

To install only some of the software components on the current host computer (either the Web

Publishing Engine, or the Web Server Module and Administration Console), choose Custom Install and

proceed to step 6.

6.

If you chose Custom, select the software components you want to install on the current host computer:

1

To install the Web Publishing Engine only, select Web Publishing Engine.

1

To install the Web Server Module and Administration Console only, select Web Server Module and

Administration Console. The Web Server Module and Administration Console are installed together as a unit.

1

To install additional language versions of the Web Publishing Engine documentation, select the appropriate language pack.

7.

If you are installing the Web Server Module and Administration Console on a different host computer than the Web Publishing Engine, enter the IP address of the host computer where the Web Publishing

Engine is installed. Otherwise, the installer does not request the IP address and you can skip this step.

Installing the Web Publishing Engine in Mac OS X 29

8.

9.

Click Install.

When installation completes, do one of the following:

1

Click Restart to leave the Installer and restart your computer.

1

If you want to install other software components before using the computer, you can either click

Continue to install the other components, or you can click Quit to quit the installer.

Note You must restart your computer before you can start using the Web Publishing Engine or

Administration Console.

Note The installer creates a group named fmsadmin and an account named fmweb to run the Web Publishing

Engine in.

Where files are stored on your hard disk

The Web Publishing Engine installer copies files to several folders on your hard disk, depending on the installation options you choose. When installation is complete, you can view the Web Publishing Engine

Installer Log File, which lists the location of each installed file, in the FileMaker Server 7 folder inside the

Library folder. You can view the log file with TextEdit or a word processing program. If the log file already exists from a previous installation, the new information is appended at the end of the file.

Uninstalling, modifying, or repairing the Web Publishing Engine

You can use the FileMaker Web Publishing Engine installer to uninstall the Web Publishing Engine software

components. Before uninstalling, be sure to stop the Web Publishing Engine services. See “Starting, restarting, stopping, or disabling the services in Mac OS X” on page 52.

Installing the FileMaker Site Assistant and FileMaker CDML Converter

You can install the FileMaker Site Assistant on any computer that has network access to the Web Publishing

Engine, or it can be installed on the same computer as the Web Publishing Engine. The Site Assistant needs access to the Web Publishing Engine to operate.

You can install the FileMaker CDML Converter, which does not need access to the Web Publishing Engine, on any computer.


To install the FileMaker Site Assistant and FileMaker CDML Converter tools:

1.

Insert the FileMaker Server 7 Advanced CD into the CD or DVD drive on the computer where you want to install the tools.

The disc’s window appears on your screen. If you see only the disc icon, double-click the CD icon to open its window.

2.

3.

Double-click the FileMaker Web Publishing Tools installer.

Follow the on-screen instructions to install either or both tools.

When installation is complete, you can view the Installer Log File in the FileMaker Server 7 folder, which is inside the Library folder.


After you install the Web Publishing Engine, you must use the Administration Console to configure the Web

Publishing Engine. For more information, see chapter 4, “Configuring the Web Publishing Engine.”

Chapter 4

Configuring the Web Publishing Engine

After installing the Web Publishing Engine software components, use the Administration Console to configure the Web Publishing Engine.

About the Web Publishing Engine Administration Console

The Administration Console software is installed with the Web Server Module software on the web server host computer. You use the Administration Console in a web browser to configure the Web Publishing

Engine via the connection through the web server. You can use the Administration Console on any computer that has access to the web server.

General steps for configuring the Web Publishing Engine

Here is a summary of the steps for using the Administration Console to configure the Web Publishing Engine.

1.

Specify the following required configuration settings:

1 user name and password for the Administration Console

1

IP address of the host computer where the Web Publishing Engine is installed

1 user name and password for the Web Publishing Engine

1

IP address of the host computer where FileMaker Server is installed

1

Web Publishing Engine identifier and optional passcode that match the identifier and passcode you registered in FileMaker Server for the Web Publishing Engine

For more information, see the next section, “Configuring the Web Publishing Engine for the first time.”

2.

As necessary, disable the individual web publishing technologies that you want to block on the Web

Publishing Engine. By default, all of the following web publishing technologies are enabled:

1

Instant Web Publishing: See “Disabling Instant Web Publishing” on page 40.

1

Custom Web Publishing with XML: See “Disabling Custom Web Publishing with XML” on page 41.

1

Custom Web Publishing with XSLT: See “Disabling Custom Web Publishing with XSLT” on page 45.


3.

As necessary, set the following options for Custom Web Publishing with XSLT:

1

Web Publishing Engine mode of operation: See “Setting the Web Publishing Engine mode” on page 41.

1

server-side stylesheet caching: See “Setting server-side XSLT stylesheet caching” on page 43.

1

database sessions: See “Configuring the interaction between web sessions and database sessions” on page 43.

1

SMTP email server settings: See “Configuring access to a mail server for the Web Publishing Engine” on page 44.

1

default text encoding settings: See “Setting the default text encoding for XSLT requests” on page 45.

4.

As necessary, set the following general settings for the Web Publishing Engine:

1

log file settings: See “Specifying logging options for the Web Publishing Engine” on page 46.

1

session time-out settings: See “Setting the session time-out for the Web Publishing Engine” on page 47.

5.

As necessary, restrict access to the Administration Console from particular IP addresses. See “Restricting access to the Administration Console” on page 49.

Configuring the Web Publishing Engine for the first time

The first time you use the Administration Console to configure the Web Publishing Engine, you must specify two sets of user names and passwords:

1 a user name and password for the Administration Console, which are used to authenticate web users who attempt to use the Administration Console. This user name and password prevent unauthorized users from using the Administration Console to take over control of your Web Publishing Engine.

1 a user name and password for the Web Publishing Engine, which are used to authenticate the

Administration Console software component when it accesses the Web Publishing Engine. This user name and password prevent unauthorized users from installing another copy of the Administration Console and taking over control of your Web Publishing Engine.

Note The system language of the host computer where you run the Administration Console for the first time sets the default status area language for Instant Web Publishing and the default text encoding for Custom Web

Publishing with XSLT on the Web Publishing Engine. You can change these default settings for the Web

Publishing Engine by using the Administration Console.

Configuring the Web Publishing Engine 33

To configure the Web Publishing Engine for the first time:

1.

Start the Administration Console by entering the following URL in a web browser on any computer that has access to the web server:

<scheme>://<host>[:<port>]/fmi/config where:

1

<scheme> can be the HTTP or HTTPS protocol.

1

<host> is the IP address or domain name of the host where the web server is installed.

1

<port> is optional and specifies the port that the web server is using. If no port is specified, then the default port for the protocol is used (port 80 for HTTP, or port 443 for HTTPS).

For example: http://192.168.100.110/fmi/config http://localhost/fmi/config http://webserver123.company.com/fmi/config

The initial setup page of the Administration Console appears. This page only appears the first time you use the Administration Console.


2.

3.

4.

5.

Enter a user name and password for authenticating a web user who attempts to use the Administration

Console.

Whenever you use the Administration Console, you must enter this user name and password.

Click Apply.

The Publishing Engine Configuration: Set Publishing Engine Address page appears.

Enter the IP address of the host computer where the Web Publishing Engine is installed.

If the Web Publishing Engine is installed on the same host as the web server and Administration Console, you can enter localhost as the address.

Click Continue.

The Publishing Engine Configuration: Set Publishing Engine Authentication page appears.

Note This page only appears the first time you use a newly installed Administration Console or you are configuring a newly installed Web Publishing Engine. If you are using a newly installed Administration

Console to configure an already installed Web Publishing Engine, this page is not displayed. Instead, you will see a page where you can enter a user name and password for the existing Web Publishing Engine.


6.

7.

Enter a user name and password for authenticating the Administration Console when it accesses the Web

Publishing Engine.

After this initial configuration of the Web Publishing Engine user name and password, you don’t have to enter this user name and password again when using the existing Administration Console. But, if you uninstall the Administration Console and then reinstall it, you must enter this Web Publishing Engine user name and password again during the initial configuration of the Administration Console.

Click Apply.

The Overview page of the Administration Console appears, which shows where the Web Publishing

Engine components are installed and their current status. The following example shows a one computer configuration. If you are using a two or three computer configuration, the Overview page shows two or three boxes to represent the number of computers and their IP addresses.

Click these links to display other pages in the

Administration Console

This box indicates all components are installed on one host that has the

IP address shown here.

The passcode authentication failed because you haven’t set it up yet. See the next section.


Configuring the connection between the Web Publishing Engine and FileMaker Server

After logging into the Administration Console for the first time, the next step is to specify the following information for the connection between the Web Publishing Engine and FileMaker Server:

1

IP address of the FileMaker Server host

1

Web Publishing Engine identifier and optional passcode that match the identifier and passcode you registered in FileMaker Server for the Web Publishing Engine

For information on the Web Publishing Engine identifier and passcode, see “Registering the Web Publishing

Engine in FileMaker Server” on page 16.

To configure the connection between the Web Publishing Engine and FileMaker Server:

1.

In the Overview page of the Administration Console, click the FileMaker Server link at the top of the page.

The FileMaker Server Configuration:Server Address page appears.


2.

3.

4.

Enter the IP address of the host computer where FileMaker Server is installed.

If FileMaker Server is installed on the same host as the web server and Administration Console, you can enter localhost as the address.

Enter an identifier for the Web Publishing Engine.

The identifier is a unique string that the Web Publishing Engine uses to identify itself when it connects to FileMaker Server. You must register the identical identifier string in FileMaker Server for the Web

Publishing Engine.

If you registered a passcode in FileMaker Server for the Web Publishing Engine, enter the same passcode in the FileMaker Server Configuration:Server Address page.

Note If you want to revert back to the previously saved settings, click Revert.

5.

If you are finished making configuration changes in the Administration Console, click Commit to save the settings. You can also wait before clicking Commit if you want to make other changes before saving all settings.

Note After changing a setting, you must click Commit to save the setting. After you click Commit, you cannot use Revert to revert back to the settings that existed before you clicked Commit.

6.

If you want the new committed settings to take effect immediately, click Restart Publishing Engine.

After committing a setting, you must click Restart Publishing Engine to have the Web Publishing Engine start using the new settings immediately. You can also wait until you are finished changing settings in all pages of the Administration Console, and then click Restart Publishing Engine to start using the new settings.

Important For more information on situations when you must restart the Web Publishing Engine, the

Administration Console, and the web server after you change settings, see “Using the Web Publishing

Engine and Administration Console services” on page 51.


Viewing an overview of the Web Publishing Engine configuration

To verify the Web Publishing Engine configuration, you can view an overview of the components by clicking the Overview link at the top of the Administration Console. If you specified the IP address, Web Publishing

Engine identifier, and passcode correctly and the Web Publishing Engine connected successfully with

FileMaker Server, the Overview page shows the addresses of all of the components.

Here is an example of an Overview page for a one computer configuration where all of the components are installed on one host with the address 192.168.123.101. Your Overview page will appear slightly different if you are using a two or three computer configuration.

This link indicates the

Web Publishing Engine is connected to

FileMaker Server.

Click this link to display the current number of sessions. The timestamp indicates when the session statistics were last updated.

You set the limit to the number of sessions in

FileMaker Server Admin.


Configuring Instant Web Publishing

You can set the language of the status area of the Instant Web Publishing page, and test the Instant Web

Publishing page with the currently published databases.

To configure Instant Web Publishing:

1.

Do either of the following:

1

Click the Publishing Engine link at the top of the Administration Console page, and click the Instant Web

Publishing link.

1

In the Overview page, click the Instant Web Publishing link in the center of the page under the Publishing

Engine heading.

The Publishing Engine Configuration: Instant Web Publishing page appears.

2.

3.

To set the language for the labels displayed in the status area of the Instant Web Publishing page, choose a language from the Status Area Language menu.

The status area language setting does not change the language of data stored in databases.

If you are finished making configuration changes in the Administration Console, click Commit to save the settings.


4.

5.


To test the Instant Web Publishing page with the currently hosted databases on FileMaker Server, click the link shown next to URL.

Disabling Instant Web Publishing

By default, Instant Web Publishing is enabled in the Web Publishing Engine. If necessary, you can disable it.

To disable Instant Web Publishing:

1.

In the Publishing Engine Configuration: Instant Web Publishing page, select Off.

If this label appears in red, you must restart the Administration

Console and the web server to have the new settings take effect

2.

3.


Restart the Administration Console and the web server. See “Using the Web Publishing Engine and

Administration Console services” on page 51.


Disabling Custom Web Publishing with XML

By default, Custom Web Publishing with XML is enabled in the Web Publishing Engine. If necessary, you can disable it.

To disable Custom Web Publishing with XML:

1.


1

Click the Publishing Engine link at the top of the Administration Console page, and click the XML

Publishing link.

1

In the Overview page, click the XML Publishing link in the center of the page under the Publishing Engine heading.

2.

3.

4.

In the Publishing Engine Configuration: Custom Web Publishing with XML page, select Off.




Configuring Custom Web Publishing with XSLT

For Custom Web Publishing with XSLT, you can set the Web Publishing Engine in development or production mode, and configure server-side stylesheet caching, a SMTP email server, and default text encoding.

Setting the Web Publishing Engine mode

You can use the Web Publishing Engine in either of these modes:

1

Development mode: Use Development mode when you are developing and testing XSLT stylesheets. In this mode, the Web Publishing Engine generates a web page with a specific error code number when an error occurs in the Web Publishing Engine itself. You cannot enable server-side stylesheet caching in

Development mode.

1

Production mode: Use Production mode when you are ready to use the Web Publishing Engine to host

XSLT stylesheets. In this mode, the Web Publishing Engine displays a general text message defined in the pe_server_error.html error page when an error occurs in the Web Publishing Engine.

For more information on error reporting for the Web Publishing Engine, see the FileMaker Server Advanced

Custom Web Publishing Guide.


To set the Web Publishing Engine mode:

1.


1

Click the Publishing Engine link at the top of the Administration Console page, and click the XSLT

Publishing link.

1

In the Overview page, click the XSLT Publishing link in the center of the page under the Publishing Engine heading.

The Publishing Engine Configuration: Custom Web Publishing with XSLT page appears.

2.

3.

4.

Select Development mode or Production mode on the Custom Web Publishing with XSLT page.




Setting server-side XSLT stylesheet caching

Server-side caching stores frequently used XSLT stylesheets in memory, which increases Web Publishing

Engine performance. The Web Publishing Engine uses caching only when it is in Production mode.

To set server-side XSLT stylesheet caching:

1.

In the Publishing Engine Configuration: Custom Web Publishing with XSLT page, select Production mode.

2.

3.

For stylesheet caching, select Enabled.

Choose a size from the cache size menu:

1

Small: for solutions using less than 25 XSLT stylesheets

1 Medium: for solutions using between 25 and 100 XSLT stylesheets

1

Large: for solutions using more than 100 XSLT stylesheets

4.

5.



Configuring the interaction between web sessions and database sessions

Sessions allow you to store data or maintain states between requests. Custom Web Publishing with XSLT supports two types of sessions:

1 database sessions: FileMaker Server creates a database session whenever it retrieves data for a request. The maximum number of concurrent database sessions is determined by your FileMaker Server license.

1 web sessions: The Web Publishing Engine creates a web session whenever you use the fmxslt:create_session() extension function in an XSLT stylesheet. For information on the fmxslt:create_session() extension function, see the FileMaker Server Advanced Custom Web Publishing

Guide. The maximum number of web sessions is limited only by the amount of memory on the Web

Publishing Engine host computer.

In the Administration Console, you can use the Database Sessions option to configure the interaction between these two types of sessions. If you enable this option, the Web Publishing Engine uses a database session for each web session. Otherwise, the Web Publishing Engine does not use database sessions. This option is disabled by default.

There are trade-offs to enabling and disabling the Database Sessions option.

If you enable the Database Sessions option:

1

Global variable values are stored between requests.

1

If a script modifies a state, that state is maintained between requests. For example, privileges that are modified by the Relogin script step to switch accounts will persist between requests.

1

The number of web sessions is limited to the maximum number of concurrent database sessions on

FileMaker Server.


If you disable the Database Sessions option:

1

Global variable values are not stored between requests.

1

If a script modifies a state, that state is not maintained between requests.

1

The number of web sessions is not limited to the maximum number of database sessions on FileMaker

Server, which allows greater scalability to the Web Publishing Engine.

If your stylesheets do not use global variables or scripts that require a state to be maintained between requests, you should disable the Database Sessions option. The setting for the Database Sessions option applies to all stylesheets deployed on the Web Publishing Engine.

To configure the interaction between web sessions and database sessions:

1.

For Database Sessions in the Publishing Engine Configuration: Custom Web Publishing with XSLT page, select

Enabled or Disabled.

2.

3.



Configuring access to a mail server for the Web Publishing Engine

You can have the Web Publishing Engine send email messages by using one of the fmxslt:send_email () extension functions in an XSLT stylesheet. To use these email extension functions, you must configure access to a mail server for the Web Publishing Engine.

To configure access to a SMTP mail server for the Web Publishing Engine:

1.

For host in the SMTP section of the Custom Web Publishing with XSLT page, enter the name of the host computer where the SMTP mail server is installed.

2.

For port, enter the port to use.

The default is 25.

3.

From the authentication menu, choose a type of SMTP authentication that is compatible with your SMTP mail server:

1

None: authentication is not used. This is the default setting.

1 Plain Text: plain text authentication is used.

1

CRAM-MD5: Challenge-Response Authentication Mechanism-Message Digest 5 authentication is used to encrypt the password for the SMTP mail server.

4.

5.

6.

For user and password, enter the user name and password for logging into the SMTP mail server.




Setting the default text encoding for XSLT requests

When the Web Publishing Engine is first installed, the initial default text encoding for XSLT requests is

UTF-8. For email messages, the default is ISO-8859-1. If necessary, you can change these default text encoding settings.

You can also override the default setting for individual requests by setting the charset attribute in the

Content-Type request header, or by specifying an encoding with the –encoding query parameter. You can override the text encoding for email messages by using the fmxslt:send_email(String smtpFields, String body,

String encoding) extension function. See the FileMaker Server Advanced Custom Web Publishing Guide.

To set the default text encoding for XSLT requests:

1.

In the Default Text Encoding section of the Custom Web Publishing with XSLT page, choose a default text encoding from the requests and output pages menu.

Encoding

US-ASCII

ISO-8859-1

ISO-8859-15

ISO-2022-JP

Shift_JIS

UTF-8

Description

The basic ASCII character set that is typically used for plain text English email.

The Latin 1 character set that is typically used for roman character based web pages and email messages requiring upper ASCII characters.

The Latin 9 character set, which is almost the same as the Latin 1 character set with the addition of the Euro

€

symbol.

The ISO Japanese encoding that is typically used for Japanese email messages.

The Japanese encoding that is typically used for Japanese web pages.

The eight-bit encoding of Unicode. Using UTF-8 for email messages and web pages is growing in popularity as major browsers and mail clients have added support. Because UTF-8 supports the full range of Unicode characters, it can handle pages for any language.

2.

3.

4.

Choose a default text encoding from the email messages menu.



Disabling Custom Web Publishing with XSLT

By default, Custom Web Publishing with XSLT is enabled in the Web Publishing Engine. If necessary, you can disable it.


To disable Custom Web Publishing with XSLT:

1.

In the Publishing Engine Configuration: Custom Web Publishing with XSLT page, select Off.

2.

3.




Specifying general settings for the Web Publishing Engine

You can specify logging and session time-out settings for the Web Publishing Engine.

Specifying logging options for the Web Publishing Engine

With the exception of user logging, the logging options apply to both Instant Web Publishing and Custom

Web Publishing. User logging applies only to Custom Web Publishing.

To change the logging options for the Web Publishing Engine:

1.

Click the Publishing Engine link at the top of the Administration Console page.

The Publishing Engine Configuration: General Settings page appears.


2.

3.

4.

For the following logging options, select Enabled or Disabled:

1

Access Logging: enables the Web Publishing Core internal access logs, which are called wpc_access_log.txt and pe_internal_access_log.txt.

1

Error Logging, Script Logging, and User Logging: enables the Web Publishing Engine application log, which is called pe_application_log.txt.

For more information on the log files, see the FileMaker Server Advanced Custom Web Publishing Guide.



Setting the session time-out for the Web Publishing Engine

Instant Web Publishing solutions automatically use sessions and you cannot disable them. The value for

Session Timeout on the Publishing Engine Configuration: General Settings page sets the session time-out for Instant

Web Publishing, which is 15 minutes by default. If necessary, you can change the Session Timeout value.

Sessions are optional in Custom Web Publishing with XSLT and you create them by using the fmxslt:create_session() extension function. The Session Timeout value sets the default session time-out for

Custom Web Publishing with XSLT, and you can override the default by using the fmxslt:invalidate_session() and fmxslt:set_session_timeout() extension functions. See the FileMaker Server Advanced Custom Web

Publishing Guide.

The Session Timeout value does not apply to Custom Web Publishing with XML.

To change the session time-out for the Web Publishing Engine:

1.

For Session Timeout on the Publishing Engine Configuration: General Settings page, enter the number of minutes.

2.

3.

You can specify up to 60 minutes.




Changing the IP address of the Web Publishing Engine host

To change the IP address of the Web Publishing Engine host.

1.

On the Publishing Engine Configuration: General Settings page, click the change address link.

2.

Enter the IP address of the host computer where the Web Publishing Engine is installed, and click

Continue.

3.

4.

5.

6.

If the Web Publishing Engine is installed on the same host as the web server and Administration Console, you can enter localhost as the address.

Click Apply.



Log into the Administration Console.

Enter the user name and password for the Web Publishing Engine.

Changing the user name and password for the Web Publishing Engine

You can change the user name and password for authenticating the Administration Console when it accesses the Web Publishing Engine.

To change the user name for the Web Publishing Engine:

1.

On the Publishing Engine Configuration: General Settings page, click the change user name link.

2.

3.

Enter a new user name for the Web Publishing Engine.

Enter the current password for the Web Publishing Engine and click Apply.

4.

Click Apply.

To change the password for the Web Publishing Engine:

1.

On the Publishing Engine Configuration: General Settings page, click the change password link.

2.

3.

For Old Password, enter the current password for the Web Publishing Engine.

For New Password, enter a new password.

4.

5.

For Confirm Password, enter the same new password and click Apply.

Click Apply.


Restricting access to the Administration Console

You can prevent unauthorized access to the Administration Console by restricting access to hosts that have the IP addresses you specify. If you restrict access to one or more IP addresses, web users on unauthorized hosts cannot use the Administration Console to change configuration settings for the Web Publishing Engine.

If you do not restrict access, all hosts can access the Administration Console.

To restrict access to the Administration Console:

1.


1

Click the Administration link at the top of the Administration Console page.

1

In the Overview page, click the Administration Console Server link in the center of the page under the Web

Server heading.

The Administration Console Configuration: General Settings page appears.

2.

3.

For Administration Console Access Control, select Enabled.

For Administration Console Server access restricted to these IP addresses, enter the IP addresses of the host computers you want to allow access to the Administration Console. Use a comma to separate the IP addresses.

For example:


4.

5.




Viewing a list of the published databases for FileMaker Server

You can view a list of the currently published databases on FileMaker Server, and the types of publishing enabled in each database.

To view a list of published databases:

1.


1

Click the FileMaker Server link at the top of the Administration Console page.

1

In the Overview page, click the FileMaker Server link in the center of the page under the Databases heading.

2.

Click the Published Databases link.

The FileMaker Server Configuration: Published Databases page appears.


Here is a summary of the symbols used in the list of published databases:

This symbol Indicates

+ The extended privilege for the web publishing technology is enabled in the database.

-

(+)

The extended privilege for the web publishing technology is not enabled in the database.

The extended privilege for Instant Web Publishing is enabled in the database, and the Don’t Display in

Instant Web Publishing homepage option is enabled in the database.

Notes

1

If you open a database hosted on FileMaker Server that has the extended privileges for web publishing enabled, the Web Publishing Engine automatically publishes it.

1

If the Web Publishing Engine stops and restarts, it automatically publishes any hosted databases that have the extended privileges for web publishing enabled.

1

If FileMaker Server stops and restarts, the Web Publishing Engine automatically reconnects with

FileMaker Server and publishes any hosted databases that have the extended privileges for web publishing enabled.

Logging out of the Administration Console

Only one user can be logged into the Administration Console at any one time. If you don’t log out, the

Administration Console times out after 15 minutes and any uncommitted changes are not saved.

To log out of the Administration Console, click Logout.

Note To log into the Administration Console after completing the initial configuration, start the console and enter the user name and password you specified for the Administration Console. The Overview page appears first.

Using the Web Publishing Engine and Administration Console services

The Web Publishing Engine and the Administration Console run as services on the host computer where they are installed.

In Windows, the Web Publishing Engine and the Administration Console services start automatically if you

selected the Automatic option in the installer (see step 11 in “Installing the Web Publishing Engine software components” on page 22). Otherwise, you must start the services manually in Windows by following the

steps in this section.

In Mac OS X, the Web Publishing Engine and the Administration Console services start automatically whenever the host computer starts.


Whenever you commit a change to a setting in the Administration Console, you must restart the Web

Publishing Engine to have the new setting take effect. You can restart the Web Publishing Engine according to the instructions in this section, or by clicking Restart Publishing Engine at the bottom of the Administration

Console.

If the red indicator Console and Web Servers Require Restart appears at the bottom of the Administration

Console, you must restart the Administration Console and web server. To restart the Administration Console, use the instructions in this section. For information on restarting your web server, see the web server documentation.

Starting, restarting, or stopping the services in Windows

To start, restart, or stop the Web Publishing Engine and Administration Console services (Windows):

1.

Log out of the Administration Console.

2.

3.

Open the Services administrative tool.

Do any of the following:

1

To start, restart, or stop the Web Publishing Core component of the Web Publishing Engine, select the

FileMaker Publishing Engine (WPC) service and click Start, Restart, or Stop.

1

To start, restart, or stop the Administration Console, select the FileMaker Publishing Engine (CONFIG) service and click Start, Restart, or Stop.

1

To start, restart, or stop the Custom Web Publishing Engine, select the FileMaker Publishing Engine

(CWPE) service and click Start, Restart, or Stop.

Note If you installed the Administration Console and the Web Publishing Engine on the same host computer, the two services are combined into the FileMaker Publishing Engine (CWPE & CONFIG) service.

Starting, restarting, stopping, or disabling the services in Mac OS X

To start, restart, or stop the Web Publishing Engine and Administration Console services (Mac OS X):

1.


2.

3.

Run the Terminal application.

On the Mac OS X command line, enter one of the following commands:

1

To start the Web Publishing Engine and Administration Console, enter: sudo SystemStarter start "FileMaker Web Publishing"

1

To restart the Web Publishing Engine and Administration Console, enter: sudo SystemStarter restart "FileMaker Web Publishing"

Note The preceding command restarts all services for the Web Publishing Engine and Administration

Console. If you only need to restart the Web Publishing Engine, you can click Restart Publishing Engine at the bottom of the Administration Console.

1

To stop the Web Publishing Engine and Administration Console, enter: sudo SystemStarter stop "FileMaker Web Publishing"


To disable the Web Publishing Engine and Administration Console (Mac OS X):

1.


2.

Drag the FileMakerPublishingEngine folder out of the StartupItems folder in the Library folder.

The next time you restart the host computer, the Web Publishing Engine and Administration Console will not start automatically.

Changing the user name and password for the Administration Console

If necessary, you can change the user name and password that you enter when you log into the Administration

Console.

To change the user name for the Administration Console:

1.


1

Click the Administration link at the top of the Administration Console page.

1

In the Overview page, click the Administration Console Server link in the center of the page under the Web

Server heading.

2.

3.

4.

On the Administration Console Configuration: General Settings page, click the Change Administration User link.

Enter a new administrator user name for the Administration Console.

Enter the current password, and click Apply.

To change the password for the Administration Console:

1.

On the Administration Console Configuration: General Settings page, click the Change Administration Password link.

2.

3.

Enter the current password for the Administration Console.

Enter a new password and click Apply.


After you finish configuring the Web Publishing Engine, you’re ready to use it for server-side Instant Web

Publishing or Custom Web Publishing. For information on how to use Instant Web Publishing, see the

FileMaker Instant Web Publishing Guide. For information on how to convert CDML solutions to FileMaker

XSLT and develop FileMaker XSLT stylesheets, see the FileMaker Server Advanced Custom Web

Publishing Guide.


A accounts

fmweb 29

IIS and Basic Authentication 24

setting up the Administration account 33

setting up the Web Publishing Engine 34

Windows user accounts 25

Administration account 33

Administration Console 10

changing password 53 changing user name 53

committing changes 37

described 31

disabling (Mac OS) 53

logging out 51

restricting access 49

security overview 32

setting up 33

starting and stopping 52

Apache web server 10

authentication, setting up (Windows) 24

B

Basic Authentication 25

C

caching, XSLT stylesheets 43

calculation plug-ins 18

CDML Converter

described 11

installing in Mac OS 29

installing in Windows 26

requirements 10

character sets 45

command line interface

installing Web Publishing Engine from

(Windows) 23

starting and stopping from (Mac OS) 52

Index

configuring


committing changes 37

Custom Web Publishing with XSLT 41

host computers 13

Instant Web Publishing 39

Web Publishing Engine 31

Web Publishing Engine with FileMaker

Server 36

create_session() extension function 43, 47

custom installs 19, 27

in Mac 28

in Windows 22

Custom Web Publishing

viewing published files 50

Custom Web Publishing Engine 11

Custom Web Publishing with XML

disabling 41

Custom Web Publishing with XSLT

configuring 41

disabling 45

customer support 8

D

database sessions 43

databases. See files, database

disabling

Administration Console (Mac OS) 53

Custom Web Publishing with XML 41


Instant Web Publishing 40

Web Publishing Engine (Mac OS) 53

E

electronic documentation 7, 23

email access for Web Publishing Engine 44

encoding, text 45

encryption, data 16

error reporting 41


extended privileges, viewing 51

extension functions for FileMaker XSLT. See

fmxslt extension functions

F

FileMaker CDML Converter. See CDML Converter

FileMaker Pro

calculation plug-ins 18

enabling web publishing in databases 12

extended privileges 51

FileMaker Publishing Engine (WPC) service

(Windows) 52

FileMaker Server Advanced

registering Web Publishing Engine in

FileMaker Server 16

updating to 8

FileMaker Site Assistant. See Site Assistant

files, database

preparing in FileMaker Pro 12

related 17

testing in Instant Web Publishing 40

viewing published 50

firewalls blocking ports 13

FMS Web Read Me 19

fmsadmin group 29 fmweb account 29

fmxslt extension functions

fmxslt:create_session() function 43, 47 fmxslt:invalidate_session() function 47

fmxslt:send_email () function 44

fmxslt:set_session_timeout() function 47

folders default

Mac OS 29

Windows 21

for plug-ins 18

G

global variables, using with sessions 43

H hardware

configurations 13

requirements 8

I

identifier, Web Publishing Engine 16, 37

IIS web server 10

enabling IIS authentication 25

setting up authentication 24

installation code. See license key

installing Web Publishing Engine

from command line (Windows) 23

in Mac OS 27

in Windows 19

Instant Web Publishing

configuring 39

disabling 40

overview of published databases 50

status area language 39

testing 40

Internet Information Services. See IIS web server

invalidate_session() extension function 47

IP addresses

changing Web Publishing Engine 48

of FileMaker Server host computer 37

setting up Web Publishing Engine 34

J

J2SE 28

Java (and Mac OS X Server 10.2.8) 28

L languages

default installation 20

in status area 39

installing additional (Mac OS) 28

installing additional (Windows) 22

license key 8

localhost 34, 37

log files installation

Mac OS 29

Windows 23, 26


logging out 51

M

mail servers 44

modes, Custom Web Publishing with XSLT 41

msiexec 23, 26

N

number of sessions 38, 43

O operating systems

mixed configurations 13

requirements 8

overview

configuring Web Publishing Engine 31

installing Web Publishing Engine 13

in Mac OS 27

in Windows 19

of connected computer’s status 38

of published databases 50

using Web Publishing Engine 12

P

passcodes 16

passwords

changing Administration Console 53

changing Web Publishing Engine 48

for access to Administration account 33

for access to Web Publishing Engine 34

pe_application_log.txt 47 pe_internal_access_log.txt 47

plug-ins, folders for 18

ports

configuring 33

making available 13

protocols 15 protocols 15

Publishing Engine. See Web Publishing Engine

R

registering Web Publishing Engine in FileMaker

Server 16, 37

related database files 17

requirements, hardware and software 8

Index 57

restarting alert 35

restarting Web Publishing Engine 51

S

scripts, behavior in XSLT publishing 43

security



send_email () extension function 44

services (Windows)

described 23


starting automatically 22

sessions


time-outs 47

viewing status of 38

set_session_timeout() extension function 47

setting up Web Publishing Engine 31

Site Assistant

described 11



requirements 10

SMTP mail servers 44

SSL 16

state, saving in sessions 43

status area language 39

stylesheets, XSLT

accessing mail servers 44

caching and performance 43

creating 11

installing tools for 26, 29

T

technical support, contacting 8

testing database files, Instant Web Publishing 40

text encoding 45

time-outs, session 47


U

updating to FileMaker Server Advanced 8

user accounts. See accounts

user names

changing Administration Console 53

for access to Administration account 33

for access to Web Publishing Engine 34

W

Web Publishing Core 11

Web Publishing Engine

accessing mail servers 44

changing IP address 48 changing passwords 48

committing Administration Console changes 37

configuring 31

described 10

disabling (Mac OS) 53

enabling web publishing 12



log files 46

overview of configurations 13

overview of using 12

plug-ins 18

registering in FileMaker Server 16, 37

requirements 8

restarting 51

security 32

services (Windows) 23

session time-outs 47

setting up an account 34


starting automatically 22

uninstalling (Mac OS) 29

uninstalling (Windows) 25

viewing published files 50

viewing status of 38

web server

port 33

requirements 10


Web Server Module 10

web sessions 43

web sites

custom 13

FileMaker, Inc. 7


wpc_access_log.txt 47

X

XML 13

XSLT

caching stylesheets 43

setting text encoding for requests 45

stylesheets 11

Filemaker FileMaker Server 7 Advanced Installation guide

FileMaker

Server 7

Advanced

Web Publishing

Installation Guide

Contents

Chapter 1

Before you begin

Using FileMaker Server documentation

Customer support

About the license key

Hardware and software requirements

Windows requirements for the Web Publishing Engine

Mac OS requirements for the Web Publishing Engine

Windows requirements for FileMaker Site Assistant and FileMaker CDML Converter tools

Mac OS requirements for FileMaker Site Assistant and FileMaker CDML Converter tools

Important note about supported operating systems

About the Web Publishing Engine software components

About the tools for developing XSLT stylesheets

Overview of installing, configuring, and using the

Web Publishing Engine

Installing the Web Publishing Engine in various host configurations

About the protocols for the Web Publishing Engine

Using SSL and FileMaker Server encryption

Registering the Web Publishing Engine in FileMaker Server

Installing plug-ins for the Web Publishing Engine

Chapter 2

Installing the Web Publishing Engine in Windows

Overview of installation

Installing the Web Publishing Engine software components

About the Web Publishing Engine services

Installing the Web Publishing Engine from the command line

Setting up authentication for a Windows IIS web site

Uninstalling, modifying, or repairing the Web Publishing Engine

Installing the FileMaker Site Assistant and FileMaker CDML Converter

Where to go from here

Chapter 3

Installing the Web Publishing Engine in

Mac OS X

Overview of installation

Installing the Web Publishing Engine software components

Where files are stored on your hard disk

Uninstalling, modifying, or repairing the Web Publishing Engine

Installing the FileMaker Site Assistant and FileMaker CDML Converter

Where to go from here

Chapter 4

Configuring the Web Publishing Engine

About the Web Publishing Engine Administration Console

General steps for configuring the Web Publishing Engine

Configuring the Web Publishing Engine for the first time

Configuring the connection between the Web Publishing Engine and FileMaker Server

Viewing an overview of the Web Publishing Engine configuration

Configuring Instant Web Publishing

Disabling Instant Web Publishing

Disabling Custom Web Publishing with XML

Configuring Custom Web Publishing with XSLT

Setting the Web Publishing Engine mode

Setting server-side XSLT stylesheet caching

Configuring the interaction between web sessions and database sessions

Configuring access to a mail server for the Web Publishing Engine

Setting the default text encoding for XSLT requests

Disabling Custom Web Publishing with XSLT

Specifying general settings for the Web Publishing Engine

Specifying logging options for the Web Publishing Engine

Setting the session time-out for the Web Publishing Engine

Changing the IP address of the Web Publishing Engine host

Changing the user name and password for the Web Publishing Engine

Restricting access to the Administration Console

Viewing a list of the published databases for FileMaker Server

Logging out of the Administration Console

Using the Web Publishing Engine and Administration Console services

Starting, restarting, or stopping the services in Windows

Starting, restarting, stopping, or disabling the services in Mac OS X

Changing the user name and password for the Administration Console

Where to go from here

Index

Related manuals

Filemaker

FileMaker Server 7