My Name in a Website

Finally, after playing tennis for almost close to 6 years, I have won a chamionship. This is the Charlotte Tennis association Spring singles challege ladder. My record in the initial rounds is 14-0 and won the playoffs and final. Moving on to 4.0 level for the summer season.

Developer requirements

Learn to focus on the customer requirements rather than the technology. That might mean become a subject matter expert in the end user application. you must be able to focus on the business problem the client/customer wants to solve. If you can see the problem/need from the customer's perspective, be able to suggest process improvements, AND be able to recommend the appropriate technologies to assist in those improvements, you'll be in demand. Discussing requirements with a client, articulating issues to a higher up, or even just giving guidance to and managing jr. developers - all require consistent and concise communication skills that can make a great developer even more valuable. You have to understand the business of the customer enough to be able to talk to them, ask the right questions and finally develop the piece of software they expect.
Next to technical experience, business experience is becoming more and more important. If you have other non IT related skills like communication skills, coaching skills, ... then this also adds extra value to you as a software developer.However, the basis of a good software developer is and stays a solid (technical) knowledge and experience of software development. Additionally we have to pick up other skills and experience in business related areas, communication, planning, organization of a project, ... So, I think in the future we software developers will spend less time on coding while we have to keep up the effort to get the code quality better.
In the end, I think the job of a software developer will be "richer" because we are able to do more then just develop software.

z/os was Request process overview

Request Process Overview
 

The following steps describe the J2EE application flow:

1. A client application sends a request to access the J2EE application.

2. The request is received by the Web server which immediately passes the request to the Web server plug-in.

3. The Web server plug-in chooses a server to handle the request based on the resource being requested, identified by its Universal Resource Locator (URL), and forwards the request.

4. The WebSphere for z/OS daemon routes the request to the application control region based on the context root in the URL.  (i.e. ibi_html or ibi_apps)

5. The control region checks that the request is authorized and places it on the Workload Manager (WLM) queue. If necessary, WLM starts a procedure that is used to start a new servant region address space in response to the queued request. WLM then passes the request to the servant.

6. Servant is the J2EE app server containing a JVM

It locates and loads the J2EE components from the configuration HFS and   starts the applications.

7. Request is handed to Web container within the server, routing it to the proper servlet, based on request’s URL

a. Servlet class is loaded by the dynamic class loader.

b. The Java Naming and Directory Interface (JNDI) looks up data sources required by the servlet.

c.  Data retrieved from one/many sources and returned to servlet.

d. Servlet sends output stream directly or sends data to JSPs.

o        Response: HTML,XML, generated as a response
o        Sent back through WebSphere plug-in to Web server.
 

8. If J2EE application component needs to access corporate data: uses connector (resource adapter) to communicate with the Enterprise Information System (EIS) such as CICS or IMS.

ForwardSourceID:NT000145DE