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.

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.

-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.

A: Each connection in a data source has its own individual cache of prepared and callable statements used on the connection. However, you configure statement cache options per data source. That is, the statement cache for each connection in a data source uses the statement cache options specified for the data source, but each connection caches it's own statements.

E: When Test Connections On Reserve is enabled, when your application requests a connection from the data source, WebLogic Server tests the connection using the query specified in Test Table Name before giving the connection to the application.

Testing reserved connections can cause a delay in satisfying connection requests, but it makes sure that the connection is viable when the application gets the connection.

They deploy command is used to deploy an application to a WebLogic Server instance. (A)

The deploy command returns a WLSTProgress object that you can access to check the status of the command. (E)

Note:

Syntax

deploy(appName, path, [targets], [stageMode], [planPath], [options])

* appName

Name of the application or standalone J2EE module to be deployed.

* targets

Optional. Comma-separated list of the target. Each target may be qualified with a J2EE module name (for example, module1@server1) enabling you to deploy different modules of the application archive on different servers. This argument defaults to the server to which WLST is currently connected.

Note 2: The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system administrators and operators use to monitor and manage WebLogic Server instances and domains.

A: If you are testing the production redeployment feature, or you want to use production redeployment with an application that does not include a version string in the manifest file, specify a unique version string by using the -appversion option when deploying or redeploying an application

B: To assign a version identifier to an application, BEA recommends that you store a unique version string directly in the MANIFEST.MF file of the EAR or WAR being deployed.

If you install the WebLogic Server Examples component, the default user weblogic is created that has permission to start and stop WebLogic Server. The default password is welcome1. If you change the password of the weblogic user, WebLogic Server does not automatically update this password in the boot.properties file, which is located in the DOMAIN_NAME/servers/AdminServer/security directory.

If you change the password for user weblogic, you can use either of the following workarounds so that you can continue to boot a WebLogic Server instance via that username and its new password:

* Remove the boot.properties file. Subsequently each time you start WebLogic Server, you are prompted for the username and password. The changed password for the weblogic user will be accepted.

* Modify the existing boot.properties file, changing the username and password as follows:

username=weblogic

password=welcome1

Subsequently during the server startup process, the boot.properties file is encrypted again.

C: If more than one copy of myLibrary is registered, WebLogic Server selects the library with the highest specification version. If multiple copies of the library use the selected specification version, WebLogic Server selects the copy having the highest implementation version.

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

A: The embedded LDAP server contains user, group, group membership, security role, security policy, and credential map information.

C: The credential (usually a password) used to connect to the embedded LDAP server. If this password has not been set, WebLogic Server generates a password at startup, initializes the attribute, and saves the configuration to the config.xml file. If you want to connect to the embedded LDAP server using an external LDAP browser and the embedded LDAP administrator account (cn=Admin), change this attribute from the generated value.

E: You can use either the WebLogic Auditing provider or a custom Auditing provider in a security realm. Although an Auditing provider is configured per security realm, each server writes auditing data to its own log file in the server directory. By default, all auditing information recorded by the WebLogic Auditing provider is saved in the following file:

WL_HOME\yourdomain\yourserver\DefaultAuditRecorder.log.

By writing a custom Auditing provider, however, you can send the records containing audit information to any one of various output repositories, such as an LDAP server, database, or a simple file.

Tasks WebLogic Server Product Installation Procedure

Step 1 - Obtain the appropriate installation file for your platform

Step 2 - Complete the installation planning requirements

Ensure that your system environment meets the requirements for the installation. Also determine your Oracle Middleware home directory, and product installation home directories.

(C) When you are installing WebLogic Server, you are prompted to choose an existing Middleware home directory or specify a path to create a new Middleware home directory. If you choose to create a new directory, the installation program automatically creates it for you.

Step 3 - Determine the appropriate installation mode for your situation

Step 4 - Determine the type of installation

(A) There are two types of installation Typical or Custom. The type of installation depends on the products and sub-components you want to install.

Step 5 - Install the software

Step 6 - Create a WebLogic domain

E: The JDK selection screen.

This screen is displayed only if you selected a Custom installation. It is not displayed if you are running an Upgrade installer.

This screen displays a list of JDKs. This list contains JDKs that are available for (and common across) previous installations of all the selected WebLogic Server components.

Select the JDK that you want to install with the product.

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.