Solution Manager 7.2 – Installation and Configuration – VII – Managed System Config – Busines Objects
Part 1: Solution Manager 7.2 – Installation and Configuration – I – Installations
Part 2: Solution Manager 7.2 – Installation and Configuration – II – Configurations
Part 5: Solution Manager 7.2 – Installation and Configuration – V – Managed System Config – ABAP System
Manage System Configuration for a Business Objects System
There is no dedicated note or wiki to explain the setup of the BOE systems in Solution Manager 7.2 yet.
I asked this to SAP also to be sure about the configuration.
They told me that as it is mentioned in the note 2248724 – Root Cause Analysis in SAP Solution Manager 7.2 that SBOP BI PLATFORM 4.0 and 4.1 are supported in the Solution Manager 7.20. So I coud be able to perform all the configuration following the note 1975394 – SolMan 7.1: Managed Sys Setup – BI Platform 4.1 ignoring the steps to upload the extractors templates which are valid for Solman 7.10 only.
The SAP notes and wiki pages that I’ve read;
Managed System Setup of BOE 4.0 system in Solman 7.1
Configurations Steps according to
Managed System Setup of BOE 4.0 system in Solman 7.1
First of all I followed the SAP Note 1975394 – SolMan 7.1: Managed Sys Setup – BI Platform 4.1 for the latest up to date information for SAP BOE 4.1. And did the configurations in this note as below.
1. Configuration of Managed System
Ignored this step which is valid for Solman 7.10 only.
2. Naming Convention for the SIDs
Decided to name SIDs of cluster and tomcat application servers as BOP_BOE and BOP_WAS.
3. Installation or upgrade of Wily introscope
Minimum version of SAP Introscope package is version 9 is needed.
Our Wily version was 9.7. So I didnot upgrade it.
If you want to upgrate your wily package you can find detailed information about the installation of Introscope Enterprise Manager in blog Part 2.
4. Configuration of Database Monitoring for Customer Databases
Refer to SAP Note 1265134 as an entry point for the configuration steps required.
5. Using the setup automation tool
Details are in below “Auto configure using AC tool” section.
6-11. These steps are done by AC Tool automatically.
12 -13. These steps are for aolder versions of Solution Manager. (only for solman lower than SP9 and the later one is for solman lower than SP11)
14. Replace “coarsegrain.jar” and “KPIScript.jar” on each host where BOE 4.X running
The latest version of these two jar files can be downloaded from Note 2164192.
KPIScript.jar and Coarsegrain.jar are used for BOE related monitoring functions. Please use the newest version, you can choose update the BI version or download from this Note and replace the old ones in the related folder.
Please download the latest version KPIScript.jar and Coarsegrain.jar from attachment.
The default path of these two jar files is (for Windows): %BOE_DIR%SAP BusinessObjects Enterprise XI 4.0javalib
15. Delete old logs for BOE4
The large number of BOE logs may cause 100% CPU consumption on the BOE host. Please delete old logs under BO dir regularly.
For troubleshooting issues with BOE managed system setup also refer to the note 1722874 – Troubleshooting Solution Manager Root Cause Analysis for BOE
Installation of Diagnostics Agent on all hosts
You must install Diagnostics Agents on BOE and Tomcat Servers.
Detail description of the step can be found in the Installation of SMD Agent with SWPM section of Part 5
Auto configure using AC tool
*Report BOE SLD data to SLD – This step is done by tool automaticallay
*Report BOE Web Application Server SLD data to SLD – This step is done by tool automaticallay
Reporting of BOE and WAS to SLD steps are performed by AC Tool. And the details of running ACTool is done according to the note
Get the tool:
Download Pass: 12345
Use the guide ACTool User Guide.pdf
5 BOE Step by Step
5.2 Structure of file tree must be like below.
5.3 conf/boe.properties Preparation
Update boe.properties config file under conf folder as seen below. For details you can check the main wiki.
This file is used by the tool for configuration of BOE and Tomcat.
boe.home = E:SAP BusinessObjects
boe.system = SAPBOPRD
boe.user = Administrator
saphostagent.install = false
saphostagent.install.path = C:Program FilesSAPhostctrl
sld.connectkey.replace = true
sld.server.host = solman.mycomp.com
sld.server.port = 50200
sld.server.user = SLD_DS_SID
sld.server.https = n
boe.cmc.introscope.enable = true
boe.cmc.introscope.host = solman.mycomp.com
boe.cmc.introscope.port = 6001
boe.cmc.introscope.type = TCP
boe.cmc.ncs.level = 10
boe.cmc.smdagent.host = localhost
boe.cmc.smdagent.port = 6404
tomcat.service.name = BOEXI40Tomcat
tomcat.service.port = 8080
tomcat.http = http
tomcat.home = E:SAP BusinessObjects omcat
tomcat.running.mode.WindowsService = true
tomcat.hostname.sld.url = localhost
wily.javaagent.install = true
wily.javaagent.installfolder = E:usrsapCCMS
wily.EM.host = solman.mycomp.com
wily.EM.port = 6001
wily.EM.webport = 8081
jmx.user = smdAgentRole
jmx.port = 9004
jmx.solman.set = true
sld.warfile.replace = true
solman.version = other
smdagent.path = E:usrsapDAASMDA98
sld.system.longSID = BOP_WAS
tomcat.sld.manualtransfer = true
jvmmond.install.path = E:SAP BusinessObjectsSAP BusinessObjects Enterprise XI 4.0win64_x64sapjvm in
jvmmond.port = 1099
console.verbose = true
boe.node.restart = false
boe.service.name = BOEXI40SIASAPBOPRD
smdagent.windows.servicename = SAPDAA_98
5.7 Run ACTool with Interactive User Input
With an admin privilidged user run the batch file as below. It will start the tool and ask your selections.
After selecting SAP BI PLATFORM 4.X you select Execute and start configurations of all steps.
If your BOE and Tomcat servers are different run BOE steps on BOE Server and Tomcat Steps on WAS Server.
BOE and Tomcat restart are needed.
You could have problem after configurations and restarts. You can check below links for troubleshooting.
using JVM=E:SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0win64_x64sapjvm in
* Auto Configurantion Tool for SAP products 2.23.0
AC Tool supports the configuration for the follwoing products:
1. SAP DATA SERVICES 4.X
2. SAP BI PLATFORM 4.X
Please choose a product to config—
[ — Input the product id 1 – 2, only single number supported! ]
[ — Type ‘quit’ to exit from this application! ]
Please choose the action you want to perform—
[ — Please input number 1 – 2, only single number supported. ]
[ — Type ‘back’ to go back to products selection. ]
[ — Type ‘quit’ to exit from this application. ]
Configuration for product SAP BI PLATFORM 4.X
The configuration includes the following steps, you may multiple choose the steps to execute or check:
1. BOE – BI 4.0 Note 1653689 Step 6.1 – Enable SLD support for BO cluster
2. BOE – BI 4.0 Note 1653689 Step 8 – Enable Introscope for Java components
3. BOE – BI 4.0 Note 1653689 Step 9 – Enable Introscope for C++ components
4. BOE – BI 4.0 Note 1653689 Step 10 – Enable Saposcol process monitoring
5. BOE – BI 4.0 Note 1653689 Step 11 – Configure step of BOE 4.0(SP level lower than SP3)
8. BOE – Enable CSJNI – Update configurations of cs.cfg
9. BOE – Enable CSJNI – Update configurations of IntroscopeAgent_CSJNI.profile
10. BOE – Enable TDA service(BOE node need to be restarted.)
12. Tomcat Wiki Step 3 (BI 4.0 Note 1653689 Step 7)- Install Introscope Agent (Tomcat restart needed)
13. Tomcat Wiki Step 4.1 – Configure JMX (Tomcat restart needed)
14. Tomcat Wiki Step 4.2 – Configure JVM GC log (Tomcat restart needed)
15. Tomcat Wiki Step 4.3 – Check Tomcat logging (Tomcat restart needed)
16. Tomcat Wiki Step 5 (BI 4.0 Note 1653689 Step 6.2) – Install and run SLD Data Supplier
17. Tomcat – Enable TDA for Tomcat
18. TDA – Start Jvmmond.exe as OS service
Please choose the steps to configure—
[ — Type step IDs(1 to 18) to execute or check. ]
[ — For multiple selection please split the step number by ‘,’. ]
[ — Press ENTER directly to configure all steps. ]
[ — Type ‘back’ to get back to Action selection. ]
[ — Type ‘quit’ to exit from this application. ]
When you run “2. Check” you must see all steps are successful as seen in below picture in order to continue to the next step.
You can run the FAILURE steps to get SUCCESS after correcting the errors.
5.10 Impact of All Steps on Managed System and How to Check
In this list you can see all steps, operations and final result checks.
Check the Technical System for BOE in LMDB
Run SOLMAN_SETUP and check the BOE System’s properties from Managed System Configurations menu.
In Technical Systems Tab select your BOE System, select System Operations and Maintain System.
Then change Extended SID to BOP_BOE as seen below.
Make sure the product version list here are set with diagnostic flag as seen below after Setting Diagnostics-Relevance
Check Applications Servers and Central Management Servers on Technical Instances node. Also check software component versions as seen below.
And host information.
Setup of the BOE Database system
You can check below link for details.
How to perform the Database configuration for BOE 4.0 and 4.1 in Solman 7.10
You run LMDB and select technical System BOP_BOE.
Edit the system Database property as seen below and assign the DB of the BOE system.
Managed System setup for BOE 4.0
In SOLMAN_SETUP Managed System Configuration node you select the BOE system and select Configure System and Full Configuration Incl. for Service Delivery/EWA.
There are 8 steps to complete managed system configuration. I will share the screenshots of some of the steps below.
In step #1 “Assign Product” SBOP BI PLATFORM 4.1 is assigned to BOP_BOE technical system.
In step #2 “Check Prerequisites” prerequisites are checked.
In step #3 “Assign Diagnostics Agent” the DAA agent is found and assigned to the BOP_BOE system.
In step #4 “Enter System Parameters” the system parameters according to system type is entered as seen below. DB parameters are provided. DB parameters are done after “Setup of the BOE Database System”.
In step #5 “Enter Landscape Parameters” the landscape parameters are verified and provided. Mostly the default ones are saved as seen below.
In step #6 “Finalize Configuration” the automatic configuration steps like extracters setup, Introscope Host Adapter, Apply Settings for EWA and System Recommendations are executed.
In step #7 “Check Configuration” the configuration is checked and System Status is refreshed.
In step #8 “Complete” you can see all steps statuses and click Finish.
Configuration for BOP_BOE is done.
Managed System setup for Web Application Server with BOE 4.0 Web Application (Apache Tomcat)
Managed System Config of BOP_WAS is very similar to BOP_BOE. It has also 8 step to complete the configuration.
You select BOP_WAS technical system and start configuration.
Step #1 “Assign Product” , step #2 “Check Prerequisites” and step #3 “Assign Diagnostics Agent” are like BOP_BOE system.
In step #4 “Enter System Parameters” you enter parameters as seen below.
In step #5 “Enter Landscape Parameters” the landscape parameters for BOP_WAS ave verified and provided as seen below.
In step #6 “Finalize Configuration” and In step #7 “Check Configuration” are similar to BOP_BOE.
In step #8 “Complete” you can see all steps statuses as seen below and click Finish.
Configuration for BOP_WAS is done.
Wily Introscope setup for BOE 4.0
For detailed information and follow the main wiki and the note 1540591 – Wily Introscope Setup for SAP BOE 4.X for Introscope configuration.
I will put some screenshots from my configuration.
I configured the Wily Introscope Java agent and SMD Agent configurations in CMC as seen below. (For details check BO installation guide’s “To configure CA Wily Introscope Agent post installation” and “To configure SMD Agent post installation” sections)
Since our Introscope EM version is 9.7 I used the note 1579474 – Management Modules for Introscope delivered by SAP for deploying extra modules to EM as seen below.
/sap/extra_modules to deploy and then to /config/modules.
/Sap/extra_scripts to /scripts folder
Changed Java VM parameters of EM according to guide CA_Interescope_v97.pdf and restarted Introscope EM.
For the configuration of Introscope Java Agent profile for BOE Java Web Application I used ISAgentBOE40WebApp.pdf document attached to the mentioned note and changed the profile as seen below.
You can use the note 1438005 – Introscope Agent for Apache Tomcat and the document attached to this note for detail information.
Thread Dump Analysis Supportability
I didnot configure this section. In need can be done according to the note 1608714.
Problems and Solutions
When I get EWA report there were missing data and I investigated the cause.
There were problems on extractors and some infocubes and bi objects were not active on my Solution Manager BW.
I checked below documents for solutions.
How to Activate BW InfoCubes when Extractors Fail in the Extractor Framework
This is the end of the configuration.
Managed System Configuration of a Java System is coming next.
Thanks for your interests.