on 02-03-2016 10:05 AM
Hi guys,
I configured SLD and NWDI on Server xyz02 with wizard.
I configured MII to NWDI with wizard “Integration of MII with existing NWDI” on Server xyz04 (D-system) and xyz03 (Q-system).
That works fine!
the cbs - component build service shows the following
In CMS – change management service i see MIIDEV for server xyz04 (D-System) and MIIQS for server xyz03 (Q-System).
I configured in MIIDEV - landscape configurator – Track Data - “runtime systems” the following
I configured in MIIQS - landscape configurator – Track Data - “runtime systems” the following
How I transport the transaction "1MIITest" from D to Q? its the right way with cms? whats wrong?
I found no documentation or how to guide for that issue.
Thanks for help!
Markus
who told u to setup like that?
one track is enough for the transport.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Whether due to the MII the concept of track connections is involved in any way, I cannot tell, maybe Jun has an idea. Frankly, I skimmed over the track connections part. If you need a simple DEV-CONS-TEST-PROD development cylcle then one track will do the trick (as thanks to the Runtime System configuration you configure separate physical j2ee engines for these development stages).
What concerns the track connections part it is used in more complex scenarios, e.g maintenance tracks, multiple-productive-deploy tracks, etc.
Cheers,
Ervin
i transfered MII transaction from D to consolidation
it works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Markus,
Have you released the activities from the NWDS?
Once they are released, then they need to be activated in CBS (provided this is not set to be done automatically).
When the Activity are activated, in CMS - Transport Studio - tab Consolidation, you will have to import the components (with this - you consolidate).
Before import in Consolidation - at this point if you have configured Dev RTS, your changes will be deployed there (automatically) and you might 'test' them before Consolidating.
If everything is fine, you have triggered Consolidation and this operation is successful - you will be able to Assemble them - tab Assembly.
After successful assembly you will be able to deploy on Test (Quality RTS). The SCs will be in TEST tab in Transport Studio.
If you like how it is on the TEST RTS, you Approve in the Apporoval tab and the SCs are in PROD tab. Once imported successfully they are deployed on PROD RTS.
So more or less in each tab in CMS - Transport Studio you have import operation which triggers different processes with regards on the current phase of the software logistics. You have to work here in order to move your changes to Production
Please let me know on which step you are?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ervin already told u the tool....please check Release activity using the cmstool
after that you can see it in cms consolidation tab
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.