• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Deploying a War file using Admin COnsole

 
Veni Velkoor
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
We are running WAS v4.0.3 on a Win2K server. I am trying to deploying a war file containg Servlets using the Admin Console. I always get the following error.
Exception:
Cannot expand the ear file under E:\WebSphere\AppServer\installedApps\CLCS_GUI.ear
com.ibm.ejs.sm.exception.OpException: Cannot expand the ear file under E:\WebSphere\AppServer\installedApps\CLCS_GUI.ear
--------
com.ibm.ejs.sm.client.command.ExecutionException: Error during install applicationat com.ibm.ejs.sm.client.command.InstallEnterpriseAppCommand.execute(InstallEnterpriseAppCommand.java:84)at com.ibm.ejs.sm.client.command.CommandManager$ExecutionThread.run(CommandManager.java:264)at com.ibm.ejs.sm.client.command.ThreadPool$PooledThread.run(ThreadPool.java:89)
Then I also noticed that it did create the appropriate directory and also expanded about half of the classes in the WAR file and
then failed. It almost seems like it gets halfway through expanding the EAR file and then fails.
As all I have is servlets and JSPs I am just creating a WAR file using the AAT and then trying to install it as a Stand-alone module using the Admin Console. Is there a step I am missing there?? Also I have all my servlets in a directory structure that I exported from Visual Age for Java v3.5 . I add all my JSP and HTML files as resource files when I create the jar.
Any direction will be very much appreciated! I am completely stumped now.
Thanks,
Veni.
 
Vinod Bijlani
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Did you verify the war file in AAT?
 
Veni Velkoor
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes I verified the file and it was fine. I found the solution though, one of the class files in the WAR file had a very long file name and WAS had problems with this and failed to expand the ear file when it reached that class name. Once that was fixed, I could deploy the application successfully.
Thanks,
Veni.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic