× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



John,

The answers to these questions could fill a book (or two) and some of it depends on what you're using to develop the apps and where it's deployed to. This would be a much better discussion for the WEB-400 list (WDSC is a tool so this is a bit like asking how to build a house on a hammer mailing list). In fact, searching through the archives of that list will likely turn up the answers to some of these questions.

That said, the two key things to learn are how the HTTP protocol works and HTML. Those two things are the basis upon which web applications are built. I would also recommend learning about how CGI works since all web programming conceptually works the same way (there are implementation details that are different with Java and .Net). HTTP, HTML, and CGI are pretty simple things to learn.

A good place to start for HTML would be http://www.w3schools.com. The book "Pro Apache" (http://www.amazon.com/Pro-Apache-Third-Experts-Voice/dp/1590593006/ref=pd_sim_b_title_1) is good and has topics on HTTP, CGI, and DNS (which covers your URL question) and is much, much better than the IBM documentation. It also covers the HTTP server that you will be using (unless you're running an OS older than V5R1 or front ending it with some other platform).

Matt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of John W. Ebrecht
Sent: Friday, May 09, 2008 12:38 PM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Web development vs production

I'm a legacy developer with an opportunity to get to work in a web
environment and I am in need of some guidance about this process from the
conceptual level ...

- 'Is there any publication that describes web application development vs
deploying to production using websphere?
- Does the development to production protocol follow the green screen
methodology? Will we have a development environment, a 'unit test'
environment and a 'system test' environment on the development LPAR (box)
and then deploy (promote) this to production?
- How does the URL for development get launched from a browser? Different
Domain name?
- What kind of operation support is required? Will the operations team
have a learning curve on the subsystems and jobs? Which publications might
describe that?

Thanks
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.