Importing items into your database

You can import items that you have exported from one Ivanti database into another Ivanti database.

We strongly recommend that you take a backup of your database before you import items into your database.

Sometimes, the new metadata added by the Design Transfer files may need to link to your existing metadata, which may cause problems. In this case, you will have to do some further design work specific to your implementation before you can use these features.

The two most likely issues with Design Transfer are when it tries to:

  • import metadata that already exists in your system, or
  • import metadata that refers to items assumed to exist in your system, but which are actually missing from your system

For example, if the design you are importing needs a specific object in the System Management module, then there are two options for Design Transfer:

  • it can assume that it needs to import this object.
    However, if your database already includes an object with this name, you need to choose how to handle this. In this instance, we recommend noting these sorts of messages and choosing NOT to import the new object, so that the system uses your existing object. You can then investigate this area of the design and fix it as appropriate.
  • it can assume that the object is already in the database.
    However, if the object is not in the database, you will need to create it as a separate piece of work to complete the design.

You cannot update existing process designs using Design Transfer.

To import into your database:
  1. Start the Design Transfer component.
  2. Expand the Import tree ().
  3. On the Actions list, click Open Import File.
    The Open dialog appears.
  4. Locate the file that you want to import.
  5. This will be a file that you have exported using the Design Transfer component. It will be in an XML format.
  6. Click Open.
    You may be prompted to make some decisions.

Referenced object missing – This appears where the business object that you are importing has a link to a business object that does not exist within either the target system or in the file you that are importing. You have to choose to either select an existing object from the list, or leave the value not set.

Process privilege mismatch – This appears when the process that the privilege is connected to does not exist within either the target system or in the file that you are importing. You have to choose to either discard the privilege or select an existing process from the list.)

Object modification is restricted – This appears when you are trying to import an object that already exists within your database but which cannot be modified. These include Windows and Queries. You have to choose to either not create a new business object and to keep the existing business object, or to update the existing business object with the changes.

Object conflict in system – This appears when the target system contains an object that has values that conflict with those of an object that you are importing. For example, a business object has the name ABC and you are importing another business object with the name ABC, but the primary keys are different. You have to choose to either not create a new business object and to keep the existing business object, or to update the existing business object with the changes.

Attempted import of deleted object – This appears when the business object has been ‘soft’ deleted from your database. This means that the business object information still exists within your database. You have to choose to either create a new business object with a modified title, or to not create a new business object.

If you are not prompted for any decisions, the file is imported.

If you are prompted for decisions, make them, then on the Actions list, click Import.

When the import is complete, a message Import completed successfully appears.

  1. Click OK to close the message box.