Migrating resources and settings to another workspace
You can migrate resources and settings from one Developer for z/OS workspace to another.
About this task
- Centralized approach
Your site can implement the push-to-client feature to store configurations and settings on a remote system and push them to a workspace when it connects to the remote system. The push-to-client feature is a good approach for large installations that support many clients. This approach provides a way to deploy a standardized, consistent workspace environment across all Developer for z/OS client workspaces.
When you adopt the push-to-client method for storing and deploying workspace settings, your client workspaces can be updated automatically whenever new workspaces are created or when the settings are updated. You can define a set of property groups, for example, and download these property groups to a client workspace so that all developers connected to a particular remote system are using the same build and preprocessor settings.
For information about implementing push-to-client, see the related topics.
- Decentralized approach
If you define settings and configurations for workspaces individually, you can migrate them to another workspace manually. Manually migrating local resources and settings usually involves exporting them from one workspace and importing them into another workspace.
For general information about exporting resources in an Eclipse framework, see the related topics.
For information about exporting individual settings and configurations for import into a new workspace, see the topics that are linked to in the following procedure.