aspose file tools*
The moose likes Websphere and the fly likes websphere 5.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "websphere 5.0" Watch "websphere 5.0" New topic
Author

websphere 5.0

william gates
Ranch Hand

Joined: Feb 21, 2007
Posts: 112
Working on a web project with struts in websphere 5.0. Tested it on Tomcat 5.0 and it worked fine. Now going to websphere with exact same application and for one reason or another the css isn't being read and the images aren't being found.

That and the fact we have to delete and reinstall every time we have either a small change or large change. We have no access to logs or even the directory where files are deployed because that is through production control. We ftp an ear file, then install running a few python scripts written by system admins on the server and then it either fails or is installed. From there we have no access to what is inside the deployed folder, any logs, or error files. At this point, not sure if Websphere 5.0 is worth it because it takes too long to change a simple file. And the admins already informed us, "that is the way it is and will be."

Any other j2ee servers out there, open source maybe, that would be worth testing out and why does the css and images work in tomcat 5.0 but not Websphere app server 5.0?
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968

True, WebSphere 5 can be less forgiving than Tomcat.

This is just an idea, but is there any chance that the WebSphere Application Server expects the .css file to be on the web server, as opposed to the application server? Just a hunch.

Good luck.

-Cameron McKenzie
william gates
Ranch Hand

Joined: Feb 21, 2007
Posts: 112
I really don't know at this point. As i've stated in another post, we don't have access to anything once it's deployed to websphere.

We have to rely on the server admin for any errors, info, issues to be resolved. It wouldn't be a problem if the admins were developers or experts at websphere, but that's not the case. And the case is management has told us that is the way it will be and to accept it.

So at this point, on the development box, if there is any errors, we have to figure out why it works or doesn't work with a blind eye unless the server admin informs us what errors were logged or reported.
Vijay Rmk
Greenhorn

Joined: Mar 27, 2007
Posts: 4
Hi evry body,I am new to this forum..But has quite some experience on websphere administration. Being a developer my self, I shifted on later stage to websphere admininistration...The process I used to follow is,
All build scripts were written on ANT and for deployment in WAS , i used JACL...A better idea would be , ask the websphere admins to transfer all logs and error files to common accessible folder...In my case I used to write unix scripts for moving, copying and updating with a copy always accessible in common folder for developers ....Unless developers and admins are in sync ..the whoel scenario will be a mess ....
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: websphere 5.0
 
Similar Threads
Caching on WAS
IBM HTTP not sending images consistently
Struts and Websphere
Error in Loading WAR file
Memory leaks