Re: deployment/debugging

I looked back in the archives and don't see as many as I remembered (mismembered?) so I have to assume that some were on other lists.

This recent one http://archive.midrange.com/egl-i/200906/msg00009.html is an example of the kind of thing I mean though. And here's another http://archive.midrange.com/egl-i/200906/msg00000.html .

Another example of what it seems should be simple is this one which even the IBMers seemed unable to resolve http://archive.midrange.com/egl-i/200901/msg00006.html

As I noted before - many of the problems can be resolved if you have enough experience in the App Server/Java arena - but most RPGers don't have that.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On 10-Jul-09, at 1:20 PM, Steve Mervosh wrote:

I haven't seen any of the deployment and debugging problems that Jon
mentions.

If you keep your WebSphere Application Server fix pack level within
RBD/RAD at the same level as WAS on IBM i, after you've auto-deployed
and tested within your WebSphere Test Environment on your PC (accessing
IBM i for DB), it's easy to generate an .ear file and install that on
WAS on IBM i. All you need is a quick sanity test because the WAS
level on your PC you tested thoroughly with is the same as on IBM i.

If a runtime problem exists, and the problem is recreatable, you can go
into step-mode graphical debug from RBD/RAD to determine what is going
on (there is even an ability to debug using the IBM WebSphere
Application Server vs the RBD/RAD WAS version, but since I try to keep
the levels of WAS the same, I just use the PC's version). If the
problem is not recreatable, there is the ability at code
development-time to monitor SQL return codes in your program logic, and
try/onException blocks to handle other types of exceptions, and do your
own more discrete error handling/feedback.

There is a trace option with EGL that I've never really used, that dumps
out tons of error messages. But it should be a rare occasion to need
to look at that if the error handling capabilities of EGL are used when
the application is developed.


********************************************************


I only wish that the deployment and debugging of EGL applications did
not seem to be so problematic. I know _you_ have no problems with it
- but you have extensive Java/JSF/JSP/J2EE/App Server experience. I
watch this list daily and all I see is problem after problem with what
it seems should be simple issues.

When the freebie version comes out I intend to have another go with
the product, but just how is one supposed to debug the problems when
all you see is a five mile long list of Java error messages? Any
suggestions on where to start with that?


--
Steve Mervosh
mervosh@xxxxxxxxxxxxx


--
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.