Hi Maurice
With IceBreak, you can choose which path you will go with your web development. You are not bound by any methods or mask programs, but can freely choose from all shelves. All the freedom which IceBreak makes available means of course that you must find the method that suits you best.
Some choose the ASP route, while others choose to split HTML, JavaScript (JS) and RPGLE in different files. Eg. I have recently programmed an "edit system value" maintain application - in ExtJs by the Way. I have divided the pieces into html, JS and RPGLE source in three different files.
You can find all sources here
http://www.icebreak.dk/sysvaledit.zip
First there is my HTML (sysValEdit.html) who is just used to link things together with references to my JS and of course the primary link to the application (
http://myserver:8080/sysValEdit.html) from the URL in the browser.
Eg.:
<html>
...
<script type="text/javascript" src="sysValEdit.js"> </ script> ...
</ Html>
sysValEdit.js is a larger file that is written in 100% JS and it is the one that contains the ExtJS code. It uses AJAX to retrieve my data from my System i. When the browser is ready for showing, it calls my RPGLE program SYSVALEDIT directly on my System i and returns data to the browser. The RPGLE program is written in pure RPGLE except for the first line of code in this example. This line is used by the IceBreak pre-compiler to switch to RPGLE. But if you like to have your RPGLE isolated in a source file in a library, you simple make your own 100 % RPGLE code and compile the source without the IceBreak pre-compiler - use whatever you like, WSDL, RDi, SEU to edit and compile - I don't care. All you need is a binding directory and guess what - it is called ICEBREAK.
This is just one way to use IceBreak on! You can choose the path that you yourself seem to suit you.
You should also know that there is an IceBreak community where you can find lot more information:
http://www.icebreak-community.com/
I hope that you can use my information in your quest for the perfect solution for Web and System i.
Regards
Bent Ronne
Technical Manager
System & Method A/S
-----Oprindelig meddelelse-----
Fra: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] På vegne af Maurice O'Prey
Sendt: 29. december 2010 21:29
Til: 'Web Enabling the AS400 / iSeries'
Emne: Re: [WEB400] 5250 programmer to web programmer
Jim
I guess this quote from
http://www.icebreak.dk/tutorials.htm tells me which
time warp we are talking about (circa 2001 IMHO)
The key to a simple web-development approach is ".asp", Active Server
Pages. This technology has been used on Microsoft web >>servers for a quite
some time. Now we are bringing ASP to the iSeries "Application Server
Program". The syntax is similar but the >>performance is faster with OS/400
program objects executing directly from the IceBreak server.
It may take a while for IceBreak to update their documentation (and product)
in order to catch up with Microsoft's newer offering, ASP.NET?
Agree or disagree?
- Maurice O'Prey
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Maurice O'Prey
Sent: 29 December 2010 19:21
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] 5250 programmer to web programmer
Jim
I'm not sure which time warp you are from, but a couple of hours HTML 101
and everything is sorted doesn't seem to me to be quite enough?
Half a day at least!
- Maurice O'Prey
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of jim t
Sent: 29 December 2010 15:21
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] 5250 programmer to web programmer
We were in the same position you are. We have web teams that were developing
non-iseries apps for the web and the users looked at the iseries as old and
antiquated. I looked at several different apps and suggested we look into
Icebreak (
http://www.icebreak.dk/).
We looked into Icebreak because it uses RPG and/or CL to send/receive data
from
the HTML/AJAX - this way the RPG & CL programmers had a small learning
curve. At
the same time we compared at other methods (like CGIDEV, WebFacing, Zend and
more) but Icebreak's performance was much better - at least 10 times faster
response times. Icebreak comes with it's own web server instead of IBMs HTTP
or
Apache server, so the configuration was simple and the web server also
supported
SSL. Our decision didn't require the developers to learn PHP, JS or Java -
all I
gave them was a couple of hours of HTML 101 instructions to get them
started.
When we started to look into Icebreak software it was a capital expense.
Before
we completed our testing phase Icebreak changed to a fee structure where you
only pay the annual maintenance, so this was easier to get our manangement
to
buy into. During our testing phase we integrated AJAX, JS, CSS, SSL and
iSeries
security for Signon & object authorities - with this setup we leaving
nothing in
the browser's cache, have 2048 bit encryption and the webpage's source does
not
show any business data. We also use the users JOBD to set the LIBL and we
allow
the users to run existing QRYS that output to either HTML or XML - the XML
is
then imported into excel as a pivot table. The webpage's output include
images,
graphs (ExtJS), excel, PDF and of course HTML.
To go along with IceBreak we use TAATool commands to get the LIBL,
WebReport/400
for creating the PDFs, DBU/RDB from Prodata to pull live data from
non-iseries
servers and WDSC for development. These are not required it's just that we
already had them on the systems and it made the development & applications
more
robust.
Finally I created a PF on the iSeries that controls what the users sees.
When
the the user signs in the initial program checks to see what graphics are
shown on the page (we have multiple divisions), which RPG or CLP programs
they
have in their menu bar, and if they have read/write/execute in each of the
programs that they can run. I also include this PF in all RPG apps as an
additional security measure.
If you visit
http://www.icebreak.dk/tutorials.htm then you could check out
their
tutorials. If you then want to impress your boss you could download and
install
a free license - I think it is a 30 day license. After installing you start
the
admin portion of the server and configure a development server. Through the
admin function you can create sample apps that will access live data.
Within
minutes you could have apps running (no business logic yet), but if given a
week
you could convert a few existing 5250 apps to web based that include your
business logic. Part of our business case was that the PC Support staff
didn't
have to install iSeries Access, we required fewer licenses of iSeries Access
&
Rumba, that the apps could run from any PC and that the apps could run on
smart
phones. During the demo to management they were impessed that the apps used
SSL,
were personalized
Jim
----- Original Message ----
From: Buck <kc2hiz@xxxxxxxxx>
To: web400@xxxxxxxxxxxx
Sent: Tue, December 21, 2010 4:10:17 PM
Subject: [WEB400] 5250 programmer to web programmer
This is not a thread about screen scraping.
This is not a thread on moving applications from 5250 to the web.
This is a thread to explore the questions of a 30+ year 5250 programmer
who wants to convince his boss to let him tackle web programming even
though the company has a web programming staff already and I have no
real world web experience.
Let me get it out of the way: my boss wants to screen scrape. He gets
to keep all of his RPG/5250 experts at 100% utilisation and he gets 'web
apps' in a short amount of time. I want to write web apps from scratch
rather than grey-screen our 5250 panels and call it 'web' because the
display device changed.
The inspiration for this post came from a Twitter conversation. I
mention that to note specifically that I'm not afraid of the web nor
modern web apps. I use Scott's socket wrapper API to send tweets from
an IBM i command line. With RPG programs, ha! I have Zend Server
running on my i (I'm testing WikiMedia, the PHP software that runs
Wikipedia) as well as an older install of Perl 5.8.7 (I'm keeping
internal documentation on TWiki, Perl software that does a darned good
job with corporate wikis IMO). All on our i. But these are no
substitute for a portfolio of web sites the boss can look at.
I always thought of the problem of web experience as a bootstrapping
issue. How do I get web experience if the business specifically gives
web experience to the web team? But my conversation with people whose
opinions I implicitly trust inexorably lead me to wonder if I'd done
enough to help myself. The idea is that you start with an open source
project on GitHub or SourceForge, add to it a little until you get
experience in the Ways Of The Web. Maybe start your own project.
I did look some time ago. But the state of most projects is such that
I'm not experienced enough with the language to be able to contribute.
That is, the mindset between my modal brain and the modeless web is too
great to bridge at the same time I'm learning a new language.
So. How did you do it? Did anyone do it? Go from a matching
record-comfy 5250 RPG programmer to AJAX-comfy web programmer by setting
up a home web site? What app did you use to get going and most
importantly, why?
I'm not afraid to learn. But at the same time, I've done HelloWorld in
like a dozen web languages and it hasn't really enabled me to be a
productive web programmer. There must be some middle ground, some
semi-guided trail that will help me move myself closer to the goal. And
the way I figure it, if there is such a path, someone here on this list
has walked it. I don't want to be carried, but I'd like a peek at a
couple of your post cards!
--buck
midrange.com
