we have searching issues in the past weeks, and after exploring it, another issue exposed that we have 2 tomcat services installed on one machine, and both connected to the same Robohelp server. So IT will work on separating the enviroment. the question is how:
1. separate DEV and Production by creating 2 different context, project could be published to one of the context and as it is ready, republished to production. this option will give the flexibility of two different set of authentification and different parameter settings of "Reindex ..." and "Substring..."
2. separate DEV and Production by installing tomcat services into 2 different machines(or virtual machines?) , and buy 2 RH9 server license. it will give us the test opportunity for upgrade or patch.
If you are running RH9 server, what's your option you have picked?
if you pick option 1, how do you deal with the upgrade and patch test?
if you running on option 2, do you know the extra price for second server license on DEV?
do the two tome cat services have to run in two different physical machine, each with their own RH( server connected with it
or they actually could run in two different virtual machines but on the same physical machine?
I use the option 1 setup. The cost of a second RHS licence would be the same as the first and the additional context functionality allows specifically for a pre-production and production set-up. In fact we go further by having contexts for each product as well (e.g. ProductADev, ProductAProd, ProductBDev, ProductBProd, etc.). We do this as some of our products have many iterations so it helps split them neatly.
I'm not sure what you mean about upgrades? Are you referring to the documentation or the RHS application and it's underlying platform? If you have another version of your documentation, just set-up another area on your context.
Thanks for your reply!
I am just wondering when it's time to upgrade RH server 9, how do we know if the upgrade will screw up production projects if we don't have a separate DEV enviroment to test it out?
also can a patch only apply to one context, and not impact other contexts?
Thanks a lot!
Ah OK now I've got you. Whilst it is normally advisable not to have two RHS versions installed on the same machine, you can do this. If it was possible to have a separate server, you could download the trial of the version and use that to test it out. The disadvantage is that you'd only have the trial period to work with. However if you planned ahead it should be sufficient to get a feel. This would prevent you having to buy a new licence until you were sure.
Oh and by the way a patch works across the entire installation (i.e. it affects all contexts).
Europe, Middle East and Africa