- This topic has 5 replies, 2 voices, and was last updated 19 years, 11 months ago by gzhuye.
-
AuthorPosts
-
gzhuyeMemberI have been using JBoss and MyEclipse, now change Jboss to WebSphere. After application is deployed into WebSphere using MyEclipse, I don’t know how to access it.
Using MyEclipse to deploy myApp.war to C:\IBM\WebSphere\AppServer\installedApps\nodename\myApp.war, how can I access it? Neither http://hostname:9080/myApp/index.jsp or http://hostname:9080/nodename/myApp/index.jsp or more does work.
Refere to WebSphere doc, some sample app can be accessed like:
http://<WAS_hostname>:9080/WSsamples, it does work. however, whatever I do, I cann’t find a directory or a file including “WSsamples” under C:\IBM\WebSphere\AppServer.I installed both IBM HTTP Server1.3.28 and Websphere application server5.1, does it need any confiuration with them to work together or default to work? I have no clue.
Could you give me a big help: what is the deployment mechanism with websphere? where can I get some reference to this issue?
gzhuyeMemberAppreciate any of your response. Thanks a lot!
Riyad KallaMemberAdditionally, I believe in Webspehere and a few other app servers there isn’t a concept of ‘autodeploy’ like in Tomcat, so you need to open up the Webspehere console and deploy the app so it runs, then you can connect to it. PLease check the WS docs, I am not versed with it.
gzhuyeMemberThank you very much, Riyad.
That means that I can use MyEclipse to deploy the application, instead, I must use Webspehere console to deploy the app, does it? a little disappointment with MyEclipse and WebSphere combination!possible for any improvement in future?
Thanks!
Riyad KallaMembera little disappointment with MyEclipse and WebSphere combination!
Don’t loose all hope yet, here is how it works:
1) MyEclipse ‘deploys’ the application to your WS apps directory (*Use a packaged deployment)
2) WS has no knowledge of this app, so you need to open up the WS admin console and ‘deploy’ it so WS loads the app
3) Now that the app is loaded in WS, you can go back to ME and erase the deployment and create a new one
4) This time us an exploded deployment, that way when you deploy from now on from MyEclipse, it will *overlay* the already deployed app running under WS and the changed files will be reloaded.The only difference between Tomcat, Resin and others that support autodeploy, is that step 2 & 3 are not necessary, for app servers that require deployment by way of their admin consoles, you need to do a little bit more leg work, but once you have the exploded deployment setup to overlay the existing deployment, you can work like that for as long as you need to until you decide to remove the deployment using the admin conosole.
gzhuyeMemberThank you very much!
-
AuthorPosts