Assuming you want to get at data residing on IBM i.
You need to provide someway to retrieve the data by some application, in
this case some UI that may be residing on various devices (mobile, PC,
etc.).
The defacto standard is to provide a RESTful API that applications may
invoke to retrieve the data. How the data is rendered I will leave it to
you.
You have a lot of options, each with its pros and cons.
On IBM i, some of the ways you have include:
CGI
PHP
Node.js
Integrated web services server (IWS)
Integrated application server (IAS)
Python
Ruby
I am not an expert on the various technologies, but here is by birds eye
view of the aforementioned technologies (with more details on the ones I
have used ;-)):
CGI - give you total control of the incoming and outgoing payloads. May
be written in any ILE language. The burden is on the application to parse
and generate payload formats such as JSON, XML, etc.
PHP - Open source scripting language. Rich in libraries.
Node.js - Open source project based on Google Chrome JavaScript Engine. It
provides a platform for server-side JavaScript applications running
without browsers.
IWS - application server in support of deploying ILE programs and service
programs as web services (SOAP or REST). ILE programmers only deal with
what they are use to - incoming data (XML or JSON) is parsed and passed as
parameters to ILE programs, and output data is handled the same way.
IAS - application server for Java applications.
Python - Open source scripting language. Rich in libraries.
Ruby - Open source scripting language. Rich in libraries.
General information on CGI and the open source technologies may be found
on the web. For IBM i specific information:
CGI -
https://www.ibm.com/support/docview.wss?uid=isg3T1026866#PASEFASTCGI
PHP -
http://www.zend.com/en/solutions/modernize-ibm-i/ibm-i-product
Node.js, Python, Ruby -
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/Open%20Source%20Technologies
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/07/2018
09:17:20 AM:
Am 7. November 2018 15:22:15 MEZ schrieb Justin Taylor
<JUSTIN@xxxxxxxxxxxxx>:
I think the de facto standard UI is probably HTML5, CSS & JavaScript.
Server-side I'd say PHP or CGI would be the first options to look at.
PHP may be a more "batteries included" option.
-----Original Message-----
From: Bob Cagle [mailto:bcagle@xxxxxxxxxxx]
Sent: Tuesday, November 06, 2018 2:23 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: CRUD app interface
Here's a loaded topic to discuss: I have a new simple CRUD app that I
need to create. Being an old RPG programmer, I have a bevy of "Work
with" green-screen programs at my disposal that I can copy and modify.
But, I want a modern interface. So, which direction would you go?
.NET, CGI, Excel spreadsheet, etc., etc.? Why?
Note: the file resides on the i, and will stay there.
midrange.com
