Conference terri::web_authoring

> How do I develop and test on Machine "A", using the Front Page server, and 
publish
> on machine "B", using Purveyor on WinNT?

	You need to add the FP Server Extensions to the system.  For Purveyor
  when you are asked, select IIS as the server since Purveyor shares the ISAPI
  with IIS.  Note that you only get the FP Server Extensions for IIS when you
  install it on NT Server, you won't get it with Workstation.

		Danny

Danny,

I think you just told me that I need to be developing on a machine with 
NT server as the OS, correct?

My development machine has NT 3.51 WS

Thanks for the input.

gc

    nope.  develop on whatever you'd like, as long as FP runs on it (I use
    NT4 Workstation).  Your "real" server, where your readers will go with
    their browsers, needs to have a web server running and the FP
    Extensions installed (in my case, NT4Server w/IIS). 
    

	Just to try and clarify, your machine "B" on which the pages reside
  needs to have the FP Extensions installed.  Machine "A" can be a Windows NT
  Workstation or Server, or Windows 95 system with FrontPage Client Installed.
  IF machine "B" is a Workstation (Machine "B" needs to be running NT), then 
  getting the Extensions installed is and useable is rather tricky and difficult
  since Microsoft set up most of the extensions to work only on NT Server.  It
  can be done, but I don't recommend it for the squeamish.  I have an idea about
  how to do it, but I've never tried and I'm not sure it will work the way I
  expect.

		Danny

Thanks for the input.  Sounds like you're helping me build the case to go to
IIS.  I'm trying to get our server (NT4.0/Purveyor) changed, and any help is
appreciated.  If I do have to install the extensions on Purveyor, I'll document
the pain and post it here.

gc

Re: -.1

I mean IIS vs Purveyor....a Gatesian slip, I'm afraid.

gc

	The pain is only with NT Workstation and Server extensions.  There's
  no pain with NT Server and either IIS or Purveyor.

		Danny

    fwiw, on my NT4 Workstation I'm using PWS (the workstation version of
    IIS that comes with NTWorkstation) and FP; the extensions were farily
    easy to install for me.   The only thing I would recommend doing
    differently than I did would be to isntall PWS before installing FP,
    else FP installs it's FPPersonalWebServer (confused with the names,
    yet?) and puts it's extensions there.
    

Ok,

So I talked to Process Software, and the said that they had no knowledge of the
server extensions working with Purveyor...but any "scripts should be installed in
Purveyor's /scripts directory.

So I shuffled off to www.microsoft.com/frontpage/softlib/fp_97_extensions.htm

and downloaded fp97ext_alpha_enu.exe.

I copied it to the scripts directory and ran setup.

It installed no scripts in the proper place, and it doesn't work.  I can neither 
connect to the server when I start to build a new web, nor load a page that calls
a bot and have it execute.

?

gc

I'd love to hear from someone that has the server extentions working
from unix. I'm out of ideas on my setup. I just copied down the primer
for WPPs to see if it has any help. When I try to publish or open a web
from my NT system to my unix server. I get there, I get an entry into the
access_log and then nothing more on the server. And in frontpage I get an
error telling me to check the remote server's error file. But it has
nothing. 

Another thing that is starting to bug is how MS avoids mentioning us at
all when it comes to which unix systems they support. I THOUGHT we were
partners. liesl

re Note 162.10 by DSNENG::KOLBE:

> I'd love to hear from someone that has the server extentions working
> from unix. 

        I'd love to be able to install the FP Server Extensions on
        Digital UNIX!

        The installation program (fpsrvadm.exe) just crashes, after
        apparently doing some but not all of the setup.

        Now in fairness to this software, I'm trying to install it on
        an existing server with a rather extensive set of pages and
        server configurations (for example, it has about 20 alternate
        document directories defined).  The installation instructions
        would seem to be biased towards a fresh install.

        In INTERNET_TOOLS Note 4389.11 I give the details of this
        repeatable crash:

        <<< GYRO::SYS$SYSDEVICE:[NOTES$LIBRARY]INTERNET_TOOLS.NOTE;1 >>>
                              -< Internet Tools >-
================================================================================
Note 4389.11   FrontPage Server Extensions on DEC UNIX w/ Netscape      11 of 13
LGP30::FLEISCHER "without vision the people perish " 54 lines  12-FEB-1997 11:21
             -< not able to install the latest server extensions >-
--------------------------------------------------------------------------------
re Note 4389.10 by EPS::MERMELL:

> The latest patch appears to work.
> 
> http://www.rtr.com/fpsupport/downl_reg.htm
  
        I am not able to install it on a Digital UNIX V4.0A system
        running Netscape Enterprise V2.01 -- the installation
        procedure coredumps:

        webu:root:/usr/local/frontpage> cd /usr/local/frontpage/version2.0/bin
        webu:root:/usr/local/frontpage/version2.0/bin> ./fpsrvadm.exe
        Type "fpsrvadm -h" for help on command line options

        Please enter command:
        0) quit
        1) install
        2) upgrade
        3) uninstall
        4) check
        5) enable authoring
        6) disable authoring
        7) change security settings
        8) recalculate links
        9) putfile
        10) recalcfile
        Your choice [1]:

        Please enter server type:
        0) apache
        1) apache-manual-restart
        2) apache-wpp
        3) cern
        4) cern-manual-restart
        5) ncsa
        6) ncsa-manual-restart
        7) netscape-commerce
        8) netscape-communication
        9) netscape-enterprise
        10) netscape-fasttrack
        11) netscape-manual-restart
        Your choice [0]: 9
        Enter server config filename: /usr/ns-home/https-webu-main/config/magnus.conf
        Enter host name for multi-hosting []:

        Starting install, port: 80, web: ""

        Enter web administrator name []: update
        Enter web administrator password:
        Confirm password:
        Creating root web
        Recalculate links for root web
        Memory fault(coredump)
        webu:root:/usr/local/frontpage/version2.0/bin>


Bob

You don't have to have the FP extensions on the server.  FP's publishing wizard
will publish by FTP, but it does have some restrictions.

	1.  There must be a web server running on the target system (lest you
	    say "Doh!", I had a legitimate reason to want to publish to a
	    system not running a server - it was a staging directory on a
	    non-web machine - and FP wouldn't let me do it.)

	2.  You must be able to specify the directory in which the pages
	    are to be placed using UNIX syntax.  FP automatically adds a "/"
	    at the end of the directory spec, which rules out VMS - sigh.

				Steve

RE: .12

	3. It won't support any of the FP97 "Bots". Something
	that makes FP97 really easy to create functional pages
	without programming.

								mike

My Assumption is that the extensions are the Bots...little canned scripts
written in VB or some other MS tool.

gc

True - but you can have perfectly functional web pages without 'bots.

				Steve

Understood, and the FP editor is really good.

I am certain we will see more and more bots available in the public domain
over time....The Microsmurfs want a plethora of widely available, low cost
bots....to capture the web development, aka networked computing market.

I think that is the real value of the FP/IIS system.

gc

Now if they'll just develop the Front Page Extensions for OpenVMS, I'll be
happy...

			Steve

Sounds like a market to me...

    On that vein, do FrontPage Extensions for Linux exist?
    
    Cheers, Laurie.

    Hi
    
    Does a FrontPage for Windows NT Alpha exist?
    
    Thanks!
    tl

	No. Just the Frontpage Extensions for IIS for Alpha. And
	to run both the extensions and FX!32-ize the Intel client
	is a pain and doesn't work. (at least not cleanly)

	Running FX!32-ized Frontpage client on an Alpha with NO
	Frontpage Extensions works ok. I haven't extensively tried
	it now that I have a decent Pentium Pro on my desk.

							mike