Re: WSAD-deploying EAR through admin console: invalid
binaries

I've experienced the same problem and found it to be an issue with the
deployment.xml file. This file is created when the EAR is installed. The issue I
had was that the deployment.xml file had the wrong location for the installed
EAR in the binariesURL attribute of the deployedObject element.<br />
<br />
When I tried to start the EAR within WSAD admin console I got the following
error:<br />
 <br />
com.ibm.etools.archive.exception.DeploymentDescriptorLoadException:
META-INF/application.xml<br />
Stack trace of nested exception:<br />
com.ibm.etools.archive.exception.ArchiveRuntimeException: Invalid binaries path:
D:\work\BCC\Workspace/localhost/MyApp.ear<br />
<br />
<hr />
<br />
The deployments.xml file had the following entry<br />
binariesURL="$(APP_INSTALL_ROOT)/localhost/MyApp.ear"<br />
<br />
Using the error message I got in the stack trace I worked out that the
{$APP_INSTALL_ROOT} was D:\work\BCC\Workspace<br />
<br />
The solution requires that you locate where the EAR had been installed on the
file system. I found the EAR installed under the server project as
follows:<br />
d:\work\BCC\Servers\WSAD V5.1 Local Only.wsc\cells\localhost\applications<br
/>
<br />
To fix the issue you need to update the binariesURL so that it points to the
location where the installed EAR resides on the file system. In my case I
updated the deployment.xml with the following:<br />
binariesURL="$(APP_INSTALL_ROOT)/../Servers/WSAD V5.1 Local
Only.wsc/cells/localhost/applications/MyApp.ear"<br />
<br />