1z0-102 Exam Dumps - Oracle Weblogic Server 11g: System Administration I

B:

Security policy for a JMS Queue (Resource Level).

When you define a security policy for an individual destination on a JMS server, you can protect all operations of the destination.

a. Login into the Admin server console –> Navigate to the Queue that needs to be secured.

b. Click on the security tab –> Policies sub tab.

You can see a small drop down list, which lists the set of the operations that can be protected.

c. Click Add Conditions to add the policy conditions.

d. From the predicate list, specify the policy conditions.

e. Specify the role (the global created in E below) which needs to have the access permissions for the JMS Queue. Click Add –> Finish.

E: Create a Global Role and assign the appropriate user accounts to it.

Note: There are two ways of securing the JMS resources.

• At the JMSModule level (Group level), where a single security policy is specified for a set of JMS resources.
• At the individual JMS resource level, which provides much more grained controlled over the operations that you want to secure.

B: The Console Context Path is an advance configuration option.

The context path that you want to use in URLs that specify the Administration Console.

Note: Create a new WebLogic Server domain based on a template. Templates allow you to re-create an existing domain for use in another context, such as migrating a domain containing an application under development to a production environment.

C: An Administration Console extension is a WAR file that contains the resources for a

section of a WebLogic Portal Web application. When you deploy the extension, the

Administration Console creates an in-memory union of the files and directories in its

WAR file with the files and directories in the extension WAR file. Once the extension

has been deployed, it is a full member of the Administration Console: it is secured by

the WebLogic Server security realm, it can navigate to other sections of the

Administration Console, and if the extension modifies WebLogic Server resources, it

participates in the change control process.

A cluster must include at least one server.

A clustered is administered through an administration server, but the cluster consists of managed servers only.

A: You can view any changes that you have saved, but not yet activated, by clicking the View Changes and Restarts link in the Change Center.

C: The View Changes and Restarts link presents two tabs, Change List and Restart Checklist:

* The Change List tab presents all changes that have been saved, but not yet activated.

* The Restart Checklist lists all servers for which non-dynamic changes have been activated, but which require restarts before the changes become effective.

Incorrect:

D: is wrong because dynamic changes usually don’t require a restart if that is all that was changed. If it were mix of dynamic and non-dynamic changes it would require a restart.

F: is wrong because in production mode the change center has the “undo all changes” button so you don’t have to activate the changes before you undo them.

MS Connection Factory: Configuration: Default Delivery

Use this page to define the default delivery configuration parameters for this JMS connection factory, such as the default delivery mode, default time to live, etc.

A: If an object is clustered, failover and load balancing for that object is available.

In a WebLogic Server cluster, application processing can continue when a server instance fails. You “cluster” application components by deploying them on multiple server instances in the cluster—so, if a server instance on which a component is running fails, another server instance on which that component is deployed can continue application processing.

The choice to cluster WebLogic Server instances is transparent to application developers and clients.

B: A clustered application or application component is one that is available on multiple WebLogic Server instances in a cluster. If an object is clustered, failover and load balancing for that object is available. Deploy objects homogeneously—to every server instance in your cluster—to simplify cluster administration, maintenance, and troubleshooting.

Web applications can consist of different types of objects, including Enterprise Java Beans (EJBs), servlets, and Java Server Pages (JSPs).

Note: Load balancing and failover for EJBs and RMI objects is handled using replica-aware stubs, which can locate instances of the object throughout the cluster.

C: Cluster Multicast Address and Port

Identify the address and port you will dedicate to multicast communications for your cluster.

A: When creating a JDBC data source using the Administration Console, you are prompted to select a JDBC driver. The Administration Console provides the driver class name and helps you construct the URL as required by the driver.

B: JDBC Data Source: Targets. Use this page to select the servers or clusters on which you would like to deploy this JDBC data source.

C: JNDI Name, The JNDI path to where this data source is bound. By default, the JNDI name is the name of the data source.

E: When deciding which JDBC driver to use to connect to a database, you should try drivers from various vendors in your environment. In general, JDBC driver performance is dependent on many factors, especially the SQL code used in applications and the JDBC driver implementation.

A: When the HTTP client requests the servlet, HttpClusterServlet proxies the request to the WebLogic Server cluster. HttpClusterServlet maintains the list of all servers in the cluster, and the load balancing logic to use when accessing the cluster. In the above example, HttpClusterServlet routes the client request to the servlet hosted on WebLogic Server A. WebLogic Server A becomes the primary server hosting the client's servlet session.

To provide failover services for the servlet, the primary server replicates the client's servlet session state to a secondary WebLogic Server in the cluster. This ensures that a replica of the session state exists even if the primary server fails (for example, due to a network failure). In the example above, Server B is selected as the secondary.

The servlet page is returned to the client through the HttpClusterServlet, and the client browser is instructed to write a cookie that lists the primary and secondary locations of the servlet session state. If the client browser does not support cookies, WebLogic Server can use URL rewriting instead.

Figure, Accessing Servlets and JSPs using a Proxy:

B: In clusters that utilize Web servers with WebLogic proxy plug-ins, the proxy plug-in handles failover transparently to the client. If a server fails, the plug-in locates the replicated HTTP session state on a secondary server and redirects the client's request accordingly.

D: The WebLogic proxy plug-in maintains a list of WebLogic Server instances that host a clustered servlet or JSP, and forwards HTTP requests to those instances on a round-robin basis.