Documentation Center

Importing WorldServer objects

After you have exported WorldServer objects, you can import them into another instance of WorldServer.

Before you begin

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

Moreover, certain dependencies that do not exist in the target system such as users, workgroups, workflow rules, and clients will not be imported alongside access control lists (ACLs). You must add those dependencies or import them separately into the target system.

Procedure

  1. Go to Management > Administration > Import Objects.
  2. Upload the file that you want to import by clicking Browse, locating it, and then clicking Upload File.
    The primary objects included in the file are displayed in the Import Objects list:

    Figure 1. The Import Objects list

  3. Select the check boxes next to the objects you want to import, and then click Next.
  4. On the Import Objects - Step 2 of 2 page, select one of the available import options.
    If you select Include missing referenced objects, WorldServer displays only the objects that are referenced by the primary objects 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 selected. In the list, referenced objects are marked with a star next to their names.
  5. When finished, click 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, such as:
    Importing User "markbrown"...
    User "markbrown" was not imported. Details: Locale "jp_jp" not found.