web.XML, weblogic.XML and application.xml

• 

  Rahul Sharma The web.xml file provides configuration and deployment information for the Web components that comprise a Web application. Examples of Web components are servlet parameters, servlet and JavaServer Pages (JSP) definitions, and Uniform Resource Locators (URL) mappings. This is located in the WEB-INF directory.
  
  Weblogic.xml is the configuration file for all the applications lying in the domain created. It lies in the META-INF directory and contains parameters such as auth-filter, charset-params, container-descriptor, context-root, description etc..

  
  
• 

  Ananth Srinivas Adding to Rahul Sharma application.xml descriptor file for an enterprise application contains basic configuration and deployment information for an application, such as the name and location ofeach module (Every EJB) in the enterprise application and application-wide security roles.
• • 

    Kiran Kumar Ravula Web applications are configured using the web.xml and weblogic.xml deployment descriptors, which:
    Define the run-time environment 
    Map URLs to servlets and JSPs 
    Define application defaults such as welcome and error pages 
    Specify J2EE security constraints 
    Define work managers for applications 
    Set the context root for the application
  • 
    
  • 

    Kiran Kumar Ravula What information will be available in “web.xml” file?
    The web.xml file is a deployment descriptor that is used to configure the following:
    Servlets and JSP registration 
    Servlet initialization parameters 
    JSP tag libraries 
    MIME type mappings 
    Welcome file list 
    Error pages 
    Security constraints and roles 
    Resources 
    EJB references

    
    
  • 

    Kiran Kumar Ravula What information will be available in “weblogic.xml” file?
    Using weblogic.xml, you can configure the following:
    The application’s root context path 
    Application logging 
    Security role mappings 
    Advanced session settings 
    Session clustering 
    References to shared libraries 
    References to server resources (data sources, EJBs, and so on) 
    Work managers and threading 
    Virtual directories 
    JSP compiler options

    
    
  • 

    Vivek Ranjan In simple word...
    Application.xml:- it specifies war files and other application level context . An application is nothing but a bunch of war file.
    Web.xml:- the web.xml hold lot more detail information for the war file . It includes the web app name , servlet mapping,Security roles etc.
    Weblogic.xml:- weblogic specified deployment descriptor file named weblogic.xml ,which define how named resourses in the web.xml file are mapped to weblogic server resourse .

Application Server Hangs

Below are the top 3 reasons why an application server hangs:

Reason #1: it’s a database problem.

This may sound strange, but the main reason an application server hangs is not directly related to the application server itself. If you manage to get a thread dump, you’ll just see a bunch of threads waiting and another group that’s actually running. Another possibility is that the number of waiting threads (or queued threads) will gobble up all available memory and, eventually, lead to an OutOfMemory error.

Reason #2: deadlocks.

If it seems that the application server is doing nothing, look for deadlocks. These can be database deadlocks that cause your SQL queries to hang, or seek the update statements. 

Reason #3: run-away thread.

In cases where the application server is indeed to blame, you should look for a run-away thread. These are hard to detect because they hardly show up on logs since they are usually only written when the request has completed. A run-away thread will probably not return until it has already affected the entire application. Therefore, the hanging request will not be written to the log. These ‘runaway’ threads typically include infinite loops in code.

Weblogic server High CPU Utilization

An error (weblogic.common.resourcepool.ResourceDisabledException: Pool BAMDataSource is Suspended, cannot allocate resources to applications..) has occurred in the Active Data Cache storage system

Steps:

1.  top command –> to know the high CPU consuming process.

2. ps -ef|grep –> to know details of the process consuming high CPU.

3. ls -lrt /proc//fd

or  ls -lrt /proc//fd |grep log  —-> to know the files accessed by the process. To know the log files and other related files.

4. Check the log files, out files etc to get the related error.

503 Bankend Server not Available

Check the Weblogic servers running fine or not.

403 FORBIDDEN (Unauthorized Access)

May be the request behind the forewall.

500 Internal Server Error

A)Check the Database is up or not from the console.

1. Open the console.
2. In the Domain Structure tree, expand Services, then select Data Sources.
3. Click the data source name.
4. Select the Monitoring: Testing tab.
5. On the Testing page, select the instance of the data source that you want to test.
   Date source instances are listed by the server on which they are deployed.
6. Click the Test Table Name button. Test results are displayed at the top of the page.

B) Check the telnet command from the unix box.

1. Login to the unix machine.
2. Use telnet <DBhost_Name> <Port_Num>

Back up of existing domain

Abhishek Porwal Simple way is to make tar File.

Atchut Ram Gundu Use domain-builder.sh file under wlsserver directory which will create a template..

Kumara Guruparan R You can take a template of the existing domain... Also config. XML can be backed up... Moreover the data on the server is backed up by tsm servers

Gaguturi Kamalbee pack means copy the pack the domain and unpack means paste the domain to multiple server

Mohammad Faisal Zakarneh pack used to 'pack' a domain or managed servers only of domain in a template file .. unpack then used to 'unpack' the package packed by pack  


PACK Process 
export PATH=/export/home/wlsuser/bea/weblogic92/common/bin:$PATH
Syntax:
pack -domain=domain -template=template -template_name=“template_name”
[-template_author=“author”][-template_desc=“description”]
[-managed={true|false}][-log=log_file] [-log_priority=log_priority]

if it is in the pack command in the path you can give pack.sh from any directory otherwise you need to goto that path.
Example

bash-3.00$ pack.sh -domain="/export/home/wlsuser/domains/wlscldom" 
-template="/export/home/wlsuser/templates/wlscltemp.jar" -template_name="WLS 
CLUSTER DOMAIN" -log=/export/home/wlsuser/logs/wlscldompack.log -log_priority=INFO

UNPACK Process


To run this we must already run the pack command on a domain which is already existing. The domain template jar must be copied to the destination machine. 

Syntax:
unpack -template=template -domain=domain [-user_name=username]
[-password=password] [-app_dir=application_directory]
[-java_home=java_home_directory] [-server_start_mode={dev|prod}]
[-log=log_file] [-log_priority=log_priority]

Example

bash-3.00$ unpack.sh -template=wlscltemp.jar -domain=domains/wlscldom 
-log=wlscldomunpack.log -log_priority=INFO

----------------------------------------------------------------------------------------------------------------------
To unpack managed server also it will work in the similar manner. But need to put the
 “-managed=true”

Example:

pack.sh -managed=true -domain="/home/wluser/domains/WLclsnm/" -template="/home/wluser/templates/WLclsnm.jar" -template_name="WLS CLUSTER DOMAIN" -log=/home/wluser/logs/wlscldompack.log -log_priority=INFO


unpack.sh -template=WLclsnm.jar -domain=domains/WLclsnm -log=WLclsnmpack.log -log_priority=INFO