aspose file tools*
The moose likes Websphere and the fly likes Regarding deployment on Websphere App server Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Regarding deployment on Websphere App server" Watch "Regarding deployment on Websphere App server" New topic
Author

Regarding deployment on Websphere App server

Jack Daniel
Ranch Hand

Joined: Jun 15, 2002
Posts: 163
Hi Everybody,

Well, till now I was developing J2ee Web applications using websphere studio and VAJ, with WAS 3.5.3 as
the production server;

Recently we upgraded to WAS-Express 5.1 on iSeries and WDSC on workStations, and I have migrated the previously
developed applications to Websphere development Studio Client 5.1 (WDSC) and I have also finished testing the
applications on WDSC,and they were running perfectly alright.

Now I wanted to deploy the applications on the production server on iSeries; Since this is the "first"time, I wanted to
clarify my doubts.

It is here I come across problems and several doubts, it would be great if anybody can help me on this.


(1) Firstly which is a better way of deploying the EAR file onto the server

using HTTP server administration console - http://serverName:2001
ORusing Websphere administrative Console - http://serverName ort/admin
where port is the port defined in the virtual host: admin_host

If I manage applications using Websphere administrative Console, I do not see those changes when I log in to
HTTP server administration console, I do not know why??


Anyway, it was really great and simple to deploy and test on WDSC, but i'm getting confused with deployment
onto the production server.

(2) Where exactly do I have to deploy the EAR file??
is it at /QIBM/UserData/WebASE/ASE5/serverInstanceName/installedApps/NodeName/ ?? or it does not matter where..??



(3) and talking about classpath, this is something that confuses me;
Previously with WAS 3.5.3, when deploying with WAS admin console, there was something like classpath for every
web application that you deploy, but here with WAS-Express 5.1, I do not see anything like classpath when
I look at the application using websphere admin console,

So the way to go is, to include all the jar files in the Libraries folder(in WDSC), in the created WAR file?? but when I
create the EAR file, I do not come across any JAR files, in the created WAR file which is included in the EAR file.

Do I have to put all the jar files in WEB-INF/lib directory?? if that is the case, they are not present as jar
files but as compiled class files, is this the way to go??


Even in WDSC, I have web application classpath in Environment Tab of the configured Server like WTE.


Can you tell me how I can find out the classpath for "adminconsole" Enterprise application, which is required
for running websphere admin console?? and which is running now.

The other option would be to put all the required JAR files on the iSeries sever and reference them in the
Shared Libraries (in Environment), is this the way?? I guess so..

(4) where do I find the application server classpath?? forget about web application classpath, so that I can put
something like jt400.jar in application server classpath, instead of web application classpath so that all applications
can access it;

Somebody, please help me on the deployment of my first application onto the WAS-Express 5.1.
I really appreciate your help in this matter.

In summary,

Is it something like application server classpath = Shared Libraries (in Environment)
web application classpath = jar files in WEB-INF/lib folder

Thanks
Scott Duncan
Ranch Hand

Joined: Nov 01, 2002
Posts: 363
Man that is quite a list. Your answers of course are all in the infocenter docs. But since I have been through the pain of migration several times, I will do my best.

1.) Use the WebSphere admin console. Forget about the HTTP Server console. In fact, I would recommend using the scripting tool instead of anything else (wsadmin) but you should take baby steps.

Do not use the admin host, use the default virtual host (9080).

2.) It deploys here by default. You can select an alternate location.

3.) There is no web application classpath as you are now working with a j2ee compliant app server (which 3.5 was not). Put you jar files specific to you application in you WEB-INF/lib directory. This keeps the application portable. You can put jar files in your .ear directory if multiple .war files in the .ear use them. Only put things in the server classpath that are used by all apps on the server (e.g. jdbc driver, etc.)

4.) The server classpath is at server configuration tab ->process definition --> java virtual machine

or you can edit the server.xml file (don't do this)
[ July 01, 2004: Message edited by: William Duncan ]

No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Regarding deployment on Websphere App server