Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Altiris integration 2.0

Altiris integration 2.0

The Altiris integration is a one direction import of the Altiris data into ServiceNow CMDB (Configuration management database). The integration keeps the ServiceNow CMDB up to date with Altiris SQLServer database.

Note: Functionality described here requires the Integration - Altiris 2.0 plugin.

Data Import

Relevant data is imported from the Altiris database to the CMDB. The Altiris database is not written to, it is considered an authoritative source. The import is achieved using a JDBC connection via the MID Server.

Figure 1. Altiris integration application
Information pulled from Altiris includes:
  • PC Hardware (Model, Manufacturer, memory, clock speed, number of CPUs, etc.)
  • Operating System Information (Name, Service Pack)
  • Printers
  • Disk information (physical, network, and logical)
  • Network (IP Address, Netmask)

Configuration and Operational Modules

Enabling this integration will create the Integration - Altiris application.

The following are the configuration and operational modules for this integration.
  • Setup
    • Configure the data sources from one form
      • Provide the Database Server IP Address
      • Provide the Database Name
      • Provide the Database User ID and Password (this will need to be created on SQL DB side, see this article for help with this step:
      • Find and select the MID Server
    • Specify Database server settings and MID server
    • Test configuration
  • Scheduled Import
    • Schedule the execution of the import or import immediately
  • Data Sources
    • A list of the pre-configured data sources defining the external CMDB database
  • Progress
    • A historical list of progress on scheduled imports
  • Transform History
    • A historical list of transformations performed during scheduled imports
Warning: If you have activated an existing integration of the previous version:
  1. Activating the 2.0 plugin does not "add to" or "remove" anything from the existing integration.
  2. If transitioning from the old integration to this new one, considerations need to be given to customizations already done eg. mapping enhancements or using different coalesce values, these will have to be re-implemented.
  3. Both plugins could run at the same time, provided data is coalescing the same way - until there is no need for the older plugin at which time it can be turned off.

Supported Versions

The Altiris integration only supports Altiris version 6.5. The integration does not currently Altiris version 7.0.

Altiris import set data

This topic lists module names displayed by the Altiris import set data.

The Altiris import set data section shows a list of import set tables used in containing data retrieved from using JDBC to query the Altiris database. The module names (hence the import set tables they point to) match Altiris's table names and structure that it is loading from.

Module names

Note: Functionality described here requires the Integration - Altiris 2.0 plugin.
  • Scheduled Cleanup
    • Configure a schedule to cleanup/delete import set data that have already been transformed
  • vComputer
  • Inv_AeX_OS_Operating_System
  • Inv_AeX_HW_CPU
  • Inv_AeX_HW_Memory
  • Inv_AeX_HW_Serial_Number
  • Inv_AeX_HW_Logical_Disk
  • Inv_AeX_OS_Add_Remove_Programs
  • Inv_AeX_AC_TCPIP

When viewing each of these table lists, at the end of the list you have links to other operational functions of the import set.

Web services import set tables for Altiris

This topic will list the modules that define the web service import set tables - the schema for the import set tables that are receiving the JDBC import.

From each web service, you can add/remove fields as well as access the transform maps to make modifications.
Note: Functionality described here requires the Integration - Altiris 2.0 plugin.
Figure 3. Import set tables
Figure 4. Import set tables