This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
This resource has all the information you are likely to need. One thing to note, WAS is really complex, if you have not already I would get a copy of a WAS IDE (e.g. Websphere application developer or the like).
Where did you try? There are quite a few examples in there.
Joined: Dec 08, 2009
Just please tell me the steps that are involved........no need of detailed description.
Joined: Mar 22, 2005
That's really not how JavaRanch works. We prefer that people learn something in the process, and are not just handed solutions.
Are you familiar with EJBs in general? It's a standard API, so there shouldn't be anything different on WAS compared to other servers (except the deployment, but that should be covered by the WAS documentation).
deva vv wrote:Just please tell me the steps that are involved........no need of detailed description.
If you are going to use WAS I'm afraid a you'll have to get used to detailed descriptions. WAS is complex; the documentation I pointed you to is vital to avoid many wasted hours trying to work things out on your own.
Joined: Dec 08, 2009
I know how to create EJB's and deploy it in weblogic......here my question is how to deploy it in wesphere....ie. I am asking about the websphere specific deployment descriptor....okay??
As I've been trying to intimate, this is not a quick and simple task on WebSphere. Please take your time to go and read the linked documentation (especially the tutorial on deploying an EJB application). There is no shortcut.
What you would typically do (as the link explains) is create your application, then prepare it for deployment (either using an admin script written in Jython or TCL or in a WebSphere IDE, such as Rational Software Architect). This will do the stuff you cannot do by hand (e.g. create the WAS specific classes and add generated identifiers to your elements in your deployment descriptor). Then, assuming you have set up any container resources your application relies on, you should be able to deploy it.
Note: the web client admin console will do much of this, but in WAS 6.0 is is missing certain important parts that will prevent you from using it exclusively.