Showing posts with label WORK MANAGERS:. Show all posts
Showing posts with label WORK MANAGERS:. Show all posts


If Weblogic receives more load than expected, there may be issue with Weblogic performance, later it may crash.
To avoid this abnormal behavior Weblogic gives us an option called WORK MANAGERS.
we have 6 different work managers along with main work manager. Those work managers are:
1.Response Time Request Class.
2.Fair Share Request class.
3.context Request class.
4.Maximum Threads constraint.
5.minimum Threads constraint.
6.Capacity constraint.
console --->environment--->work Managers. new and create the work manager you want out of 6 work managers. new and create main work manager. the main work manager and add the child work managers to main work manager, before you crate work managers. the work manager to cluster.
using overload option we can define how many user requests, your each manage server can hold at a time.
            The defaulttotal number of user requests is 65536.
HOW TO CONFIGURE OVERLOAD:                                                                                                  
1.Goto console ---------->environment---->servers------>open individual server.
2.Goto configuration and goto overload.
3.provide the number for user requests. the configuration.
When we provide Weblogic access to outside Application members or outside organization peoples,it is very easy to hack because we provide the URLs. The URLs  have host name or IP address and port numbers.
To avoid this situation we go for an option called create an alias. And map actual host name and port numbers to particular alias name. To create alias Weblogic provides an option called VIRTUAL HOST.
 → Using virtual host option we can create the virtual servers, target the virtual servers to the cluster. And deploy the Application to the virtual host.
Once Virtual host is created, this virtual host name is one of the option to target the Application during Application deployment.
1.Goto console----->environment---->virtual host.
2.provide virtual host name.
3.Target the virtual host to the cluster. the configuration. the virtual host and provide the server names to which servers virtual host is associated. the configuration.
process wise virtual hosts are equal to the manage servers and it has both Weblogic and access logs.
The process of verify your username and password and allow you to login to your Application is called as authentication.
To authenticate users Weblogic maintains all the userdata in LDAP.
LDAP:(Lightweight Directory Access Protocol) 
LDAP is used for storing the user profiles apart from storing the profiles LDAP provides an extra advantages like:
Applying password policies, Applying roles and other restrictions.
when we installed Weblogic both LDAP and DATABASE will be installed automatically. And inbuilt with Weblogic.
While database stores the data in the row and column format, LDAP stores the data as profile. And profile has n number of attributes.
                                        |                           |------------------->
                                        |                          |------------------>
                                        |                          |------------------->
                                                                     |--------------->      profile