Websphere error handling

**ScotsPine** · 12 April 2005, 09:18

and how much

are they paying you for your in-depth expertise in this matter? :rollin

**Rhino** · 12 April 2005, 09:26

Re: and how much

Hi Scotspine

I was wondering what kind of character traits were required to become a moderator on this forum - well now I know :lol

....but seriously I am paid to be a Cobol programmer but have recently done Java training with a view to writing a small pilot application in a Websphere environment. Could do with some advice rather than pisstaking, if that is possible

**HankWangford** · 12 April 2005, 10:09

Re: and how much

all .netted here I'm afraid

**ScotsPine** · 12 April 2005, 10:57

what a savage

put-down, dino. :rollin

like hank, i'm all dotnetted but i imagine you'd have similar (though not as good of course) error handling in java. deal with exceptions at appropriate level, throw where appropriate. use the structured methodologies available. make sure you deal with unhandled exceptions. all depends on the size/extent of your project too i guess.

**Rhino** · 12 April 2005, 13:07

Re: what a savage

.....get outta here - I'm in an uncharacteristically good mood today

Trouble is I have only done the Java courses and know nothing about Websphere - we are currently using eclipse, as the memory upgrades for our machines to run Websphere have not come through yet

If Java follows mainframe logic all errors that did not terminate the application would be handled in the Java, with standard screens and error logs to database files. I am guessing that Websphere error handling would only be necessary where a catastrophic application error occured and the Java could not handle the error - not even sure if this is actually possible. Also not sure whether Websphere is flexible enough to communicate with Java whilst applications are running and could therefore handle standard application errors as well ?

**SandyDown** · 12 April 2005, 15:02

errors

Rhino there are different levels of error handling, at the java / program handling level, programmers need to write and extend from the ususal exception classes (using libraries or prefebly writing their own the latter is a better practice) then logging errors (log4j seems to be popular), at the application server level, included with recent app-servers there should be some easy interfaces which allows you to tune the server, you need to learn the tricks and tips on how to tune it to handle application level and runtime errors. I have good experience in weblogic not websphere but I believe they are identical, there should be built in error and log files that you can tune for error handling and reporting at various levels (warning/critical/fata errors etc bit like log4j). I suggest read documentation there should be a chapter about this subject in every websphere book , even websphere for dummies should contain this information.

**Rhino** · 12 April 2005, 17:35

Re: errors

Hi Sandy

Thanks very much for that.

It would seem like the log4j with custom written error handling routines within the application is the way to go.

Although the Application Server side of Websphere will be useful in larger projects, I don't think we will need it for this one. Have been reading up on the Application Server side and it would appear it is used for 'Enterprise Java Beans' which probably won't be written for this app where there will only be 2 or 3 users in total.

**SandyDown** · 12 April 2005, 18:52

app server

Rhino, if you are not bulding EJBs, and users are very few then I do advise Tomcat, its a very simple app server and quite reliable(that's if your client is happy with an open source server) you can esily deploy an online aplication of JSPs/Java Beans/Servlets html etc...

**Rhino** · 13 April 2005, 08:52

Re: app server

Sandy

Yes - if it weren't for a directive from Ford to use their Websphere environment, it would definately make more sense to use Tomcat for this application.

Websphere error handling