1z0-599 Oracle WebLogic Server 12c Essentials Free Practice Exam Questions (2025 Updated)

Follow the on-screen instructions to access the table of WebLogic Server installers.

After accessing the installer table, click the File1 link for the Generic Package or OS-specific Package installer, as appropriate for your operating environment. For example, if your operating system is Linux x86, click the File1 link under the Linux (32-bit JVM) column, on the Oracle WebLogic Server 12cR1 + Oracle Coherence row.

A:

* The WEB-INF directory contains the deployment descriptors for the Web application (web.xml and weblogic.xml) and two subdirectories for storing compiled Java classes and library JAR files.

* Web Application - WEB-INF/web.xml ( WEB-INF/weblogic.xml )

The WEB-INF directory is a vital component of your web application. Web application wont run without it.It contains a heirarcy in which you’ll find the necessary configuration information for your web application, and all the class files for your servlets and classes that are called up by your JSPs.

WEB-INF folder contains all the class files for your servlets and classes that are called up by your JSPs

B:

Enterprise Application - META-INF/application.xml (META-INF/weblogic-application.xml) and META-INF/ejb-jar.xml ( META-INF/weblogic-ejb-jar.xml )

Generally comprises of EJBs. Bussiness Tier of an application and EJB basically handels the Bussiness logic of application (distributed objects)

META-INF/application.xml containes Mappings and security roles etc.whereas META-INF/ejb-jar.xml containes ejb classes , session beans mapping etc.,

The META-INF directory is related to .jar files, It contains the manifest file which has list of jars.

A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml (The context root of a web application determines which URLs weblogic will delegate to your web application.

Note:

* Deployment descriptors are xml documents that describe runtime behaviour for the deployment unit. The XML file contains information such as the context root of the web application and the mapping of the portable names of an application's resources to the application Server's resources

The major components of the WebLogic JMS Server architecture, as illustrated in the figure below.

*(A) JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

*(B) JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jmsmd.xsd schema.

*Client JMS applications that either produce messages to destinations or consume messages from destinations.

*(E) WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.

The following figure illustrates the WebLogic JMS architecture.

A:

* Troubleshooting Slow Response Time from the Client and Low Database Usage

These symptoms are usually caused by a bottleneck upstream of the database, perhaps in the JDBC connectionpooling. Monitor the active JDBC connections in the WebLogic Console and watch for excessive waiters and wait times; increase the pool size, if necessary.

* Attribute: Maximum Capacity

Maximum number of physical database connections that this connection pool can contain. Different JDBC Drivers and database servers may limit the number of possible physical connections.

C: Attribute: Statement Cache Size

The algorithm used to maintain the statement cache:

LRU - After the statementCacheSize is met, the Least Recently Used statement is removed when a new statement is used.

Fixed - The first statementCacheSize number of statements is stored and stay fixed in the cache. No new statements are cached unless the cache is manually cleared.

E: If the queue appears starved but adding execute threads does not improve performance,

there may be resource contention. Because CPU utilization is low, the threads are probably

spending much of their time waiting for some resource, quite often a database connection.

Use the JDBC monitoring facilities in the console to check for high levels of waiters or long

wait times. Adding connections to the JDBC connection pool may be all that is required to

fix the problem.

Note:

* If you had a JDBC connection pool where the Initial Capacity and Maximum Capacity attributes were different, you might want to create a gauge monitor to monitor the maximum and minimum number of connections.

By setting the Threshold Low value to be one less than the Initial Capacity, your gauge monitor trapcould monitor the ActiveConnectionsCurrentCount attribute of the JDBCDataSourceRuntime MBean and alert you whenever the number of active connections are less than the Initial Capacity (which might indicate database connectivity problems).

Note:

* When you configure multiple Authentication providers, use the JAAS Control Flag for each provider to control how the Authentication providers are used in the login sequence.

 You can choose the following the JAAS Control Flag settings, among others:

REQUIRED—The Authentication provider is always called, and the user must always pass its authentication test. Regardless of whether authentication succeeds or fails, authentication still continues down the list of providers.

SUFFICIENT—The user is not required to pass the authentication test of the Authentication provider. If authentication succeeds, no subsequent Authentication providers are executed. If authentication fails, authentication continues down the list of providers.

OPTIONAL—The user is allowed to pass or fail the authentication test of this Authentication provider. However, if all Authentication providers configured in a security realm have the JAAS Control Flag set to OPTIONAL, the user must pass the authentication test of one of the configured providers.

* Example:

Setting the Order of Providers

Re-order the OAM Identity Asserter, OID Authenticator, and Default Authenticator by ensuring that the control flag for each authenticator is set as follows:

OAMAuthenticator (REQUIRED)

OracleInternetDirectoryAuthenticator (SUFFICIENT)

DefaultAuthenticator (SUFFICIENT)