Importing WorldServer objects from the user interface

After you have exported a file that contains WorldServer objects, import it into another instance of WorldServer.

Before you begin

When you import objects, WorldServer does not import the custom components referenced by those objects with them. For example, if you want to import a workflow that contains custom automatic actions, you need to add or import those custom automatic actions from Management > Administration > Customization before you import the actual workflow.

Moreover, certain dependencies related to access control lists (ACLs) that do not exist in the target environment (such as users, workgroups, workflow rules, and clients) are not exported. You need to add those dependencies or import them separately into the target environment.

Before you import AIS properties into a new environment, you need to configure their corresponding mount on that environment. The import process does not create the mount for you.

Procedure

  1. In WorldServer, go to Management > Administration > Import Objects.
  2. Upload the .tml file that you want to import by selecting Browse, locating it, and then selecting Upload File.
    The primary objects included in the file are displayed in a tree. The overwrite value in the Action column indicates that the object already exists on that WorldServer instance; you will overwrite the existing object if you import it again.
  3. Select the check boxes next to the objects you want to import, and then select Next.
  4. On the Import Objects - Step 2 of 2 page, next to Import Options, select one of the available import options 1:
    • If you select Include missing referenced objects, WorldServer displays only the objects that are referenced by the primary object you selected and that are missing from your server.
    • If you select Include all referenced objects, WorldServer displays all the objects that are referenced by the primary objects you selected2.
  5. Select Import.
    The objects imported successfully are displayed in a new window. If there are any objects that could not be imported, the import log provides a reason for this.
1 WorldServer automatically analyzes the list of objects when the page is loaded and when you change the import option. The analysis searches for the following conditions:
  • A primary object references a dependent object which is neither in the file, nor in the target system.
  • A referenced object references a dependent object which is neither in the file, nor in the target system.
If it finds any of these conditions, you cannot import the objects. The Import button is not available, the tree with all the objects is hidden, and the page displays a list of object with errors.
2 If you import clients by selecting Include all referenced objects, the WorldServer overwrites the configurations of default user types, which means that permissions are also changed according to the configurations you imported.