This Knowledgebase article provides information about how to install an AMX (Application Module Extension) post installation of Neverfail Heartbeat (prior to Neverfail Heartbeat V4.4).
This Knowledgebase article applies to versions prior to Neverfail Heartbeat V4.4 only.
Note: Dependency checking is only done when an AM(X) is installed at Neverfail install time where all services are known and the dependencies can be checked. If any service(s) are added post install via an AM(X) script, then Neverfail recommends checking for dependant services via the Service Control Manager. If dependencies exist, then move the entry for the new service in the start script so that it appears after the service it depends upon. You should also check that the stop script stops the newly added service before the service it is dependant upon.
- Check File System Status and Registry Status are both ‘Synchronized’. From the Neverfail Heartbeat Management Client on the Primary-active server, click the Shutdown button.
- Select 'Exit Neverfail Heartbeat but leave protected applications running’ and click OK .
- Start the Neverfail Configuration wizard, select the 'License' tab, and enter the new license key. Apply changes and exit.
- On the Primary server, double-click on the AMX script and follow any on screen instructions.
- Start Neverfail Heartbeat on both Primary and Secondary servers.
- From the Neverfail Heartbeat Management Client, check that any new File Filters for the Application have been added as expected.
- On the Primary server, copy the Start and Stop scripts from c:\neverfail\r2\scripts\application_name into C:\Protected.
From C:\Protected on the Secondary Passive server, copy the new Start/Stop scripts into c:\neverfail\r2\script\application_name. See Note
Note: For WAN installations, the start stop scripts may differ because of DNS specific commands. It may be advisable in those instances to paste the new commands into the scripts on the Secondary server.
Neverfail Heartbeat prior to V4.4