Search your topic in Java2share
Home > FAQs
eXTReMe Tracker

Weblogic Application Server FAQs

61.What is the user of Log Filters in Weblogic?
Log filters:

    • Control the log messages that get published
    • Are based on the values of message attributes
    • Can be applied to different message destinations:
      • Server log file
      • Server memory buffer
      • Server standard out
      • Domain log file

62.What is the user of Network channels in Weblogic?
Adds flexibility to the networking configuration:

    • Multiple NICs for a single WLS server
    • Specific NICs or multiple port numbers on a NIC for specific WLS servers
    • Ability to use multiple IP addresses with each server
    • Ability to use a single IP address with multiple ports
    • Ability to configure the cluster multicast port number independently of the port numbers used by the cluster members
    • Multiple SSL configurations on one server

Network channels:

    • Define the set of basic attributes of a network connection to WLS
    • Can assign multiple channels to a single server (segment network traffic)
    • Can prioritize internal (non-URL) connections
    • Can separate incoming client traffic from internal server to server traffic in a domain
    • A “default” channel gets generated when a server is created.

63.How will you configure a web application in Weblogic?
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

      64.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

      65.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

      66.To configure a “web service” Applications in Weblogic, what are all the files required as a deployment descriptor?
      A Web service application:

        • Responds to HTTP client requests using the Simple Object Access Protocol (SOAP)
        • Uses the same structure as a Java EE Web application
        • Supports two additional deployment descriptors:
          • webservices.xml
          • weblogic-webservices.xml

      67. What is the Virtual directory Mappings? Which file you are going to provide these virtual directory mappings?
      Virtual directories:

        • Can be used to refer to physical directories
        • Enable you to avoid the need to hard code paths to physical directories
        • Allow multiple Web applications to share common physical directories for specific requests such as images
        • Decrease duplication of files across applications
        • Are configured in weblogic.xml


      68.What is the deployment descriptor file for ejb applications? What are all the information is going to provide in that file?
      Ejb application deployment descriptor file in Weblogic is “weblogic-ejb-jar.xml”.
      Using weblogic-ejb-jar.xml, you can configure the following:

        • Security role mappings
        • Advanced security settings
        • EJB clustering
        • EJB pooling and caching
        • Work managers and threading

      69.What is an Enterprise Application?

        • An enterprise application is a grouping of several resources into one deployable unit that is packaged in an .ear file.
        • These resources include:
          • Web applications (.war)
          • EJB applications (.jar)
          • Java applications (.jar)
          • Resource adapters (.rar)

      70.What is the user of Enterprise Applications?
      Use enterprise applications to:

        • Avoid namespace clashes
        • Declare application wide security roles
        • Deploy an application as one unit
        • Share application wide EJB resources
        • Configure local JDBC data sources
        • Configure local JMS resources
        • Configure local XML resources