CA Embedded Entitlements Manager (EEM) can be configured for Server failover which automatically routes requests to a secondary EEM Server when the primary EEM server is not available. However, for this configuration to function properly, an initial connection must first be established with the primary EEM server. Some applications, such as CA Process Automation (formerly CA IT Process Automation Manager or CA IT PAM ), CA Service Catalog, CA AutoSys and others, allow multiple EEM servers to be listed. This enables those EEM servers to be rotated if the initial connection is not established, however, for the purposes of Disaster Recovery (DR - or if you want to move an EEM Application to a different server - you will need to backup up the existing EEM Application Instance and restore it onto a new server. This document provides procedures and best practices for performing this action. Note: The steps outlined in this document only apply to the backup and restore of individual EEM Application instances. They are not designed to handle multiple application instances To backup and restore an EEM Application Instance do the following: 1. Obtain the following information for the EEM Application Instance that is being backed up: Eiam Admin User ID and Password. User defaults to EiamAdmin if not specified. EEM Server name. Defaults to your local hostname Application Instance Name. 2. Download the EEM_Export_Import.zip and extract the contents to a folder on your EEM Server. Here you can see the contents of the EEM_Export_Import.zip file: 3. Determine if the application instance has a certificate file associated with it. CA Process Automation uses a certificate file which is created when the application instance is created. If it does, you must copy that certificate file or generate a new one. For example for CA Process Automation, the certificate is itpamcert.p12. Note: If you are restoring an ITPAM instance to a different EEM server, you will have to regenerate this certificate. Please review the CA Process Automation Certificate section for details on how to generate this certificate. 4. Execute the eem_safex command to export the EEM instance.
For example: Cd /d <resourcekit_dir> eem_safex.cmd -mexport p<eiamadmin_password> - a<application_instance_name> -e<eem_servername> Here you can see an example of the command results: In this example, the CA Spectrum Service Assurance Application Instance SSA- SQLVIRTUAL will be backed up. To view the supported syntax for this command execute it using the h switch. For example:
Important! The specified EEM Application Instance must already exist for the export to work. If it does not, the EEM utility will abend as no validation is performed. 5. To restore the Application Instance to a different EEM server, execute the EEM_safex.cmd script using Import mode and point the e switch to your DR server. For example: Cd /d <resourcekit_dir> eem_safex.cmd -mimport p<eiamadmin_password> -e<new_eemservername> - r<yes No> Specify ryes to delete the Application Instance from your new EEM server prior to import. If you specify rno or if the r switch is not specified, the Application Instance will not be deleted prior to import. 6. If the global settings were also exported (backup), then you need to update the password for the external directory binding as shown in the Global Settings section
If you wish export your global settings, such as external directory configuration, as well, then set the g switch to Yes. Note that, for security reasons, the password value will not be exported. Therefore, if you set the g switch to Yes after import (restore) application instance, you must launch the Eiam GUI and set the password for the external directory binding. To set the password for EEM external directory configuration, do the following: 1. Launch the CA EEM UI https://localhost:5250/spin/eiam/eiam.csp 2. Select <Global> application, enter your EiamAdmin password and click Login. 3. Select the Configure Tab. 4. Select the EEM Server subtab: 5. Select Global Users / Global Groups from the right pane.
6. Provide the external directory bind password and Click Save 7. Verify that the bind was successful CA Process Automation (formerly, CA IT Process Automation or CA IT PAM) uses certificates for EEM Authentication. The itpamcert.p12 certificate is generated when the ITPAM instance is created and is copied to the EEM ITechnology folder. The CA Process Automation installer also copies file to the following CA Process Automation folder: Program Files\CA\ITPAM\server\c2o\.c2orepository\public\certification If the Application Instance ITPAM is being restored to a different EEM server, CA Process Automation authentication will fail unless the itpamcert.p12 is regenerated from the new server and copied to the new server s itechnology folder and the certificate is replaced in the in the CA Process Automation folder (noted above). Note: The certificate will only be generated when the application instance is created. If the ITPAM application instance already exists, the certificate it will not be generated. If you are restoring an ITPAM application instance to a different EEM Server you must generate the certificate prior to restoring the ITPAM application instance. To generate itpamcert.p12 certificate do the following: 1. Cd to the EEM_Export_Import folder 2. Review the Templates\template_itpam_cert.xml file and verify that the password is correct. Since the file lists the default password if you have previously changed the password, you must then update the password in this template file. 3. Execute the eem_itpam_cert.cmd script. This will display usage information.
Here you can see that the itpamcert.p12 file has been generated by temporarily creating the ITPAM application instance and then de-registers or deletes it (to allow for clean restore) 4. Copy the itpamcert.p12 file to your itechnology folder. This location of this folder is displayed on your usage information 5. Replace your CA Process Automation manager folder itpamcert.p12 file. The default location for this is: C:\Program Files\CA\ITPAM\server\c2o\.c2orepository\public\certification 6. Restore the ITPAM application instance
Here you can see examples of several Application Instances that were imported from a different EEM Server: This example depicts the following instances: <Global>: Registered when CA EEM is installed. CAELM: CA Enterprise Log Manager (CA ELM) Application Instance registered when CA EEM is installed. SSA-SQLVIRTUAL: CA Spectrum Service Assurance (CA Spectrum SA) Application Instance Name. The name does vary as it is a configurable option in CA Spectrum SA. ITPAM: CA Process Automation Manager Instance Name. Note this requires that the itpamcert.p12 file be copied as well. Service Catalog: CA Service Catalog Application Instance Name. AIP CA Spectrum Automation Manager Application Instance CAACM CA Application Configuration Manager Instance Spectrum CA Spectrum IM Application Instance