cancel
Showing results for 
Search instead for 
Did you mean: 

Local J2EE Engine - not sneak preview

Former Member
0 Kudos

Can anybody tell me whether somebody is really productively using NW Dev Studio with a local J2EE engine? Did you install the Developer Workplace for this or does there exist another easier way for a development client with a local J2EE engine?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

For our SAP J2EE 6.20 based developments we are using local J2EE's.

For our 6.40 developments we are using a central development server (since we only have one 6.40 server yet). I'm now working for Philips, which has 15 character hostnames for the workstations and since 6.40 has some stupid restriction (max. 13 characters) we cannot install it on the workstations yet.

The Developer Workplace installs NWDS and the WebAS in one go, what could ever be an easier way?

Former Member
0 Kudos

Thanks for your answer! I'm refering to NW4.

We tried installing the developer workplace several times on our PCs:

1. It needs much to much resources

2. It is much to complicated in case of an error

3. We had problems using it while logged in with our NT Domain accounts.

Are you using NT Domain users?

How are youre experiences with the central development server? This seams to be a good approach to me. Isn't it?

Do you're developers work with the same track if they're working on the same application?

Former Member
0 Kudos

Yes, we have NT domain users, no problems at all.

The central development server works fine, but we will surely switch to local servers as soon as possible. We have quite heavy development workstations (dual Xeon with 1 GB of memory), so we don't have the resources problems that you are suggesting.

And yes, we have multiple developers working on the same application in the same track (we use scenario 3). Development is going quite well I may say, but we have been experiencing some problems with the CMS part of NWDI. So transporting developments across the system landscape has been done manually up till now. We expect to resolve these CMS issues this week.

What do you mean with "It is much to complicated in case of an error"? Can you give examples?

Answers (0)