Generalities about wdeploy architecture
wdeploy GUI tool
The wdeploy tool is quite simple and its documentation complete, please refer to it.
help.sap.com/bobip40 > Installation, Upgrade & Deployment > Web Applications Deployment Guide
wdeploy command line tool
What can the command line do that the GUI can't
predeploy, deploy specifc apps only, prepare http static content only package, NW Java AS 7.3 is supported on the command line only, Apache (for static content of the webapps) is supported on the command line only.
wdeploy --help is your best friend
Deploying BOE without the CMC
Edit wdeploy.conf in [BI4 INSTALL PATH]/SAP BusinessObjects Enterprise XI 4.0/wdeploy/conf and set property disable_CmcApp to true.
Then return the wdeploy tool (GUI or command line) with the options you like.
Deploying html static content to pure web server
To prepare static content you need to run wdeploy on the command line using apache as the webapp server.
Have a look at the [BI4 INSTALL PATH]/SAP BusinessObjects Enterprise XI 4.0/wdeploy/conf/config.apache file.
- Using the BI4 installer, install the BI4 web tier on the machine hosting the webapp server.
- Patch this installation up to your required patch level.
- Then deploy to web app server using wdeploy GUI or command line.
Notes regarding deployment to SAP NW Java AS 7.3
SAP NW Java AS 7.3 is supported from and only from BI 4.0 SP01 patch 01.
Maximal heap size of SAP NW Java AS Java VM shall be at least 4GB for a successfull deployment.
In order to launch the "configtool" application, go to usr/sap/<SID>/ABC/j2ee/configtool and launch configtool.sh or configtool.bat (in our case we added 6GB - ABC is the our instance folder)
Preparing the webapps
You have to at least update the SAP_metadata.properties file located in [BI4 install path]/SAP BusinessObjects Enterprise XI 4.0/wdeploy/SLDSupport/NWSLD/BOE for the BOE webapp, same thing apply for the other webapps.
The name and scn parameters in this file have to be the same, it is recommended to set the verstion parameters to the correct values (counter to 4.0 (BI4 RTM), servicelevel to 1 (SP01), patchlevel to 1 (SP01 Patch 1)).
For instance here is my SAP_metadata file for the BOE webapp :
You can also change the web.xml file etc...
Predeploying using wdeploy
wdeploy doesn't support doing the full deployment to NW Java as 7.3, use the wdeploy command line tool to do the predeployment only with :
for instance (here we predeploy only BOE webapp) ("deploy.sh sapappsvr73 predeployall" to prepare everything)
The wdeploy will create a .sca file.
Deploying using JSPM
- Then copy the generated sca file (in [BI4 install path]/SAP BusinessObjects Enterprise XI 4.0/wdeploy/workdir/sapappsvr73/application) to /usr/sap/trans/EPS/in .
- Then use the JSPM tool (start it from /usr/sap/<SID>/ABC/j2ee/JSPM/ with go.bat or go.sh).
- Logon to the NW Java WAS 7.3.
- Click "New Deployment" button
- Choose "New Software Component" the tool will scan the /usr/sap/trans/EPS/in folder.
- Click "Next" button
- Select the BOE webapp, then click "Start". The deployment(s) will commence.
Note: displayed version is not correct, to have it display correct version, before running wdeploy, you have to update the SAP_metadata.properties file located in [BI4 install path]/SAP BusinessObjects Enterprise XI 4.0/wdeploy/SLDSupport/NWSLD/BOE for the BOE webapp, same thing apply for the other webapps.
Note that the name and scn parameters in this file have to be the same.
Note: there is no undeploy option with JSPM, when upgrading your BOE, after the installers finish patching, you need to re predeploy, recopy the sca file and rerun JSPM, it will then overwrite the previous version, customizations, if any, will be merged in the new version.
How to undeploy the BOE
Under /usr/sap/<SID>/ABC/j2ee/console (where ABC is the our instance folder)
In order to launch the "textconsole" application, go to usr/sap/<SID>/ABC/j2ee/console and launch textconsole.sh or textconsole.bat
Check that your application was already deployed : list_app
And type the following command :
- undeploy name=BOEWEBAPPJAVA on_deploy_error=stop (Where BOEWEBAPPJAVA is the name of our BOE application)
How to force JSPM to deploy over already deployed BOE
It might happen that JSPM does not want to deploy over and existing deployment of BOE, to force it to do so :
Just go to JSPM config file (in /usr/sap/<SID>/ABC/j2ee/JSPM/param/ folder), edit jspm_config.txt
To make deployment in force mode, add the lines: