The article says that WebFacing has been rolled into the HATS
toolkit, which would seem to make it "HATS" as far as the usage
restriction is concerned. Clarification from IBM on this point
would be helpful.
One of the things I like about WebFacing is that it is integrated
into the WebSphere security model better, and can leverage EIM to
achieve Single Sign-On regardless of how the user originally
authenticated. Doing the same thing with HATS is either hard-ish
or requires the user to authenticate to a Windows domain.
--Robert
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Aaron Bartell
Sent: Tuesday, July 15, 2008 8:21 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Webfacing out, EGL in
I was reading an article from Alex Woodie this morning (
http://www.itjungle.com/fhs/fhs071508-story03.html) and it seems it is
basically giving an EOL (End Of Life) to Webfacing. In exchange IBM is
directing people towards EGL.
Because my exposure to Webfacing has been minimal (just played with it)
I am
curious to know how much "change" this actually is, concerning how much
code
or processes will need to be migrated. For example, lets say somebody
fully
embraced Webfacing when it first came out and they now have over 1000
screens using it (with customizations). I am guessing they are out of
luck
in a really bad way - right? Because the customizations they have done
will
basically need to be re-done/re-written using EGL? Are there migration
tools?
I am curious as I have customers who have fully embraced Webfacing.
Thanks for anybody that can shed light on the subject,
Aaron Bartell
http://mowyourlawn.com
midrange.com
