there are indeed some different specific issues around distributed
mobile ERP transactions.
Spent yesterday at SAP's Technical Education conference in Vienna and
the firm is trying to address these issues. which in SAP's case are as
significant for desktops as any other mobile device!!! (they have an
installed base of fat client users)
So SAP is trying to work out how to enable things like:
1. "flicker free" screens. how to seperate the presentation of the
screen from the presentation of the fields within it. moving towards a
new approach called Web DynPro, rather than SAP's trad Dyn Pro. this
could be a diffucult migration, but SAP claims it will build automated
tools that can do this automatically.
2. automated error-checking on fields. (where can this logic reside? how
to do auto checking without the latency of a call to a middle tier
server. SAP is looking at using tag library extensions to Java Server
Pages to achieve this. SAP's flavour will be called Business Server
Pages. Again, the problem is that SAP is trying to extend its
proprietary ABAP development and runtime environment (basically three
tier) into an n-tier world.
I guess I haven't said much, except that SAP is aware of, and working
on, solutions to these problems. It *has* to, in order to offer
customers a zero footprint desktop. (which can then also be extended to
multiple devices)
It's approach looks a bit proprietary, but the firm has a legacy to look
after. doesn't have advantages of green field development.
[ Need archives? How to unsubscribe? http://www.appelsiini.net/keitai-l/ ]
Received on Wed Nov 28 15:19:44 2001