FileMaker PHP (FM9) und XAMPP (MacOS)

Spezielle Fragen zu FileMaker Unlimited, Webhosting, CDML, FX.php, Lasso und verwandte Themen
Forumsregeln
Sie befinden sich im Archivforum! Sie können hier alte Beiträge lesen und vorhandene Diksussionen ergänzen.
Neue Diskussionen können Sie in diesem Archiv nicht erstellen!

FileMaker PHP (FM9) und XAMPP (MacOS)

Beitragvon Armin » So 22. Jun 2008, 11:01

Hinweis: Eintrag wurde aus altem Forum importiert. Ggf. kann es dadurch zu Darstellungsproblemen kommen.
Nachrichtensymbol: Bild

Hallo Leute,

hat schon jemand den FileMaker Server 9 (nicht Advanced) mit einer XAMPP/MAMP (MacOS) Umgebung zum laufen gebracht?
Ich versuche mich nun seit einigen Tagen an der Umsetzung. Der MacOS eigene Apache WebServer ist deaktiviert - es wird nur auf der XAMPP Umgebung im Moment versucht.
Ziel ist es, eine administrations-/umzugsfreundliche Installation des Servers zu erreichen. So dass wir von Rechner zu Rechner einfach und schnell umziehen können. Dies gewährleistet eine XAMPP und MAMP Umgebung. Außerdem sind nur in diesen Umgebungen die "GD Librarys" eingebunden, was beim Standard MacOS Apache nicht der Fall ist (Wird für Captcha benötigt)
Das Laden der Dateien

- libphp5.so (von FileMaker Server geliefert)
# LoadModule php5_module '/Applications/xampp/xamppfiles/FMI_WebPublishing/publishing-engine/php/apache-2.2/libphp5.so'

- mod_jk_fm.so (von FileMaker Server geliefert)
# LoadModule jk_fm_module '/Applications/xampp/xamppfiles/FMI_WebPublishing/publishing-engine/web-server-support/apache-2.2/mod_jk_fm.so'

funktioniert nicht. Diese Dateien wurden in die XAMPP/MAMP Umgebung kopiert und die Benutzerrechte für XAMPP gesetzt. Auch sind die anderen "include" Dateien in das Verzeichnis kopiert worden und die Benutzerrechte für XAMPP gesetzt. Die Pfade sind absolute Pfade und gültig.

Die Apache Konfiguration wurde dahingehend geändert, dass die Standard "libphp5.so" nicht mehr eingebunden ist (auskommentiert). Auch wurde die Apache Konfiguration auf eine einzige "FileMaker - include" Datei reduziert, um den Fehler beim "Nichtstart" des Apache leichter finden zu können.
Die Konfigurationsdateien hänge ich den nächsten Postings einmal an.

Was passiert nun?
1. Es wird, wenn alles auskommentiert ist, der Apache WebServer gestartet - funktioniert also.
Nun ist also kein "libphpX.so" Modul geladen - PHP ist somit deaktiviert.
2. Wenn die "- libphp5.so (von FileMaker Server geliefert)" versucht wird zu laden (aus der neuen xampp.conf Datei), startet der Apache Server nicht mehr - funktioniert also nicht. Ist die Version denn nicht zu der von XAMPP kompatibel?
3. Wenn die original von XAMPP mitgelieferte "libphp5.so" geladen wird, funktioniert wieder alles wie gewünscht und PHP arbeitet korrekt, aber eben nicht mit der von FileMaker angepassten Library.

Bin für jeden Tipp dankbar.

Grüße

Armin

XAMPP für Mac OS X 0.7.2, Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.8e DAV/2 PHP/5.2.5
FileMaker Server: 9.0v3 (9.0.3.325)
PHP.ini File: /Applications/xampp/etc/php.ini
Mac OS X 10.4.11

Armin Egginger
[x] cross solution
Kurfuerstenstr. 28
82110 Germering
Germany
Phone: +49 - (0)89 - 84 10 25 70
Fax: +49 - (0)89 - 84 10 25 73
Armin
 
Beiträge: 4
Registriert: So 22. Jun 2008, 00:00
Wohnort: Germering

Antwort

Beitragvon Armin » So 22. Jun 2008, 11:02

Hinweis: Eintrag wurde aus altem Forum importiert. Ggf. kann es dadurch zu Darstellungsproblemen kommen.

Apache Konfiguration:

#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/Applications/xampp/xamppfiles" will be interpreted by the
# server as "/Applications/xampp/xamppfiles/logs/foo.log".

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "/Applications/xampp/xamppfiles"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule cache_module modules/mod_cache.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule dbd_module modules/mod_dbd.so
LoadModule bucketeer_module modules/mod_bucketeer.so
LoadModule dumpio_module modules/mod_dumpio.so
LoadModule echo_module modules/mod_echo.so
LoadModule case_filter_module modules/mod_case_filter.so
LoadModule case_filter_in_module modules/mod_case_filter_in.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
LoadModule charset_lite_module modules/mod_charset_lite.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
LoadModule ident_module modules/mod_ident.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule asis_module modules/mod_asis.so
LoadModule info_module modules/mod_info.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule cgid_module modules/mod_cgid.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
#LoadModule php5_module modules/libphp5.so
#LoadModule php4_module modules/libphp4.so

# FMI XAMPP Change - START
<IfDefine PHP4>
# LoadModule php4_module modules/libphp4.so
</IfDefine>
<IfDefine PHP5>
# LoadModule php5_module modules/libphp5.so
</IfDefine>
# AddType application/x-httpd-php .php .php3 .php4 .php5
# AddType application/x-httpd-php-source .phps
# AddHandler cgi-script .cgi .pl

# FMI XAMPP Change - END

# The following line was added by FileMaker Server Web Publishing Engine in order to add
# Web Publishing Engine request redirection feature to Apache Web Server.
# FMI_Configuration_V1
# Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf'
# Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fm-server-status.conf'
# Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_jk.conf'
# Include '/Library/FileMaker Server/Web Publishing/publishing-engine/php/apache-2.2/httpd.conf.php'
# mod by [x] cross solution, Armin Egginger - FMI_Configuration for XAMPP
Include '/Applications/xampp/xamppfiles/FMI_WebPublishing/xampp.conf'


<IfModule !mpm_netware_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User nobody
Group admin
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#
ServerAdmin you@example.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/Applications/xampp/xamppfiles/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/Applications/xampp/xamppfiles/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks ExecCGI Includes

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride AuthConfig

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html index.php index.htmls index.htm home.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common

<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog logs/access_log common

#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog logs/access_log combined
</IfModule>

<IfModule alias_module>
#
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
#
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
#
ScriptAlias /cgi-bin/ "/Applications/xampp/xamppfiles/cgi-bin/"

</IfModule>

<IfModule cgid_module>
#
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#
#Scriptsock logs/cgisock
</IfModule>

#
# "/Applications/xampp/xamppfiles/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
Alias /phpmyadmin /Applications/xampp/xamppfiles/phpmyadmin
<Directory "/Applications/xampp/xamppfiles/phpmyadmin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

<Directory "/Applications/xampp/xamppfiles/cgi-bin">
AllowOverride None
Options None +ExecCGI
Order allow,deny
Allow from all
</Directory>

Alias /phpsqliteadmin /Applications/xampp/xamppfiles/phpsqliteadmin
<Directory "/Applications/xampp/xamppfiles/phpsqliteadmin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>



#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig /Applications/xampp/etc/mime.types

#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

# For type maps (negotiated resources):
#AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile /Applications/xampp/etc/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the /Applications/xampp/etc/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include /Applications/xampp/etc/extra/httpd-mpm.conf

# Multi-language error messages
#Include /Applications/xampp/etc/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include /Applications/xampp/etc/extra/httpd-autoindex.conf

# Language settings
#Include /Applications/xampp/etc/extra/httpd-languages.conf

# User home directories
Include /Applications/xampp/etc/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include /Applications/xampp/etc/extra/httpd-info.conf

# Virtual hosts
#Include /Applications/xampp/etc/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include /Applications/xampp/etc/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include /Applications/xampp/etc/extra/httpd-dav.conf

# Various default settings
#Include /Applications/xampp/etc/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include /Applications/xampp/etc/extra/httpd-ssl.conf

<IfDefine SSL>
Include /Applications/xampp/etc/extra/httpd-ssl.conf
</IfDefine>


#
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
Armin Egginger
[x] cross solution
Kurfuerstenstr. 28
82110 Germering
Germany
Phone: +49 - (0)89 - 84 10 25 70
Fax: +49 - (0)89 - 84 10 25 73
Armin
 
Beiträge: 4
Registriert: So 22. Jun 2008, 00:00
Wohnort: Germering

Antwort

Beitragvon Armin » So 22. Jun 2008, 11:03

Hinweis: Eintrag wurde aus altem Forum importiert. Ggf. kann es dadurch zu Darstellungsproblemen kommen.

include Datei - eine Datei aus 4 Original FileMaker .conf Files

# The following line was added by FileMaker Server Web Publishing Engine in order to add
# Web Publishing Engine request redirection feature to Apache Web Server.
# FMI_Configuration_V1
# Step 1 - Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf'
# Step 2 - Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fm-server-status.conf'
# Step 3 - Include '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_jk.conf'
# Step 4 - Include '/Library/FileMaker Server/Web Publishing/publishing-engine/php/apache-2.2/httpd.conf.php'

# Include - Step 1 --------------------------------------------------------------------------
# fmi-test.conf
# Origin: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fmi-test.conf
#
#- Alias /fmi-test "/Library/FileMaker Server/Web Publishing/web-server-support/test/fmi-test"
#- <Directory "/Library/FileMaker Server/Web Publishing/web-server-support/test/fmi-test">
#- Options Indexes FollowSymLinks MultiViews ExecCGI
#- AllowOverride All
#- Order allow,deny
#- Allow from all
#- </Directory>

# Include - Step 2 --------------------------------------------------------------------------
# fm-server-status.conf
# Origin: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/fm-server-status.conf
#
#Configuration to enable the server-status and server-info
#- Listen 80
#- Listen 127.0.0.1:9010
#- LoadModule info_module libexec/httpd/mod_info.so
#- LoadModule status_module libexec/httpd/mod_status.so
#- <Location /server-status>
#- SetHandler server-status
#- Order deny,allow
#- Deny from all
#- Allow from 127.0.0.1
#- </Location>
#- <Location /server-info>
#- SetHandler server-info
#- Order deny,allow
#- Deny from all
#- Allow from 127.0.0.1
#- </Location>
#- ExtendedStatus Off
#- AddDefaultCharset utf-8


# Include - Step 3 --------------------------------------------------------------------------
# mod_jk.conf
# Origin: /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_jk.conf
#
# LoadModule jk_fm_module '/Library/FileMaker Server/Web Publishing/publishing-engine/web-server-support/apache-2.2/mod_jk_fm.so'
# mod by [x] - Path to XAMPP /Applications/xampp/xamppfiles/FMI_WebPublishing/
# LoadModule jk_fm_module '/Applications/xampp/xamppfiles/FMI_WebPublishing/publishing-engine/web-server-support/apache-2.2/mod_jk_fm.so'

# JkFmWorkersFile '/Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/workers.properties'
# JkFmLogFile '/Library/FileMaker Server/Logs/web_server_module_log.txt'
# JkFmShmFile '/Library/FileMaker Server/Logs/mod_jk_shm.txt'
# JkFmLogLevel error
# JkFmLogStampFormat "[%a %b %d %H:%M:%S %Y]"
# JkFmOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
# JkFmRequestLogFormat "%w %V %T"
# JkFmMount /fmi/config config
# JkFmMount /fmi/config/* config
# JkFmMount /fmi/iwp wpc
# JkFmMount /fmi/iwp/* wpc
# JkFmMount /fmi/xml/* wpc
# JkFmMount /fmi/xsl/cnt/* cwpe
# JkFmMount /fmi/xsl/relay/* cwpe
# JkFmMount /fmi/xsl/*.xsl cwpe


# Include - Step 4 --------------------------------------------------------------------------
# httpd.conf.php
# Origin: /Library/FileMaker Server/Web Publishing/publishing-engine/php/apache-2.2/httpd.conf.php
#
# Apache PHP directives for FileMaker PHP Engine
#
# PHPIniDir '/Library/FileMaker Server/Web Publishing/publishing-engine/php/lib/php.ini'
# LoadModule php5_module '/Library/FileMaker Server/Web Publishing/publishing-engine/php/apache-2.2/libphp5.so'
# mod by [x] - Path to XAMPP /Applications/xampp/xamppfiles/FMI_WebPublishing/
# PHPIniDir '/Applications/xampp/xamppfiles/FMI_WebPublishing/publishing-engine/php/lib/php.ini'
# LoadModule php5_module '/Applications/xampp/xamppfiles/FMI_WebPublishing/publishing-engine/php/apache-2.2/libphp5.so'

# AddType application/x-httpd-php .php
# AddType application/x-httpd-php-source .phps
# DirectoryIndex index.html index.php home.php
Armin Egginger
[x] cross solution
Kurfuerstenstr. 28
82110 Germering
Germany
Phone: +49 - (0)89 - 84 10 25 70
Fax: +49 - (0)89 - 84 10 25 73
Armin
 
Beiträge: 4
Registriert: So 22. Jun 2008, 00:00
Wohnort: Germering

Antwort

Beitragvon schube » So 22. Jun 2008, 21:00

Hinweis: Eintrag wurde aus altem Forum importiert. Ggf. kann es dadurch zu Darstellungsproblemen kommen.

Hi Armin!

Warum in alles in der Welt willst Du die PHP Lib von FileMaker verwenden?
Vergiss die bitte und verwende die von XAMPP.

Problem gelöst. Bei Fragen ruf mich (ab Dienstag nachmittag) an - meine Nummer hast Du ja.

Ciao,
Bernhard
Dipl-Ing. (FH) Bernhard Schulz,
Geschäftsführer von http://www.schubec.com
Leiter des FileMakerProfis-Team
FileMaker Schulungen unter http://www.fm-training.info
Benutzeravatar
schube
Administrator
 
Beiträge: 2339
Registriert: Mi 7. Jul 2010, 15:59
Wohnort: Salzburg, Österreich

Antwort

Beitragvon qt2fm » Mo 8. Mär 2010, 12:17

Hinweis: Eintrag wurde aus altem Forum importiert. Ggf. kann es dadurch zu Darstellungsproblemen kommen.
Nachrichtensymbol: Bild

Hallo zusammen

Diese Diskussion liegt zwar schon einen Weile zurück, aber wir sehen uns gerade mit einem ähnlichen Problem konfrontiert.
Und da die *Lösung* (von Bernhard erwähnt) nicht gepostet ist, fragen wir nochmals nach.

Folgende Problemstellung:
System: OS X 10.6.2
FileMaker Version: 10 Adv.

Wir arbeiten mit dem Pakete-System *MacPorts* und verwenden nicht die Standard-Apache/PHP-Installation.
Webserver/PHP läuft tadellos.
Allerdings *findet* der FileMaker Server 10 (Adv.) den Webserver nicht. Auch nicht nach Eingabe aller erdenkklicher *lokalen* Hosts.

Der FileMaker Server wurde bei laufendem *MacPorts*-Apache installiert.

Hat jemand einen Tipp, wie man den FMS dazu bringt nicht auf den Standard-Apache zu *warten*.

Für alle Infos und Hilfestellungen besten Dank um Voraus.

Grüsse, QT
qt2fm
 
Beiträge: 2
Registriert: Di 26. Mai 2009, 00:00

Antwort

Beitragvon schube » Mi 10. Mär 2010, 19:20

Hinweis: Eintrag wurde aus altem Forum importiert. Ggf. kann es dadurch zu Darstellungsproblemen kommen.

Hallo!

Nachdem ich eine Mail bekommen habe und diese beantwortet habe, lasse ich hier gerne jeden mitlesen :-)
--------
Vielen Dank für Ihre Anfrage. Ich habe das schon im Forum gesehen, aber auf solche Postings ohne Namen antworte ich prinzipiell nicht.
Meiner persönlichen Meinung nach ist mir meine Zeit zu schade eine Antwort zu posten wenn der Fragende nicht mal Zeit hat einen Namen zu schreiben. Vielleicht finden Sie das komisch, aber so sehe ich das.

Nun zu Ihrem Problem: Ich kann Ihnen nicht sagen, was Sie tun müssen, damit der FileMaker Server Installer den MacPorts Apache sieht, aber ich würde wie folgt vorgehen:
Konfiguration/Installation FileMaker Server mit dem eingebauten Apache
Dann die veränderte Konfiguration ansehen und diese in Ihren MacPorts Apache übernehmen. Soweit ich es im Kopf habe sind das nur ein paar Zeilen in der httpd.conf Datei. Das sollte also nicht weiter schwer sein.

Grüsse,
Bernhard Schulz
Dipl-Ing. (FH) Bernhard Schulz,
Geschäftsführer von http://www.schubec.com
Leiter des FileMakerProfis-Team
FileMaker Schulungen unter http://www.fm-training.info
Benutzeravatar
schube
Administrator
 
Beiträge: 2339
Registriert: Mi 7. Jul 2010, 15:59
Wohnort: Salzburg, Österreich


Zurück zu FM & Internet