Correct Answer: D

A Managed Server is a WebLogic Server instance that runs deployed applications. It refers to the Administration Server for all of its configuration and deployment

information. Usually, you use Managed Servers to run applications in a production environment.

See step 4 and 5 below in particular:

To use the WebLogic Server scripts to start Managed Servers:

1.

Refer to Starting Servers: Before You Begin for prerequisite tasks.

2.

If you have not already done so, create one or more Managed Servers.

See Creating WebLogic Domains Using the Configuration Wizard or "Create Managed Servers" in the Administration Console Online Help.

3.

Start the domain's Administration Server.

4.

In a shell (command prompt) on the computer that hosts the Managed Server, change to the directory that contains the startManagedWebLogicscript:

DOMAIN_NAME\bin\startManagedWebLogic.cmd (Windows)

DOMAIN_NAME/bin/startManagedWebLogic.sh (UNIX)

where DOMAIN_NAME is the directory in which you located the domain. By default, this directory is BEA_HOME\user_projects\domains\DOMAIN_NAME.

5.

Enter one of the following commands:

startManagedWebLogic.cmd managed_server_name

admin_url (Windows)

startManagedWebLogic.sh managed_server_name

admin_url (UNIX)

where managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address (host name or IP address) and port number

of the domain's Administration Server.

For example, the following command uses startManagedWebLogic.cmd to start a Managed Server named myManagedServer. The listen address for the domain's

Administration Server is AdminHost:7001:

c:\bea\user_projects\domains\mydomain\bin\startManagedWe bLogic.cmd myManagedServer http://AdminHost:7001

6. For each Managed Server that you want to start, open a separate command shell and follow steps 4 and 5. If you are starting Managed Servers on another machine, log in to that machine (remotely or locally) and then follow steps 4 and 5.

Reference: Starting Managed Servers with a Startup Script

Correct Answer: D

This directory is created when the server is started for the first time.

Correct Answer: CDE

C: Choose the Startup Mode Specify the startup mode for your domain. Either Development or Production

D: The Create WebLogic Domain window prompts you to specify the name and pathname for the domain, and initiate its creation.

E: The Configure Administrator Username and Password window prompts you to specify a username and password to be used for starting the Administration Server.

Reference: Creating WebLogic Domains Using The Configuration Wizard http://docs.oracle.com/cd/E13179_01/common/docs92/confgwiz/newdom.html

Correct Answer: A

The WLST life cycle shutdown command gracefully shuts down a running server instance or cluster.

Reference: WebLogic Scripting Tool ,Life Cycle Commands

Correct Answer: C

A managed server (not a CMO, not an administration server) is created.

Port is 8008.

Note: Listing: Creating a Managed Server

connect("username","password")

edit()

startEdit()

svr = cmo.createServer("managedServer")

svr.setListenPort(8001)

svr.setListenAddress("my-address")

save()

Reference: WebLogic Scripting Tool, Using WLST Online to Update an Existing Domain

Correct Answer: C

To set up your environment for WLST:

1.

Install and configure the WebLogic Server software

2.

Add WebLogic Server classes to the CLASSPATH environment variable

Note: Although the process should be able to build the correct classpath by default, you might hit this issue in some cases. To overcome the problem, you must explicitly set the classpath in the admin console accordingly. Reference: WebLogic Scripting Tool, Using the WebLogic Scripting Tool

Correct Answer: B

For durable subscriptions, WebLogic JMS stores a message in a persistent file or database until the message has been delivered to the subscribers or has expired, even if those subscribers are not active at the time that the message is delivered.

Note #1: Durable subscriptions means that weblogic server will store the messages in a persistent store (i.e a file-store or a JDBC-store) until those messages are delivered to the subscribers/listener. This technic helps weblogic server to make sure that the messages get delivered even if those subscribers/listeners are not active at the time that the message is getting delivered.

As all of us know that in Topic's the senders/producers just send the messages to the topic and the receivers/listeners have subscribe them self to get those messages, hence senders/producers does not have any concern if the messages are been received or not. However with this feature weblogic make sure all the subscribers would get the messages as the messages gets stored in a persistence store.

Note #2:

*

Consumers Current Count: Current number of consumers accessing this destination

*

MessagesCurrentCount: The current number of messages in the destination. This does not include the pending messages.

*

MessagesPendingCount: The number of pending messages in the destination.

Pending messages are over and above the current number of messages. A pending message is one that has either been sent in a transaction and not committed, or that has been received and not committed or acknowledged.

Incorrect answers:

A: When a topic is paused for production, it prevents any new message production operations from both new and existing producers attached to that topic.

C: There is no pending message here. So there cannot be a message that a consumer has not acknowledged.

D: Non-durable messages are not stored.

Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Programming WebLogic JMS > Developing a WebLogic JMS Application, Setting Up Durable Subscriptions

Correct Answer: C

File persistence use less memory than in-memory replication, and does not need access rights to the company's database.

Note:

You use session persistence to permanently store data from an HTTP session object to enable failover and load balancing across a cluster of WebLogic Servers.

When your applications stores data in an HTTP session object, the data must be serializable. There are five different implementations of session persistence:

*

Memory (single-server, non-replicated)

*

File system persistence

*

JDBC persistence

*

Cookie-based session persistence

*

In-memory replication (across a cluster)

Incorrect answers:

A: Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.

D: JDBC persistence stores session data in a database table using a schema provided for this purpose. You can use any database for which you have a JDBC driver. You configure database access by using connection pools.

Note: When you use memory-based storage, all session information is stored in memory and is lost when you stop and restart WebLogic Server.

Reference: Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, Using Sessions and Session Persistence

Correct Answer: BC

The WEB-INF directory contains the deployment descriptors for the Web application (web.xml (C) and weblogic.xml) and two subdirectories for storing compiled

Java classes (B) and library JAR files. These subdirectories are respectively named classes and lib. JSP taglibs are stored in the WEB-INF directory at the top

level of the staging directory. The Java classes include servlets, helper classes and, if desired, precompiled JSPs.

Reference:

Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, Creating and Configuring Web Applications

Correct Answer: BD

In WebLogic Server, you configure database connectivity by adding data sources to your WebLogic domain. WebLogic JDBC data sources provide database access and database connection management. Each data source contains a pool of database connections that are created when the data source is created and at server startup. Applications reserve a database connection from the data source by looking up the data source on the JNDI tree or in the local application context and then calling getConnection(). When finished with the connection, the application should call connection.close() as early as possible, which returns the database connection to the pool for other applications to use.