NWDI and CTS integration

[Former Member]

I am setting up enhanced CTS and have a question regarding java changes. If I set the flag in NWDI for CTS, what is the process for migrating changes downstream to QA and production?

If I deploy a WD Java app to my first dev system and then want to migrate it, once I attach the WD Java to a change request, does CTS handle the deployment into the QA and Prod system? or does CTS actually call NWDI which then deploys the WD java to the QA and Prod systems/

Thanks Mikie

[ThomasByM]

Hi Mikie,

thre basic idea of the NWDI integration into the enhanced CTS is that you use the transport studio in NWDI just until the assembly step. If you connect your track to the enhanced CTS (and maintained the destination service in Visual Administrator correctly) during assembly you are ased to "assemble and attach" which means that the SCA file will be handed over to an ABAP TMS transport request. After releasing the ABAP transport request this request (containing your SCA file) is ready for import into the QA-system defined in STMS transport route editor. Import into the QA-System will take place using transaction STMS. During import, tp takes the transport request and hands obver the "java-part" (that is your SCA) to the SDM of the QA-System (using the Deploy Web Service). So for the import into the QA-Runtime System and the PROD-System the NWDI itself is no longer used.

Best regards

Thomas

[Former Member]

In addition to what Thomas said.

Level of integration between NWDI and CTS varies greatly depending on the SPS you are on, because the functionality is being added and modified with each SP.

NW7.0 EHP1 has extensively redesigned NWDI<->CTS integration as well.

It has things like ability to transport on DC level, defining tracks via wizards from CTS etc.

Regards,

Slava