Professional Documents
Culture Documents
Yuksel AKCINAR
more by this author
SAP Solution Manager
sap solution managersolman setupsolution managersolution manager 7.2
share 0
share
tweet
share
Follow RSS
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.1ignoring 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;
2248724 – Root Cause Analysis in SAP Solution Manager 7.2
1472465 – SAP Solution Manager 7.1 and 7.2 – System Landscape Setup Guide
2229953 – Solution Manager 7.2 SP Stack 01: recommended corrections
Maintenance of Product in the System Landscape
Managed System Setup of BOE 4.0 system in Solman 7.1
1975394 – SolMan 7.1: Managed Sys Setup – BI Platform 4.1
2137275 – AC Tool release NOTE
2164192 – KPIScript.jar && Coarsegrain.jar release note
1722874 – Troubleshooting Solution Manager Root Cause Analysis for BOE
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
thelatest 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.
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.
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.0\java\lib\
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
This file is used by the tool for configuration of BOE and Tomcat.
boe.system = SAPBOPRD
boe.user = Administrator
boe.password = <YourPassword>
boe.os.user = <YourOSUuser>
saphostagent.install = false
saphostagent.password = <YourPassword>
sld.connectkey.replace = true
sld.server.host = solman.mycomp.com
sld.server.port = 50200
sld.server.user = SLD_DS_SID
sld.server.password = <SLD_DS_SID_UserPassword>
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.running.mode.WindowsService = true
tomcat.hostname.sld.url = localhost
wily.javaagent.install = true
wily.javaagent.installfolder = E:\usr\sap\CCMS
wily.javaagent.folder =
wily.EM.host = solman.mycomp.com
wily.EM.port = 6001
wily.EM.webport = 8081
jmx.user = smdAgentRole
jmx.password = <YourPassword>
jmx.port = 9004
jmx.solman.set = true
sld.warfile.replace = true
solman.version = other
smdagent.path = E:\usr\sap\DAA\SMDA98
sld.system.longSID = BOP_WAS
tomcat.sld.manualtransfer = true
jvmmond.port = 1099
jvmmond.password = <YourPassword>
console.verbose = true
boe.node.restart = false
boe.service.name = BOEXI40SIASAPBOPRD
smdagent.windows.servicename = SAPDAA_98
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.
You could have problem after configurations and restarts. You can check below links for
troubleshooting.
http://wiki.scn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Apache+Tomcat+System+i
n+Solman+7.1
1975394 – SolMan 7.1: Managed Sys Setup – BI Platform 4.1
E:\BOCD\actool>run_actool.bat
using JVM=E:\SAP BusinessObjects\\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin
******************************************************************************
* 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 input:2
1. Execute
2. Check
You can run the FAILURE steps to get SUCCESS after correcting the errors.
In Technical Systems Tab select your BOE System, select System Operations and Maintain System.
Check Applications Servers and Central Management Servers on Technical Instances node. Also check
software component versions as seen below.
And host information.
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.
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.
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.
<EM folder>/sap/extra_modules to deploy and then to <EM folder>/config/modules.
<EM folder>/Sap/extra_scripts to <EM folder>/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.