FX.php with FileMaker PHP API

[Michael Maher]

I assume this has been discussed somewhere, but I haven't found it as yet, so if anyone could point me to where I can find info on this I'd appreciate it.

I have always build with FX.php, and am only now doing a job using the FM API.

What is the best way to combine these on the same server?

Does it matter if FMSA installs it's own PHP, or is it better to do a manual install, and retain the normal install of PHP?

I assume if the FM install is chosen, then the FX folder has to be moved into the FileMaker area somewhere. Does the php.ini need modification after FM has mucked with it? Can I switch back and forth from the FM Admin module without stuffing it up somewhere, or is it better to uninstall and reinstall FMSA and PHP?

Is there a best deployment practice discussed somewhere?

I am interested in both the Windows and Mac platform. Plus I am developing on Vista.

thanks,

Michael

FMSA 9

Cross Platform

[Genx]

1) Install PHP yourself - this will ensure you get the most recent secure version on your server. Using the FMS installer will get you some older version.

2) FM will not muck with your custom PHP install - i don't know what it does with its own. It mucks with your web server (IIS or Apache).

3) FX doesn't need to be moved anywhere - use as per usual.

[Michael Maher]

1) Install PHP yourself - this will ensure you get the most recent secure version on your server. Using the FMS installer will get you some older version.

2) FM will not muck with your custom PHP install - i don't know what it does with its own. It mucks with your web server (IIS or Apache).

3) FX doesn't need to be moved anywhere - use as per usual.

Thanks Genx, in the absence of any other comments to the contrary, that looks sensible advice.

The reason I asked about FMSA mucking with the php.ini, is because I installed the FM version before I changed my mind, then reverted it via the Admin module - then I noticed FMSA had added stuff into the php.ini, although it did appear to have commented it out after the reversal. Just can't be sure these people go to as much trouble undoing things as they do in doing them in the first place. But it does look to be working fine so far. Anyway I can always reinstall everything if absolutely necessary - God knows how many times I have done that in the past.

m

[sdcagle]

Can anyone help me find a detailed guide for configuring and using fx.php?

Thanks,

Scott

[sdcagle]

Hi, still looking for help setting up fx.php.

I am not getting the following error when trying to use the sample files/db:

Error: Communication Error: (22) The requested URL returned error: 404 - This can be due to an invalid username or password, or if the FMPHP privilege is not enabled for that user.

I know the permissions are correct. I really need to get this solved. Any help is greatly appreciated.

Scott

[Genx]

Communication Error: (22) The requested URL returned error: 404 - This can be due to an invalid username or password, or if the FMPHP privilege is not enabled for that user.

... sounds like an fmapi error to me, not fx.php ...

[sdcagle]

Right, this is where I'm getting completely stuck, confused, etc.

What exactly do I need to make this work? Some of the things I've read make it seem like I don't need the FM API, but some things appear to make it seem like I do. The FMS sees the web server and I have a green light for php (red lights for IWP, etc). I also get a WPE could not be started error message on the Admin Console. Does this mean php will not work?

I have zero experience getting FM to the web so I'm really looking for explicit instructions.

I am trying to do the following:

FMS Adv v9 on one machine, web server and WPE (I guess) on another machine. I did install FMS on the web machine, picked multiple, worker machine etc and then re-installed FMS on the db (master) server. Everything in the deployment goes well except getting the WPE working.

Web server is using Apache and the already installed version of php, not the FMS version and both servers are OS X 10.5.5.

I really appreciate the help. I am getting completely lost.

I can supply screen shots if needed.

Thanks,

Scott

[Genx]

I also get a WPE could not be started error message on the Admin Console. Does this mean php will not work?

... Most likely.

For testing purposes install everything on the one box.

1) Install FMS

2) Run the deployment wizard (per the fm manual) and install the WPE (if it already has php installed, keep the php installation).

3) Run the little test utility they give you

[sdcagle]

You've hit the issue. I already had this working in the one machine configuration. I used the php site assistant, started customizing, everything worked great.

I was then told it was more ideal to get this workin g in the two machine configuration. So...

I un-installed FMS and started the process of re-installing and re-deploying. I installed the worker machine first and then the master.

So that's where I am now. Everything working except the WPE.

Any other ideas (other than re-install)?

Scott

[Genx]

Quickest path = re-install.. Sure it's more efficient (slightly) splitting, but it working is more efficient than it not working.

[sdcagle]

Yea, I was afraid of that.

Ever heard of anyone installing FMS on the worker machine(s) after the master and successfully deploying the WPE on the web (worker) server?

I'm going to meet alot of resistance to putting everything back on one machine due security issues. The client really doesn't want to open their FM server to the web.

Scott

[Genx]

Lol, i was gonna point you to my blog post, but you've been there already..

If you look at it again, there are 3 machines.

1) FMS

2) Worker Machine (Passed XML queries to FMS)

3) The Exposed to internet webserver (shove this on your other box).

In any case, thinking that your FMS is going to be "exposed" with port 80 pointing to that box is just weird. If you're client's network has that much of a security hole in it, it's going to be just as exposed from one box to the next (in via the webserver, once in the lan, happily over to the FMS box)

Just because AN application is open to the internet, doesn't mean the whole machine necessarily is... Here, watch this: http://www.filemakerdesign.com/blog/?bid=11

[sdcagle]

OK. I'm going to go back and try to re-start the whole process.

Here's one more thing I'm confused about.

What exactly to I need on the FM end? Do I still need the FMI for API stand alone folder? Or do I just need to install FMS Adv. 9 and make sure everything is enabled?

Sorry to be so high maintenance but I don't think the FM documentation on this is very clear.

Thanks,

Scott

[Genx]

just need to install FMS Adv. 9 and make sure everything is enabled

The API folder goes on machine 3.

[sdcagle]

Thanks. I've watched your video, good stuff.

I think I'm going to try re-starting the process all over with the two machine (alternate) configuration. That is, db server and WPE on the same machine and web server on a separate machine.

Of course, I tried doing this simply by editing my current deployment but I got the following error:

'Deployment/Configuration error - 150 Starting WPE (wpe1) component failed: error code=2504.'

From some other things I've read I wasn't surprised to get this error, I just figured what the heck.

Hopefully starting from scratch and keeping the WPE on the same server as the db will work.

Scott

[lannon]

Not sure if this is helpful at all, but when configuring your Web Publishing Engine, you need to make sure that XML Publishing is enabled (in addition to PHP Publishing). Fx.php uses the XML interface exclusively. If you do not have XML Publishing enabled, Fx.php will not work at all.

Additionally, you should confirm that the account or accounts used to access the server via XML have the "fmxml" extended privilege set.