Search your topic in Java2share
Home > FAQs
eXTReMe Tracker


Weblogic Application Server FAQs

71.What is the user of “weblogic-application.xml” deployment descriptor file?
Using weblogic-application.xml, you can configure:

    • References to shared libraries
    • Work managers and threading
    • Default EJB and Web application parameter values

We can configure enterprise wide WLS-specific features with the weblogic-application.xml deployment descriptor:

    • XML parsers
    • XML entity mappings
    • JDBC data sources
    • JMS connection factories and destinations
    • Security realms

72.What is the user of Weblogic shared java EE Libraries?
A Shared Java EE library:

    • Is a reusable portion of a Web or enterprise application
    • Is referenced by other deployed applications
    • Avoids duplicating source files among Java EE projects
    • Can contain deployment descriptors that are merged with the application’s descriptors

73.Explain about deployment methods in Weblogic?

    • WLS supports three deployment methods:
      • Auto-deployment
      • Console deployment
      • Command-line deployment
    • You can deploy:
      • Enterprise, Web, and EJB applications
      • Web services
      • J2EE libraries
      • JDBC, JMS, and Diagnostic Framework modules
      • Resource adapters
      • Optional packages
      • Client application archives
    • Applications and EJBs can be deployed:
      • In an archived file (.ear, .war, .jar)
      • In an exploded (open) directory format

74.How many ways we can deploy an application to Weblogic servers?
Several methods are available to deploy the Oracle WebLogic Server applications and shared libraries, including:

    • Administration Console
    • WebLogic Scripting Tool (WLST)
    • weblogic.Deployer Java class
    • wldeploy Ant task
    • Auto-deployment folder

75.Explain about auto deployment in Weblogic?
If Production Mode is OFF:

    • You can install an application simply by copying it (manually or using the console) to the “autodeploy”
      directory of the domain
    • The Administration Server monitors this directory for new, changed, or removed applications
    • This configures, targets, and deploys the application only to the Administration Server
  • Location of Applications Directory:
  • $BEA_HOME/user_projects/domains/domain_name/autodeploy

76.Explain about FastSwap and On-Demand Deployment in Weblogic?

    • WebLogic’s FastSwap feature is:
      • Enabled using the WebLogic deployment descriptors
      • Available only if the domain is not running in production mode
      • Applicable only to Web applications that are not archived
    • When enabled:
      • WebLogic automatically reloads the modified Java class files within applications
      • Developers can perform iterative development without an explicit redeployment
  • On-demand deployment:

Excerpt from weblogic.xml:
<fast-swap>true</fast-swap>

77.While deploying an application to Weblogic, what is the difference between Development and Production Mode?

    • An Administration Server starts using either:
      • The development mode, which turns auto-deployment on
      • The production mode, which turns auto-deployment off
    • The Administration Server starts in the mode selected at domain creation time.
    • The mode is set for all Oracle WebLogic Servers in a given domain.

78.Explain about console deployment method?
Deploying with the console allows full administrator control:

    • Installation from a location of your choice
    • Manual configuration of application name
    • Targeting of application to individual servers and/or clusters
    • Configuring the application without targeting it
    • Activating deployment when desired

79.Explain about command line deployment?

    • The weblogic.Deployer utility allows you to perform deployment operations similar to those available in the console.
    • weblogic.Deployer actions can also be scripted with the Ant task wldeploy.

weblogic.Deployer Syntax:
% java weblogic.Deployer [options]
[-deploy|-undeploy|-redeploy|-start|-stop|-listapps] [file(s)]
Prepare and deploy a new application:
java weblogic.Deployer -adminurl t3://adminserver:7001
   -username myuser –password mypass –name HRServices
   -source /usr/HRServices.ear -targets serverA –deploy
Redeploy an application:
java weblogic.Deployer -adminurl t3://adminserver:7001
   -username myuser –password mypass –name HRServices
   –redeploy
Undeploy an application:
java weblogic.Deployer -adminurl t3://adminserver:7001
   -username myuser –password mypass –name HRServices
   –undeploy
List all applications:
java weblogic.Deployer -adminurl t3://adminserver:7001
   -username myuser –password mypass -listapps

80.What is JNDI?

    • The Java Naming and Directory Interface is an API for uniformly accessing the different naming and directory services.
    • This is a major step forward because:
      • Different services use vastly different naming schemes
      • Java applications can now navigate seamlessly across databases, files, directories, objects, and networks