CTS+ with NWDI Single System Track

[Former Member]

Hi,

We intend to use NWDI for source control of PI and Portal JAVA developments.CTS+ is configured for transport management.

There is an option to use Single System Track in NWDI when CTS+ integration is configured. This means Development tab is available but not the Consolidation tab. At Assembly, CTS+ should kick-in to transport the objects using transport landscape setup in CTS+ system.

Has anyone tried this scenario? Are there in pros/cons you know of?

Thanks and regards,

Shehryar

[Former Member · Accepted solution]

Based on information available at https://cw.sdn.sap.com/cw//docs/DOC-23011?treeid=DOC-7684, it is clear that upon activation and release, the software component is assembled and will be ready for transport through CTS+. The question I have is: can the developer make further changes to the object in NWDS for later release, and still use the same transport request? Or does this process result in a new transport request everytime the developer activates changes and releases them?

Regards

[daniel_noethe · Accepted solution]

Hello,

In a Single System track each assembly will use current active dev state to create the SCA. This SCA is then attached to a transport request.

Using Single System Tracks does not have any influence on releasing transport requests - this is only a matter of configuration in TMS. If the system is not configured in TMS to release a request automatically as soon as a file has been attached, the request can be used for further attachments. Even the same SCA can be attached. The parameter WBO_REL_REQ_STRATEGY defines when a transport request is released. Take a look at the SAP help portal for details: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c5/d9012e437d4c318976edc9791f2ae4/frameset.htm

Best regards,

Daniel Nöthe