In working with Miguel and R&D, it appears wsstack isn’t designed for clustering. However, we’d like to pursue possible options that we were provided from R&D feedback.
Our options are:
We could use a shared filesystem for these items so that any addition or change on one server will be immediately available on the other. This assumes that the application doesn’t lock the files or maintain any state information about the files. It also assumes that the app doesn’t index or track the files in any way.
We could also set up a nightly (or other interval) synchronization process that copies the files from one server to the other. This also assumes that the app doesn’t index or track the files in any way and can recognize updates or changes immediately.
Our questions in order to know which one is preferable:
Does the WSStack application lock the files or maintain any state information about the files?
Does it index or track the files in any way?
Can it recognize updates or changes immediately?
This will help us choose either:
- Shared filesystem
- Synchronization job between two separate filesystems.
-
Neither option being feasible.
Thanks in advance!
-Brian
#webMethods#EntireX#Mainframe-Integration