[Openroad-users] David Tondreau will be giving a web cast...

[David Tondreau]

Well almost.  I understand it better now.  When Robert says "client" he
was referring to his customer, not a workstation on the premises.  I
should have known better because I am familiar with their infrastructure
at Ports of Auckland.

HTTP indeed does take care of the firewall problem but it does not the
deal software installation problem.  I agree that adding the eClient to
the SOE is a legitimate approach and it deserves a hard look.  OpenROAD
and the eClient can keep development costs down and improve the end-user
experience in a rich application environment.  The benefits of this are
clear to both organizations.  However, it would take a senior level
decision to establish a policy that says if you are going to do business
with us, you have to run our bits on your computers.  No IT department
likes to be told what they have to allow on their computers and you can
end up with a "one bad apple spoils the whole bunch" problem.  

Ports is in the unfortunate situation of having to provide a lowest
common denominator interface to it's business infrastructure.  Citrix
wouldn't be any better because again, it requires a plug-in on every
machine.

One option to consider is to build out a well designed OpenROAD Server
infrastructure that can provide basic functionality when driven by a
browser (e.g., ASP.NET or JSP) interface and advanced functionality with
an eClient.  The MeetingPoint demo that is part of OpenROAD 4.1 is an
example of this exact architecture.  Customers that want to prioritize
"lock down PCs over everything else" can choose the browser interface
and a lower Service Level Agreement.  Customers that are willing to run
the eClient can get the higher SLA.  You still get the reusability of
the 4GL server side code and tight control over database access.  I
suspect you have the skills to write that in house perhaps along with
the eClient version of the application.  The outsourcing for the browser
development is still possible since all the vendor would be doing is
writing the U/I logic that calls the OpenROAD Server via either the
documented COM, JNI or C# APIs.

Regards,
 
David 

David Tondreau
Architect, Ingres Corp.
http://community.ingres.com/



-----Original Message-----
From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Simon Lovell
Sent: Wednesday, May 02, 2007 1:15 AM
To: openroad-users at peerlessit.com; allelyr at axis-intermodal.co.nz
Subject: Re: [Openroad-users] David Tondreau will be giving a web
cast...

What David T is about to say is "But the HTTP transport in OR 2006
overcomes this problem".  It still requires local administrator rights
for the first use, but like he says, that's the same with every other
technology.  If your clients with locked down computers require access
to your website, you can tell them to include OR in the SOE.




-----Original Message-----
From: "Robert Allely" [allelyr at axis-intermodal.co.nz]
Date: 02/05/2007 03:18 PM
To: "International OpenROAD Users" <openroad-users at peerlessit.com>
Subject: Re: [Openroad-users] David Tondreau will be giving a web
cast...

Note: Original message sent as attachment