Securing CA NSM › Integrating with eTrust Access Control › How Integration and Migration Works

How Integration and Migration Works

eTrust AC r8 provides automatic integration with CA NSM using options when you install eTrust AC. You must install eTrust AC r8 before you attempt to migrate CA NSM 3.x security. After you migrate CA NSM 3.x security, you can install CA NSM r11.x.

• On Windows, eTrust AC automatically migrates CA NSM 3.x data during eTrust AC installation if the "Migrate Unicenter Security data to eTrust Access Control" option is selected.
• On UNIX and Linux, you must install the Unicenter Integration and Migration package and then run the migration scripts.
• Once the integration and migration process completes successfully, CA NSM login intercepts are disabled (but not removed), and no longer used. However, logon and file protection intercepts are removed when you migrate CA NSM 3.x to CA NSM r11.x.
• After migration on Windows, CA NSM 3.x Security Management is disabled and can no longer be started.
• After migration on UNIX and Linux, a gateway daemon called sessfgate is installed and activated. Sessfgate processes the CA NSM security API (EMSec) requests sent through the CA NSM security message queue and routes these reformatted and rerouted requests to eTrust AC. eTrust AC return codes are translated to the CA NSM equivalents. This process protects the integrity of existing applications that are currently using the EMSec API.

  If the CA Event Notification Facility (CAIENF) is running, sessfgate is automatically started or stopped whenever the eTrust AC services are started or stopped. If CAIENF is not running, eTrust AC does not start the sessfgate daemon. You must start it manually.

  Note: After CA NSM Security Management is disabled and eTrust AC is started, the sessfgate daemon can accept API requests instead of the Secure Sockets Facility (SSF).

• On Windows, the EMSec API requests channel calls into the CAUSECR.DLL. This DLL is replaced during the integration process. The new DLL receives calls to the EMSec APIs, and then reformats and redirects these requests to equivalent eTrust AC APIs. The return code from the eTrust AC APIs are converted back into their corresponding EMSec API return codes and control is returned to the caller of the EMSec API. This approach protects the integrity of existing applications that are currently using the EMSec API.
• CA NSM 3.x asset types are pre-loaded during eTrust AC r8 installation. After the migration, CA NSM 3.x assets are protected by eTrust AC.
• eTrust AC provides programs that extract data from the CA NSM 3.x Security database and translate it into eTrust AC commands that populate the eTrust AC database. The following data is migrated:
  • CA NSM Security users
  • CA NSM Security user groups
  • CA NSM Security rules
  • CA NSM Security assetgroups