Anonymousprnt::Y
Click on images to see them in full screen

Clustering

Installing smsPULSE in a Domino Server Cluster

smsPULSE may be configured to Work in a Domino Server cluster. As a general rule, smsPULSE will rely on the Domino clustering to ensure the databases are synchronised and that the load is balanced. In the event that one of the smsPULSE servers goes off-line, the other cluster member must be started by issuing a single console command. The secondary server must be shut down when the primary smsPULSE server is reinstated.

Please note that if you use smsPULSE in a cluster environment, the secondary smsPULSE server requires a Disaster Recovery (DR) license.

Installation of smsPULSE in a Domino Cluster

  1. Install smsPULSE on your first server (one of your cluster members). This will be regarded as the smsPULSE Primary server
  2. Make sure that the "smspulse" task is listed in the server's notes.ini "tasks" list so that it starts automatically (you should not list smsrouter and smslines). Please note that the smsPULSE setup program will normally do this for you
  3. Run smsPULSE on the primary server and allow it to create all its databases. It is recommended that smsPULSE is licensed and fully operational before you proceed with the installation of the secondary server
  4. Create replicas of all the databases on another cluster member (call this the smsPULSE Secondary server). Ensure you maintain the same directory name (ie all the smsPULSE DBs are stored in the smspulse directory, off the data directory)
  5. Replicate the databases and ensure that all the databases are fully initialized on the Secondary server
  6. On the secondary server, shut the Domino server and install the same version of smsPULSE
  7. Edit the notes.ini on the secondary server and remove the "smspulse" task from the tasks list
  8. You should now also copy the smsPULSE registration and license files to the secondary server (smspulse.reg and smspulse.lic). The files should be placed in the Domino data directory
  9. Start the Domino server
You are now done.

Testing the Secondary server
It is recommended that you do the following after installation:
  1. Shut all the smsPULSE tasks on the smsPULSE Primary server. Type "tell smspulse ab" on the server console (ab stands for abort)
  2. Start the smsPULSE Secondary server by typing "load smspulse"
  3. smsPULSE should start and start broadcasting messages
  4. When you have confirmed that the secondary server is operational, shut it down - type "tell smspulse ab"
  5. Start smsPULSE on the primary server to resume normal operations

When the Primary server fails
In such an event, you will get a notification by the cluster monitor.
  1. If the Primary server can be restarted quickly, simply start it and take no further actions
  2. If the Primary server is not likely to recover quickly, start the smsPULSE tasks on the secondary server by typing "load smspulse" on the server console
  3. When the Primary server is operational again, shut the smsPULSE Secondary server which you have started manually above. Type "te smspulse ab" on the secondary
  4. Start smsPULSE on the Primary server

Using a GSM devices or a GSM Array
If you use any of these devices you will need to physically move them from one server to the other. However, you may wish to consider using a COM server which becomes available on your cluster network over IP. In such a case, the devices may remain where they are but the COM server client must be started manually on the secondary server before the COM ports become visible on the smsPULSE Secondary server.