1z0-102 Practice Exam Questions with Answers Oracle Weblogic Server 11g: System Administration I Certification

Note #1: If your EJBs will run on a WebLogic Server cluster, Oracle recommends that you deploy them homogeneously—to each Managed Server in the cluster. Alternatively, you can deploy an EJB to only to a single server in the cluster (that is, “pin” a module to a server). This type of deployment is less common, and should be used only in special circumstances where pinned services are required.

Note #2: When you deploy an EJB, you specify the servers and clusters to which the EJB deployment is targeted. After you have deployed an EJB, you can update the servers and clusters to which it is targeted.

To set target servers and clusters for a deployed EJB:

• If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit
• In the left pane of the Administration Console, select Deployments.

The right pane lists the EJBs and other modules that you have deployed, or tried to deploy.

• In the right pane, click the desired EJB.
• Select the Targets tab.

Servers and clusters in the domain are displayed.

• Select the check box next to the individual servers and/or clusters to which you wish to deploy the EJB and click Save.

By default, the Administration Console deploys an EJB to all server instances in the cluster (the "All servers in the cluster" option). To deploy the EJB to selected servers in a cluster, select "Part of the cluster", and then select the individual server instances to which you want to deploy the EJB.

• To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart

B: WebLogic Server supports SSL on a dedicated listen port which defaults to 7002. To establish an SSL connection, a Web browser connects to WebLogic Server by supplying the SSL listen port and the HTTPs schema in the connection URL, for example, https://myserver:7002.

C: Note: Enabling SSL under WLS 10.3

Steps to configure WLS for SSL:

1) Open the WLS console

2) Select from the Domain Structure -> (your domain) -> Environment -> Servers

3) Select the server from the Summary of Servers page you wish to configure for SSL.

4) Under the Settings for (server name) page, select the Configuration tab, then General tab (the defaults).

5) If WLS is running in production mode, select the Lock & Edit button.

6) Select the SSL Listen Port Enabled checkbox, and enter your preferred port in the SSL Listen Port.

7) Press the Save button.

8) If WLS is running in production mode, select the Release Configuration button.

A: The Configure the Administration Server window prompts you to define the configuration information for the Administration Server, including:

Administration Server name

Listen address

Nonsecure and secure (optional) listen ports

B: The Configure Managed Servers window prompts you to define the configuration information for one or more Managed Servers, including:

Managed Server name

Listen address

Nonsecure and secure (optional) listen ports

E: The Configure Clusters window prompts you to define the configuration information for one or more clusters, including:

Cluster name

Multicast address and port

Cluster address that identifies the Managed Servers in the cluster

Frontend host if you are using a proxy server or a firewall.

Frontend HTTP port if you are using a proxy server or a firewall.

The server instance for which you configure the listen address does not need to be running. If it is running, you must restart it after you complete these steps.

Note: You can use the Administration Console to configure selected deployment descriptor element values for an EJB that is deployed as an exploded application.

To configure editable deployment descriptor values for an EJB that is deployed as an exploded application:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

2. In the left pane of the Administration Console, select Deployments.

3. In the right pane, click the desired EJB module.

4. Select the Configuration > General tab.

Selected deployment descriptor elements for the EJB are listed.

5. Enter new values for the elements you want change, and click Save.

6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Not all changes take effect immediately—some require a restart

B: keytool – import

Reads the certificate or certificate chain (where the latter is supplied in a PKCS#7 formatted reply) from the file cert_file, and stores it in the keystore entry identified by alias. If no file is given, the certificate or PKCS#7 reply is read from stdin. keytool can import X.509 v1, v2, and v3 certificates, and PKCS#7 formatted certificate chains consisting of certificates of that type.

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.

-targetstarget_list (for the redeploy command) is not specified here.

It is used to specify the targets on which to distribute, deploy, or redeploy the application or module.

If you do not specify a target list with the -deploy command, the target defaults to:

* the Administration Server instance for new deployments (not the case here)

* the application's current targets for deployed applications (the case in this scenario)

Note:

Syntax:

java [SSL Arguments] weblogic.Deployer [Connection Arguments]

[User Credentials Arguments] COMMAND-NAME command-options

[Common Arguments]

Connection Arguments

The -adminurl value must specify the listen address and listen port of the Administration Server.

-usernameusername. The Administrator username. If you supply the -username option but you do not supply a corresponding -password option, weblogic.Deployer prompts you for the password.

-redeploy.redeploys a running application or part of a running application.

-name deployment_name. Specifies the deployment name of a deployed application or module. The -name option can be omitted, in which case the name is taken from the -source fileargument.

Note: weblogic.Deployer is a Java-based deployment tool that provides a command-line interface to the WebLogic Server deployment API. weblogic.Deployer is intended for administrators and developers who want to perform interactive, command-line based deployment operations.

B:

A reference to a shared Java EE library. Enclose all other elements within library-ref.

Note: A Java EE application can reference a registered shared Java EE library using entries in the application’s weblogic-application.xml deployment descriptor.

Elements include:

library-ref

library-name

D:

Specifies the Work Manager that is associated with the application.

Note: The weblogic-application.xml file is the BEA WebLogic Server-specific deployment descriptor extension for the application.xml deployment descriptor from Sun Microsystems. This is where you configure features such as shared Java EE libraries referenced in the application and EJB caching.

The file is located in the META-INF subdirectory of the application archive.

JMS Configuration option ' Messages Threshold High':

The upper threshold (number of messages stored in this JMS server) that triggers flow control and logging events. A value of -1 disables the events for this JMS server.

If the number of messages exceeds this threshold, the triggered events are:

Log Messages

- A message is logged on the server indicating a high threshold condition.

Flow Control

- If flow control is enabled, the JMS server becomes armed and instructs producers to begin decreasing their message flow.