Rational Developer for System z

Synchronizing manually

To manually synchronize a local project or file with a remote system, do these steps:
  1. Right click the project or file.
  2. Select the Team > Synchronize with remote.
Rational® Developer for System z® checks for changes in the selected resources and displays the Synchronize perspective. The Synchronize perspective displays the resources in which changes have occurred and indicates the direction in which the change should be synchronized.
In the Synchronize perspective, there are four possible states as shown in the following table. You can compare resource content between the local workspace copy and the remote copy, or simply push the change out to the appropriate location.
Table 1. Possible states for resources in which changes have occurred
Symbol Meaning Possible actions
Gray arrow pointing right An outbound change. This is a change that occurred only in the local workspace.
  • Copy the local file to the host using the Copy changes to host action.
  • Replace the local file using the Override changes to local action.
Blue arrow pointing left An incoming change. This indicates a change has occurred only on the host.
  • Copy the remote resource to the local project using the Copy changes to local action.
  • Replace the remote resource using the Override changes on host action.
Red arrow pointing left and right Conflicting changes. This indicates that changes have been made both to the remote version and the local copy. The conflict needs to be resolved to continue. You can resolve the conflict by taking the following actions:
  • Indicating that you have inspected the conflicts (usually using the compare editor) and resolved any differences using the Mark as Merged action.
  • Replacing the local copy with remote contents using the Override changes to local action.
  • Replacing the remote copy with the local contents using the Override changes on host action.
Red arrow pointing left and right and containing a plus sign An item that has been newly mapped and never inspected before. This is considered a conflict and should be resolved as a conflicted resource.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)