4.6. Transferring a Workspace Between EKM Servers

Engineering Knowledge Manager

Administration Guide | Chapter 4: Creating and Managing Workspaces |

4.5. Creating a New, Empty Workspace |  | 4.6.1. Exporting a Workspace
Prev |  | Next

## 4.6. Transferring a Workspace Between EKM Servers

EKM provides administrative users with the ability to copy a workspace from one EKM server to another. This is useful, for example, when you want to upgrade your EKM server to a new version, and you want to transfer an entire workspace to the new server.

Transferring a workspace involves exporting the workspace on the source server and then importing the exported workspace on the destination server.

Note:

- The source and destination EKM servers must be running the same release of EKM. For example, if you exported a workspace in EKM 17.0, you could import that workspace into EKM 17.1 and 17.2, but you could not import that workspace into EKM R18. If the source and destination EKM servers are different versions within the same release (for example, 17.0 and 17.2), workspaces from the older version can be imported into the newer version, but not vice versa.

- You cannot import an exported workspace that has been converted into human-readable format. For more information see Converting an Exported Workspace into a Human-readable Format.

- If a workspace contains custom object types that use the `initializeMacro` attribute to call a script containing transactions, certain transactions in the script may cause the import/export of the workspace to fail. You should disable such scripts before exporting the workspace.

In this section:

- Exporting a Workspace
- Importing a Workspace
- Converting an Exported Workspace into a Human-readable Format

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.