Interview Questions.

Q1. What Are Deployment Descriptors?

Modules and applications have deployment descriptors—XML files—that describe the contents of the listing or JAR document. Deployment descriptors are text documents formatted with XML tags. The J2EE specifications define widespread, transportable deployment descriptors for J2EE modules and applications.

Q2. What Are The Admin Default Ports?

The non-SSL concentrate port for the Administration Server's default network configuration is 7001 by means of default.

 The SSL concentrate port for the Administration Server's default network configuration is 7002 by means of default.

WebLogic Admin servers and Managed servers could communicate with Admin port that is separate network channel. So that different communications may be run on specific networks.

Q3. How To Configure A Db Connection Pool?

Choose the DB type (Oracle, Sybase, Mysql, and so forth...).

Then choose the driving force type for the DB.

Give the connection pool name.

Give the DB Service ID, schema call and password.

Then it's going to ask for trying out the connection pool/DataSource.

After a success connection, it will ask you to create and set up the relationship pool target to server or cluster. After creating new connection pool constantly factor the jdbcstore to the connection pool created. This is needed because A JMS JDBC shop will be used for persistent messaging.

After every JDBC connection, we should restart the server if there is startup classes dependancy exists otherwise no restart required in WebLogic nine.X and higher versions.

Q4. What Is The Difference In The Web.Xml And Weblogic.Xml?

An application-specific XML-based deployment descriptor report named web.Xml, which lists your software's J2EE additives and their configurations as J2EE modules. Each J2EE module is a set of one or more J2EE additives of the identical field type (Web or EJB) that are represented via one thing deployment descriptor for that type inside the net.Xml report.

  A WebLogic-particular deployment descriptor report named weblogic.Xml, which defines how named resources within the net.Xml file are mapped to WebLogic Server sources. Examples of weblogic.Xml attributes consist of HTTP session parameters, HTTP cookie parameters, JSP parameters, useful resource references, security role assignments, and box attributes.

Q5. What Is Jndi?

Java Naming and Directory Interface:

 Applications use naming offerings to find objects information resources, EJBs, JMS, MailSessions, and so forth in the WebLogic domain. A naming service friends names with objects and reveals gadgets t3 protocol will be used. (The RMI registry is a great instance of a naming carrier.)

 JNDI affords a not unusual-denominator interface to many current naming services, including LDAP (Lightweight Directory Access Protocol) and DNS (Domain Name System). These naming offerings maintain a fixed of bindings, which relate names to items and offer the potential to appearance up objects through name. JNDI permits the components in allotted applications to locate each other.

 The WebLogic Server implementation of JNDI materials techniques that:

Give clients get entry to to the WebLogic Server naming services

Make gadgets available in the WebLogic namespace

Retrieve items from the WebLogic namespace

Q6. What Are Weblogic Clusters?

A WebLogic Server cluster includes more than one WebLogic Server server instances strolling simultaneously and operating collectively to provide increased scalability and reliability. A cluster seems to customers to be a unmarried WebLogic Server example. The server times that constitute a cluster can run at the same gadget, or be placed on unique machines. You can increase a cluster's ability through including additional server instances to the cluster on an existing machine, or you could add machines to the cluster to host the incremental server times. Each server instance in a cluster ought to run the same version of WebLogic Server.

 Benefits of clustering:

Scalability:

 The capacity of an software deployed on a WebLogic Server cluster may be improved dynamically to fulfill call for. You can upload server instances to a cluster without interruption of provider, the application continues to run with out effect to customers and stop users.

High-Availability:

In a WebLogic Server cluster, application processing can hold whilst a server instance fails. You "cluster" software components through deploying them on multiple server instances within the cluster, so, if a server instance on which a issue is strolling fails, any other server example on which that thing is deployed can hold utility processing.

Q7. What Is The Default Jvm Used For Weblogic?

Sun Hotspot JDK default for Development installation, JRockit is for Production mode for WebLogic 11g and 12c. Operating environment also thing to select the Certified JDK JVM. If you want to exchange you need to specify it.

Q8. How To Change From Default Jvm To Other?

When you upgrade a website to WebLogic Server eight.1, keep in mind upgrading your JVM to JRockit. WebLogic JRockit is a JVM designed for strolling server-aspect programs in Windows and Linux going for walks on Intel architectures. For server-side applications, JRockit has those benefits over different virtual machines:

 It employs adaptive optimization, which detects and removes bottlenecks within the deployed software.

 It is designed in particular for the unique requirements of server-aspect applications, which have a tendency to be parallel and thread-in depth, to run for longer durations of time, and no longer to use graphical interfaces.

 You can screen JRockit the use of the WebLogic Server Administration Console.

 Steps to change:

 In the server begin scripts, set JAVA_HOME (or equivalent) shell variables to factor to the JRockit root directory. For example, alternate:

@rem Set person-defined variables.

Set JAVA_HOME=WL_HOMEjdk131

 in which WL_HOME is the WebLogic Server 7.0 set up directory, to

@rem Set user-defined variables.

Set JAVA_HOME=WL_HOMEjrockit81_141_02

 in which WL_HOME is the WebLogic Server 8.1 set up directory.

 Change the domain’s config.Xml to apply the JRockit javac.Exe. For example, change

JavaCompiler="WL_HOMEjdk131binjavac"

 wherein WL_HOME is the WebLogic Server 7.0 set up listing, to

JavaCompiler=WL_HOMEjrockit81_141_02binjavac”

wherein WL_HOME is the WebLogic Server eight.1 installation directory.

 Remove from server start scripts any switches particular to the Sun JVM. For instance, from the begin command:

echo on "%JAVA_HOME%binjava" -hotspot .... Weblogic.Server delete “-hotspot”.

Q9. What Are The Modes Of Operation For Weblogic Server Domains?

There are two modes: Development and manufacturing mode:

 Development mode:

You use development mode whilst you're developing your packages. Development mode makes use of a at ease security configuration and allows you to car-installation programs.

You can use the demonstration virtual certificate provided by means of the WebLogic Server protection offerings. With those certificates, you could layout your software to paintings within environments secured by way of SSL.

WebLogic Server instances can robotically install and update packages that are living in the domain_name/programs directory.

When you start a server, the server mechanically renames (rotates) its nearby server log report as server-call.Log.N. For the the rest of the server session, the server rotates its neighborhood log document whenever the scale of the record reaches 500 kilobytes.

The default quantity of threads to be had to Execute Queues is 1@

 The default ability is 15 JDBC connections.

 Production mode:

 You use manufacturing mode while your utility is walking in its final form. A production domain makes use of full protection and might use clusters or different superior functions.

A caution message is displayed if you use the demonstration virtual certificate.

The automobile-deployment function is disabled, so that you ought to use the WebLogic Server Administration Console or the weblogic.Deployer tool.

A server rotates its nearby log document after the dimensions of the report reaches 500 kilobytes.

The default quantity of threads to be had to Execute Queues is two@

The default capacity is 25 JDBC connections.

Q10. How To Make A Managed Server?

Backup the configuration with the aid of rename config.Xml with config.Xml_date

Configure the modifications inside the  startManagedWebLogic.Sh /cmd  with weblogic domestic and java domestic and deliver the admin severs URL up to date

Go to weblogic admins console and upload a controlled server and deliver the IP and port of the managed server. All the changes confirmed then begin the server the use of startManagedWebLogic.Sh script gift inside the area bin.

Q11. What Is A Domain Template?

A area template is a jar file default one is wls.Jar report, that's '/bea/weblogic81/common/templates/domain names/, it has all the functions this is required for the same old weblogic area, we are able to even create area template of our very own configuration. By this template we dont need to configure on every occasion we create a new domain.

 By using template we will:

Create servers.

Clusters.

Machines.

Configure offerings which include JMS, JDBC, Applications

Q12. How To Configure Jms?

      JMS (Java Message Service) is a widespread API for accessing enterprise messaging systems. Specifically, WebLogic JMS:

      Enables Java applications sharing a messaging system to change messages.

      Simplifies application improvement with the aid of providing a standard interface for growing, sending, and receiving messages.

      Using the Administration Console, you outline configuration attributes to:

  Create JMS servers and target a WebLogic Server instance or a Migratable Target where the JMS server may be deployed.

 Create and/or customise values for JMS servers, connection factories, destinations (queues and topics), JMS templates, destination sort order (the usage of vacation spot keys), chronic shops (document or JDBC), paging stores, session pools, and connection customers.

 Define message and/or bytes thresholds and quotas, as well as a maximum allowable message size on your JMS servers, destinations, and templates.

Enable any preferred WebLogic JMS functions, together with:

Server clustering the usage of multiple connection factories.

      High availability and cargo balancing for destinations throughout a cluster by the use of dispensed locations.

      Persistent messages and sturdy subscribers.

      Paging out message bodies during top load intervals to free up reminiscence.

      Controlling message drift in the course of peak load durations, inclusive of blocking off message manufacturers.

      Establishing a message expiration coverage to make sure that expired messages are cleaned up immediately.

      Preventing message quota errors via temporarily blockading message producers from sending messages to a destination when it exceeds its specified most message quota.

      Concurrent message processing thru session swimming pools.