Importing CI relationships from SQL databases
You can import the CI relationships into FootPrints from an external Microsoft SQL server database that has both encrypted and non-encrypted connections.
For more information about importing CIs, see Importing CIs from SQL databases.
To import CI relationships from a SQL database
- Click the Administration tab.
- In the System Management section, click Import.
The Task Scheduler page appears, showing a list of scheduled tasks and their status.
- Click New Task, and select Import Task > CI Relationships.
The Import CI Relationships page appears, showing the Source Type pane.
- In the Source Type field, select SQL Database.
- In the left pane, click Source Configuration.
- In the Source Configuration pane, complete the following fields:
- In the Server Address field, enter the IP address or the name of the SQL server for this import task.
- In the Server Port field, enter the port number for the server.
- In the Database Type field, select the appropriate option:
- Sql Server
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=falseparameter and restart the Tomcat service.
- In the Database field, enter the name of the source database.
- In the Server User ID and Server Password fields, enter the credentials for logging in to this server.
- Click Test Connection.
- In the left pane, click Data Destination.
- In the Data Destination pane, in the Import into CMDB field, select the CMDB where you want to import the relationships.
- In the left pane, click Map Fields.
- In the map field pane, complete the following fields:
- In the Table or view field, select the location of the CI data that you are importing.
- In the Relationship for import section, select whether to specify a relationship or use the one identified in the source data:
- To select a relationship, in the Specify Relationship field, select a relationship type.
- To use a relationship identified in the source data, select Use Relationship Specified in Source and select the source field.
The second option lets you to select multiple relationships for a single import file.
- In the From CI Identifiers section, perform the following actions:
- Click Add.
- Select a Source Field and an Attribute.
- Click Update.
In the To CI Identifiers section, perform the following actions:
- Click Add.
- Select a Target Field and an Attribute.
- Click Update.
- To edit a From CI or To CI Identifier entry, click the pencil icon next to it.
- To delete a From CI or To CI Identifier entry, select it and click either the Delete button or the red X at the right of the entry. A confirmation message appears. Click Yes.
- In the left pane, click Schedule Task.
The Schedule Task pane appears.
- In the Schedule Task pane, complete the fields:
- In the Task Name field, enter a specific name for this task.
- (Optional) In the Notes field, enter any useful information about this task.
- (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. Separate multiple user names and email addresses with semicolons. A notification is sent about the import outcome and includes results, task name, date, and so on. The notification also includes the number of records that were rejected, created, updated, and unchanged.
- (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.
- 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.