Nope, not really....
IMO, there's not much adoption of EGL (it seems), so opinions are
scarce. I'm losing support for this product (within my department) at
an increasing rate, as we can't find much to get us started. Too many
of the tutorials we've found are for EGL versions we no longer use, or
we applied a fix which changed a dialog, or it just doesn't work as
described... We'd love to find someone using it, and IBM is supposed to
be getting back to us with local EGL customers, but so far, we're just
waiting.
I'm getting really frustrated with this whole infrastructure change.
We've reviewed IBM's Modernization Road Atlas (Roadmaps are no longer
comprehensive enough, it seems..) One thing is certain; there is risk
in the selection of technologies that we adopt, and we are ill-equipped
to assess these risks. Will the technologies we target be viable for
the duration of this project? Which technologies meet our needs for
secure, web-services-based applications deployment across IBM i and
Microsoft platforms? What other infrastructure do we need to support
user access to these services-based applications? Portal server?
Someone here suggested we use SharePoint... Does that support portlets
generated by Rdi-SOA? Right now, there are just too many questions...
My hope with EGL was the extensibility of the runtime. As new
technologies come into fashion, EGL should be able to accommodate them.
This would seem to ensure the relevance of this technology far enough
into the future to ease that worry, but the apparent lack of adoption
paints an alarming picture...
If anyone has anything to say about this, please chime in.
Thanks,
Eric DeLong
-----Original Message-----
From: egl-i-bounces@xxxxxxxxxxxx [mailto:egl-i-bounces@xxxxxxxxxxxx] On
Behalf Of Dave Odom
Sent: Tuesday, December 23, 2008 12:47 PM
To: egl-i@xxxxxxxxxxxx
Subject: Re: [EGL-i] Targeting "enterprise architecture"
Eric,
Did you get some good responses? If so, care to share?
Thanks,
Dave
"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> 12/16/2008 14:59 >>>
Just wondering if there are any general recommendations or
considerations when selecting an enterprise application architecture.
By that, I mean which technologies are recommended: WEB 2.0 (business
mashups), Portal Server / Portlets, etc.
We have development teams for IBM i and MS .net, and we want to
understand which technologies help to bridge the gap between the two
platforms. I have been reviewing some of the differences between the
Business Mashup hybrids and Portal based aggregators, but I'm unsure of
how .net relates to either of these approaches. I assume that there
must be some way for IBM i to generate services that are compatible with
MS, but I'm unclear on this.
Sorry if these are newbie questions, but we're meeting with IBM tomorrow
to discuss our modernization strategy, and I want to have some idea of
where to focus my attention.
Thanks in advance,
Eric DeLong
--
This is the EGL on and around the IBM i (EGL-i) mailing list To post a
message email: EGL-i@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit:
http://lists.midrange.com/mailman/listinfo/egl-i
or email: EGL-i-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/egl-i.
--
This is the EGL on and around the IBM i (EGL-i) mailing list To post a
message email: EGL-i@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit:
http://lists.midrange.com/mailman/listinfo/egl-i
or email: EGL-i-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/egl-i.
midrange.com
