Search your topic in Java2share
Home > FAQs
eXTReMe Tracker


Weblogic Application Server FAQs

171.Explain about Large Buffer Attacks?

    • Individuals can try to bring down a Web site by sending a large buffer of data, which starves the system of memory.
    • Administrators can combat this attack by setting a threshold for incoming data.

172.Explain about Connection Starvation?

    • Individuals can try to take down a Web site by sending small, incomplete messages that cause the server to wait.
    • Administrators can combat this attack by setting a threshold.
    • Connections time out while waiting for the remainder of the data if they have reached the threshold set by the administrator.

173.Explain about User Lockout?

    • Individuals attempt to hack into a computer using various combinations of usernames and passwords.
    • Administrators can protect against this security attack by setting the lockout attributes.
    • The administrator can unlock a locked user using the console.

174.How will you Protecting the Administration Console?

    • You can configure a separate administration port for all administration traffic.
    • You can change the Context path of the console.
    • You can disable the console (application).

175.What are the advantages of Deployment Plan?

    • Works by setting or overriding the deployment property values that are defined in an application’s WLS deployment descriptor
    • Helps to easily modify an application’s WLS configuration for deployment into different multiple WLS environments without modifying the deployment descriptor files that are included in the application archive

Enables an application to be deployed to multiple domains or to multiple target servers and clusters that have a different configuration within the same

    1. domain

176.What is the user of weblogic.PlanGenerator?

    1. Is a Java-based deployment configuration tool
    2. Is primarily intended for developers who want to export portions of an Oracle WebLogic Server deployment configuration into an XML deployment plan
    3. Enables you to generate a basic Oracle WebLogic Server configuration for applications that have only J2EE deployment descriptors

177.How will you generate a Deployment Plan Using the Administration Console?

    1. The Administration Console automatically generates or updates the deployment plan.
    2. You can generate a deployment plan using the Administration Console using the following steps:
      • Prepare the deployment files.
      • Install the application archive.
      • Save the configuration changes to a deployment plan.

178.How many types of Staged Deployment are available in WLS?
You can configure deployment per server or for each application as:

    1. staged (default): Files are copied to the preconfigured staging directory for preparation and activation.
    2. nostage: Files are deployed from a static location.
    3. external_stage: Files are copied by a user or a third-party tool before deployment.

179.Explain about Production Redeployment?

    1. You can redeploy a revised version of a production application alongside the older version:
      • Without affecting the existing clients to the application
      • Without interrupting the availability of the application to the new client request
    2. Oracle WebLogic Server automatically manages client connections so that:
      • Existing clients continue to use the older application
      • New client requests are directed to the newer application

The older version is undeployed after all current clients complete their work.

180.Explain about Application Availability, after deploying/install to WLS?

    1. By default, when an application is redeployed:
      • It is unavailable to clients for a brief time
      • Existing clients lose any conversational state
    2. Some types of applications require availability 24 hours a day, seven days a week.
    3. Third-party proxy solutions are possible, but they require multiple servers.