Oracle 1Z0-102 Exam Dumps

Correct Answer: BE

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.

1.

At the JMSModule level (Group level), where a single security policy is specified for a set of JMS resources.

2.

At the individual JMS resource level, which provides much more grained controlled over the operations that you want to secure.

Reference: SECURING WEBLOGIC JMS RESOURCES

Correct Answer: CDE

C: If you created Managed Server while creating domain then you can start Managed Server using startManagedWebLogic command

$BEA_HOME/user_projects/domains//bin

startManagedWebLogic.cmd (for Windows) startManagedWebLogic.sh (for Unix)

Assume that we a created Managed Server MS1 with Admin Port as 7003. startManagedWebLogic.cmd ms1 http://localhost:7003 (Windows)

D: Starting Administration Server (startWebLogic.cmd or .sh)

E: Starting Managed Server (startManagedWebLogic.sh or .cmd)

Correct Answer: BE

B: When in-memory replication is enabled for a web application, WebLogic Server copies session state from one server in the cluster (primary) to one other server

in the same cluster (secondary). The replica on the secondary server is kept up-to-date so that it may be used if the primary server fails.

E: To utilize in-memory replication for HTTP session states, you must access the WebLogic Server cluster using either a collection of Web servers with identically

configured WebLogic proxy plug-ins, or load balancing hardware.

If you choose to use load balancing hardware instead of a proxy plug-in, it must support a compatible passive or active cookie persistence mechanism, and SSL

persistence.

Note 1: In its default configuration, WebLogic Server uses client-side cookies to keep track of the primary and secondary server that host the client's servlet session state. If client browsers have disabled cookie usage, WebLogic Server can also keep track of primary and secondary servers using URL rewriting. With URL rewriting, both locations of the client session state are embedded into the URLs passed between the client and proxy server. To support this feature, you must ensure that URL rewriting is enabled on the WebLogic Server cluster.

Note 2: To support automatic failover for servlet and JSP HTTP session states, WebLogic Server replicates the session state in memory. WebLogic 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. The process of copying a session state from one server instance to another is called in-memory replication.

Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Using WebLogic Server Clusters > Failover and Replication in a Cluster, Failover and Replication in a Cluster