[Bili Peles]

Hello
We work myEclpse 8.6 (installation details attached bellow)
The test environment is Websphere application server 7.0.0.11
Then we make deployment on the stopped server we get deployment error (the log is bellow)
It says that application .xml is not found but it is in the project and SERVICE_TESTER_EAR.ear that created as result of deployment is correct.
Then I deploy it by Admin console of WAS there are no problems and application works correctly.
The Websphere deployment log is :
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[C:\IBM\SDP\runtimes\base_v7\profiles\AppSrv01\installableApps\SERVICE_TESTER_EAR.ear, michael-xpNode05Cell, michael-xpNode05, server1, SERVICE_TESTER_EAR, {{“SERVICE_TESTER_WEB.war” “SERVICE_TESTER_WEB.war,WEB-INF/web.xml” default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, false, true, false, C:/MyEclipseBlueEdition8.6/configuration/org.eclipse.osgi/bundles/12/1/.cp/scriptutil/scriptutil.jar, C:/IBM/SDP/runtimes/base_v7/profiles/AppSrv01/installableApps/SERVICE_TESTER_EAR.ear/SERVICE_TESTER_EJB.jar, 6.0]”
C:\IBM\SDP\runtimes\base_v7\profiles\AppSrv01\installableApps\SERVICE_TESTER_EAR.ear
michael-xpNode05Cell
michael-xpNode05
server1
SERVICE_TESTER_EAR
{“SERVICE_TESTER_WEB.war” “SERVICE_TESTER_WEB.war,WEB-INF/web.xml” default_host}
{.* .* AppDeploymentOption.Yes 1}
-nopreCompileJSPs -distributeApp -useMetaDataFromBinary -deployejb -deployejb.complianceLevel {6.0} -appname “SERVICE_TESTER_EAR” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -noprocessEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“SERVICE_TESTER_WEB.war” “SERVICE_TESTER_WEB.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{.* .* AppDeploymentOption.Yes 1}}
false
true
false
C:/MyEclipseBlueEdition8.6/configuration/org.eclipse.osgi/bundles/12/1/.cp/scriptutil/scriptutil.jar
C:/IBM/SDP/runtimes/base_v7/profiles/AppSrv01/installableApps/SERVICE_TESTER_EAR.ear/SERVICE_TESTER_EJB.jar
-deployejb -deployejb.complianceLevel {6.0}
6.0
ADMA5016I: Installation of SERVICE_TESTER_EAR started.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
ADMA5018I: The EJBDeploy program is running on file C:\Documents and Settings\d614344\Local Settings\Temp\app5109828276060128873.ear.
Starting workbench.
EJB Deploy configuration directory: c:\IBM\SDP\runtimes\base_v7\deploytool\itp\configuration/
framework search path: c:\IBM\SDP\runtimes\base_v7\deploytool\itp\plugins
build: RAD755-I20091202_2257
Creating the project.
Writing output file
Shutting down workbench.
EJBDeploy complete.
0 Errors, 0 Warnings, 0 Informational Messages
ADMA5007I: The EJBDeploy program completed on file C:\Documents and Settings\d614344\Local Settings\Temp\app5109828276060128873.ear
org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0006E Archive is not a valid EAR File because the deployment descriptor can not be found (case sensitive): META-INF/application.xml
IWAE0006E Archive is not a valid EAR File because the deployment descriptor can not be found (case sensitive): META-INF/application.xml

at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl.openSpecificArchive(CommonarchiveFactoryImpl.java:1525)
at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.CommonarchiveFactoryImpl.openEARFile(CommonarchiveFactoryImpl.java:1209)
at com.ibm.etools.commonarchive.impl.CommonarchiveFactoryImpl.openEARFile(CommonarchiveFactoryImpl.java:612)
at com.ibm.ws.management.application.client.AppInstallHelper.getArchive(AppInstallHelper.java:284)
at com.ibm.ws.management.application.client.AppInstallHelper.getArchive(AppInstallHelper.java:188)
at com.ibm.ws.management.application.ArchiveSchedulerImpl.getArchive(ArchiveSchedulerImpl.java:218)
at com.ibm.ws.management.application.InstallSchedulerImpl.getEarFile(InstallSchedulerImpl.java:126)
at com.ibm.ws.webservices.combined.deploy.WSDeployTask.performTask(WSDeployTask.java:101)
at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:285)
at java.lang.Thread.run(Thread.java:736)
ADMA5011I: The cleanup of the temp directory for application SERVICE_TESTER_EAR is complete.
ADMA5014E: The installation of application SERVICE_TESTER_EAR failed.
WASX7017E: Exception received while running file “C:\MyEclipseBlueEdition8.6\Common\plugins\com.genuitec.eclipse.blue.websphere7_8.6.0.me201007292038\installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7132E: Application install for C:\IBM\SDP\runtimes\base_v7\profiles\AppSrv01\installableApps\SERVICE_TESTER_EAR.ear failed: see previous messages for details.

Installation details are:
*** Date:
16:10:20 IDT 19/04/2011
** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Blue Edition
Version: 8.6 Blue
Build id: 8.6-Blue-20100723

*** Eclipse details:
MyEclipse Blue Edition

Version: 8.6 Blue
Build id: 8.6-Blue-20100723

Eclipse Platform

Version: 3.5.2.R35x_v20100210-0800-9hEiFzmFst-TiEn9hNYgDWg1XN8ulH_JvCNGB
Build id: M20100211-1343

Eclipse Java Development Tools

Version: 3.5.2.r352_v20100108-7r88FEwFI0WTuoBl0iaG0tyhfZH6
Build id: M20100211-1343

Eclipse Plug-in Development Environment

Version: 3.5.2.R35x_v20100119-7Z7_FA2FDX-aXQYWqYDBz-z0qufo
Build id: M20100211-1343

Eclipse Graphical Editing Framework GEF

Version: 3.5.2.v20100111-1352-777928194B66D5D476C33B2A
Build id: 201001111753

Eclipse RCP

Version: 3.5.2.R35x_v20100119-9SA0FxwFnoCU5XxWItFdXXb27BA6
Build id: M20100211-1343

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\MyEclipseBlueEdition8.6\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\MyEclipseBlueEdition8.6\Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\MyEclipseBlueEdition8.6\Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/MyEclipseBlueEdition8.6
-data
D:\MYEclipce\ServiceTester
-vm
C:\MyEclipseBlueEdition8.6\Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

[support-swapna]

yaniv_illouz ,

Sorry that you are seeing this issue.

Can you answer some more questions for us ?

1. Is the project you are trying to deploy created in MyEclipse or in any other IDE and imported to MyEclipse?

2. If its created in another IDE, did you enhance the project to work with MyEclipse after importing to MyEclipse ?

3. Can you clarify if you are seeing this issue only for this particular project ?

4. We have released latest version 10.1 which has significant improvements from 8.6. I suggest you install MyEclipse Blue 10.1 along side the 8.6 version. The license you hold for 8.6 is valid for 10.1 too as our licenses are time based and not version based.

You can download ME Blue 10.1 from this link :
http://myeclipseide.com/index.php?name=Recommend_Us&req=Download&version=MEBlue

Alternatively you can use Pulse to install ME Blue 10.1. Here is the FAQ to install using Pulse. The tutorial is based on earlier version of MyEclipse. Select Eclipse 3.7 -Indigo and MyEclipse Blue 10.1 and follow the FAQ.
https://www.genuitec.com/forums/topic/installation-how-to-install-myeclipse-from-pulse/

5. Once you have installed ME Blue 10.1, import the project,enhance it if its created in another IDE, and try deploying to WAS 7.

Let us know how it works for you.

[Bili Peles]

Hello
Thank you for your help
I’ve found the problem
Our Ear project contains directory “lib” that was filled with jars file by Ant script
We have to make ear file with our constrains for deployment on server.
When I clear the “lib” directory the deployment from MyEclipse runs without the problem

[support-swapna]

yaniv_illouz ,

Glad that you got it working.
Do let us know if you see any issues.

[Author]

Posts