Importing CIs from SQL databases

You can import configuration items (CIs) and CI relationships into FootPrints from an external Microsoft SQL server database that has both encrypted and non-encrypted connections. You can populate the Assignment type field values with users or teams. If you want to import multiple values for the Assignment type field, the values must be separated by a semi-colon (;), for example, User1;User2;Team3. For more information about importing CI relationships, see Importing CI relationships from SQL databases.


You cannot import users for the Assignment field in the following format:

To import CIs

  1. Click the Administration tab.
  2. In the System Management section, click Import.
    The Task Scheduler page appears, showing a list of scheduled tasks and their status. 
  3. Click New Task and select Import Task > Configuration Items.
    The Import CI page appears, showing the Source Type pane.
  4. In the Source Type field, select SQL Database.
  5. In the left pane, click Source Configuration.
  6. In the Source Configuration pane, complete the following fields:
    1. In the Server Address field, enter the IP address or the name of the SQL server for this import task.
    2. In the Server Port field, enter the port number for the server.
    3. In the Database Type field, select an appropriate option: 
      • Sql Server
      • Postgres.
    4. If you select Database Type as Sql Server, in the External DB Security Type field, select an appropriate option:

      • For non-encrypted connection: None

      • For encrypted connection: SSL Connection (Default certificate)


        To complete the encrypted connection configuration, on the Java tab (C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin > Tomcat7w.exe), you must enter the -Djsse.enableCBCProtection=false parameter and restart the Tomcat service.

    5. In the Database field, enter the name of the source database.
    6. In the Server User ID and Server Password fields, enter the credentials needed to access the data source server.
    7. Click Test Connection.
  7. In the left pane, click Data Destination.
  8. In the Data Destination pane, complete the following fields:
    1. In the Import into CMDB field, select the CMDB where you want to import the CIs.
    2. (Optional) To search existing contacts for matches and link the imported CIs to them:
      1. Select Link imported CIs to matching entries in address book checkbox.
      2. In the Address Book field, select from the address books associated with the selected CMDB.
      3. In the Contact Type field, select the appropriate contact type.
  9. In the left pane, click Map Fields.
  10. In the Map Fields pane, complete the follwoing fields:
    1. In the Table or view field, select the location of the CI data that you are importing.
    2. If you selected to link the imported CIs to an address book, the Link to Address Book section appears. Complete the fields:
      1. In Map data source field, select the source field that you want to map.
      2. In To this Address Book field, select the target field in the Address Book.
    3. In the Map CI Type Rules section, perform the following steps:
      1. In the Default CI Type field, select from the CI types defined for the selected CMDB and click Add.
      2. If you want to customize the import process, perform steps iii through vi. If you want to use the default import process, continue with step 10d.
        With the default process, all CIs are assigned the default type.
      3. Click Add and in the If Column field, select a condition.
      4. In the Contains Text field, type the text to match.
      5. In the Set CI Type as field, select a CI Type.
      6. Click Update.
      7. Repeat steps i through vi to add as many rules as you need.
    4. In the Map Attributes section, perform the following steps:
      1. Click Add.
        Select values for Attribute and Source Field. You must map at least one attribute.
        The available values are based on selections already made on this pane.
    5. In the Status for all CIs field, select the initial status for the uploaded CIs.
    6. (Optional) To update existing CIs, select Update the Status for existing CIs.
    7. In the Unique Key field, select the fields in the Source Columns list that are used as unique keys and move them to the Unique Key list.
  11. In the left pane, click Schedule Task.
  12. In the Schedule Task pane, complete the following fields:

    1. In the Task Name field, enter a specific name for this task.

    2. (Optional) In the Notes field, enter any useful information about this task.

    3. (Optional) In the Notify by Email field, enter the email addresses of anyone who should be notified when this task runs.
      You can also enter an agent's user name to send notification to the agent's primary email address. You can enter multiple user names and email addresses with semicolons. A notification is sent about import outcome and includes results, task name, date, and so on. The notification includes the number of records that were rejected, created, updated, and unchanged.

    4. (Optional) Select whether to run this task immediately or at a specific time, and whether and when to run it again.

      If you do not select any settings, the task will only run manually. For more information, see Scheduling tasks.
  13. Click Schedule Task.
    Your selections are validated by the system. If no errors are found, the Task Schedule page appears. Local files that won't change between scheduling and running are validated immediately. Web and network server files are validated at run-time. Next Run Time is the next or first time a task will be run.

Next step

To import the relationships for these CIs, follow the instructions provided in Importing CI relationships from SQL databases.

Related topics

Viewing task logs

Importing CIs from CSV files

Importing CIs from BMC Client Management

Importing CI relationships from CSV files

Importing CI relationships from BMC Client Management

Working with mappings

Was this page helpful? Yes No Submitting... Thank you