Problem In Opening WAS Admin Console After Starting The Server

2. Problem In Opening WAS Admin Console After Starting The Server

Like

Like

Gabriel Aberasturi

Posted 11/16/12 05:35 AM

Saleem,

ApplicationMg A WSVR0204I: Application: Saleemapp Application build level: Unknown
webapp I com.ibm.ws.webcontainer.webapp.WebGroupImpl WebGroup SRVE0169I: Loading Web Module: Saleemapp.war.
WASSessionCor I SessionContextRegistry getSessionContext SESN0176I: Will create a new session context for application key default_host/althaf
webcontainer I com.ibm.ws.webcontainer.VirtualHostImpl addWebApplication SRVE0250I: Web Module null has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443].
ApplicationMg A WSVR0221I: Application started: Saleemapp
CompositionUn A WSVR0191I: Composition unit WebSphere:cuname=Saleemapp in BLA WebSphere:blaname=Saleemapp started.

You are binding application with default_host virtualhost. This default host attends the ports 9080, 80, 9443, 5060, 5061 and 443.

So to access in secure (i think that you are trying in secure) to your application:

"https://localhost:9443/YourApplication"

if not secure:

"http://localhost:9080/YourApplication"

try and tell.

13. Problem In Opening WAS Admin Console After Starting The Server

Like

saleem sheik

Posted 11/16/12 06:12 AM

Gabriel,

i tried accessing the application with https://localhost:9443/saleemapp/althaf url but i am getting following error

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

please take a look in this issue...........

14. Problem In Opening WAS Admin Console After Starting The Server

Like

Gabriel Aberasturi

Posted 11/16/12 07:12 AM

Saleem,

I think that you you are putting wrong URL/URI to access your application.

What is the context root of your application?

Adminconsole->Application types->WebSphere enterprise applications->APPLICATION->View Deployment Descriptor

Find your web module your context-root and then:

    https://localhost:9443/Application_ContextRoot

I suggest to review the next links

   IBM® WebSphere® Application Server: V6.0, V6.0.1 System management-> Application management section

publib.boulder.ibm.com/infocenter/ieduas...

WebSphere Application Server V8.5 Administration and Configuration Guide
www.redbooks.ibm.com/redpieces/abstracts...

try and tell

15. Problem In Opening WAS Admin Console After Starting The Server

Like

saleem sheik

Posted 11/16/12 07:47 AM

Gabriel,

Finally i got welcome page of webapplication which is deployed in Websphere,the mistake that have done here is "i should not mention webapplication name in URI".so the uri should be https://localhost:9443/althaf it should no be https://localhost:9443/Saleemapp/althaf....thanks for your help.......really i am very thankfull to u for helping me.........

16. Problem In Opening WAS Admin Console After Starting The Server

Like

Gabriel Aberasturi

Posted 11/16/12 08:08 AM

Great Saleem!!!!

Glad to help.

Regards

17. Problem In Opening WAS Admin Console After Starting The Server

Like

Erik Solinger

Posted 11/16/12 08:36 AM

Based on the SystemOut.log from earlier in the thread, it appears that you're running WebSphere BASE 8.5.0.1... No worries there!

Later in the thread, the error you're seeing is SRVE0255E: A WebGroup/Virtual Host to handle localhost:9043 has not been defined when trying to access your deployed application.

For the moment, I'm going to make the assumption that the app deployed correctly to the JVM. If it didn't, then the below may not be applicable.

If the code got deployed, then I think it's the port that's the problem.

Try this to confirm the port:
1. Navigate on the left side of the admin console to "Servers->Server Types-> WebSphere application servers" and click on the name of the JVM.
2. In the content screen (on the right) find the section called "Communications" and there will be a link called "Ports".
3. Expand "Ports" and look for the "WC_defaulthost" named port. I'm guessing that it has a value of "9060"
4. Also note the value of the port named "WC_defaulthost_secure" (we may or may not need it)

Next, we confirm the virtual host of the JVM...
1. While on the JVM details page where you found "Communications" and the "Ports", look in the top right for "Container Settings"
2. Below "Container Settings" is "Web Container Settings". Expand it.
3. Click on "Web Container"
4. This should take you to the details of the Web Container where you should see under "General Properties" a drop-down box with a value. That's the virtual host definition that the JVM is associated with. I am going to assume that it reads "default_host"

Confirming the virtual host setup:
1. on the left,navigate to "Environment->Virtual hosts"
2. Click the "default_host" link (unless the name of the virtual host was different in the above section)
3. Next, click the "Host Aliases" link under "Additional Properties" on this screen.
4. Confirm that you see an entry on the screen for the "Port" for the values you found in the first set of steps above. They are likely there and the host name will be "*" which is fine for now.
5. If the value isn't there, you'll need to add it.

Confirm your application is started (it doesn't sound like I need to provide steps for this as you indicated earlier it was okay...)

All of the above was geared at identify the values and confirming the setup is correct, and i'm speculating it's all fine.

Try to access your application, open a web browser and enter http://:9060//

The "9060" should be the value "WC_defaulthost" port that we identified above. If it was different, you'll need to change it to match.

If your app requires a secure connection, that where you use https and the "WC_defaulthost_secure" value we found earlier.

In the off chance you don't know what your < context root > value is:
1. Navigate to "Applications-> Application Types->WebSphere enterprise applications" and click on the name of your app
2. Under the "Detail Properties" section, click the "View Deployment Descriptor" link
3. XML should be displayed on the screen and you're looking for the context-root value

Good Luck and hopefully this addresses the issue.

Erik

18. Problem In Opening WAS Admin Console After Starting The Server

Like

Gabriel Aberasturi

Posted 11/16/12 09:04 AM

wow Erik!!!!!!

I have needed ten post to explain the same.

The first problem has been the port used to login is trying to access to secure port (9043) but without https.

The second problem has been the port used again (is using the secure admin virtualhost 9043) to access application deployed in default virutalhost (9443)

And the last problem is the URI to access application.

I think that the problem is solved.

Saleem, Erik's has explained perfectly resolution methodology

19. Problem In Opening WAS Admin Console After Starting The Server

Like

saleem sheik

Posted 11/19/12 02:09 AM

Thanks Erik...From Your Explanation I got clear picture on why the problem's ocured in accessing the application which i deployed in the server.....

@Gabriel : Thank You Very Much

20. Problem In Opening WAS Admin Console After Starting The Server

Like

saleem sheik

Posted 11/19/12 04:39 AM

Hi Gabriel,

currently i am using base trial version of websphere.Could you please tell me abt network deployement websphere server? and also tell me do i need to install it seperately...

21. Problem In Opening WAS Admin Console After Starting The Server

Like

Gabriel Aberasturi

Posted 11/19/12 04:57 AM

Hi Saleem,

To get full Network Deployment, you need to be IBM Business Partner or buy it.

You can get a full WAS BASE for developement purpose at:

www.ibm.com/developerworks/downloads/ws/...

You need to install separately but you can install in the same machine (diferent directory and diferent ports).

Hope this helps.

Kind regards,

22. Problem In Opening WAS Admin Console After Starting The Server

Like

Joseph Amrith Raj Paturi

Posted 11/19/12 06:12 AM

If you are just looking for Network deployment to learn ..

you can download a 60day full featured trail download @ www14.software.ibm.com/webapp/download/s...

This is version 8.5 which is very close to v8 and can be used to educate yourself on v7 as well.

23. Problem In Opening WAS Admin Console After Starting The Server

Like

Erik Solinger

Posted 11/21/12 08:20 AM

Saleem -

While you can install different versions of WebSphere on the same server (in different directories as Gabriel called out) there's one critical thing to keep in mind... the ports!

The WebSphere installer, from my expereince, may use the default port settings for all services during the intial installation of the product. It doesn't matter that you have another version of WAS installed, or even running. The WAS isntaller blindly installs on the default ports (unless you specify a "ports" file for use during installation.)

Assuming you have one version of WAS already running, when you try to start the newly installed version of WAS, you'll likely get errors and it just won't start. The root cause - port conflicts!

There's ways to change the values, if you want multple WAS versions running concurrently. If you don't care about the running multiple instances at once, just shut down the others and run the version you desire - thus avoiding the port conflict issues all together.

Good luck and welcome to WAS!

WebSphere Application Server & Liberty

WebSphere Application Server & Liberty