Backing Up CA SOI Components › Back Up Post Installation Configuration

Back Up Post Installation Configuration

If you want to restore your post-installation customization and configuration over an existing or new installation of the same release with all relevant maintenance applied, back up all custom data.

Follow these steps:

1. Back up the SOI_HOME\jsw\conf folders on all systems with CA SOI components installed. This folder includes files that define class paths and other properties for the JVM under which the product services run.

   Note: These files include information about system paths. If you are migrating to a new system and the CA SOI installation folder has changed, update the paths to reflect the new installation directory path.

2. Back up the following files and folders on all connector systems and the SA Manager (which always installs the IFW):
   • All connector policy files that you have customized located at SOI_HOME\resources\Core\Catalogpolicy
   • The SOI_HOME\resources directory, which contains IFW and connector configuration files in the Configurations directory and current and archived event records in the EventStore directory. Also, the log4j.xml file may have been updated to customize the diagnostic logging configuration.

     Note: SSA_IFW_servername.xml and eventManagerServerConfig.xml include hostname information related to the local host, connector hosts, and the ActiveMQ host for connector and SA Manager communications. If you are migrating to a new system, update this information to reflect changes in hostname. You must also update all individual connector configuration files to include the proper hostname.

3. Back up the following data if you have installed CA Event Integration to use the Event connector:
   • The EMAADB database using the standard Microsoft SQL Server backup procedure
   • The EI_HOME\manager directory on the CA Event Integration manager system, which contains all adaptors, associated catalogs, and policy files
4. Back up the following data on the SA Manager (or all SA Manager systems in a multi-tiered deployment):
   • The SAMStore database using the standard Microsoft SQL Server backup procedure
   • All scripts or executables that run as part of escalation or enrichment actions
   • The SOI_HOME\tomcat\custom directory, which contains files with help desk, CA Process Automation, email, and other connection settings

     Note: If you are moving the installation to another system, set the email host (mailhost) for the email server connection in the Windows\system 32\drivers\etc\hosts file on the new system. If you use the usm_web_view_cfg.xml or mobile_ui_srvr_cfg.xml files when defining help desk properties, you must change the host name if you are moving the UI Server installation.

   • The SOI_HOME\tomcat\webapps\sam\eem-config.xml file to save the CA EEM configuration settings
   • The SOI_HOME\jsw\bin\sam_topo_images directory if you have added custom images to the service topology views
   • The following CA Catalyst Registry files located at SOI_HOME\tomcat\registry\topology\physical\node0\sor if you have customized them in the file system:

     Note: If you have updated Registry files in the Registry Administration UI, they are backed up with the database. Several of the files contain connection settings that you must update if you are moving the installation to a different system.

     • ssaserver.xml file (default reconciliation formula, contains connection settings)
     • defaultsheet.xml file (property-specific reconciliation formulas)
     • singlesourceoftruthmdr.xml file (single source of truth, contains connection settings)
     • sorapp.xml and plancontrol.xml (synchronization, contains connection settings)
     • ssaweb.xml file (USM Web View connectivity properties)
     • ucf-broker.properties.xml (UCF Broker properties)
5. (Optional) Run the following command from SOI_HOME\plugin\ServiceDiscovery\bin in a command prompt if you want to back up defined service discovery policies:

   read_rules_from_db.bat filename.xml
   

   All service discovery policies are saved to the specified XML file. The policies reside in the database and should be backed up with the database. However, you can back up the service discovery policies to a file for extra protection or if you want to reload the database.

6. (Optional) Back up the SOI_HOME\plugin\UniversalConnector conf and jsw folders if you are using the Universal connector.
7. Back up the following data on all UI Server systems:
   • The SOI_HOME\SamUI\conf\soi_conf \mobile.properties file if you have changed any Mobile Dashboard connection or timeout properties
   • The SOI_HOME\SamUI\webapps\mobile directory if you have customized the Mobile Dashboard metric icons or performed a custom standalone Mobile Dashboard implementation
   • The SOI_HOME\SamUI\webapps\mobile_extra_style.css file if you have customized the Mobile Dashboard display
   • The SOI_HOME\SamUI\webapps\sam\eem-config.xml file to save the CA EEM configuration settings
   • The SOI_HOME\SamUI\custom\email-config.xml file to save the email server configuration for the Operations Console

     Note: If you are moving the installation to another system, set the email host (mailhost) in the Windows\system 32\drivers\etc\hosts file on the new system.

   • The SOI_HOME\SamUI\custom\common\config\custom-jnlp-config.xml file to save changes in the JNLP configuration
   • The SOI_HOME\SamUI\custom\console\config\custom-menu-config.xml if you customized the Operations Console menu
   • The SOI_HOME\SamUI\webapps\sam\thinuiconf\custom_metric_definition.xml file if you added custom metrics to the Dashboard
   • The SOI_HOME\SamUI\webapps\sam\thinuiconf\tables_definition.xml file if you customized the service hierarchy on the Dashboard
   • The SOI_HOME\SamUI\webapps\sam\ui\refresh.properties file if you customized the dashboard refresh rate
   • Any custom images in the SOI_HOME\SamUI\webapps\sam\ui\images directory if you customized the dashboard logo
   • Any custom PNG file in the SamUI\webapps directory if you configured a custom Mobile Dashboard logo
   • The SOI_HOME\SamUI\webapps\sam\WEB-INF\console\config\custom-menu-config.xml file if you added custom Dashboard links
8. (Optional) Back up CA Business Intelligence and reporting systems by following the backup procedures documented in the SAP BusinessObjects documentation.
9. Follow the backup procedures documented in the CA EEM Getting Started Guide, including how to back up CA EEM data in CA Directory.