Originally posted by: TimUK
We have a production environment on Windows 2000 that operates in a cluster.
In essence we install WTX launcher on each nodes local disk. All maps and systems and runtime material is then installed on the drive thats swings.
There is a setting in the .ini file to specify a cluster directory (on the swing device).
Another setting on the advance tab of the launcher admin tool specifies an RMI server address - its documented in the Infocentre.
The Event Server is then specified in the server cluster administration (MSCS in our case) and the failover criteria set. The service is alsways started and stopped from there.
It does get more complicated than that when you add other installs on the server such as MQ Series or a database as each product has its own oddities and they need to work together.
We have set up an active/passive scenario as that suits us but it has its downsides. When OS or software products need patching it may not be possible to do one node at a time. Certainly thats the case with Oracle database as the patches often affect the data dictionary which has to be stored on the shared drive.
From a performance perspective failover is pretty quick (<90secs) when at full tilt. It does depend on your requirements though. This design is not sufficent on its own if you want faster failover.
Hope that heelps
Tim
#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender#DataExchange