Importing HiPer Objects

Important: Before you import objects, consider the following:

To import HiPer objects from an migration file:

  1. Select Import. A new text box and button display allowing you to upload the migration file.

  2. Click Browse and select the migration file.

  3. Click Continue.

  4. After the migration file is uploaded, the objects included in the file are listed under their appropriate object types. If the object was stored in a subfolder (for example, system notifications are stored in the System Notifications folder), the folder and path are listed.
    Note:
    If the subfolders do not already exist, they will be create automatically.

    If the object has any dependent objects they are listed under the parent object. The dependent objects are also listed under their appropriate object types, but their check boxes are disabled (since you must import dependent objects with their parents).

    If you do not want to import a particular object, select it and click Remove next to its object type.
    Note:
    You cannot remove dependent objects (their check boxes are disabled). If you remove a parent object, the dependent objects are automatically removed (unless the objects are still dependencies for other selected objects).

  5. When you are ready to import objects, click OK.

  6. After the objects have been imported, the import status displays. Read through the status carefully to understand what actions were taken and if there is anything more you must do (for example, if you import a rule that does not exist in the target HiPer BAM System, the import status informs you that you must recreate the rule in the BAM system). Remember that you must reassociate users with any imported system notifications.
    Important:
    If any objects fails, the entire import is aborted.