Dear Readers, Welcome to IBM Websphere Interview Questions and Answers have been designed specially to get you acquainted with the nature of questions you may encounter during your Job interview for the subject of IBM Websphere. These IBM Websphere Questions are very important for campus placement test and job interviews. As per my experience good interviewers hardly plan to ask any particular questions during your Job interview and these model questions are asked in the online technical test and interview of many IT companies.
The word web sphere popularly refers to IBM middleware technology products. Web sphere is known for its turn key operation in e business applications. It has run time components and tools which can help in creating applications which run on WAS. WAS refers to web sphere application server.
IBM web sphere commerce has a single platform which offers complete ecommerce solutions to developers. It can be very productive if you are planning to do business with consumers, business and indirectly through channel partners. This can be used to perform business with consumers, business and channel partners altogether.
Web Sphere is built on three main components they are
• Database
• J2EE application server
• A web server
The databases which it supports are
• DB2
• Oracle
• Cloudscape
Application server is IBMWAS and the supported web servers are
• IBM server
• Microsoft IIS
• Sun web server
Some of the features which are present in web sphere are: -
• Order management
• Web sphere commerce accelerator
• Analytical and business intelligence
• Open standards such as Java, EJB, etc
• Web sphere commerce payments and customer care, etc
Web sphere edge server is used to improve the performance of web based systems. It can be used as forward or proxy server. Basically four components are present in the web sphere they are Network dispatcher, Caching proxy, Content distribution and application service at the edge.
Web sphere application server extended deployment increases the functionality of the server in two main areas they are manageability and performance. Dynamic virtualization between servers is possible with the help of XD. A stand alone distributed cache was added to it under the performance header, it is known as Object Grid.
Security model for web sphere is primarily based on JAVA EE security model. It also depends upon the operating system. User authentication and authorization mechanisms are also provided in WAS. Light weight third party authentication mechanism is the main security feature present in WAS.
Asymmetric clustering applications are primarily used in electronic trading systems employed in banks. Some of the features are, partitions can be declared during run time and are usually run on a single cluster at a time. Work specific to a particular can be routed to that cluster.
Web sphere almost reduces the work of server administrator as he can manage load on servers efficiently without any hassles. It also gives him flexibility to divide the load and applications among different server farms. He can also predict about the incoming load on servers. Email alerts, restart options, memory leak detection, etc.
A caching proxy can be configured in forward direction or as a proxy. Content requested by the user is cached by edge before sending or adhering to the query. Page fragments arising from JSP or servlets are cached by Edge and the caching process is slow. Performance and scalability of J2EE applications can be increased by edge.
Managing singletons will be a thing of the past and it also provides hot recovery of singletons which makes you forget about your GC collected singletons. Transaction logs can stored on a shared file system. For clustering run time operations deployment manager`s role was eliminated. J2EE failover support and cell configuration support is also present.
Web sphere integration developer provides an IDE to build applications based on service oriented architecture. Web sphere process server and web sphere ESB were built with WID. WID was built with RAD Eclipse based technology.
Compute grid is also known as Web sphere batch. Web sphere extended deployment offers a Java batch processing system called as Compute Grid. This forms an additional feature to Web sphere network environment. Various features are provided which help a developer to create, manage and execute batch jobs. Job scheduler, xJCL, batch container and batch programming controller.
This feature is very useful in instant messaging across different clients through intranet and internet. This supports high volume and high performance across different clients. It uses the concept of light weight transport which is again based on IP rather than the queue process.
Web sphere MQ and Web Sphere Business integration manager Broker are very useful in providing Java messaging services to wide range of clients (publisher –subscribe, point to point). Java classes are chiefly responsible for translating the API calls to API`s defined by web sphere. It is very useful to have knowledge of Web sphere MQ for proper configuration.
CHANNEL specifies the name of the server connection channel. Generally this is Web Sphere MQ network abstraction. The default standard used by CHANNEL is SVRCONN which is the server connection channel. This server is generally used to communicate to the queue manager by the client.
Yes, the naming of connection factory is independent of the name specified by JMS client. This is made possible by WAS (Web sphere application server) with its resource references. It isolates the application from object names. This feature is important because it gives us the flexibility to change the administered object without changing the JMS client code.
classloader
Node with NodeAgent
Remote webserver access through local (dmgr/cell)
deployment manager contains the MASTER configuration and application files. All updates to the configuration files should go through the deployment manager.
Apache, ApacheMonitor, htpasswd, htdigest, htdbm, ldapstash, httpd.exe
identify the web server (port, virtual hosts) to configure the web server definition
select web server machine (remote)
system out, system err, trace, native out , native err, activity.
express, base, network deployment
profiles are a set of files that represent a websphere application server configuration.
A trace is an informational record that is intended for service engineers or developers to use. As such, a trace record might be considerably more complex, verbose and detailed than a message entry.
Objects storage space for objects references created at run time in a jvm is heap memory.
To incrise heap memory size
IHS (IBM HTTP Server) is one of the web servers. It serves the static content only and it takes up only http requests.
plug-in is one of the modules it is interface between application server and web server, the plug-in process receives the request from the client first. If the request is for dynamic content, the plug-in diverts the request to the websphere application server. If the request is for static content, the plug-in forwards it to the Http server.
it provides the authentication and authorization for websphere application server domain (administration client or console).
open console and then select security option in the right side menu, and then select localOs registry in the user registry, then enter the username, passwords. And again select global security then ltpa option then provide the password, then save the configuration. And restart the deployment server and then relogin the console.
ssl is a protocol for providing encrypted data communications between two processes.
monitoring and tuning–>PMI–>select any process (server1, nodeagent, dmgr) and then enable PMI–>then apply and then save. Select performance viewer–>current activity and then select enabled process and click the start monitoring button after that process select.
ps –ef| grep java
logical group of servers.
startserver.sh server1
Custom Profile
addnode.sh 8879
The application server provides a runtime environment in which to deploy, manage, and run j2ee applications.
A node corresponds to a physical computer system with a distinct IP host address.The node name is usually the same as the host name for the computer.
A node corresponds to a physical computer system with a distinct IP host address. The node name is usually the same as the host name for the computer.
1.deployment manager profiles 2.application server profiles 3.custom profile
dmgr app custom
1.its used for administration 1.admin console is there 1.plain node purpose of remaining profiles 2.initially one app server there 2.empty node 2.it supports the distributed 3.work independently environment. 4. Put applications 3.it is not included app server 4.admin console is there 5.work independently 6.do not put applications
Web Sphere Studio 3.5, comes up with Visual Age for Java. WSAD 5.0 supports J2EE 1.3 java specifications. RAD 6.0 supports J2EE 1.4 and integrated with Eclipse 3.0, UML Visual Editor, Tomcat Jakarta, Ant scripting, EJB universal test client and SOA tools.
Application Server: takes care of Security, Transaction, Multithreading, Resource pooling, load balancing, clustering, performance, highly availability, scalability, etc. Exposes business logic to client applications through various protocols, possibly including HTTP. Supports deployment of .war and .ear files Application server = web server + EJB container.
Both BEA Weblogic and IBM’s WebSphere provide J2EE based application servers which are competitors. WebSphere leverages more on connectivity issues with MQ and legacy systems with strong dominance in J2EE.
http.log, plugin.log
jdbc is a low level pure java api used to execute sql statements.
A data source is associated with a jdbc provider that supplies the specific jdbc driver implementation class
type4 type2
1. It is pure java oriented 1.it is not a pure java oriented driver 2.require client side software 2.no need any client software
systemout, systemerr
server side machine
possible
we can register resources in the application server’s java naming and directory interface (jndi) namespace. Client applications can then obtain the references to these resource objects in their programs.
client applications use the bootstrap port to access websphere’s built-in object request broker (orb) to use enterprise java beans in applications installed on the application server. The java naming and directory interface service provider url used by the client application needs to reference the bootstrap port to obtain an initial context for looking up ejb’s it wants to use. (For communicate two servers)
admin server, web container, ejb container,j2c service, naming server, messaging engine, security server.
startserver.sh server1
express, base, network deployment
The web container provides a runtime environment for servlets, jsp’s, javabeans, and static content.
du -sk (kb) du -sm (mb)
through admin console.
possible
environments–>websphere variables
see jvm & application are up, check plugin-cfg.xml file for the root context used by the web application if it does not exist generate plugin and restart web server.
plugin.log
9060, ssl 9043
2809
webcontainer port on application server
console,,,JMX
Admin console…..jython (jacl) scripts
Node uses this port to talk to DMGR
DMGR uses this port to talk to node
There is an algorithm that websphere uses to find the timestamp of .jsp and .class files. It checks that timestamp of .class file is always later than its corresponding .jsp file.
classloader
Node with NodeAgent
Remote webserver access through local (dmgr/cell)