cancel
Showing results for 
Search instead for 
Did you mean: 

Running ant build scripts from cmd fails on Windows Server

Former Member
0 Kudos

Hi all!

I'm trying to build and package ME on a Windows Server calling the ant build script targets from cmd. This works fine on a Windows XP machine. On a Windows Server machine however the ant internal calls to nwcetool.bat are failing because -files are not found in DEPLOYARCHIVES. And these files are really not there although they should have been created by nwcetool.

Does anyone have a clue why calling ant build script in cmd on a Windows XP machine will work but fails on Window Server?

Thanks a lot!

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Juliane,

Could you post the build log here?

We faced with the similar issue a while ago.

In our case the root cause was with the jdk.home property in the file custom.properties - incorrect path to JDK had been entered there. Check the path and make sure it is correct.

Thanks

Former Member
0 Kudos

Hi Ivan!

Thanks for the quick answer. I've checked again and jdk.home in custom.properties-file is set correctly. All targets that are not using the ceclt-tool are working fine. Only when it comes to packaging it's not working.

Calling nwcetool.bat directly using the absolute path of BUILDARCHIVES and DEPLOYARCHIVES works fine (not using ant):

nwcetool.bat -c "createsda -n me/ear -v sap.com -l local -type J2EE -counter 5.2.5.3.320 -scn ME -scv sap.com -deps sap.com:me/security/loginmodule C:\SAP\SAPME\SDK\build\results\server\package.sca\sca\BUILDARCHIVES\me.ear C:\SAP\SAPME\SDK\build\results\server\package.sca\sca\DEPLOYARCHIVES\me.web-ext.sda-5.2.5.3-Base" -e

I'll put the log entry in the following post as it rendered this post unreadable.

Thanks for you help!

Former Member
0 Kudos

This is part 1 of the cmd output for packaging using ant build:

C:\SAP\SAPME\SDK\build\script>ant -buildfile build.dev.sobsap2.xml package

Buildfile: build.dev.sobsap2.xml

validate.publish.server:

increment.buildID:

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\increment.buildID

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\increment.buildID

echo 2011-04-07 09:33:43 No base build counter, incrementing counter ofset only.

xslt Processing C:\SAP\SAPME\SDK\build\build_counter.xml to C:\SAP\SAPME\SDK\build\results\server\increment.buildID\build_counter.xml

xslt Loading stylesheet C:\SAP\SAPME\SDK\build\xslt\build_counter.xsl

copy Copying 1 file to C:\SAP\SAPME\SDK\build

echo 2011-04-07 09:33:43 build_counter.xsl build number=330

xslt Processing C:\SAP\SAPME\SDK\build\buildID.xml to C:\SAP\SAPME\SDK\build\results\server\increment.buildID\buildID.xml.tmp

xslt Loading stylesheet C:\SAP\SAPME\SDK\build\xslt\buildID_xml_update.xsl

xslt newBuildNumber

copy Copying 1 file to C:\SAP\SAPME\SDK\build

create.archive.names:

create.server.release.file:

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\create.server.release.file

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\create.server.release.file

copy Copying 1 file to C:\SAP\SAPME\SDK\build\results\server\create.server.release.file

validate.integration.xslt:

package.xslt:

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\package.xslt

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\package.xslt

zip Warning: skipping zip archive C:\SAP\SAPME\SDK\build\results\server\package.xslt\saltXSLT.zip because no files were included.

package.sca:

create.version.properties:

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\create.version.properties

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\create.version.properties

delete Deleting: C:\SAP\SAPME\SDK\build\results\server\sda\APP-INF\lib\customBuildID.jar

jar Building jar: C:\SAP\SAPME\SDK\build\results\server\sda\APP-INF\lib\customBuildID.jar

create.version.xml:

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\create.version.xml

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\create.version.xml

echo 2011-04-07 09:33:45 Base version file found, adding custom version information.

echo 2011-04-07 09:33:45 Custom build ID (source control stamp)=""

echo 2011-04-07 09:33:45 Extended info=""

xslt Processing C:\SAP\SAPME\SDK\build\buildID.xml to C:\SAP\SAPME\SDK\build\results\server\create.version.xml\version.xml

xslt Loading stylesheet C:\SAP\SAPME\SDK\build\xslt\custom_version.xsl

xslt baseVersionFile=C:\SAP\SAPME\SDK\build\results\server\master\resources\xml/version.xml

jar Updating jar: C:\SAP\SAPME\SDK\build\results\server\sda\APP-INF\lib\me.common.api-5.2.5.3-Base.jar

Former Member
0 Kudos

And this is part 2 :

package.sca.impl:

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\package.sca

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\package.sca

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\package.sca\ear

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\package.sca\sca\BUILDARCHIVES

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\package.sca\sca\DEPLOYARCHIVES

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\create.application.xml

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\create.application.xml

echo 2011-04-07 09:33:45 Creating application descriptor.

xslt Processing C:\SAP\SAPME\SDK\extension\META-INF\application.xml to C:\SAP\SAPME\SDK\build\results\server\create.application.xml\application.xml

xslt Loading stylesheet C:\SAP\SAPME\SDK\build\xslt\create-application-xml.xslt

xslt ejbModule=

xslt webModule=salt-webservice

copy Copying 1 file to C:\SAP\SAPME\SDK\extension\META-INF

delete Deleting directory C:\SAP\SAPME\SDK\build\results\server\merge.application.xml

mkdir Created dir: C:\SAP\SAPME\SDK\build\results\server\merge.application.xml

echo 2011-04-07 09:33:45 Merging application descriptor "C:\SAP\SAPME\SDK\extension\META-INF/application.xml" with "C:\SAP\SAPME\SDK\build\results\server\master\resources\xml/application.xml".

xslt Processing C:\SAP\SAPME\SDK\build\results\server\master\resources\xml\application.xml to C:\SAP\SAPME\SDK\build\results\server\merge.application.xml\merged.xml

xslt Loading stylesheet C:\SAP\SAPME\SDK\build\xslt\jee-application-merge.xslt

xslt jee-application-merge: file to merge is C:\SAP\SAPME\SDK\extension\META-INF/application.xml

xslt jee-application-merge: checking for module conflicts...

xslt jee-application-merge: Base EJBs=me.activity.ejb-5.2.5.3-Base.jar m

e.alarm.ejb-5.2.5.3-Base.jar me.appconfig.ejb-5.2.5.3-Base.jar me.backgroundproc

ess.ejb-5.2.5.3-Base.jar me.browse.ejb-5.2.5.3-Base.jar me.common.frame.ejb-5.2.

5.3-Base.jar me.container.ejb-5.2.5.3-Base.jar me.correctiveaction.ejb-5.2.5.3-B

ase.jar me.customdata.ejb-5.2.5.3-Base.jar me.datacollection.ejb-5.2.5.3-Base.ja

r me.dbsequence.ejb-5.2.5.3-Base.jar me.defaultvalue.ejb-5.2.5.3-Base.jar me.dem

and.ejb-5.2.5.3-Base.jar me.integration.xml.ejb-5.2.5.3-Base.jar me.inventory.ej

b-5.2.5.3-Base.jar me.nonconformance.ejb-5.2.5.3-Base.jar me.productdefinition.e

jb-5.2.5.3-Base.jar me.production.ejb-5.2.5.3-Base.jar me.status.ejb-5.2.5.3-Bas

e.jar me.numbering.ejb-5.2.5.3-Base.jar me.diagnostics.ejb-5.2.5.3-Base.jar me.d

ocument.ejb-5.2.5.3-Base.jar me.httpserver.ejb-5.2.5.3-Base.jar me.integration.c

nc.ejb-5.2.5.3-Base.jar me.integration.collaboration.ejb-5.2.5.3-Base.jar me.int

egration.sap.ejb-5.2.5.3-Base.jar me.labor.ejb-5.2.5.3-Base.jar me.user.ejb-5.2.

5.3-Base.jar me.ods.ejb-5.2.5.3-Base.jar me.plant.ejb-5.2.5.3-Base.jar me.produc

tiondate.ejb-5.2.5.3-Base.jar me.reasoncode.ejb-5.2.5.3-Base.jar me.reporting.ej

b-5.2.5.3-Base.jar me.rtw.ejb-5.2.5.3-Base.jar me.script.ejb-5.2.5.3-Base.jar me

.security.ejb-5.2.5.3-Base.jar me.solutionverification.ejb-5.2.5.3-Base.jar me.t

imegranularity.ejb-5.2.5.3-Base.jar me.tooling.ejb-5.2.5.3-Base.jar

xslt jee-application-merge: SSP EJBs=

copy Copying 1 file to C:\SAP\SAPME\SDK\build\results\server\sda\META-INF

copy Copying 163 files to C:\SAP\SAPME\SDK\build\results\server\package.sca\ear

jar Building jar: C:\SAP\SAPME\SDK\build\results\server\package.sca\sca\BUILDARCHIVES\me.ear

echo 2011-04-07 09:33:45 nwce.tool=C:\SAP\SAPME\SDK\build\tools\ceclt\nwcetool\nwcetool.bat, nwce.tool.lib=C:\SAP\SAPME\SDK\build\tools\ceclt\lib, CECLT JDK=C:Program Files (x86)Javajdk1.5.0_22

echo 2011-04-07 09:33:45 Executing CECLT with the following arguments:

-c "createsda -n me/ear -v sap.com -l local -type J2EE -counter 5.2.5.3.330 -scn

ME -scv sap.com -deps sap.com:me/security/loginmodule BUILDARCHIVES\me.ear DEPLOYARCHIVES\me.web-ext.sda-5.2.5.3-Base" -e

exec The filename, directory name, or volume label syntax is incorrect.

exec Result: 1

BUILD FAILED

C:\SAP\SAPME\SDK\build\script\build.dev.sobsap2.xml:1665: The following error occurred while executing this line:

C:\SAP\SAPME\SDK\build\script\build.dev.sobsap2.xml:1723: Warning: Could not find file C:\SAP\SAPME\SDK\build\results\server\package.sca\sca\DEPLOYARCHIVES\me.web-ext.sda-5.2.5.3-Base.ear to copy.

Former Member
0 Kudos

Hi Juliane,

The fact that you can successfully execute nwcetool.bat directly may indicate that there is a problem with JAVA_HOME variable. When you execute nwcetool.bat directly the JAVA_HOME is the system value, which may be different from the value that is set by ant script. The JAVA_HOME value set by the ant script is the value of jdk.home property.

Try to check if the system JAVA_HOME value matches jdk.home value.

Also you may try to use DOS name for the JDK path in jdk.home property. For you it will look like


C:\PROGRA~2\JAVA\JDK15~1.0_2