b_gilmore
Well Known Member
Re: [Re: JDE HTML]
All I can say is that if any of you are thinking about going with the HTML
client or the portal, don't concentrate of the "coolness" of being able to run
OneWorld thru a Web Browser and spend the majority of your evalution time on
the following:
Supportability after go-live (internal and external) who can do it and what is
in place to facilitate the education of your resources
Change Management strategy (every service pack comes with a JAS update you
MUST put on) (Do you have multiple foundations yet? You'll need it with this
after go-live.)
Availability and Stability (what's the down time estimates look like
(maintainance, outages, etc) How many users potentially affected.
Troubleshooting. What's the estimates of issue resolution given the current
availability of troubleshooting skills in house and external?
Complexity vs. other options (More complex mean more moolah most times
right?) Complexity for your users and complexity for your support staff.
If you have the bore and stroke to support OneWorld AND this product for your
business, then bless you. Please clone yourself and send me two copies (UPS
ground).
year plus ago and it was very buggy. When I first saw the HTML client, JDE
was agressively pursuing the Java client because of it's richness.
PORTAL. While at MUG in December I heard many JDE insiders say the Java
client was pretty much worthless, but the HTML client/Portalb was the future
of the product. B9 seems to very Portal/HTML focused.
pleased with the product. This is a lab, I run Citrix for production, and
would'nt yet roll everyone to HTML but will likely switch a single machine off
the Citrix farm and dedicate it to be a production JAS server for use by
remote users instead of NFuse.
posting is already long enough.
http://www.jdelist.com/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=31367
All I can say is that if any of you are thinking about going with the HTML
client or the portal, don't concentrate of the "coolness" of being able to run
OneWorld thru a Web Browser and spend the majority of your evalution time on
the following:
Supportability after go-live (internal and external) who can do it and what is
in place to facilitate the education of your resources
Change Management strategy (every service pack comes with a JAS update you
MUST put on) (Do you have multiple foundations yet? You'll need it with this
after go-live.)
Availability and Stability (what's the down time estimates look like
(maintainance, outages, etc) How many users potentially affected.
Troubleshooting. What's the estimates of issue resolution given the current
availability of troubleshooting skills in house and external?
Complexity vs. other options (More complex mean more moolah most times
right?) Complexity for your users and complexity for your support staff.
If you have the bore and stroke to support OneWorld AND this product for your
business, then bless you. Please clone yourself and send me two copies (UPS
ground).
year plus ago and it was very buggy. When I first saw the HTML client, JDE
was agressively pursuing the Java client because of it's richness.
PORTAL. While at MUG in December I heard many JDE insiders say the Java
client was pretty much worthless, but the HTML client/Portalb was the future
of the product. B9 seems to very Portal/HTML focused.
pleased with the product. This is a lab, I run Citrix for production, and
would'nt yet roll everyone to HTML but will likely switch a single machine off
the Citrix farm and dedicate it to be a production JAS server for use by
remote users instead of NFuse.
posting is already long enough.
http://www.jdelist.com/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=31367
