Quantcast
Channel: The Middleware Shop
Viewing all articles
Browse latest Browse all 156

Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /ibm/console

$
0
0

You have tried to connect to the Administrative Console for a new WebSphere Application Server profile. You get the following error

Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /ibm/console

The most common reason, is that the console will want to redirect to the secure HTTP/s port and that port is not open on the firewall for example

Let’s say you have the following portsFile :

appserver_ports.props

and you have created a WAS  profile using the following command:

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -profileName DV_AppServer01Prof -profilePath /opt/IBM/WebSphere/AppServer/profiles/DV_AppServer01Prof -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -cellName DV_AppServer01 -hostName localhostcell01 -nodeName DV_AppServer01 -portsFile /var/apps/scripts/was8manage/appserver_ports.props -isDefault

We need to look at the portsFile

#This file is hand crafted, though numbers are in sequence, it was not generated using -startPort
#This example is for a standalone application server
WC_defaulthost=10020
WC_adminhost=10021
WC_defaulthost_secure=10022
WC_adminhost_secure=10023
BOOTSTRAP_ADDRESS=10024
SOAP_CONNECTOR_ADDRESS=10025
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=10026
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=10026
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=10027
ORB_LISTENER_ADDRESS=10028
DCS_UNICAST_ADDRESS=10029
SIB_ENDPOINT_ADDRESS=10030
SIB_ENDPOINT_SECURE_ADDRESS=10031
SIB_MQ_ENDPOINT_ADDRESS=10032
SIB_MQ_ENDPOINT_SECURE_ADDRESS=10033
SIP_DEFAULTHOST=10034
SIP_DEFAULTHOST_SECURE=10035

We can see that the WC_adminhost_secure port is 10023, you were most likely connecting to the web container’s default port of 10020 to get this specific error. But you may have also not have secured the console, and so HTTP will be the required protocol, not HTTP/s so in this case the URL required  may have been http://192.168.0.80:10021/ibm/console/ required not the secure port http://192.168.0.80:10023/ibm/console/

When a console is secured i.e Global Security is turned on then the HTTP will direct to HTTP/s. But if Global security is off, then only the HTTP port will be available for example 10021 in my example which = WC_adminhost., which was the case because Global Security was disabled for this profile.


Viewing all articles
Browse latest Browse all 156

Latest Images

Trending Articles



Latest Images