I am working on a product that supports both WebLogic and Websphere J2EE server. I can do one of the following
1) create 1 installer, and have install code prompt user for which j2ee server, and installer will do the appropriate copy/setup steps based on user input
2) create 2 installer, each is written for the specific j2ee server
With option 1, no code duplication for non j2ee portion.
with option 2, I have to duplicate non j2ee code into 2 project files
In real world, are there any trend/preference which approach customer/end user are expecting?
Thanks
K.K.
kkfong@amdocs.com
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

Installation Design
Started by
kkfong
, Apr 21 2004 23:24
2 replies to this topic
Posted 29 April 2004 - 16:15
Hi K.K.,
In the real world, the user will always be expecting the simplest solution. In other words, the one that requires the least effort.
So I would definitly go with option #1.
However, keep this in mind:
(1) Make sure you clearly present the 2 choices. Leave no room for ambiguity.
(2) Determine which choice should be the default. If that is impossible, make the user choose, do not choose a default option for him.
Good Luck.
In the real world, the user will always be expecting the simplest solution. In other words, the one that requires the least effort.
So I would definitly go with option #1.
However, keep this in mind:
(1) Make sure you clearly present the 2 choices. Leave no room for ambiguity.
(2) Determine which choice should be the default. If that is impossible, make the user choose, do not choose a default option for him.
Good Luck.
The Eskimo
"Evil shall come upon thee, which thou shalt not know how to deprecate"
- Robert Lowth, eighteenth-century Bishop of Winchester
"Evil shall come upon thee, which thou shalt not know how to deprecate"
- Robert Lowth, eighteenth-century Bishop of Winchester