Skip to Content

Automatic transport after Activate

Hi,

Basically, we have NWDI configured for SAP MII 15.2 where can already see the Source Control menu option on SAP MII Workbench from where we can Share projects, Import projects, Create Activities, Check In, Check Out and Activate Activities successfully.

Out intent is to use transport mechanisms between D, Q and P systems, where I heard that it is possible to automatic transport MII objects from one system to another in background without any human intervetion, after activating an activity on Workbench, and I have a question about it.

My main question is: How to set up automatic transport of activities from DEV to QAS after Activating in DEV?

Basically, I want to activate an activity and have its content automatically transported from D to Q, for example.

How to implement that?

Thanks very much,

Add comment
10|10000 characters needed characters exceeded

  • On "Consolidation" tab before Importing, the DC refers to P47_DFMII58_D buildspace. After I import, I starts to refer buildspace P47_DFMII58_C. Does this make any sense?

    untitled.png (149.6 kB)
  • In your screenshot I only see a reference to development, D, in the "Version". The "Version" that is shown as "..._D.8" is the exported file from development, therefore it is "_D". It will be imported to "System" = "DFMII58-Consolidation" .

    Does this answer the question?

  • Hi Ervin Szolke and Daniel Kordes , thanks for the inputs. My broken DC problem is now fixed and the transport from Dev to Qas works as expected. Thank you very much for your inputs so far.

    That said, as it is working now and I have played around, I realized that all Released DCs, after they are imported on Consolidation, stays grouped together on Assembly tab waiting to be assembled. My question now is: What happens if I have an emergency bug fix that must be transported from D to P? When it gets to Assembly, it will join the others that are already there, but I can´t transport the whole DC once it has other content. How can I transport this emergency bug fix separately from the other transports that are waiting to be assembled? Thanks

  • Follow
  • Get RSS Feed

5 Answers

  • Best Answer
    Apr 02 at 08:52 AM

    Hello Manoel,

    The scenario needs manual intervention at two stages:

    1, First when releasing the activity either using CMS tool or from the NWDS.

    2, Then in CMS Transport Studio. The import is an important step, as troubleshooting might be needed in case of build or dependency errors.

    Even if you use CM Services and CTS+ the import has to be triggered.

    So I am afraid you cannot avoid human interaction fully.

    Best Regards,

    Viktor

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 04 at 11:09 AM

    Hi Manoel,

    I also like to share some thoughts on MII and NWDI and CTS+.

    In some comment you asked about a guide. There is an older guide available on how to configure MII with CMS using the configuration wizard. It also explains a bit some concepts of MII Transports with NWDI. The guide can be found at https://archive.sap.com/documents/docs/DOC-1839

    You also asked on how should a track look like. That's hard to answer because it depends on your landscpae and your requirements. For example: In CMS you can configure a runtime system for the consolidation system/state. With this you could do testing directly after import into consolidation without doing an assembly. During Import to consoliaiton the changes are build by CBS and then deployed by CMS. But deployment is only triggered when build was successful. The assembly can be done once your testing on the consoildation system was successful. With regards to assembly you need to keep in mind, that assembly always takes all current active DCs from consolidation buildspace and stores it in the SCA file. So all activities/changes that have been imported to consolidation before assembly will be part of the assembled SCA file.
    Another option is, to not define a runtime system in consolidation but define a runtime system as test system in CMS. This system only can be updated after assembly. So when you want to test the released changes you need to import to consolidation, do the assembly and then import to test.
    Some customers integrated MII with CTS+ and want to do testing there. In this case they do not define a runtime system for conslidation and not or test in CMS but define the test system in CTS+. In this case the process looks like this: After release of activities you need to import to consolidation, then do an assembly which will upload the SCA to CTS+ and then you release the transport request in CTS (or it is released automatically during assembly, depending on CTS+ settings) and finally you import the change to the test system in CTS+.
    So with regards to your problem "but it does not work and nothing is transported to QAS, even though it shows success statuses" it depends on the landscape setup, where your QAS is defined and whether all previous required steps, see above, were executed. E.g. if you use the runtime system i consolidation, you will only see the changes there, when the Import of the changes was executed and was successful. You can also check the following guided answers for this question:

    https://ga.support.sap.com/dtp/viewer/index.html#/tree/1123/actions/12576:15662

    Last comment on your initial question. You can automate the release of activities and Import to consolidation and assembly with the CMS Tool and some scheduler around. However I have never tested yet whether assembly with CMS tool also works, when the track is connected to CTS+.

    Best regards,
    Daniel

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Daniel Kordes ! Thank you very much for such detailed and valuable information. The guide you provided is the one we have used, but thanks anyway! :) The transports are working fine now, after I could fix the broken DCs.

      Your Landscape explanation is very useful and I believe this is what I need to invest more time now as I have the following question: I realized that all Released DCs, after they are imported on Consolidation, stays grouped together on Assembly tab waiting to be assembled. My question now is: What happens if I have an emergency bug fix that must be transported from D to P? When it gets to Assembly, it will join the others that are already there, but I can´t transport the whole DC once it has other content. How can I transport this emergency bug fix separately from the other transports that are waiting to be assembled?

      How my landscape should look like to allow that emergency transport to happen individually from the other waiting transports?

      Thanks!

  • Apr 02 at 11:26 AM

    Hi Viktor Romasz , thanks for you reply. I believe we can live with that, so it is fine. :)

    As of now, we can only transport SAP MII projects as a whole, by going into MII Projects Menu, Exporting a project and selecting Export Method as CTS+. After doing this and following all other required steps, the project successfully shows up on the QAS system. Nevertheless, this option as I see it, completely ignores what is activated on NWDI and transport the whole project, so on going changes are transported as well and we don´t want that.

    The other way we are trying to do is to Activate an Activity on SAP MII Workbench, Release it on NWDS, on CMS we: Consolidate/Import it, Assembly it and Release it, nothing is transported to QAS system. We believe that this should be the way carry only Activated Activities from NWDI, but it does not work and nothing is transported to QAS, even though it shows success statuses.

    Do you have any suggestions, a guide, or anything that I could check in this case?

    Thank you very much!

    Thanks.


    8ff3b941.png (25.7 kB)
    82894e4e.png (26.1 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • Have you activated the activity on the CBS? After releasing it from the NWDS, the activity has to be activated in the CBS (otherwise the s.code will not be copied to the active dtr ws & neither there will a consecutive CBS build)...

      Activation in the CBS

      "It is important to activate the activities of the Design Time Repository (DTR) in the correct sequence. The CBS guarantees this with the check for overlapping. Every DTR activity contains versions of files in the DTR. Two activities overlap on data level if there is at least one file that was changed in both activities.

      In this case, the activity that was the first to be checked in or integrated into the inactive workspace must also be the first to be activated. If there is an overlap with younger or not yet activated activity, you can integrate it into the activation or cancel the activation."

      Activation in MII workbench is a different thing from activation in the CBS.

      Activity

      "To make the versions of an activity available for all the developers who use the software component, you must activate the activity. To activate an activity, DTR and Component Build Service (CBS) cooperate. You trigger the activation. During the activation, the CBS tries to rebuild the development components (DCs) changed by the activity. If this build is successful, it creates new archives for the DCs and finishes the activation by integrating the activities from workspace inactive into workspace active . The changes become visible in both the active workspace and the archives created in the build."

      Regards,

  • Apr 03 at 01:38 PM

    Hi Milen Dontcheff , thanks for your response. I´m using cmstool to Release the Activities instead of NWDS and I can see that they are all Active on DTR.

    Any chance you have a guide about this MII+NWDI+CMS etc... configuration so we can double check our config? Thanks.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 03 at 02:00 PM

    Hi Milen Dontcheff , yes! They are activated in CBS :)


    untitled.png (136.1 kB)
    Add comment
    10|10000 characters needed characters exceeded