Runtime System NWDI

[Former Member]

Hello,

The developers are now working in enhacements in a track for WEC; but they say they cannot view the packages they build. Do I have to configure runtime system for they to review the changes in the server or theres a way for they to test in the server they components, maybe this is a more development related question but I just want to make sure I'm not missing nothing with this track.

[ErvinSzolke]

Hello Alejandro,

from the developers point of view a deployment can take place in two ways.

- Centrally via NWDI or

- directly to an arbitary engine configured in NWDS' preferences.

Of course if each developer would deploy directly to the same engine, that way they could interfere with each others work. The developers can test on the given runtime system where the application has been deployed (as per the runtime systems configuration of the involved track). If you set up a server for development, consolidation, test and production, then you can test on all these once the corrsponding transport took place. Still the developers' demand is rather to deploy and test the application in runtime locally, before checking-in/activating the change (and by this deploying it centrally via NWDI). In order to solve the above problems we usually suggest the setup of Developer Workplace installation. This means each developer has a local j2ee engine installed on their developer PCs, laptops, etc, and they can deploy the change to their local j2ee engine first, and if everything is fine, if the test passed, they can checkin/activate the change that will be then deployed by NWDI to the given runtime system (central deployment). This way the developers are not interfering with each others work and it is not interfering with any configured runtime systems on server side (because they use their own local j2ee engine). This kind of engine of course musn't be used in productive use, only for the developers for testing.

For a developer workplace installation please have a look at the guide (730 version):

http://service.sap.com/instguidesnw73 -- Installation -- 2 - Installation - SAP NetWeaver Systems  -- SAP NetWeaver 7.3 Developer Workplace - Installation Guide.PDF

If this was not your question and/or you are already using developer workplace, could you please elaborate your scenario? What packages exactly the developers cannot see? Can you attach some screenshots?

Best Regards,

Ervin

[junwu]

for dev server, the developer can deploy directly from their NWDS.

anyway you can configure the runtime system, it has no harm.