cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

wdeploy Issue

Madhu-Teklink
Explorer
0 Likes
2,440

Hi

To enable authentication options on the BI Launch Pad logon screen(BOE XI 4.0), we added the parameters and restarted web application server. As per the administration guide, we are supposed to deploy BOE.war file with wdeploy tool. Following is the error message when I run wdeploy tool manually.

*******************************************************

E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0 \wdeploy>wdeploy.bat tomcat6 -DAPP=BOE deploy

JAVA_HOME not set, trying E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk

Using JAVA_HOME=E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk

Buildfile: wcommon.xml

AuroraConfig:

Loading message.properties

Loading wdeploy.conf

config:

Loading conf\config.tomcat6

Loading BOE.properties

set default for E:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/wdeploy/workdir/tomcat6/application

Warning: as_mode property not set. Standalone deployment assumed. (DEP00104)

preconfig:

checkargs:

Validating configuration...

Tomcat6

Result: 1

BUILD FAILED

E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\wdeploy\wcommon.xml:219: The following error occurred while executing this line:

E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\wdeploy\tomcat6.xml:123: Error: service name Tomcat6 is not correct. (DEP00136)

*******************************************************

Please let me know how to resolve this..

Regards

Madhu Bommala

View Entire Topic
Former Member
0 Likes

Hi Madhu

please check if the service name (if you have windows, try the windows services or CCM) is realy Tomcat6. In my case, it wasn't.

Regards

Christoph

denis_konovalov
Active Contributor
0 Likes

Yes, looks like by default config.tomcat6 is populated with wrong service name. change it to the actual one and wdeploy should work