After you select the objects that you want to export, the system gathers information about the objects and, optionally, about any other objects that they refer to. It writes this information as a collection of XML elements to a file that uses a format specific to WorldServer — TML. The default name of the file is
ExportObjectDefinitions.tml, but you can change its name when you export it.
The export includes each object in the output file only once, even though some objects may occur multiple times. For example, a user who is assigned to multiple exported locales is still exported to the file only once.
Important: When you export objects, the custom components referenced by those objects are not exported with them. For example, if you want to export a workflow that contains custom automatic actions and import it into another WorldServer instance, you must add or import those custom automatic actions from
before you import the workflow into the other WorldServer instance.
Moreover, if you want to export cost models or other resources that have references to cost models, certain dependencies related to access control lists (ACLs) such as users, workgroups, workflow rules, and clients will not be exported. You must add or import them separately before importing the cost models to another WorldServer instance.
You can export the following objects:
- AIS properties — See the list below for information about which AIS properties you can export.
- Attributes (of other exportable objects)
- Clients
- Cost model rules
- Cost models
- File types
- Human actions
- Linkage
- Locales
- Mounts
- Project type
- QA checker profile
- Quality model
- Recurrences
- Rules
- Scoping configurations
- Term database (TD) sequences
- Translation memory (TM) sequences
- Term databases
- Translation memories
- User types
- Users
- Vendors
- Workflow phases
- Workflow roles
- Workflows
- Workgroups
AIS properties. You can export AIS properties for any AIS path, subfolder, asset, or any combination of these. If you select a folder, its contents are selected automatically. Only the properties that you have specified explicitly for a particular path are exported. When you import AIS properties to a new system, their corresponding mount should already exist in the system. The import process does not create the mount for you. (Even though you can export mounts, they are not referenced by AIS properties. You must export the mounts independently.) If the mount does not exist, the import still succeeds and it reports that paths were not found.
The following AIS properties are exported:
- Locale
- Context URL
- Comments
- Translation memory (for target assets)
- Term database (for target assets)
- Encoding
- Access Control: View, Read, Write, and Change ACL
- Any custom AIS properties you have created
Attributes. Note the following information about exporting attributes:
- You can only export the attributes of those objects that are exportable. For example, you can export user attributes, because users are exportable.
- You cannot export the files referenced in an
attachment attribute. The path to the attached file is exported with the attribute, but not the actual file. Therefore, the path is not valid unless the referenced attachment exists in the same location in the new deployment. For example, you want to export an object with an attachment that has the following location:
C:\MyImages\image1.jpg. When you deploy that object on a new system, the attachment still points to the old location. As a result, you must either create
C:\MyImages\image1.jpg on the new system or update the path after the deployment.