WebSphere Application Server Interview Questions - Part -3

1)  What is the default admin console port number in websphere?

A)  WebSphere Application Server default ports

 •Web container port (HTTP_TRANSPORT) - 9080
•Web container secure port (HTTPS_TRANSPORT) -  9443
•Administrative console port (HTTP_TRANSPORT_ADMIN) -  9090
•Adminstrative console secure port (HTTPS_TRANSPORT_ADMIN) -  9043
•Name service or RMI connector port (BOOTSTRAP_ADDRESS) -  2809
•Simple Object Access Protocol (SOAP) port (SOAP_CONNECTOR_ADDRESS) -  8880
•Data replication service client port (DRS_CLIENT_ADDRESS) -  7873
•Java Message Service (JMS) queued port (JMSSERVER_QUEUED_ADDRESS) -  5558
•JMS security port (JMSSERVER_SECURITY_PORT) -  5557
•JMS direct port (JMSSERVER_DIRECT_ADDRESS) -  5559
•Secure Association Services (SAS) SSL server authentication port (SAS_SSL_SERVERAUTH_LISTENER_ADDRESS) -  9501
•Common Secure Interoperability Version 2 (CSIV2) server transport port (CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS) -  9503
•CSIV2 client transport port (CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS) -  9502

    WebSphere Deployment deployment manager default ports

 •Administrative console port (HTTP_TRANSPORT_ADMIN) - 9090
•Adminstrative console secure port (HTTPS_TRANSPORT_ADMIN) - 9043
•Name service or RMI connector port (BOOTSTRAP_ADDRESS) - 9809
•Simple Object Access Protocol (SOAP) port (SOAP_CONNECTOR_ADDRESS) - 8879
•Data replication service client port (DRS_CLIENT_ADDRESS) - 7989
•Cell discover port (CELL_DISCOVERY_ADDRESS) - 7277
•Secure Association Services (SAS) SSL server authentication port (SAS_SSL_SERVERAUTH_LISTENER_ADDRESS) - 9401
•Common Secure Interoperability Version 2 (CSIV2) transport port (CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS) - 9402
•CSIV2 transport port (CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS) - 9403•Object Request Broker (ORB) listener port (ORB_LISTENER_ADDRESS) - 9100

  WebSphere Application Server node agent default ports

•Name service or RMI connector port (BOOTSTRAP_ADDRESS) - 2809
•Simple Object Access Protocol (SOAP) port (SOAP_CONNECTOR_ADDRESS) - 8878
•Data replication service client port (DRS_CLIENT_ADDRESS) - 7888
•Secure Association Services (SAS) SSL server authentication port (SAS_SSL_SERVERAUTH_LISTENER_ADDRESS) - 9901
•Common Secure Interoperability Version 2 (CSIV2) transport port (CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS) - 9101
•CSIV2 transport port (CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS) - 9201
•Object Request Broker (ORB) listener port (ORB_LISTENER_ADDRESS) - 9900
•Node discovery port (NODE_DISCOVERY_ADDRESS) - 7272
•Node multicast discovery port (NODE_MULTICAST_DISCOVERY_ADDRESS) - 5000

WebSphere Application Server JMS server default ports

•Java Message Service (JMS) queued port (JMSSERVER_QUEUED_ADDRESS) - 5558
•JMS security port (JMSSERVER_SECURITY_PORT) - 5557
•JMS direct port (JMSSERVER_DIRECT_ADDRESS) - 5559
•Simple Object Access Protocol (SOAP) port (SOAP_CONNECTOR_ADDRESS) - 8876


2)  Is it possible to a server to listen to multiple port numbers in WebSphere? Explain

A) ---->  yes.. There is a possibility to listen the multiple port numbers in Websphere.This is possible when we deployed the two applications on the single server.

---->  We must add the ports of that particular servers in virtual host.

---->  Environments---> virtual hosts---> default_host---->host aliases---> new --->add that ports in the virtual host.




3) What are the responsibilities of Web container, EJB container and JNDI?

A) ---->  The webserver plug-in examines the url, verifies the list of host name aliases from which it will accept traffic based on the virtual host information, and chooses aserver to handle the request.

  WEB CONTAINER :

----->  A stream is created. A stream is a connection to the web container.The web container receives the request and based on the url, dispatches it to the proper servlet.

----> If the servlet class is not loaded, dynamic class loader loads the servlet. 

JNDI : (JAVA NAMING AND DIRECTORY INTERFACE) 

----> JNDI is used to look up of either databases or ejb connection by the servlet. JNDI directs the servlet depending on the servlet request.

----> To the corresponding database and gets a connection from its connection pool in the case of servlet wants the datasource

----> To the corresponding EJB container, which then instantiates the EJB when EJB is requested.

----> IF ejb container have to execute some sql operation , it has to go to the jndi to lookup the datasource.

----> The sql statement is executed and the retrieved data is sent back to the EJB or to the servlet.

----> Data beans are created and handed off to jsps in the case of EJBs

-----> The jsp generates the html, i e sent back to through the plug-in to the webserver

-----> The webserver sends the output page to the requested browser



4)  What happens to applications if node agent is not running?

A) ----> When DMGR goes Down then there is no impact to the end-users. If NA is goes Down then there is no problem in Distributed Environment/Clustered the servers will server the application when we maintaining fail over mechanism. (NA is nothing but communication between Dmgr and federated nodes). 

-----> Before starting the app server the applications NA must be up and running then only it serves the applications which are running on that app server.
----> If the application is deployed on multiple servers, the remaining  servers will serve the application request.



5) In WebSphere 6.0 and 6.1, If you got a problem before creating a log's directory, at that time where will you the check status of installation?

A) ----> After installing the websphere product. you can see the status of the installation either it is success or failure. 

----> you can see this status in WAS product home--->logs------> install------> see the log.txt

----> If your installation is not success. i e your product is not created... u can see the status of the installation in windows user account waslogs. you can see the status there