When I was preparing a document to explain the capabilities of Sap Netweaver development infrastructure, I came across the following statement with one of the presentation – “DTR’s versioning mechanisms allow the synchronization of different DTR servers – this is the basis for distributed development and a modification and update concept for customers”. After having worked only with single DTR server and seeing few forum threads about working with distributed NWDIs, I have decided to explore this possibility.
I can think of the following customer scenarios’ in which the existence of multiple NWDI make sense.
1. An organization might develop a large scale application and it can have its development canters in two or more geographical locations
2. You might be thinking of changing SAP’s standard ESS Webdynpro’s. (ofcourse developers should understand the floor plan manager concept of ESS webdynpro’s before changing them). In that case SAP and the customer organization will be working on the same software component at the same time
4.What happens when the active version in the target workspace is not same as the predecessor version of the activity being integrated? This is called integration conflict and they are detected automatically. One can resolve them by selecting either to keep active/conflicting version or merging them