View the earlier version.Version 7.10

The third step in the alarm import process (after selecting a zip file and selecting the alarms to be imported) is to map the source environment information with the destination environment. During the alarm export process, if the alarm in the source environment was configured to monitor BizTalk server, SQL servers, SQL Server Instances and all of their associated artifacts, then it is mandatory to set up the mapping in the destination environment.

For the purpose of understanding the process better, let's consider the source environment to be ACME and the destination environment to be ACME-QA

Please note that we will be using the above two environment names throughout the Export/Import functionality documentation sections.

Say, the alarm in the source environment was configured to monitor the BizTalk Server, SQL Server, and SQL Server Instances and their associated artifacts. In the Map Environment screen, you can choose to map these source alarm configurations to one of the available environments in the destination environment.


Let's take a deep dive into the map environment screen.


  1. Navigation Menu - This menu displays the current step that is visible to the user
  2. Environment Details - Displays the name of the Source Environment and Destination Environment. The Source environment is the environment that was selected during the alarm export process. The Destination environment is the environment that is currently selected during the import process
  3. BizTalk Servers - Map the BizTalk server configuration in the import file to the destination environment. In this section, all you need to do is to select the BizTalk server from the drop down where you want to import the configuration information
  4. SQL Servers - Map the SQL server configuration in the import file to the destination environment. In this section, all you need to do is to select the SQL server from the drop down where you want to import the configuration information
  5. SQL Server Instances - Map the SQL Server instances configuration in the import file to the destination environment. In this section, all you need to do is to select the SQL server instance (if available in the environment)
  6. If your exported alarm was configured to monitor the applications and its associated artifacts, even these configuration information will get imported into the destination environment. However, you can view this information only in the next screen - Import Summary screen
    If there are no BizTalk server/SQL server/SQL server instance configuration found in the alarm export file, you will see a notification message as " There are no BizTalk Server(s)/SQL Server(s)/SQL Server Instance(s) configuration found in the import file
  7. General Guideline - All the screens in the alarm import process will have this general guideline section. This will provide information about the operations that can be performed in the current screen
  8. Next - Click Next to proceed to the next step of alarm import process
  9. Back - Navigates to the 'Select Alarms' section
  10. Cancel Import - Cancel's the import operation. The system will prompt "Are you sure you want to cancel Import process?". Click Yes to cancel the alarm import process. You will be redirected to the manage alarms page. Click No to continue the alarm import process