IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Building mediation flows > Optimizing a mediation flow for team development

Considerations for team development of mediation flows

When you choose to save a mediation flow in multiple files, the mediation flow is split into several files to facilitate team development. A specific file with an extension of .mfcflow is created for each source operation, and a common file with an extension of .mfc is created for the mediation flow. Depending on the type of change you make, you may need to synchronize the common file in addition to updating the changes to the operation .mfcflow file.

When more than one developer is working concurrently on a mediation flow, it is a good practice for each developer to synchronize all of the files related to the mediation flow before making changes.


Important: Always synchronize at the project level, so that you can see the .mfcflow files of added and deleted operations.

  1. In the Physical Resources view, select the mediation flow project, and synchronize.
  2. Update new, changed or deleted file from the repository.
  3. Make changes to your mediation flow.
  4. Synchronize the mediation flow project.

  5. You may now see changes that other developers may have made, in addition to your local changes

  6. Accept changes from the repository, and commit your own changes.
These are some of the situations where you may get conflicting changes if you do not synchronize before making a change:

Optimizing a mediation flow for team development