Java Enterprise and Web Technologies

The Application Object Manager (AOM) is the server component that provides the runtime environment for Siebel applications. It handles user sessions, executes business logic, manages data access through business components, and coordinates all application server operations. The other options serve different purposes - file management, data synchronization, and web page generation.

When a Siebel URL is requested, the Web Server (with the Siebel Web Server Extension) recognizes the URL and forwards it to the Siebel Web Engine (SWE) on the application server. The SWE then compiles the templates and data into HTML to send back to the user.

Applets are compiled into platform-independent Java bytecode. They can run on any client machine because the user's web browser contains or integrates with a JVM plug-in that executes this bytecode locally.

Servlets are Java programs that run on a web server or application server, dynamically generating web content in response to client requests. They extend the server's capabilities by enabling dynamic, interactive web applications that go beyond static HTML pages.

The application object holds data that is shared by all users across the entire application scope. Session objects hold data per user session, request objects hold data for a single HTTP request, and page objects are scoped to individual page instances.

WSDL (Web Service Description Language) is the standard XML-based interface definition language for web services. It describes the service's location, available operations, and message formats. SOAP is a protocol for message exchange, not an interface description language.

UDDI (Universal Description, Discovery, and Integration) is the XML-based registry standard for publishing and discovering web services. It acts like a phone directory for services. SOAP is for messaging, WSDL describes interfaces, CORBA is a different technology.

In Java web applications, the deployment descriptor file used to define servlet mappings is standardly named web.xml, which resides in the WEB-INF directory. A file named servlet.xml is not standardly used for this purpose, making the statement false.

When forwarding requests between servlets in different web applications, the session and servlet context are not shared. HttpServletRequest attributes are preserved during forward operations and are accessible only to the target servlet, making them the ideal mechanism for data sharing in this scenario. HttpSession and ServletContext are shared within the same web application, not across applications.

A session represents the duration of a user's interaction with an application, typically spanning from login to logout. During this period, the server maintains user-specific state and data. While sessions are often implemented using cookies or server-side variables, the fundamental concept is the time duration itself, not the implementation mechanism. Sessions are generally persistent across multiple requests within the same login period.

The Runtime Audit Browser is specifically designed to view deployment and execution audit information in OWB. Deployment Manager handles deployment operations, Metadata Reporting Browser generates reports, and Runtime Repository stores the data - but the Runtime Audit Browser is the interface for viewing audit trails.

Struts is designed to be thread-safe by creating a new (or reusing a pooled) lightweight Action instance for each request. Each Action invocation operates on its own ActionForm instance with no shared state between requests, making thread safety the default when developers follow best practices.

These are indeed the core classes in Struts 1.x: ActionServlet (front controller), Action (request handler), ActionForward (navigation), ActionMapping (configuration mapping), ActionErrors/ActionMessages (error messaging), RequestProcessor (processing pipeline), and ActionForm (data transfer). The list is comprehensive and correct.

J2EE design patterns include Front Controller, View Helper, Dispatcher View, Composite View, Service to Worker, and Synchronizer Token. Option C lists all these patterns comprehensively. Option A is incomplete (missing Service to Worker), and Option D is too limited.

Object interfaces provide external applications with specific APIs to interact with Siebel, but they do not directly provide database access or support all mentioned technologies (CORBA, COM, Java beans). External applications use Siebel's proprietary interfaces (COM Data Control, Java Data Bean, Web Services) rather than generic CORBA or direct database connections.