NWDI Configuration

[Former Member]

Hello All,

We are planning  to configure NWDI for ESS/MSS Customization,we are having 3 runtime systems but Dev system is 7.0 and Test and Prod are 7.0.2

so is there any issue if we configure NWDI in Dev system .

and How many tracks we have to create For ESS/MSS Customization one track is enough.

Regards,

Trilochan

[junwu · Accepted solution]

i think it has no issue to configure the nwdi in dev.

check Note 872892 - JDI/NWDI Cookbook for ESS/XSS

[Former Member · Accepted solution]

Hi,Thanks for ur reply.

ESS/MSS is allready deployed in All Systems, now if we import The components(ESS,MSS) through NWDI then it will create any problem.

Regards,

Trilochan

[junwu · Accepted solution]

i don't see any problem there.

[Former Member · Accepted solution]

The packages for ESS/ MSS on 7.02 version would be different as compared to 7.0

NWDI tracks will not pose any problem as such, though deployment to 7.02 may give unexpected results with respect to functioning of ESS/ MSS apps.

Please check PAM for version compatibility.

Thanks,

Nikhil

[Former Member · Accepted solution]

I have a created a track for ESS Customization with only one runtime system DEV ,but when we are importing SAP_BUILDT,EP_BUILDT,JEE,JTECHS,PCUI_GP 603 and ESS 603 Componets from Devlopment to Consolidation its sucsscesufuly imported but in CBS we can see Broken DC'S for PCUI_GP and ESS.

i am not able to find out the reason.

Regards,

Trilochan

[dao_ha · Accepted solution]

Hi Trilochan,

Please refer to the 'Top Rated Content' documents in the Overview tab of this NWDI space. You'll find useful docs/best practices related to NWDI track designs, trouble shootings, etc. (including the doc 'CBS Secrets Unveiled - Understanding Brokern and Dirty DCs').

Hope it helps.

Dao

[ErvinSzolke]

Hi,

I think this will be a problem, but other colleagues in this discussion please confirm/deny.

The thing is that a track has maximum 4 RunTimeSysyems: DEV, CONS, TEST, PROD.
Fist rule: All of them has to be the same release and SP. Inside one track it is not allowed that say DEV is 700 SPX while TEST is 702 SPY and say PROD is 720 SPZ. All of them has to be in sync, i.e. mixing is not welcome and not supported.

The track configuration itself will point out the release (since on track config we specify which SCs we would like to use and what are their dependencies. At this level we have no option to deal with the SP). The SP will be specified at Check-in. After that we have no chance to change on this (and makes no sense anyway).

At RTS config we can only specify the host/port deployer [user]/pass of the given RunTime System, nothing more, so we have to be sure those RTSs are having the very same release and SP like the one specified in the track.

See more about these rules at:
http://scn.sap.com/people/marion.schlotte/blog/2005/10/25/jdi-software-vs-jdi-content

Please let me know if I misinterpreted the problem, but if this is the case, there is no workaround or fix. The golden rules have to be followed as described above.

Please also if the originally reported issue (question about RTSs and their versions) is answered, then close this thread and open a new one for the Broken DC issue. It is important becuase it helps in future search (i.e. "1 thread 1 problem description" principle).

Thank you and Best Regards,
Ervin