You could use a URL shortening service such as Bitly to create a shortened version of the WebDirect URL:
Otherwise you could setup a simple HTML page on your server that redirects to the WebDirect URL using the HTML refresh tag:
<meta http-equiv="refresh" content="0; url=http://www.mydomain.com/new-page.html">''
Thanks for the rapid response! Only other question I have is: Where on the FM server should this simple page go?
1 of 1 people found this helpful
The root folders for the web server are:
IIS (Windows) through HTTP or HTTPS:
[drive]:\Program Files\FileMaker\FileMaker Server\HTTPServer\Conf
where [drive] is the drive on which the Web Publishing Engine component of your FileMaker server deployment resides.
Apache (OS X) HTTP:
Apache (OS X) HTTPS:
but you can put an HTML page like this on any web server and it will redirect to the specified URL.
Okay, one last question:
On my Mac-based development server (single server deployment) I added the redirect to the Index.html file, and it worked like a charm. Thank you! Only thing I found was that I needed to restart the Web Publishing Engine to get the change to "take."
So off I went and applied the same change to the worker machine in the two-server Windows deployment, but when I went to launch the admin console on the worker to restart the web server, I got a 404 error. As this is my first two-server deployment, my question is: Is there an Admin Console on a worker machine?
I did jump on the Database Server's Admin Console, but Web Publishing is all grayed-out there (though it does properly list the IP of the worker machine.
was the two-machine install done following the instructions? we did a two-machine install and web server info was showing in the Master (Server) Admin console. the ip of the worker machine shows correctly.
Well I think I did it right! ;-)
I just had the client restart the servers (I don't have the rights to do it)...I'll be logging in shortly to see if anything has improved.
There's only one admin console whether you do a single machine deployment or a 2 machine deployment. You can normally start/stop the WPE from the Admin Console for both deployment types.
correct! OP was trying to launch it from the Worker (WD) machine, when it's mainly used from the Master/main machine.
Remote people can also launch & see the Admin Console when permissions are granted to do so with proper login.
Well it's good to know that there's only a single Admin Console. So here's some new information:
When the servers were originally deployed a few months ago, they were both in the same domain. For security reasons, the IT department recently moved the worker machine to their DMZ. My guess is that although the worker is communicating with the database server (I can log into my databases via Web Direct), I'll bet that the move broke some critical communication link for the Admin Console to communicate with the worker.
Sound plausible? As the databases are not live yet, I'm thinking that an uninstall/reinstall of the server software is the most expedient course of action.
Thanks for the responses! Much appreciated.
Yes, uninstall & reinstall is a good choice. After that is done, and the Admin console up and running, use the test page to see if the sample db is being seen by FMPro and WebDirect correctly.
Sent from my miPhone