You use a web browser to log in to a web application that is deployed to WebLogic Server.
When you click link named "publish" on the site, an "Access Denied" message appears.
Which two statements must be true about this server's security configuration?
Answer : D,E
Explanation: D: You were able to log in to the web application that is deployed through
In WebLogic Server, Authentication providers are used to prove the identity of users or system processes.
This implies that your account exists in an authentication provider.
E: Extra security is needed to use the publish link. This could be explained by a security policy attached the publish Link URL.
Reference: Developing Security Providers for WebLogic Server, Authentication Providers
You have set Server log Rotation criteria to either size or time. When a domain is in
Production Mode, which statement is true?
Answer : C
Explanation: By default, when you start a server instance in production mode, the server rotates its local log file whenever the file grows to 5000 kilobytes in size. It does not rotate the local server log file when you start the server.
You can change these default settings for log file rotation. For example, you can change the file size at which the server rotates the log file or you can configure a server to rotate log files based on a time interval. You can also specify the maximum number of rotated files that can accumulate. After the number of log files reaches this number, subsequent file rotations delete the oldest log file and create a new log file with the latest suffix.
Reference: Administration Console Online Help, Rotating Log Files http://docs.oracle.com/cd/E13222_01/wls/docs81/ConsoleHelp/logging.html
Which three methods does WebLogic provide to implement persistent JMS messaging?
Answer : A,B,E
Explanation: A: The main steps for creating a custom file store are as follows:
1.Create a directory where the file stores data will be persisted.
2.Create a custom file store and specify the directory location that you created.
3.Associate the custom file store with the subsystem(s) or migratable target that will be accessing it, such as:
*For JMS servers, select the custom file store on the General Configuration page.
*For Store-and-Forward agents, select the custom file store on the General Configuration page.
*For a Path Service, select the custom file store on the General Configuration page.
B: The main steps for creating a JDBC store are as follows:
Create a JDBC data source or multi data source to interface with the JDBC store.
Create a JDBC store and associate it with the JDBC data source or multi data source.
It is highly recommended that you configure the Prefix option to a unique value for each configured JDBC store table.
Associate the JDBC store with the subsystem(s) that will be using it, such as:
For JMS servers, select the JDBC store on the General Configuration page.
For Store-and-Forward agents, select the JDBC store on the General Configuration page.
For a Path Service, select the custom file store on the General Configuration page.
E: Each server instance, including the administration server, has a default persistent store that requires no configuration.
When a persistent message is sent, it is stored in the WebLogic Persistent Store.
The persistent store provides a built-in, high-performance storage solution for WebLogic
Server subsystems and services that require persistence. For example, it can store persistent JMS messages or temporarily store messages sent using the Store-and-Forward feature. The persistent store supports persistence to a file-based store or to a JDBC- enabled database.
Note 2: A persistent message is guaranteed to be delivered once-and-only-once. The message cannot be lost due to a JMS provider failure and it must not be delivered twice. It is not considered sent until it has been safely written to a file or database. WebLogic JMS writes persistent messages to a WebLogic persistent store (disk-base file or JDBC- accessible database) that is optionally targeted by each JMS server during configuration.
Reference: Using the WebLogic Persistent Store
Managed Server Independence enabled is not selected in the configuration of myserver1.
Which statement is true?
Answer : D
Explanation: To prevent the Administration Server from becoming a single point of failure,
Managed Servers can always function without the presence a running Administration
Server. When a Managed Server starts, it contacts the Administration Server to retrieve its configuration information. If a Managed Server is unable to connect to the specified
Administration Server during startup, it can retrieve its configuration directly by reading a copy of the config.xml file and other files located on the Managed Server's own file system.
A Managed Server that starts in this way is running in Managed Server Independence mode. In this mode, a server uses cached application files to deploy the applications that are targeted to the server.
Reference: Overview of WebLogic Server System Administration, Managed Server
You have opened a terminal window (or a Window command prompt) to run a WLST script named weeklydeployer.py. You enter the following command:
Java weblogic.WLST weeklydeployer.py
Instead of the WLST initializing and the script running, however, you receive the
NoClassDefFoundError java exception for weblogic/WLST.
What is the problem?
Answer : C
Explanation: To set up your environment for WLST:
1. Install and configure the WebLogic Server software
2. Add WebLogic Server classes to the CLASSPATH environment variable
Note: Although the process should be able to build the correct classpath by default, you might hit this issue in some cases. To overcome the problem, you must explicitly set the classpath in the admin console accordingly.
Reference: WebLogic Scripting Tool, Using the WebLogic Scripting Tool
You monitor a running JMS topic with the console and note the following values:
Consumers Current = 3 -
Message Current = 1 -
Message Pending = 0 -
These values do not change for several minutes. Which is the most plausible explanation?
Answer : B
Explanation: For durable subscriptions, WebLogic JMS stores a message in a persistent file or database until the message has been delivered to the subscribers or has expired, even if those subscribers are not active at the time that the message is delivered.
Note #1: Durable subscriptions means that weblogic server will store the messages in a persistent store (i.e a file-store or a JDBC-store) until those messages are delivered to the subscribers/listener. This technic helps weblogic server to make sure that the messages get delivered even if those subscribers/listeners are not active at the time that the message is getting delivered.
As all of us know that in Topics the senders/producers just send the messages to the topic and the receivers/listeners have subscribe them self to get those messages, hence senders/producers does not have any concern if the messages are been received or not.
However with this feature weblogic make sure all the subscribers would get the messages as the messages gets stored in a persistence store.
* Consumers Current Count: Current number of consumers accessing this destination
* MessagesCurrentCount: The current number of messages in the destination. This does not include the pending messages.
* MessagesPendingCount: The number of pending messages in the destination.
Pending messages are over and above the current number of messages. A pending message is one that has either been sent in a transaction and not committed, or that has been received and not committed or acknowledged.
Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Programming
WebLogic JMS > Developing a WebLogic JMS Application, Setting Up Durable
Which statement best describes WebLog’s default application staging behavior?
Answer : D
Explanation: Deployment Staging Mode: stage
Behavior: The Administration Server first copies the deployment unit source files to the staging directories of target servers specified by the Staging Directory Name attribute.
The target servers then deploy using their local copy of the deployment files.
Note: The deployment staging mode determines how deployment files are made available to target servers that must deploy an application or standalone module. WebLogic Server provides three different options for staging files: stage mode, nostage mode, and external_stage mode. The following table describes the behavior and best practices for using the different deployment staging modes.
Reference: Overview of WebLogic Server Deployment, Staging Modes
Indentify two valid elements that can belong in the weblogic-application.xml deployment descriptor.
Answer : B,D
Explanation: B: <library-ref>
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 applications weblogic-application.xml deployment descriptor.
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.
Reference: Developing Applications With WebLogic Server. weblogic-application.xml
Deployment Descriptor Elements -
Reference: Referencing Shared Java EE Libraries in an Enterprise Application
You create a system-wide JMS module named Payroll-JMS and set its default target to an existing cluster in your domain named PayrollCluster. Next, you add a standard JMS topic to Payroll-JMS. To which are you permitted to target this topic?
Answer : B
Explanation: JMS system modules are owned by the Administrator, who can delete, modify, or add JMS system resources at any time. With the exception of standalone queue and topic resources that must be targeted to a single JMS server, the connection factory, distributed destination, foreign server, and JMS SAF destination resources in system modules can be made globally available by targeting them to server instances and clusters configured in the WebLogic domain. These resources are therefore available to all applications deployed on the same targets and to client applications.
Note #1: JMS modules are application-related definitions that are independent of the domain environment. You create and manage JMS resources either as system modules or as application modules.
System modules are globally available for targeting to servers and clusters configured in the domain, and therefore are available to all applications deployed on the same targets and to client applications.
Note #2: JMS servers are environment-related configuration entities that act as management containers for the queues and topics in JMS modules that are targeted to them. A JMS server's primary responsibility for its destinations is to maintain information on what persistent store is used for any persistent messages that arrive on the destinations, and to maintain the states of durable subscribers created on the destinations. JMS servers also manage message paging on destinations, and, optionally, can manage message and/or byte thresholds, as well as server-level quota for its targeted destinations. As a container for targeted destinations, any configuration or run-time changes to a JMS server can affect all the destinations that it hosts.
Reference: Understanding JMS Resource Configuration, JMS System Modules http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_admin/overview.html
The projects architect has provided you with a design diagram that identifies the key components of the new insurance system. From the diagram, you can clearly see that JMS will be used as the communication channel between several applications. Identify four tasks that you may need to perform to support this design.
Answer : A,C,E,F
A: If necessary, create a JMS server to target the JMS module.
F: Target the JMS Server to a weblogic server
Note: The major components of the WebLogic JMS Server architecture:
* JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.
* JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jms.xsd schema.
* Client JMS applications that either produce messages to destinations or consume messages from destinations.
* JNDI (Java Naming and Directory Interface), which provides a resource lookup facility.
JMS resources such as connection factories and destinations are configured with a JNDI name. The runtime implementations of these resources are then bound into JNDI using the given names.
* WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.
Reference: Understanding WebLogic JMS
Which three statements are true about the Node Manager?
Answer : A,B,E
Explanation: A, E: Node Manager enables you to perform these tasks:
* Start and stop remote Managed Servers. (E)
* Monitor the self-reported health of Managed Servers and automatically kill server instances whose health state is "failed".
* Automatically restart Managed Servers that have the "failed" health state, or have shut down unexpectedly due to a system crash or reboot. (A)
B: The WebLogic Server installation process installs Node Manager to run as an operating system service: a daemon on UNIX machines, or a Windows service on Windows-based machines. An operating system service starts up automatically each time the operating system boots.
A key Node Manager feature is the ability to restart Managed Servers after a failure. If the failure is a machine crash, running Node Manager as a service ensures that Node Manager starts up automatically when the machine reboots, and is available to restart Managed
Servers on that machine.
E: Requests from the Administration Console (or JMX utilities such as weblogic.Admin) to start a Managed Server using Node Manager are issued to the Administration Server for the domain that contains the Managed Server.
Reference: Configuring and Managing WebLogic Server, Overview of Node Manager
You have made several changes to variable attributes on a managed server within a domain.
You first locked the console, made some nondynamic changes, made some dynamic changes as well, and then activated your changes. Which statement is true?
Answer : C
Explanation: If a change is made to a non-dynamic configuration setting, no changes to dynamic configuration settings will take effect until after restart. This is to assure that a batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated.
Note: Some changes you make in the Administration Console take place immediately when you activate them. Other changes require you to restart the server or module affected by the change. These latter changes are called non-dynamic changes.
Changes to dynamic configuration attributes become available once they are activated, without restarting the affected server or system restart. These changes are made available to the server and runtime hierarchies once they are activated. Changes to non-dynamic configuration attributes require that the affected servers or system resources be restarted before they become effective.
Reference: Overview of the Administration Console, Dynamic and Non-Dynamic Changes
When you use the Embedded LDAP that is supplied by Oracle WebLogic Server, which three statements are true?
Answer : A,C,E
Explanation: 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:
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.
An application is deployed to your domain and its manifest indicates version 1.1. You then perform an application update by using a manifest that indicates version 1.2.
Indentify two outcomes of this scenario.
Answer : C,E
Explanation: As long as the HTTP Session is valid, the old user will continue to use
All new users will be using "Version 2.
Reference: Oracle WebLogic Server 12c: Configuring and Using Production
View the exhibit.
You are logged in to the WebLogic Server administration console and you are editing the fields shown in exhibit. Which type of WebLogic Server resource are you currently editing?
Answer : E
Explanation: MS Connection Factory: Configuration: Default Delivery
Use this page to define the default delivery configuration parameters for this JMS connection factory, such as the default delivery mode, default time to live, etc.
Reference: JMS Connection Factory: Configuration: Default Delivery