why we need local j2ee engine in netweaver 7.1

[Former Member]

why we need local j2ee engine in netweaver 7.1 DI envt client side, please help in identifying any specific need

[Former Member]

Hi,

This is called Developer Workspace, When you install this you get a local was and NWDS.

As suggested in the posts it is very much recommended because the develpoer can develop and deploy in his local was and check the functionality of the apps.

When you install Developer workspace it give you the portal usage type also. You need not to deployi t again seperately.

Regards,

Vamshi.

[Former Member]

It's not needed, but recommended. Especially if you have multiple developers working on the same components. With local J2EE's they will not be over-deploying the components, which may result in the deletion of another developer's work on the J2EE server.

[Former Member]

In that case what is the ware minimum component for Java AS would be required on developeres PC?

Regards,

-Praveen Soni

[Former Member]

That depends... If you only want to build regular Java components, you only need the engine. If you want to build Portal components, you'll need a Usage Type Portal...

[Former Member]

That depends... If you only want to build regular Java components, you only need the engine. If you want to build Portal components, you'll need a Usage Type Portal...

[Former Member]

That depends... If you only want to build regular Java components, you only need the engine. If you want to build Portal components, you'll need a Usage Type Portal...