Is it recommended to run CA ENF in the same MUF with CA 7?

book

Article ID: 129969

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server

Issue/Introduction

Many companies work to reduce the resource consumption for their applications, and one of the ways is to consolidate applications within an environment where possible.

Because CA Workload Automation CA 7® Edition (called CA 7) and CA Common Services/ENF (called ENF) both use a MUF for CA Datacom/AD, it it possible to run both applications in the same MUF?

Environment

Release: DATABB00200-14.0-Datacom/AD
Component:

Resolution

Even though the CA Datacom/AD MUF performs similar functions of data retrieval and maintenance for both CA 7 and ENF, the usage of these products indicates that they should not be run together. In addition, the documentation for ENF advises that the MUF be used only for ENF. In the installation documentation, in the section "Install, Configure, and Deploy CA Datacom/AD," it says:
For new and existing customers of CA Datacom/AD, each system running CAIENF requires a unique MUF used only for CAIENF.
The CAIENF event data is unique to each system. Sharing 
CA Datacom/AD MUF with other CA products is not practical for the following reasons:
  • Other CA products generally share data across systems using across system MUF.
  • Maintenance and backup might be a problem.
This means that while the typical CA 7 configuration supports the use of XCF to manage data from both the LPAR which is LOCAL to the MUF as well as those LPARs that are remote, ENF cannot support this, and must be configured to only use LOCAL mode for ENF data.

Another significant difference between the configurations needed for CA 7 and ENF is that since the data in ENF is transient and point-in-time, it is neither practical nor necessary to restore the data from a backup to be used with a forward recovery process. Consequently, the ENF MUF is configured to not use the logging recovery feature by using the MUF Startup Option LOGRCV NEVER. On the other hand, since the CA 7 data is perpetual, it is critical to capture any maintenance activity, and to be able to use logging transactions to recover to a particular point of failure. This is done through the use of the MUF Startup Option LOGRCV NO and accompanying processes to spill the logfile data to a recovery file.

Enabling transaction logging for ENF has shown that performance can be degraded due to the volume of database activity being tracked.

Finally, while a failure of the CA 7 application normally affects only that application, a failure that causes the CA Datacom/AD MUF to fail could cause ENF and other tasks on that LPAR to also fail, resulting in a significant outage. Isolating these applications helps ensure better performance and reliability of both applications.

Additional Information

As always, please contact CA Technologies support for CA Datacom if you have further questions.