Skip to Content

Making BOE SOAP WebServices work on JBoss application server requires a few steps.


Step 1:

Once BOE is installed, locate the “wdeploy\rsa_module” directory.


Copy all files from the following WDeploy RSA module directory:

Path : “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy\rsa_module”

(Below images are just a reference install on Windows.)/wp-content/uploads/2015/12/step1_copyfiles_851971.png

Step 2:

On installed JBoss application server,

Create a “com\rsa\main” directory under  this “modules” directory.

Path : “<JBOSS_INSTALL_DIR>\modules\”

Place all files copied in step#1 above.

Path: “<JBOSS_INSTALL_DIR>\modules\com\rsa\main”/wp-content/uploads/2015/12/step2_pastefiles_851981.png

Step 3:

Move the jboss-deployment-structure.xml file from:

Path:  “<JBOSS_INSTALL_DIR>\modules\com\rsa\main”


And place the file in the following dswsbobje source file directory:

Path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\dswsbobje\WEB-INF”


Step 4:

Remove the listed RSA JAR files from the dswsbobje war:

1. certjFIPS.jar,

2. cryptojFIPS.jar

3. ssljFIPS.jar


Path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\ dswsbobje \WEB-INF\lib”


Step 5:

Predeploy the modified dswsbobje web application using the Wdeploy tool.


Path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy

Command:  “wdeploy jboss6 predeploy -DAPP= dswsbobje”/wp-content/uploads/2015/12/step5_commandtodeploy_851985.png

Step 6:

A dswsbobje.war file will be generated in following directory.

path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy/workdir/jboss6/application”/wp-content/uploads/2015/12/step6_wargenarated_851986.png

Step 7:

Deploy on JBoss.

Place “dswsbobje.war” file copied in step#6 above.

Path:   “<JBOSS_INSTALL_DIR>\standalone\deployments”


Step 8:

Restart the JBoss application server.

Step 9:

Verify deployment

Check list of BOE services available:  http://<server>:<port>/dswsbobje/services




Follow the same steps for AdminTools application.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member


    Could you please tell me what BO version you referred for this Doc?

    I am trying to Deploy 4.1Sp7 webapps on Jboss6.4 and only BI Launch Pad is working that too the preferences page is displaying page not found error.

    CMC login page is also showing 404 Page not found.

    Could you please tell do I have to do any setting for Jboss before deploying webapps.


  2. Former Member

    Hi Bharath,

    I have installed Jboss6.4EAP in our environment with BO4.1SP7.

    Changed the As_dir and As_instance in the config.jboss7 file and used wdeploy to Predeployall the webapps.

    The webapps are created under wordir/jboss7/application.

    I copied these war files and placed them in Standalone/Deployments folder in Jboss.

    The Jboss has deployed all the war files without any issues.

    But when i open CMC URL, its giving 404 page not found.

    The BI LaunchPad works , but the preferences,help pages are throwing 404 error.

    Am i missing anything?


  3. Lisa Liao

    Hi Bharath,

    Thanks very much for sharing.

    I can see in Supported Platform guide that BI 4.2 supports JBOSS EAP 6.4.

    However, as per PAM of BI 4.1 JBOSS 7.1.1 is supported.

    Here is my question:

    Can you please advise when JBOSS7 will be supported in BI4.2?

    Thanks very much.

    Best regards,


  4. Former Member

    Thanks Bharat.

    Even though it is not supported for BO 4.2 version it is working fine in standalone environment.

    We have to implement the JBOSS version on another server and integrate it with BO 4.2 server.

    I know there is a risk of using this version with 4.2 which is not supported.

    It would be helpful if you can provide steps to deploy the JBOSS 3 version.


    With Regards,

    Amit Kathe

    1. Denis Konovalov

      if it is not supported it means there are no steps to implement it. It means that SAP will not support your deployment in case you run into issues and that you might get unpredictable results.

      So, why would you ever wont to use unsupported version ??


Leave a Reply