Java Enterprise and Web Technologies

The getServletConfig() method returns the ServletConfig object passed to the servlet's init() method. This allows access to initialization parameters and servlet context throughout the servlet's lifecycle.

HTML and JavaScript are client-side technologies that run in the browser. JSP and Servlets are server-side Java technologies that execute on the web server to generate dynamic content.

JSP stands for Java Server Pages. It is a server-side technology that allows developers to embed Java code in HTML pages to create dynamic web content.

JSP is primarily used for creating the view/presentation layer (GUI) in web applications. It generates HTML that is sent to the browser. Controllers are better implemented as Servlets, and business logic should be in separate Java classes.

Modern servlet containers automatically map JSP files - you don't need to configure them in web.xml. The container compiles JSPs into servlets on first access. web.xml configuration is only needed for Servlets and custom URL mappings.

JSP requires a servlet container or engine with JSP support to run. Apache Tomcat and Bea WebLogic are application servers/servlet containers. JSP Engine is the generic component that processes JSP. Servlets are Java classes that run inside containers, not platforms themselves.

IBM WebSphere is a full-featured Java EE application server that supports Servlets, JSP, and EJBs. It includes enterprise features like pooled database access for major databases (DB2, Oracle) and is a comprehensive platform for enterprise Java applications.

The scriptlet element syntax in JSP is <% code %>. Scriptlets allow embedding Java code directly into JSP pages. The code inside runs during the request processing phase and can generate dynamic content.

JSP has four standard scopes: page (default), request, session, and application. Response is not a scope - it's an object for sending data back to the client. Scopes determine the lifespan and visibility of data.

In JSP, there are three standard JavaBean actions: useBean (to instantiate or locate a bean), setProperty (to set bean property values), and getProperty (to retrieve bean property values). Option D 'All' correctly identifies that useBean, setProperty, and getProperty are all JavaBean actions.

Both syntax examples (1 and 2) are valid. In option 1, setProperty is nested inside the useBean body. In option 2, setProperty appears after the useBean tag closes. Both approaches work correctly - the nested approach is more compact while the separate approach is more flexible. Therefore option C 'both' is correct.

The jsp:getProperty action requires exactly two attributes: 'name' (the bean identifier matching the useBean id) and 'property' (the specific property name to retrieve). Option D correctly identifies these two required attributes. Options A, B, and C list incorrect attribute combinations.

To distribute formatted reports through a web browser in TM1, the report must be saved to an application folder. This makes it accessible through the TM1 Web interface. Reporting folders, data directory, and TM1 Server locations are not correct for web distribution.

In EJB (Enterprise JavaBeans), ejbLoad() is a callback method specific to Entity beans that is invoked by the container to synchronize the bean's state with the underlying database. This method is called when the container needs to refresh the entity bean's state from persistent storage.