Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

simple question about the WebSphere series tool relationship

 
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am studying the websphere studio application developing(WSAD),and
i see Websphere application server(WAS),both can develope J2EE application
and deploy them.
So I wander what's the difference of the job they can do ,and how i make a choice when i begin to work.
thx
 
Ranch Hand
Posts: 118
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi.
You would use the WSAD to write your J2EE applications.
Then when you're done, you would deploy the application and run it on a "normal" WAS installation. (You cant actully write applications using the WAS, it's only for running them)
WSAD - write applications.
WAS - run applications.
What might confuse you here is that the WSAD is shipped with a couple of "test servers", which is basically a WAS server that runs inside the WSAD (or at least in close proximity to it). These servers are used for testing your applications. But when it comes to setting whole shebang in production, you'd normally want a normal WAS installation without all the WSAD-stuff clinging to it.
hope this helps
/Peter
 
Daniel Washington
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
to Peter:
you are so kind,i understand now,especially"a normal WAS installation without all the WSAD-stuff clinging to it".Bow!!!

Originally posted by Peter Kristensson:
Hi.
You would use the WSAD to write your J2EE applications.
Then when you're done, you would deploy the application and run it on a "normal" WAS installation. (You cant actully write applications using the WAS, it's only for running them)
WSAD - write applications.
WAS - run applications.
What might confuse you here is that the WSAD is shipped with a couple of "test servers", which is basically a WAS server that runs inside the WSAD (or at least in close proximity to it). These servers are used for testing your applications. But when it comes to setting whole shebang in production, you'd normally want a normal WAS installation without all the WSAD-stuff clinging to it.
hope this helps
/Peter

 
Tell me how it all turns out. Here is a tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic