Creating Redwood Platform Clusters

Using Redwood Platform cluster nodes you can create a web application cluster that has the same availability characteristics as the cluster.

Active/Passive

Configure each pair of active-passive nodes with the same hostname, that way you may use a single license for each pair. Both nodes of a pair should share a file system, which should be used to store data. You use the System_SetSystemDataRootDirectory process definition to set the storage location of process data.

note

Redwood recommends strongly against installing the software on a networked file system. If this recommendation is ignored, and you have random errors that Redwood believes are caused by the NAS (NFS or SMB share), that Redwood cannot reproduce on local storage, you will be required to demonstrate that the issue can be reproduced when installed on local storage. The resolution to this issue may require that you reinstall on local storage.

Active/Active

All nodes need to share the same database connection settings; they may share a filesystem, although it is not mandatory, it is highly recommended. Redwood Platform immediately detects that multiple nodes are serving the web application, all you have to do is install a license for all nodes.

Procedure

1. Deploy the web application on your application servers.
2. Start the application server housing the admin server on the first node and as usual, create the database objects. If you are using Redwood Platform, start the adminserver1 with the j2ee/cluster/adminserver1/bin/start.{bat|sh} shell script.
3. Stop the admin server once the database objects have been created (j2ee/cluster/adminserver1/bin/stop..{bat|sh.} on Redwood Platform) and start the application server housing the scheduler web application. If you are using Redwood Platform, start the server1 using the j2ee/cluster/server1/bin/start..{bat|.} shell script.
4. Once the scheduler web application has finished populating the database and has come up, login and install the license.
5. If you are running on MS Windows.
6. Shut down the application server if started and install a Windows service using the <install_dir>/j2ee/cluster/global/bin/rw_service.bat shell script.
7. Start the service, make sure the web application comes up properly and that you can log in, then stop the service again.
8. If you want an Active/Passive setup, fail-over to the other node and perform the last two steps for the new node.
9. Submit the process definition System_SetSystemDataRootDirectory with the parameter Directory pointing to the desired directory; note that for Active/Passive setups, this directory must reside on the shared filesystem.
10. Start additional application servers as required and install a license for each.

onsiteTopic