Questions on Runtime systems

Question

Hi to all
I have two questions:
1)
SAP says do not use the system where the JDI s installed as runtime system, I suppose in order to avoid the CMS deadlock described in note 754143. Right ?
Suppose we have three system D (develop), T (test) and P (Pro). Teh JDI is instaleld in D. We define the track Development with the runtime systems T as "test" and P as "production".
As I understood the deploy on the D system happen automatically as soon the activation is triggered into the Dev Studio IF the system D is used as runtime system.
Please could you clarify how we can keep aligned the D environment with the system T and P from the point of view of he deployment if we cannot use the D system as runtime environment ?
2) Suppose we have three system D (develop), T (test) and P (Pro). Teh JDI is instaleld in D.
We defined the tracks DEVELOP and MAINTENANCE, connected by a 'repair' connection.
If I understood weel the DEVELOP track and the MAINTENANCE track should have the Development and the Test runtime system in exchanged order:
the system indicated as Test for the DEVELOP track has to be indicated as Develop for the Maintenance track.
Then the runtime Production system has to be defined for the DEVELOP track only ?
Regards

Answer 1

Hi, thanks H. for the info.
I understood the MAINTAIN track and the DEVELOP track MUST to have different runtime systems.
We need at least, (minimun), 3 different systems (development1 and test on the DEVELOP track and development2 on the MAINTEN track) in order to maintain an old relese of SC while a new release is in progress, right ?
It's then responsability of the 'connection repair' defined between the tracks to move the software from the DEVELOP track to the MAINTEN track.
Please, in which moment of the DEVELOP track the software will be copied also to the MAINTEN track ?
New question about the Consolidation phase.
At the beginning we configured ONLY the runtime development for the DEVELOP track. So the work o teh developers was deployed automatically on that system as they activate their activities into the Developer studio.
As traiing we released the activities and we saw them into teh Consolidation tab queue ready for transport (NO Consolidation runtime system was in place).
Anyway we selected them and run the import. The CMS said it gone well.
After that the activities of the developers were into the Assebly tab queue.
My dubt is that after the import we saw our application working fine on the envirnment indicated as runtime develop system.
I need to clarify if this is the correct behaviour:
A) In this case using only the development runtime system into a track it does not have sense to relase the activities.
The development activity then end at that point and there is nothing else to do into the CMS.
If you need at that point the SCA of your work, to import them elewhere you can find it under the ../Jtrans directory (on condition that you reeased them)
Right?
B) It's an bug of the CMS to allow to run the import from the Consolidation tab while there is no consolidation runtime registered ?
Or it do not represents a real, physical import of software but only a logical step needed to move ahead the sw ?
we suppose when we run the import from the Consolidation tab queue we overwritten again the application on the development runtime system, but I'm not sure of that.