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

A Managed Server is a WebLogic Server instance that runs deployed applications. It refers to the Administration Server for all of its configuration and deployment information. Usually, you use Managed Servers to run applications in a production environment.

See step 4 and 5 below in particular:

To use the WebLogic Server scripts to start Managed Servers:

• Refer to Starting Servers: Before You Begin for prerequisite tasks.

• If you have not already done so, create one or more Managed Servers.

See Creating WebLogic Domains Using the Configuration Wizard or "Create Managed Servers" in the Administration Console Online Help.

• Start the domain's Administration Server.

• In a shell (command prompt) on the computer that hosts the Managed Server, change to the directory that contains the startManagedWebLogicscript:DOMAIN_NAME\bin\startManagedWebLogic.cmd (Windows)DOMAIN_NAME/bin/startManagedWebLogic.sh (UNIX)

where DOMAIN_NAME is the directory in which you located the domain. By default, this directory is BEA_HOME\user_projects\domains\DOMAIN_NAME.

• Enter one of the following commands:

where managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address (host name or IP address) and port number of the domain's Administration Server.

For example, the following command uses startManagedWebLogic.cmd to start a Managed Server named myManagedServer. The listen address for the domain's Administration Server is AdminHost:7001:

c:\bea\user_projects\domains\mydomain\bin\startManagedWebLogic.cmd myManagedServer http://AdminHost:7001

• For each Managed Server that you want to start, open a separate command shell and follow steps 4 and 5. If you are starting Managed Servers on another machine, log in to that machine (remotely or locally) and then follow steps 4 and 5.

Applications look up the data source on the JNDI tree or in the local application context (B) and then reserve a database connection with the getConnection (E) method. Data sources and their connection pools provide connection management processes that help keep your system running and performant.

B: JNDI Name - Enter the JNDI path to where this JDBC data source will be bound. Applications look up the data source on the JNDI tree by this name when reserving a connection.

Note: If you've done any work with JDBC DataSources in a Web application, you already understand the basic process: create an initial JNDI (Java Naming and Directory Interface) context, then use the context to perform a "lookup" to retrieve your DataSource.

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.

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.

This directory is created when the server is started for the first time.