This Knowledgebase article describes how to configure application Start/Stop Scripts when multiple and dependent Neverfail Application Modules are installed on a single server.
In some application environments protected by Neverfail Heartbeat, the stop scripts run by Neverfail Application Modules may need to be modified. This step is only required when there are multiple and dependant applications on a single server, particularly those applications that depend upon SQL Server to store configuration and state information.
In these cases, Application Modules are installed in a particular order; please refer to documentation for each product for the exact sequence. The Application Module install order is used to determine the startup sequence for the applications. For all applications that depend upon the Neverfail for SQL Server Application Module, this must be installed and therefore started first to ensure that the application that depends upon it can start successfully.
Problems Starting the Applications
If an application fails to start correctly then the most likely cause is that the Neverfail for SQL Server Application Module was not installed first and the dependent application was started first. Please consult the readme.txt in the application kit for details relevant to that application. To confirm the actual start sequence:
- Open the Neverfail Heartbeat Management Client and select the 'Application Manager' pane.
- Check that the first application listed is Neverfail for SQL Server.
- Check the 'Status' tab. This should show the results of the start commands.
- Confirm that the SQL Server services are being started last.
If the applications are listed in the wrong sequence, you should uninstall the Application Modules following the advice in Knowledgebase article #462 - 'How to Upgrade or Reinstall an Application Module to Protect Previously Unprotected Features' and install them in the correct order.
Problems Stopping the Applications
Applications are stopped in the same order they are started, so the first Application Module installed will be stopped first. In the majority of cases, including the example above, SQL Server will be stopped first, followed by BlackBerry Enterprise Server.
Applications that depend upon SQL Server do not expect the database to stop before it and in some cases, this can result in errors being logged to the relevant application log file, including the Windows Application Log. Neverfail Heartbeat provides a special utility designed to alleviate these dependency issues, nfnet.exe. It is similar in function to the standard Windows net.exe command with one exception, it identifies service dependencies and stops those services first. In cases where no explicit dependency is stated, then manual customization may be required.
- Open the following scripts in a text editor and replace the name of the affected application with the text ‘DependentApplication’.
- Copy all the stop commands from the dependent applications Stop Script and paste them into the SQL Server’s Stop.bat above the 'Stop' commands for the SQL Services.
Neverfail for BlackBerry Enterprise Server with Neverfail for SQL Server
Neverfail for BlackBerry Enterprise Server installed with the AM(X) for MobileMonitor
Neverfail for BlackBerry Enterprise Server with Neverfail for SQL Server and Neverfail for Lotus Domino
Neverfail for RightFax with Neverfail for SQL Server
Knowledgebase article #520
- Modifications Required When Neverfail for RightFax and Neverfail for SQL Server Are Installed on the Same Server
Knowledgebase article #1230 - Post Install Steps for Conceivium MobileMonitor AM(X) installed with Neverfail for BlackBerry Enterprise Server