What is the best method to get the HTML and resources generated by PlanetPress Connect to place into an external web server such as IIS or Apache? Currently I have my PlanetPress Connect web pages being served by the PlanetPress Workflow tool, but occasionally there are odd things that occur. In the help files it suggests that it is better to have an external web server host the pages. Are there any examples/samples that demonstrate using PlanetPress Connected generated HTML on an external web server. I can get a simple post to work, but want to leverage other elements of PlanetPress Connect.
I know that this is probably very simple, but I must be missing something.
I’m guessing you’re the one who asked this to Juan at Support? Because he just came to me with the exact same question…
Anyways essentially if you want to serve HTML generated by Connect through IIS, you could simply take the output of the Create Web Contents and send that to… well, a folder that is served by IIS (or Apache). If it’s on the same server, if you put the HTML in, say, C:\inetpub\wwwroot\foo\bar.html , it’ll be accessible on http://localhost/foo/bar.html . If it’s on a separate server you can use your regular output tasks like Send to Folder (on a network drive perhaps), or FTP Output.
Or you can do it the other way and leverage Workflow’s HTTP Server Input, and use various process as API endpoints to request files generated by Connect - especially PDFs and Web pages, obviously. Juan will be sending you an example file you can use as a starting point for that.
I watched the video that Juan sent me which appears to be working. The customer website is internal only. I installed IIS and then the Application Request Routing. I added the internal domain to the binding of the default web site. Next I added a new web page and added a binding that included my PP Connect server name.domain name. Then I added a URL Rewrite rule for a Reverse Proxy with the rewrite settings of PP Connect Server:8080 to value PP Connect Server.domain name and then adding in the wildcard pattern ^(,*)$ to the inbound rule and adding Base on the outbound rule.
My PP Connect designed pages are now display when use server-name.domain-name\http-action in the browser url.
Yep, that’s exactly it! So you should be able to request HTML and Print content on your server-name.domain-name/http-action , as well as accessing static resources (if you configure them in HTTP Server Input 2) through server-name.domain-name/_iRes/ (by default).
I’m happy the videos were useful to the first end-user that watched them!
