We have a scenario where we have a Windows server on which we have the help hosted on Apache Tomcat web server. This Windows machine is a dedicated help hosting server. Technical publications team can generate the help output manually and copy and paste the output folder to the help hosting server by doing a remote desktop connection. This however is error-prone and not the best way.
Can someone throw some light on how the Publishing options FTP and/or HTTP would work?
When they generate the output, there is a Publish option in the dialog.
The easiest way would be to select File System, browse to the server and enter the password. They would of course need to be able to see the server as part of their network.
The two options you mention are also just cases of filling in the information required but I can't help with that, it needs to come from the IT admins.
See www.grainge.org for free RoboHelp and Authoring information.
Sorry, one more related question. This worked on a Windows server/machine.
Would this work on a Linux machine? If the folder is on a Linux server with Apache Tomcat 9, would this work the same way?
Has anyone tried publishing on a Linux server?
Certainly using FTP should work as that is a standard (file) transfer protocol.
Do note that by default Linux is case sensitive, whereas Windows is case insensitive, so there is a chance you could run in to problems running the help depending on how you've named your topics and created the links. For example, say you call a topic MyTopic.htm, but manually create a link to mytopic.htm. On Windows the link would work, but on Linux it would not. So either you have to make sure the case of your links matches the topic, or you have to convince your web server admin to make a change to the Apache server (which they generally seem reluctant to do). There is a setting to use lowercase file names, but I feel like I've seen reports of issues with it. I'd suggest searching the forums before using it, just to check. if there are issues.
Thanks so much. That is a great insight you've shared.