NWDI Usage

[HuseyinBilgen]

Hi,

I want to clarify the usage of NWDI.

We've two seperate Development locations and will develop Dynpro for Java Applications for the same project.

<b>Is this scenario a right approach for the Usage NWDI?</b>

Clients will install NWDS on their computer and develop Dynpro applications. We have DEV and PRD Portal Systems. NWDI and SLD runs on DEV.

Developers will develop applications and deploy them into DEV Portal. After Tests apps will be transferred into PRD Portal.

All Versioning and Transports will be handled by NWDI.

[Former Member · Accepted solution]

Hi,

refer this weblog

/people/guenter.schiele/blog/2005/12/21/best-practices-for-running-the-nwdi

Regards,

RK

[HuseyinBilgen]

time to close

[Former Member]

As long as both development locations have access to the NWDI on your DEV system, there's no problem in using NWDI.

For the rest there's nothing wrong with your set up.

One special remark: If you have a lot of developments, it's better though to install NWDI on a separate system. The CBS is a very cpu intensize application (because of the compilations it executes) and might drastically degrade the performance of your DEV Portal.

[HuseyinBilgen]

Hi Pascal,

There will be no local J2EE installation on Developer PCs. Is this correct? I forget to tell this.

[Former Member]

That's fine, though it's actually better to have local J2EE's to improve the quality of the code that gets checked-in: If there's no local J2EE, the developer will have to check-in and activate to trigger deployment of his changes to DEV. So in this case, you will probably have a lot more activities.

[sid-desh]

Or what you can also be done is that on the DEV system developers can deploy using NWDS manually and in the track you can have only one runtime system i.e. PROD in your case. This way as Pascal has mentioned only clean and relevant will be moved in to the production.

In your case this may prove beneficial as you dont have local j2ee engines installed and developers will have a system for developing and deploying test apps without the need to check-in changes or activate them.

Just a thought.

Regards

Sidharth