Best practices: Sharing projects

You need to consider controls when several people share work on a project.

When working in a team environment, one way of working may be to allow all users to edit resources concurrently, then merge the various files later. This approach is not a good approach when working with WebSphere® Integration Developer unless all the users are very familiar with managing the physical files for artifacts and working with their code. To help avoid overlapping changes to files, set up the repository systems to avoid concurrent modification. For example, set up ClearCase in exclusive checkout mode or use the Watch/Edit feature when using the CVS repository system.

Related concepts
Modules and libraries
Modules and libraries dependencies
Business integration capabilities and roles
Business integration cheat sheets
Related tasks
Creating a module for business services
Creating a mediation module
Changing default namespaces
Enabling tools capabilities
Adding dependencies to modules and libraries
Creating the library
Sharing your integration project
Related reference
Best practices: Modules and packaging for business services
Best practices: Mediation modules and packaging
Business Integration perspective and views
Documentation of resources

Related information

Tutorial: Work with modules and libraries

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.