Hi, I am trying to build my ejb module useing ANT 1.6.1 on WAS6.1. I'm getting the following error: Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified.) at com.ibm.ws.ant.utils.ProjectUtils.reportError(ProjectUtils.java:30) at com.ibm.ws.ant.utils.WasUtils.parseScriptFile(WasUtils.java:257) at com.ibm.ws.ant.utils.WasUtils.parseProfileScriptFile(WasUtils.java:13 6) at com.ibm.ws.ant.utils.WasUtils.parseSetupCmdLine(WasUtils.java:115) at com.ibm.websphere.ant.tasks.WsEjbDeploy.execute(WsEjbDeploy.java:519)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:301) at org.apache.tools.ant.Target.performTasks(Target.java:328) at org.apache.tools.ant.Project.executeTarget(Project.java:1215) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:383) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:301) at org.apache.tools.ant.Target.performTasks(Target.java:328) at org.apache.tools.ant.Project.executeTarget(Project.java:1215) at org.apache.tools.ant.Project.executeTargets(Project.java:1063) at org.apache.tools.ant.Main.runBuild(Main.java:632) at org.apache.tools.ant.Main.startAnt(Main.java:183) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:197) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:56)
I saw a few links on this particular error, but couldnt find any proper solution. Please do let me know if anyone came across this issue and solved it successfully.
Originally posted by Deboshree Roy: I'm using apache-ant-1.6.1 for building my code.
Right. But more specifically, are you typing "build" or are you running an IBM script? IBM specific variables will only work if you use the IBM script.
Joined: Oct 03, 2007
Hi, I provide the path for the build.xml and key in the ant command to start the build process.That is how it was done when my code was originally on WAS and WPS 5.1 and I'm following the same procedure on migration to WAS and WPS 6.1
author & internet detective
Deboshree, Not sure what WPS is, but the ejb related stuff got stricter between 5 and 6. In particular, it was possible to run ejbdeploy without having a full WebSphere installation in 5 and that seems to be gone in 6.
Joined: Oct 03, 2007
Hi I have made a full installation of Webspere Portal Server(WPS)6.1 on my system. ejb2.0 was the version that was working on my portal 5.1. But I have migrated on RAD 7.5 using the Migration Wizard to ejb2.1. The error is coming while executing the wsejbdeploy task.It is not able to lookup the AppServer path (I guess),But when I echo the WASHome path in the script it is displaying the correct path.
Not sure if you have gotten around the problem.
Can you try to defined -Duser.install.root=<Your Profile Dir> on the java command you use to invoke ant? Or is it possible to use the ws_ant command which is shipped with WAS?
My sincere apologies, I got our naming policy dead wrong, happy Ranching!
Joined: Jan 07, 2009
Actually, the more that I think about the problem, the more I wonder if a profile exists on the install?
I believe that starting on WAS 6.0, a profile needs to exist. Do you have a profile create? You can look at <WAS_INSTALL>/properties/profileRegistry.xml
<?xml version="1.0" encoding="UTF-8"?>
<profile isAReservationTicket="false" isDefault="true" name="AppSrv01" path="/opt/WebSphere/profiles/ProcSrv01" template="/opt/WebSphere/profileTemplates/default">
You may be able to pass the install root as the user.install.root, or simply create a profile using the pmt in <WAS_INSTALL>/bin/ProfileManagement/pmt