WebSphereHome

Here We will See the below updated point

1. Architecture and Application Request Flow
2. Requirement 
3. Download binary




WebSphere is a set of Java-based tools from IBM that allows customers to create and manage sophisticated business Web sites. The central WebSphere tool is the WebSphere Application Server (WAS), an application server that a customer can use to connect Web site users with Java applications or servlets. Servlets are Java programs that run on the server rather than on the user's computer as Java applets do. Servlets can be developed to replace traditional common gateway interface (cgi) scripts, usually written in C or Practical Extraction and Reporting Language, and run much faster because all user requests run in the same process space.

REQUEST FLOW:

once the end user hits the url, that will be going to DNS, from there it will be coming to edgecomponents and it will be routed to webservers.If it is static request,it will be serverd by webserver, if it is dynamic request, then will be forwarded to App.server. if it's related to Servlets/jsps, WebContainer will serve the request or else it will be forward to EJB container, if it requires any communication with DB, it will pick a connection from connection pool using jndi, and it will execute queries on the database and fetch the o/p , responds back.mean while, if request is related to authentication, then uid and pwd will be verified in LDAP and request has to cross the firewalls and ssl handshakes will be done.






















The typical application flow is as follows:

1. A Web client requests a URL in the browser (input page).
2. The request is routed to the Web server over the Internet.
3. The Web server immediately passes the request to the Web server plug-in. All requests go to the Web server plug-in first.
4. The Web server plug-in examines the URL, verifies the list of host name aliases from which it
will accept traffic based on the virtual host information, and chooses a server to handle the
request.
5. A stream is created. A stream is a connection to the Web container. It is possible to maintain
a connection (stream) over a number of requests. The Web container receives the request
and, based on the URL, dispatches it to the proper servlet.
6. If the servlet class is not loaded, the dynamic class loader loads the servlet (servlet init (),
then doGet () or doPost ()).
7. JNDI is used for lookup of either datasources or EJBs required by the servlet.
8. Depending upon whether a datasource is specified or an EJB is requested, the JNDI directs
the servlet:
– To the corresponding database and gets a connection from its connection pool in the case of a
data source.
– To the corresponding EJB container, which then instantiates the EJB when an EJB is
requested.
9. If the EJB request involves an SQL transaction, it goes back to the JNDI to look up the
datasource.
10. The SQL statement is executed and the retrieved data is sent back either to the servlet or
to the EJB.
11. Data beans are created and handed off to JSPs in the case of EJBs.
12. The servlet sends data to JSPs.
13. The JSP generates the HTML that is sent back through the plug-in to the Web server.
14. The Web server sends the output page (output HTML) to the browser.

Requirements:

H/W: 



Comments

Popular posts from this blog

Understanding SSL

Session Management Part-1

WebSphere Application Server