How do Clients communicate with WLS?

Clients can communicate with WLS as :

  1. Web-Client : A web client is an application that communicates with a web server, using Hypertext Transfer Protocol (HTTP).
  2. Applet : An applet is a small Internet-based program written in Java, a programming language for the Web, which can be downloaded by any computer. The applet is also able to run in HTML. The applet is usually embedded in an HTML page on a Web site and can be executed from within a browser.
  3. Client Application : A client/server application is a piece of software that runs on a client computer and makes requests to a remote server.WLS1

How do WLS accept these requests?

  1. listen address:port (Receive Request)
  2. listen thread (establish Connection)
  3. Socket Muxer (Read request)
  4. Default Execute Thread / WorkManager ( process request over j2EE Container)

Now, once request is received by Execute threads/work Manager, It is processed by Weblogic Server.  So how do WLS process these requests?

 

How do WLS process these requests?

—Of-course we have application deployed on WebLogic Server. What are major components of J2EE applications to reply response for the requests ??

—We have JAVA Servlet, —JSP, —EJB etc at WLS server to process the requests received. In Weblogic Application server we have different containers to provide run-time environment for these components :

  1. Web container : —Web container is the component of a web server that interacts with Java servlets. A web container is responsible for managing the lifecycle of servlets, mapping a URL to a particular servlet and ensuring that the URL requester has the correct access rights. It provide the required run-time environment for the execution of web resources.
  2. EJB Container : An enterprise javabeans (EJB) container provides a run-time environment for enterprise beans within the application server. Click here for more details on EJBs.

Requests from web-client and Applets are handled by Web Container. They do not interact with EJB container directly. As per the request type, if required, web-container further interacts with EJB container for request processing and then respond back to Web-Client/Applet.

Web Client / Applet –> Web Container –> EJB Container

Client Applications can directly interact with Web Container/EJB Container

—Client Application –> Web Container/EJB Container

—Client Application/ EJB can interact with J2EE services like JMS, JDBC, JAAS, etc.

—Client Application/ EJB –> J2EE sevices

 

—EJB/J2EE Components can interact with Backend Services Like DB, Tibco MQ, etc.

—EJB/J2EE Components –> Backend Services Like DB, Tibco MQ, etc.

This is architecture of Weblogic server 🙂

Please post comment for any suggestions/questions on this topic!

Author

12+ Year IT professional SME with expertise in Middleware, Cloud Computing & DevOps Methodology.

3 Replies to “Understanding Weblogic Architecture”

Comments are closed.