RE: Websphere Learning Curve

[michael@xxxxxxxxxxxxxxxxxx]

Jay -

The decision is more along the lines of application serving versus
Common Gateway Interface. And there's a whole debate about that. IMO,
most things that people want to do can be done with CGI stuff. However,
that usually means that you're hosting the CGI program on your business
logic server (iSeries), where an application server (like WAS) could be
hosted on Linux or Windows and talk to the backend. This should reduce
security exposure. 

Some people say that CGI doesn't scale well. Others say it scales fine.
I think the application server concept is more flexible, but it's more
complicated to implement. There are also many applications that need an
application server, so your choices could be limited by that.

But, if you want to put up some web pages that are served by your
iSeries, and have users fill out forms and get data back from the
iSeries, you can do that simply with CGI. If you need to implement
someone else's code, and they require an application server, then you
need WAS...or Tomcat.

> -------- Original Message --------
> Subject: RE: Websphere Learning Curve
> From: jns <JNS@xxxxxxxxxx>
> Date: Mon, June 20, 2005 11:55 am
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> Michael, the forms are primarily NON Static. 
> Your point is good, but it raises another question, Why would anyone go to a 
> websphere platform?
> 
> > -----Original Message-----
> > From: michael@xxxxxxxxxxxxxxxxxx [mailto:michael@xxxxxxxxxxxxxxxxxx]
> > Sent: Monday, June 20, 2005, 8:40 AM
> > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Subject: RE: Websphere Learning Curve
> > 
> > Do they just want static forms (PDFs maybe) posted on a web site for
> > download, or do they want interactive forms that will accept
> > information and access a database and post information back? For the
> > former, WAS is not needed at all - the Apache web server will work
> > fine. If it's the latter, then also look at CGI programming.
> > 
> > > -------- Original Message --------
> > > Subject: RE: Websphere Learning Curve
> > > From: jns <JNS@xxxxxxxxxx>
> > > Date: Mon, June 20, 2005 11:21 am
> > > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > 
> > > Yes WAS. The company wants to have their shipping rates, ins.  posted, the
> > tracking of shipments, the import forms.
> > > > -----Original Message-----
> > > > From: michael@xxxxxxxxxxxxxxxxxx [mailto:michael@xxxxxxxxxxxxxxxxxx]
> > > > Sent: Monday, June 20, 2005, 7:23 AM
> > > > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > > Subject: RE: Websphere Learning Curve
> > > > 
> > > > Installing Websphere on iSeries is easy. A few clicks and it's
> > > > installed. Creating applications to work under Websphere Application
> > > > Server is a different story. What is your planned use of Websphere? And
> > > > I assume you're talking Application Server (WAS).
> > > > 
> > > > > -------- Original Message --------
> > > > > Subject: Websphere Learning Curve
> > > > > From: jns <JNS@xxxxxxxxxx>
> > > > > Date: Mon, June 20, 2005 9:38 am
> > > > > To: <midrange-l@xxxxxxxxxxxx>
> > > > > 
> > > > > I know this has been discussed, but if someone has no Websphere
> > > > > practical knowledge what is the learning curve like? Suppose a company
> > > > > decides to install Websphere, what is the training needed for staff, -
> > > > > Operators, Programmers. Is this something that is a matter of 
> > > > > following
> > > > > a set of instructions, say like doing an OS upgrade, 5.2 to 5.3? 
> > > > > Thanks,
> > > > > Jay
> > > > > ---------------------------------------------------------------------
> > > > > -- 
> > > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > > > > list
> > > > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > > > To subscribe, unsubscribe, or change list options,
> > > > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > > > Before posting, please take a moment to review the archives
> > > > > at http://archive.midrange.com/midrange-l.
> > > > > 
> > > > > 
> > > > 
> > > > -- 
> > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > > To subscribe, unsubscribe, or change list options,
> > > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > > Before posting, please take a moment to review the archives
> > > > at http://archive.midrange.com/midrange-l.
> > > > 
> > > -- 
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> > > list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> > 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.