WebSphere Application Server Interview Questions - Part -2.1

6)  How many JVMs will there for each server ?

A) ----> It depends on the enironment. There can be any number no limit.
    ----> Generally in Producation a JVM is put in two servers clustered horizontally to avoid single point of failure (SPOF)

7) what is Embedded HTTP Server ?

A) ----> The embedded HTTP Server receives requests for WebSphere assets from the WebSphere plug-in and passes them to an application server for processing.

   ---->   Any response from the application server is passed back to the WebSphere plug-in for display.

 ----->   The embedded HTTP server supports both HTTP and secure HTTP (HTTPS) protocols for connecting Web servers to application servers.
----> By default, the embedded HTTP server listens for requests on TCP/IP port 9080 but this is configurable.

For example: http://server-name:9080/servlet

You can also use the embedded HTTP server to test your WebSphere applications, but it should never be used as a production Web server.


8)   How to know whether the plug-in ic propagated or not ?

A) Check the plugin-cfg.xml file in webserver


9) what are the different types of log files we have ? what is the use of each log file ?

A)  1)  SystemOut.log :  standard JVM output log
          ---> Indicates if the code running on the Application Server started and stopped successfully. 
          --->Destination and name are configurable. 
         ----> Can be used for user messages. 
2)      SystemErr.log : standard JVM error log 
         ----> Identifies exceptions thrown by the code running on the Application Server. 
         ----> Destination and name are configurable. 
3)     startServer.log and stopServer.log :
         ----> Describes the startup and shutdown of the Application Servers. 
4)  Activity.log: events that show a history of activities 
         ----> Use Log Analyzer to read output from this file. 
          
5)  http_plugin.log : plug-in trace log 
       ----> Errors and data from the Web server plug-in. 
6) trace.log :  output from diagnostic trace. 
       ----> Destination and name are configurable. 
       ----> All WebSphere Application Server log files are under the logs directory. where is the WebSphere Application Server installation directory (for Windows 2000 the default is: C:Program FilesWebSphereAppServer). 

----> SystemOut.log and SystemErr.log are the default names for the JVM logs. They contain server and user program information (sent by: System.out.xxx code in the program). The default location is logs. 

----> startServer.log and stopServer.log can also be found under the logs directory. These files contain information logged by the server as it starts up and shuts down. 

-----> The activity.log file contains information about normal events that are occurring to the system. For example, when a module is first accessed and loaded into the server container, or when a JSP is compiled, or when requests are directed from the HTTP server to the Application Server. Activities such as these are time stamped and recorded in the activity.log file. The activity.log file size can be set. 

-----> The default value is 1024K, or 1 megabyte. The minimum size is 8K and maximum is 1048576K (1 gigabyte). To do this, set the com.ibm.ws.ras.ActivityLogSize value in the logging.properties file in the properties directory.

10)   what are the parameters available in IHS servers response file ?

A) ---->   # In real life, you must concatenate these

   -----> # parameters onto one continuous line. They

----- ># may NOT be split as we do here

-----> -W maintenance.package=

-----> "/fixPaks/7.0.0-WS-IHS-LinuxX32-FP0000011.pak;"

----> -W product.location="/IBM/WebSphere/HTTPServer"

----> -OPT checkFilePermissions="true"

----> -OPT disableNonBlockingPrereqChecking="true"

----> -W update.type="install"