Question:- Mention how does a WebSphere or any Application server clustering work?
Answer:- A WebSphere’s web server plugin component routes requests to WebSphere cluster web containers. If there is a communication failure with a particular cluster member, it will mark that member down and start routing all requests to the remaining cluster member till the original is available.
Question:- Mention what type of files are required to deploy an application into Websphere?
Answer:- WAR or EAR files are required to deploy an application into Web-sphere.
Question:- Mention what is asymmetric clustering in Web-sphere?
Answer:- In asymmetric clustering, the partition can be defined dynamically and runs on a single cluster at a time. The task which is particular to an appropriate cluster can be routed to that cluster. Usually, clustering is used by banks.
Question:- Explain what is node, node agent and node groups?
Answer:- • Node: It is a logical grouping of server processes maintained by WebSphere and that share common configuration and operational control • Nodeagent: Each node has a nodeagent that works along with the deployment manager to manage administration processes. It acts as a mediator between the node and deployment manager • Node Group: A node group is a grouping of nodes within a cell that have same capabilities
Question:- Explain what is a cell in WebSphere?
Answer:- A cell is referred as a grouping of nodes into a single administrative domain. A cell can have multiple nodes which are all managed from a single point.
Question:- Mention what are the default ports you use to use WebSphere Application Sphere?
Answer:- The default ports you use are: • Administrative Console Port (WC_ adminhost) : 9060 • Administrative Console Secure Port (WC_ adminhost_ secure): 9443 • HTTP Transport Port (WC_ defaulthost): 9080 • HTTPS Transport Secure Port (WC_ defaulthost_ secure): 9443
Question:- Mention when does WebSphere Application server contact the registry for user information?
Answer:- Web-sphere application server contact the registry for user when users Checks the users password Maps certificate information to a userid Converts userid to registry uniqueid Obtains group information
Question:- Explain what is WebSphere is MQ?
Answer:- WebSphere MQ is an application program that allows you to communicate with each other using messages and queues. This form of communication is referred as commercial messaging. There are two methods for application to communicate, Request/Response and Fire & Forget.
Question:- Explain what is QueueManager in IBM Websphere MQ?
Answer:- QueueManager is the important component of WebSphere MQ. It is accountable for storing and routing messages to other queue manager within MQ, and it also communicate with the outside world.
Question:- Explain what is QueueManager in IBM Websphere MQ?
Answer:- QueueManager is the important component of WebSphere MQ. It is accountable for storing and routing messages to other queue manager within MQ, and it also communicate with the outside world.
Question:- Explain what is SSLPEER in IBM Websphere MQ?
Answer:- SSLPEER is a string usually distinguished name of MQ client, which links to QueueManager securely using QueueManager. This is a mechanism used to identify client.
Question:- Explain what is extended deployment in WebSphere?
Answer:- The extended deployment in WebSphere leverages enhanced qualities of service with features optimizing IT resources. It spans three areas • WebSphere Virtual Enterprise • WebSphere eXtreme Scale • Compute Grid
Question:- Explain what is WebSphere edge server?
Answer:- The WebSphere edge server is used to enhance the performance of web based systems. It can be used as a proxy server. There are basically four components in the web sphere they are caching proxy, content distribution, network dispatcher and application server at the edge.
Question:- Explain how caching proxy of WebSphere on the edge server is done?
Answer:- A caching proxy can be configured in forward direction or as a proxy. When user requests the content, it is cached by the edge before sending or following to the query. Page fragments arising from Servlets or JSP are cached by Edge, and the Caching process becomes Slow. Performance and scalability can be optimized by edge.
