This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 53482 - Add support to create App server's domain in user dir
Summary: Add support to create App server's domain in user dir
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on: 55372
Blocks:
  Show dependency tree
 
Reported: 2005-01-17 08:47 UTC by Petr Blaha
Modified: 2006-03-24 13:15 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Blaha 2005-01-17 08:47:23 UTC
App server create new domain dir in NetBeans
install directory for EA2 release. However, this
can be issue for multiusers installation,
directory isn't writable. 
Netbens will create a new domain in userdir which
will be used by default. This should be
implemented for FCS.
Comment 1 _ ludo 2005-02-22 02:38:26 UTC
We need to expose a create domain action in the IDE.
This will need a new dialog with all the input params necessary to a
create-domain command.
We cannot handle cross users consistency regarding port numbers.

We cannot have netbeans blindly create a domain with calculated port
numbers (unless we use the UID as a root seed for the ports. Even that
might not be perfect.

Also maybe we do not want this domain in the nb user directory.
One of the main remedy to 'fix' netbeans is to start from a fresh user
dir, because the user dir content is not very stable (i.e it's not
stable at all for regular heavy netbeans users). We would not want to
scratch the app server domain created there.
Comment 2 _ ttran 2005-02-22 13:52:44 UTC
should be fixed for FCS -> P2
Comment 3 Vince Kraemer 2005-02-22 19:50:28 UTC
ludo asked me to piick this up
Comment 4 Vince Kraemer 2005-02-23 23:47:59 UTC
Exposing domain creation is a feature. Not a defect.

Domain creation hasn't been supported by the plugin in the past.

It wasn't on the feature list for 4.1 (as best I can tell).

While I don't understand the user issue that Petr is describing, I am
assuming that Ludo's evaluation is correct.
Comment 5 _ ludo 2005-02-24 00:04:06 UTC
We need  an implementation in the 4.1 fcs bits :-)
The real defect is that it was not in the feature list... and we need
to fix this defect for 4.1
Comment 6 _ ttran 2005-02-24 09:30:49 UTC
Ludo's right.  It doesn't matter how we want to classify this issue. 
Should be fixed for FCS one way or another

See also issue 55377
Comment 7 Vince Kraemer 2005-02-24 15:53:00 UTC
If this issue was related to 55377, I would have already noted that.

It isn't, so I haven't.

Adding features this late in the game is risky. You know that. If you
want to add risk at this point, I will support you.  I won't let it
happen quietly, though.
Comment 8 Pavel Buzek 2005-02-26 00:59:25 UTC
Can somebody explain more clearly why you cannot just quitely (and
maybe blindly) create a domain in userdir? Tomcat plugin has been
using this approach  for several releases and I do not see any major
issues. We select a port that is not used by default (8084 instead of
8080), not UID (it is probably hard to use UID as a port number, right?).

I think you missed the main point of this issue, which is out of the
box experience. As a user I want the IDE to just work. If I want to
set all the parameters then I can as well go to the admin console or
this can be added as a convenience feature in some future release.

Then you also do not need any UI specs.
 
Please consider this option seriously.
Comment 9 Vince Kraemer 2005-02-26 01:17:37 UTC
While I know how to detect the presents of a running app server
instance I know of no algorithm that can pick a port number "randomly"
that is safe for multi-user machines, where server instances are not
running 24/7/365.25.

If multi-user systems are "outside" the requirements, then somebody
should say so.

Unfortunately the number of ports consumed by the app server makes the
just pick a number strategy a bit more "dangerous" on multi-user
systems, too.
Comment 10 _ ludo 2005-02-26 01:30:12 UTC
I agree with Vince.
Blindly does not work at all on a multi user systems and for sure, we
would create conflicting domains between users, depending on the fact
that other servers are running or not during this blind operation...

Allocating port numbers is a SYS ADMIN activity on a linux or Unix
system, and has to be coordinated.
Now, the only way to solve this is to let the user decides (by maybe
asking for help to the machine sysadmin! 
Giving the user the option to fine tune the settings is well known
activity when it comes to unix multi users administration.

Remember, this has to work on a JDS laptop, but also on a muti-user
unix system, maybe SunRays.
Solving only the JSD mono user system is not enough and in fact this
mono-user system should be better configured with file based installer
that does not require to be root to install the IDE
Comment 11 Pavel Buzek 2005-02-28 19:38:23 UTC
I agree with Ludo's last comment that alocating ports on multiuser
environemnts is not something you do by random generator.

It would be great if the user could fine tune the IDE for multiuser,
maybe with the help of sys admin, but if it also could work out of the
box (without help of a sys admin) in a single user environment. Single
user env is the vast majority of the IDE users out there.

Installing software with root/admin priveledges is IMO a good and
recomended practice - even on windows system which are single user.
I've seen more then one large organization where users did not have
the right to install software on their computers - it was installed by
admins. This was with windows. Tomcat plugin would work there.
Comment 12 _ ludo 2005-02-28 19:59:04 UTC
"Installing software with root/admin priveledges is a good and
recomended practice"...
Yes, by using Linux RPMs or Solaris Packages, not file based
installers, as made *mandatory* by Solaris ARC group.

The current NetBeans installer is file based and does not require the
user to be root...This is the main advantage of this type of
installation, but it's not even considered by the ARC group.

For now, the UI Vince is working on to add a domain will have an extra
step in the wizard where the user can enter the location and different
port numbers necessary to create a domain. This will cover the feature
for Nb4.1.
The nice improvement between App server 7.x and App Server 8.x is that
now to create a domain, you do not need to be root :-) so this
activity can be done by a regular user. Guidelines regarding port
allocation should still be coordinated between different users on a
same linux or solaris box, just to be a good neighbor..

Comment 13 Vince Kraemer 2005-03-04 15:58:40 UTC
Domain/instance creation for the "special case" is integrated.
Comment 14 Petr Blaha 2005-03-21 12:27:03 UTC
[Build 20050320]