Monday, 13 October 2014

UNABLE TO ACCESS THE WEBSPHERE ADMINISTRATIVE CONSOLE BUT ALL THE DEPLOYED APPLICATIONS ARE RUNNING SUCCESSFULLY



UNABLE TO ACCESS THE WEBSPHERE ADMINISTRATIVE CONSOLE BUT ALL THE DEPLOYED APPLICATIONS ARE RUNNING SUCCESSFULLY

Descripion : Trouble in opening the admin console for the websphere server. The server is up and running though, the application deployed and all. 
Error : Console which gives a 404 error. 
Fix : 
1. Enable the transport chains for the admin_host and use the respective port number (9060 or 9043) in the URL.
2. To enable the transport chains check the server.xml file in the <WAS_HOME>/profiles/default/config/cells/<cellname>/nodes/<nodename>/servers/<servername    > 
(      Eg: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\tamwsNode01Cell\nodes\tamwsNode01\servers\server1) directory and find the entries for the 2 transport chains WCInboundAdmin and WCInboundAdminSecure.

For example:

<chains xmi:id="Chain_1183122130078" name="WCInboundAdminenable="false" transportChannels="TCPInboundChannel_1183122130078 HTTPInboundChannel_1183122130078 WebContainerInboundChannel_1183122130078"/>

<chains xmi:id="Chain_1183122130082" name="WCInboundAdminSecureenable="false" transportChannels="TCPInboundChannel_1183122130080 SSLInboundChannel_1183122130078 HTTPInboundChannel_1183122130080 WebContainerInboundChannel_1183122130080"/>

3.      3. Change the value from enable="false" to enable="true" for both of them.

<chains xmi:id="Chain_1183122130078" name="WCInboundAdminenable="true" transportChannels="TCPInboundChannel_1183122130078 HTTPInboundChannel_1183122130078 WebContainerInboundChannel_1183122130078"/>

<chains xmi:id="Chain_1183122130082" name="WCInboundAdminSecureenable="true" transportChannels="TCPInboundChannel_1183122130080 SSLInboundChannel_1183122130078 HTTPInboundChannel_1183122130080 WebContainerInboundChannel_1183122130080"/>

 4. Save the file and restart the server.

By Nandavaram Pavan Kumar

No comments:

Post a Comment