FMSA 7.1, OSX Web Publishing Config

[jfwarren1]

Hello. Installed FMSA 7.1 and having problems with locating the Web Publishing Console. My solutions host fine for client boxes that have FM Pro (via Host)but I cannot fine anywhere how to get client boxes to access FM solutions on the server via Web Browser. Apache is running, but when client browser goes to server ip, only default apache index files show up. Additionally, I am trying to upgrade the Web Publisher to v3 but installer won't proceed because it says "cannot proceed web publishing service is running". I don't see anywhere in the server panel of osx that this service is there or even running. Any help or guidance wound be greatly appreciated.

[jfwarren1]

Hello. Installed FMSA 7.1 and having problems with locating the Web Publishing Console. My solutions host fine for client boxes that have FM Pro (via Host)but I cannot fine anywhere how to get client boxes to access FM solutions on the server via Web Browser. Apache is running, but when client browser goes to server ip, only default apache index files show up. Additionally, I am trying to upgrade the Web Publisher to v3 but installer won't proceed because it says "cannot proceed web publishing service is running". I don't see anywhere in the server panel of osx that this service is there or even running. Any help or guidance wound be greatly appreciated.

[jfwarren1]

Hello. Installed FMSA 7.1 and having problems with locating the Web Publishing Console. My solutions host fine for client boxes that have FM Pro (via Host)but I cannot fine anywhere how to get client boxes to access FM solutions on the server via Web Browser. Apache is running, but when client browser goes to server ip, only default apache index files show up. Additionally, I am trying to upgrade the Web Publisher to v3 but installer won't proceed because it says "cannot proceed web publishing service is running". I don't see anywhere in the server panel of osx that this service is there or even running. Any help or guidance wound be greatly appreciated.

[Vaughan]

I assume you mean FMSA 7.0v1... there is no "7.1" version.

The FMSA 7.0v3 patch has been released, before doing anything install it and see if it improves.

[Vaughan]

I assume you mean FMSA 7.0v1... there is no "7.1" version.

The FMSA 7.0v3 patch has been released, before doing anything install it and see if it improves.

[Vaughan]

I assume you mean FMSA 7.0v1... there is no "7.1" version.

The FMSA 7.0v3 patch has been released, before doing anything install it and see if it improves.

[jfwarren1]

Well that's the thing, every time I try and run the 7.0v3 patch it halts saying that "Web Publishing Engine Service Running, Cannot Continue".

[jfwarren1]

Well that's the thing, every time I try and run the 7.0v3 patch it halts saying that "Web Publishing Engine Service Running, Cannot Continue".

[jfwarren1]

Well that's the thing, every time I try and run the 7.0v3 patch it halts saying that "Web Publishing Engine Service Running, Cannot Continue".

[Claus Lavendt]

Hi

Try to read the README file, which is located in the same folder as the updater....

There is a reason that it is distributed along with the updater file......... :-)

...You need to stop the web engine, and since this runs as a process you need to do this from the terminal on OS X.

In the README file there is a very precise guide on how to do this. Make sure you write the command exactly as it's written in the guide. Unix and the terminal commands is case sensitive !

;-) Claus

[Claus Lavendt]

Hi

Try to read the README file, which is located in the same folder as the updater....

There is a reason that it is distributed along with the updater file......... :-)

...You need to stop the web engine, and since this runs as a process you need to do this from the terminal on OS X.

In the README file there is a very precise guide on how to do this. Make sure you write the command exactly as it's written in the guide. Unix and the terminal commands is case sensitive !

;-) Claus

[Claus Lavendt]

Hi

Try to read the README file, which is located in the same folder as the updater....

There is a reason that it is distributed along with the updater file......... :-)

...You need to stop the web engine, and since this runs as a process you need to do this from the terminal on OS X.

In the README file there is a very precise guide on how to do this. Make sure you write the command exactly as it's written in the guide. Unix and the terminal commands is case sensitive !

;-) Claus

[jfwarren1]

ok, Thanks Claus L. Figured it out. I am completely updated now to the new versions but when my users go to www.mywebpage.com the default apache page shows up. What has to be placed inside the Apache default web location so that when user go to the web page they can launch a filemaker web session? The manual talkes about moving certain files to the default web folder but does not mention where these files are or there names. I assume the databases database.fm7 stay in the FM7 server directory right?

[jfwarren1]

ok, Thanks Claus L. Figured it out. I am completely updated now to the new versions but when my users go to www.mywebpage.com the default apache page shows up. What has to be placed inside the Apache default web location so that when user go to the web page they can launch a filemaker web session? The manual talkes about moving certain files to the default web folder but does not mention where these files are or there names. I assume the databases database.fm7 stay in the FM7 server directory right?

[jfwarren1]

ok, Thanks Claus L. Figured it out. I am completely updated now to the new versions but when my users go to www.mywebpage.com the default apache page shows up. What has to be placed inside the Apache default web location so that when user go to the web page they can launch a filemaker web session? The manual talkes about moving certain files to the default web folder but does not mention where these files are or there names. I assume the databases database.fm7 stay in the FM7 server directory right?

[Claus Lavendt]

Remember that the default address for filemaker instant web publishing is:

http://www.mywebpage.com/fmi/iwp

xslt custom web

http://www.mywebpage.com/fmi/xslt/foldername/home.xsl

This is beccause the default webpages can run simultanious with filemaker web.

If you want your users to go directly to the filemaker web, you can:

1) Edit the DNS record of your domain to point at your IP and the desired path to filemaker web

2) Make a redirect html webpage, name it index.html and put it in the default Apache Web folder.

;-) Claus

[Claus Lavendt]

Remember that the default address for filemaker instant web publishing is:

http://www.mywebpage.com/fmi/iwp

xslt custom web

http://www.mywebpage.com/fmi/xslt/foldername/home.xsl

This is beccause the default webpages can run simultanious with filemaker web.

If you want your users to go directly to the filemaker web, you can:

1) Edit the DNS record of your domain to point at your IP and the desired path to filemaker web

2) Make a redirect html webpage, name it index.html and put it in the default Apache Web folder.

;-) Claus

[Claus Lavendt]

Remember that the default address for filemaker instant web publishing is:

http://www.mywebpage.com/fmi/iwp

xslt custom web

http://www.mywebpage.com/fmi/xslt/foldername/home.xsl

This is beccause the default webpages can run simultanious with filemaker web.

If you want your users to go directly to the filemaker web, you can:

1) Edit the DNS record of your domain to point at your IP and the desired path to filemaker web

2) Make a redirect html webpage, name it index.html and put it in the default Apache Web folder.

;-) Claus