Note: This product is no longer available or supported.
This Knowledgebase article explains the protection offered by this particular AM(X). There is a sister article ( Knowledgebase article #873 - 'Omega Legal - Application Module eXtension - Versions') that lists all the versions of the AM(X). In addition, there are links from that sister article to (usually brief) articles that explain the unique features of each version.
Omega Legal is a time, billing, and accounting and case management software system. The AM(X) protects the services, registry, and data associated with the application
This is a list of all services protected by this AM(X). Please note that where an AM(X) supports multiple vendor versions, some services may not be present in a particular version.
- Cache Controller for Cache (Cache_c-_cachesys)
When the AMX is installed, all protected services will be set to manual unless otherwise stated.
This is a description of the protected data set; exact filters are based upon the configuration of the system at install time. If the configuration is changed post Heartbeat installation then the AM(X) will need to be re-installed.
- Registry data relating to the following applications; Omega Legal, Cache, and Borland software.
- Cache configuration and namespaces present at install time.
- The following cache data: VB Template Library, Cache Journal, User folder.
Automatic Filter Discovery
This AM(X) product does not provide an automatic filter discovery component. If the location of the protected data changes then the AM(X) must be reinstalled following advice in Knowledgebase article #462 - 'How to Upgrade or Reinstall an Application Module to Protect Previously Unprotected Features'.
Post Install Customization
In accordance with advice in the Omega documentation, the Omega namespace database must be started and stopped using a command that will perform integrity checks on the data. This may increase the time taken to perform a switchover or failover. The time taken will depend upon the size of the database being protected; typical times may be between 20 minutes to one hour. To accommodate this, configure the application time out in the Neverfail Management Client to a value suited to the Omega installation.
Please refer to the ReadMe.txt in the kit and the Neverfail product documentation on how to perform this configuration change.