Thanks Dave for your prompt response…Is there any limitation or constraints we need to be worry about when setting the maximum heap size for Rhythmyx server. Again it is a LINUX box on which we are running the Rhythmyx server.
To the best of my knowledge the same restrictions on heap size apply to 6.7 like they did on previous versions. When the JVM max memory is set to anything higher than 1536MB, Rhythmyx server may not be stable or even refuse to start at all. I believe this limitation aplies to all platforms. The setting can be changed in <rx_root>\RhythmyxServer.lax under LAX.NL.JAVA.OPTION.ADDITIONAL where the -Xmx parameter is set.
Since we are a Windows shop here, I’m going to take a chance and say that they are probably equivalent. EXE(Windows) and BIN(*nix) indicate that the file can typically be “executed” as a process. As for an “exe” on Linux - shouldn’t matter. Try taking any “executable” file in Linux and append “.exe” to it and it should still behave the same.