Java Enterprise and Web Technologies

WebLogic allows multiple JMS servers on a single WebLogic server instance (C is true). A JMS server is deployed to and runs on exactly one WebLogic server (D is true). A JMS store typically backs one JMS server, not multiple (A is false). JMS queues support multiple producers AND multiple consumers (B is false).

WebLogic Server uses one-way authentication as the default, not two-way. Two-way (mutual) authentication requires explicit SSL configuration where both client and server verify each other's identities. The other statements are true: JAAS is used for authentication, the default realm is File-based (in older versions), and Administration Server configures individual servers or clusters.

JNDI is used by EJB clients to locate resources, including obtaining a reference to the UserTransaction object under the standard path java:comp/UserTransaction in WebLogic.

The standard JSP actions for interacting with JavaBeans are jsp:useBean, jsp:setProperty, and jsp:getProperty. The action jsp:getBean is not defined in the JSP specifications, making it the correct choice for not being a valid JSP action in web applications.

Local rendering portlets display content retrieved from the same WebSphere Portal server instance where Web Content Management (WCM) is installed. This means the rendering happens locally on the same server, avoiding cross-server calls. Option B is incorrect because local rendering specifically refers to same-server content delivery.

The Bridge pattern separates abstraction from implementation, allowing them to vary independently. JMS acts as a bridge between the Order Entry application and various subsystems by providing a messaging layer that decouples the producer from consumers. Observer is about one-to-many dependencies, Mediator centralizes communication, Adapter converts interfaces, and Visitor separates operations from object structure.

The Service Activator pattern enables asynchronous processing by receiving messages from JMS and invoking business services in a separate thread or process. It decouples message reception from business logic processing. DAO handles data access, Domain Store provides transparent persistence, and Business Object represents business entities.

The Session Facade simplifies client access to business tier components by providing a unified interface that aggregates multiple business objects. It eliminates the client's need to interact with multiple fine-grained business components directly. Service Locator finds and creates services, Application Service provides business logic, and Business Delegate reduces tier coupling.

The Domain Store pattern provides transparent persistence for an object model by abstracting the mapping between objects and their persistent storage. It handles the complexity of saving, loading, and managing object state without exposing persistence details to business logic. Web Service Broker exposes business services as web services, DAO provides data access operations, and Service Activator enables async processing.

The Web Service Broker pattern is applicable when you need to bridge the gap between business requirements and existing service capabilities, exposing business logic as web services. It facilitates service integration and reuse. Entity beans are a persistence concern, web container is a deployment environment, and sophisticated business logic describes domain complexity rather than service bridging.

The faces-config.xml file is the standard configuration file in JSF applications where managed beans are registered and configured along with their properties, navigation rules, and other application-wide settings. web.xml is for general web application configuration, not JSF-specific managed bean registration.

WebLogic Server is an application server that runs Java EE applications. While it can serve web content and handle HTTP requests (which might make it seem like a web server), its primary purpose and classification is as an application server that provides enterprise services like transaction management, security, database connectivity, and messaging. A web server (like Apache HTTPD) only serves static content and doesn't provide these enterprise services.

WebLogic Server is a Java EE application server that supports multiple deployment archive formats. WAR (Web Application Archive) files contain web applications, EAR (Enterprise Application Archive) files contain enterprise applications with multiple modules, and SAR files are service archives. Since WebLogic can deploy all these types, 'All of the above' is the correct answer. Each format serves different application packaging needs.

WebLogic Server has three main modes: Development mode (optimized for development with auto-deployment and relaxed security), Staging mode (for testing applications before production), and Production mode (optimized for security and performance with stricter settings). The option 'A & C' is correct because Development and Production are the two primary operational modes that administrators choose between. Staging is more of a deployment phase than a server mode.

Oracle WebLogic Server messages follow a specific format with the BEA- prefix followed by a 6-digit number. The BEA prefix comes from BEA Systems, the original creator of WebLogic before Oracle acquired it. This format is consistent across all WebLogic log messages, errors, and system messages. The other formats (ORACLE-BEA-, MESSAGE-, ERROR-) are not valid WebLogic message number formats.