Get Oracle 1Z0-102 Exam Dumps

Answer : C

The backup of the embedded LDAP server is enabled for a domain at a time. See step 2) in Note below.

Incorrect answers:

A: No need to shut down the server. See Note below.

B: The backup feature need to be configured. See Note below.

D: The format of the backup file is not comma-seperated.

Note: To configure the backups of the embedded LDAP server:

* If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit

* Select the Domain you want to configure (for example, mydomain).

* Expand Security > Embedded LDAP.

* Set the Backup Hour, Backup Minute, and Backup Copies attributes on the Embedded LDAP Server page.

* Click Save to save your changes.

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

Answer : A, B

A: Target

The target that this JMSServer is deployed to.

See step 5) in the Note below.

B: Persistent Store

The file or database in which this JMS server stores persistent messages. If unspecified, the JMS server uses the default persistent store that is configured on each targeted WebLogic Server instance.

Note: See step 4) below.

To create a JMS server:

* If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit

* In the Administration Console, expand Services > Messaging and select JMS Servers.

* On the Summary of JMS Servers page, click New.

Note: Once you create a JMS server, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

* On the Create a JMS Server page:

* In Name, enter a name for the JMS server.

* In Persistent Store, select a pre-configured custom file or JDBC store that will be used by the JMS server or click the Create a New Store button to create a store on the fly.

* On the Select Targets page, select the server instance or migratable server target on which to deploy the JMS server. Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host a pinned service, such as a JMS server.

* Click Finish

Incorrect answer:

C: There is no such JMS Server destination attribute.

Answer : A, C, E, F

A: Steps to Deploy Application using Administration Console

* Start the Admin Server and Managed Server.

* Navigate to Administration console http://localhost:7001/console and login.

* Navigate to Domain Environment --> Deployments. Lock the console.

* Etc.

E: To enable the administration port for your domain:

* If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit

* Shutdown all Managed Servers in the domain. You cannot enable the administration port dynamically on a Managed Server.

* Ensure that all servers in the domain are properly configured to use SSL.

* In the left pane of the Console, under Domain Structure, select the domain name.

* Select Configuration > General and select the Enable Administration Port check box to enable the SSL administration port for this domain.

* In the Administration Port field, enter the SSL port number that server instances in the domain use as the administration port. You can override an individual server instance's administration port assignment on the Advanced options portion of the Configuration: General page for the server instance.

* Click Save.

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

Note: If you want to use the Administration Console to make configuration changes, you must first click the Lock & Edit button in the Change Center. When you click Lock & Edit, you obtain a lock on the editable hierarchy of Configuration MBeans for all servers in the domain (the edit tree).

As you make configuration changes using the Administration Console, you click Save (or in some cases Finish) on the appropriate pages. This does not cause the changes to take effect immediately; instead, when you click Save, you are saving the change to the edit tree and to the DOMAIN_NAME/pending/config.xml file and related configuration files. The changes take effect when you click Activate Changes in the Change Center. At that point, the configuration changes are distributed to each of the servers in the domain. If the changes are acceptable to each of the servers, then they take effect. (Note, however, that some changes require a server to be restarted.) If any server cannot accept a change, then all of the changes are rolled back from all of the servers in the domain. The changes are left in a pending state; you can then either edit the pending changes to resolve the problem or revert the pending changes.

Incorrect answers:

G: There is no need to lock the configuration when you add a user (to the default authentication provider).

Note: To create a new user in the embedded WebLogic LDAP server:

1. Log in to the Oracle WebLogic Server Administration Console

2. In Oracle WebLogic Server Administration Console, select Security Realms from the left pane and click the realm you are configuring. For example,myrealm.

3. Select Users and Groups tab, then Users. Click New.

etc.

Answer : B, C

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.

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

Answer : E

The following signature takes the URL, user name, and password all as part of a URL parameter:

getConnection(String URL);

Where the URL is of the form: jdbc:oracle:<drivertype>:<user>/@<database>