0001975394

SAP Note

Header Data

Symptom

You want to setup Root Cause Analysis for the product SAP BusinessObjects Enterprise BI Platform 4.1 with Solution Manager Version 7.10. This note explains what needs to be updated within the BusinessObjects system to enable proper collaboration with Solution Manager.

Other Terms

Solution Manager, RCA, Root Cause Analysis, SAP BI Platform 4.1, BOE

Reason and Prerequisites

This note is only relevant for Solution Manager 7.10 in combination with SAP BI Platform 4.1(any SP level).

Depending on the detailed BO system version additional steps have to be performed manually.

Solution

1. Configuration of Managed System

----------------------------------

*Before the configuration of managed system setup, please upload the latest config.xml from note 1259109 - Latest version of configuration file for E2E CA, EA, WA.

*Before the configuration of managed system setup, please upload the new extractors for 4.1 from note 1849781 - Missing RCA Extractor for BOE 4.1 in Solman7.1 before SP13.

*Before the configurtaion of managed system setup, please upload the latest CV template for 4.1 (BOE_CVs.zip) from the following notes (before sp12):

1783884 RCA template for Solution Manager 7.10 SP05

1783885 RCA template for Soltuion Manager 7.10 SP06






Perform the managed system configuration for your SAP BusinessObjects Enterprise technical system as described in the System Landscape Setup WIKI. Please use the following link:

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+BOE+4.0+system+in+Solman+7.1

2. Naming Convention for the SIDs

---------------------------------

Attention: As of SP 20 of Software Component ST-SER this naming convention is no longer necessary.

1975394 - SolMan 7.1: Managed Sys Setup - BI Platform 4.1

Version 9 Validity: 09.09.2014 - active Language English (Master)

Released On 09.09.2014 11:30:11

Release Status Released for Customer

Component SV-SMG-DIA Solution Manager Diagnostics

BI-BIP-DEP SBOP Web Application Deployment, Wdeploy

Priority Recommendations / Additional Info

Category Customizing

Other Components

A typical BI platform 4.1 system in Solution Manager includes:

1) 1 Technical System for Business Object Cluster

2) 1 or more Technical System(s) for Web Application Servers

Solution Manager depends on the technical system definition in the Landscape Management(LMDB). Even though BI platform doesn't have an original System ID concept, SIDs must be assigned to all BI platform relevant technical systems.

In BI platform 4.1, Solution Manager assigns the SID for each technical system automatically after enabling SAP System Landscape Directory (SLD) support. Solution Manager builds the System ID from the first 3 chars of the BO cluster name. By default the BO cluster name is built from the hostname and the CMS port number. The SID will then be the first 3 characters of the hostname. In addition to this 3 character SID Solution Manager also assigns a 8 character extended SID which is built from the 3 character SID and if that is not unique it is extended with a 5 digit number. The extended SID is the unique identifier of a system in Solution Manager and it can be manually adjusted to another unique 8 character string. By changing the extended SID Solution Manager will also adjust the SID to become the first 3 characters of the extended SID. Chapter 2.1 explains the SAP recommendations on how to choose the SID and extended SID for the BOBJ and Web App Systems.

2.1 SAP recommendation for renaming the SID and extended SID

-------------------------------------------------------------

In Solution Manager Technical System Editor you can only change the extended SID. The SID is implicitly adjusted (to be the first 3 characters of the extended SID).

The Extended SID has to be changed at the very beginning of the managed system setup. If you change the extended SID later you have to repeat the managed system setup again and you will loose all data for the system within Solution Manager that was collected earlier. Also the collection extractors for the old extended SID have to be manually deleted - otherwise they will continue to collect data which cannot be accessed any longer.

In step 1 of managed system setup, please open Technical System Editor. Now You could switch to Edit mode and change the extended SID. SAP recommends to follow the naming convention:

<SID>_BOE for the BI Platform system where <SID> is a 3 character SID which is unique and meaningful within your landscape. For the Web Application Servers that are connected to this BI platform system we recommend to follow the naming convention:

<SID>_WAS<x> where <SID> is the same SID as chosen for the BI platform system and <x> is either empty or one digit per separate Web Application System. Only if this naming convention is followed it is possible to get BO specific checks for the Web Application Systems included within the BO systems EarlyWatchAlert report. For enabling EarlyWatchAlert in addition a product system has to be defined within Solution Manager for the BI platform system with the same name as the extended SID of the BI platform system.

3. Installation or upgrade of Wily introscope

---------------------------------------------

In order to benefit from BOE instrumentation and dashboards, minimum version of SAP Introscope package is version 9. This version is available on SAP Market Place and should be installed or upgraded as described in SAP Note 797147.

Remark: the entry point for SAP BusinessObjects Enterprise dashboards is console "BOE Overview". Please, note that some of the "BI Platform" dashboards listed on the right side of the screen are relevant only for native instrumentation and might not be available depending on the BOE version.

4. Configuration of Database Monitoring for Customer Databases

--------------------------------------------------------------

In addition to the monitoring of the BOE's database (Central Repository), you can also monitor the source databases for the reports (aka customer databases). Those databases are not linked to a SAP system in Solution Manager and must be configured directly in DBA Cockpit. Refer to SAP Note 1265134 as an entry point for the configuration steps required.

5. Using the setup automation tool

---------------------------------------------------------------

In order to reduce manual effort for the setup steps required to be performed on BO side (on BO cluster hosts or BO web application server hosts) we are providing a setup automation tool. The tool is available for Windows(Windows 32bit and 64bit) and UNIX(Silent mode only). That means it can be used to automate the setup steps required to be performed on Windows and UNIX based hosts running BO server or BO web application components. It currently supports Tomcat only as BO web Application server type. For other web application server types the required setup steps still have to be performed manually following the detailed description steps below.

Please download AC tool from note 1653689 - SolMan 7.1: Managed Sys Setup - BI Platform 4.0. Please check "how to use guide" in the zip file to do the related operation, moreover, it is also possible to use the AC tool for checking the correctness of an already performed setup respective to check which steps have not yet been performed. You can then still decide whether to let the AC tool do the required changes or whether you want to perform them manually following the detailed step descriptions below.

Notice: As the setup steps needed, if you choose to use AC tool for the BOE setup, you need to realize that the tool will modify the data of CMS DB, the content that changed in CMS DB is about the Introscope configruation parameters. More details about the changing you may refer to the following manually configruation step "8. Enable Introscope metric propagation for BO Java based components".

6 Enable SLD support

----------------------

In order to get the BO cluster system as well as the BO web application server system(s) known to Solution Manager it is mandatory to connect them to the Solution Landscape Directory (SLD) used by Solution Manager.

6.1 Enable SLD support for BO cluster

-------------------------------------

**This step can be executed and checked by the attached AC tool attachment(for all Windows and UNIX based BO cluster system hosts).

Please follow the steps below to enable SLD support for BO cluster:

1. Download SAP Host Agent (SAPHOSTAGENT.SAR) from the SAP Software Distribution Center of the SAP Service Marketplace ( http://service.sap.com/swdc).

Log on with your SAP Service Marketplace ID using the URL above. Navigate to "Support Packages and Patches" --> "Browse our Download Catalog" --> "SAP Technology Components" --> SAP HOST AGENT --> "SAP HOST AGENT 7.20". Then select the operating system of the host where you want to install it. Then locate the latest available version (with the highest SP number, typically also the last changed one).

Download the corresponding version of the SAPHOSTAGENT.SAR.

2. Extract SAPHOSTAGENT.SAR by entering the following command:

sapcar -xvf SAPHOSTAGENT.SAR

3. Install SAPHOSTCONTROL by entering the following command:

saphostexec -install

4. Locate the sldreg tool, which is usually located in the following folder:

%Program Files%\SAP\hostctrl\exe

5. Create an SLD key with the following command:

sldreg -configure connect.key

You will be prompted to supply a username, password, host, port, and protocol for connecting to the SLD server.

6. Enter the information requested.

The sldreg tool creates a connect.key file that will automatically be used by sld-ds to push information to SLD server.

6.2 Enable SLD support for Web Application Server

-------------------------------------------------

**This step can be executed and checked by the AC tool (for Tomcat BO web application servers running on Windows and UNIX).

BOE system contains at least one Web Application Server. Tomcat is the WebAs installed by default but more are supported (like IBM WebSphere).

Please refer to SAP Note 1508421 SAP SLD Data Supplier for Apache Tomcat for details.

Please refer to SAP Note 1482727 SAP SLD Data Supplier for IBM WebSphere Application Server for details.

7. Configuration of Introscope Java Agent for BO web application server

-----------------------------------------------------------------------

**This step can be executed and checked by the AC tool (for Tomcat BO web application servers running on Windows and UNIX)

CA Wily Introscope Java agent is a bytecode agent monitoring the Java components of the BOE landscape.

Minimum version of Introscope Java agent required is 8 SP02. Remark: version of the IS Agent must be less or equal to the version of the server (server should be installed or upgraded first).

Java IS agent should only be installed and configured for Java Web Application Server.

If you use Apache Tomcat as BOE Java Web Application Server, detailed installation and configuration procedure is attached to the note 1540591 (see the attachment ISAgentBOE40WebApp.pdf) and note 1438005(see the attachment Introscope_Agent_for_Tomcat.pdf). The agent's name should be formatted like <Host Name>_< TOMCAT_SERVER_PORT> where <HOST_NAME> is the (in lower case!) host name there Apache Tomcat installed on and <TOMCAT_SERVER_PORT> is the Tomcat's server shutdown port as defined in the server.xml file.

If WebSphere is used as BOE Web Application Server, no matter the BOE version is 3.x or 4.x, you should configure Java IS Agent for WebSphere.

Detailed installation and configuration procedure for WebSphere is described in SAP Note 1418638. WebSphere's agent should follow the naming rule <CELL _NAME>_<NODE_NAME>_<APP_SERVER_NAME>.

There

<CELL_NAME> - the name of the WebSphere CELL, like diagp010Cell01

<NODE_NAME> - the name of WebSphere Node of the application server

<APP_SERVER_NAME> -name of WebSphere application server

BOE instrumentation should be used by Java IS agent following the note 1540591. The brief procedure is as below:

You should append string "sap_boe_webapp.jar" in the property introscope.autoprobe.directivesFile of file "<IntroscopeAgent>.profile". The profile name which is used depends on the web application server type and is specified in the JVM startup parameters of the web application server.

If the host name where the web application server is running on is not completely in lower case you also need to specify explicitly the host name in lower case within the introscope agent profile used for the web application server by adding the line:

introscope.agent.hostName=<lower case HOST_NAME>.

8. Enable Introscope metric propagation for BO Java based components

---------------------------------------------------------------------


This step may have been already performed during the BOE installation. If you find the following settings already present you have nothing to do - otherwise adjust them as recommended here:

Open the BOE CMC management console (URL: http:<boewebapphost>:<port>/BOE/CMC) and choose "Servers->Nodes". Right click on "Nodes" and per node select "Placeholders".

Make sure that the following entries are present with the following values:

%IntroscopeAgentEnableInstrumentation% = true

%IntroscopeAgentEnterpriseManagerHost% = <Your EM's host>

%IntroscopeAgentEnterpriseManagerPort% = <Your EM's port>

%IntroscopeAgentEnterpriseManagerTransport% = TCP

The BOBJ server system also is running several Java processes which are using a introscope Java agent with their own introscope agent profile. These profiles are built based on a template file and automatically customized per BOBJ server process type. For any BOBJ system node running on a host with a host name that is not completely in lower case you have to also add the same parameter (introscope.agent.hostName=<lower case HOST_NAME>) to the introscope profile template file on each affected BOBJ system host. The introscope profile template file is located under the BOBJ installation in the directory:

On Windows:

<drive>:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\IntroscopeAgent.template

On Unix:

../sap_bobj/enterprise_xi40/java/wily/IntroscopeAgent.template

9. Enable Introscope metric propagation for C++ based components

----------------------------------------------------------------


This step may have been already performed during the BOE installation. If you find the following settings already present you have nothing to do - otherwise adjust them as recommended here:

Open the BOE CMC management console (URL: http:<boewebapphost>:<port>/BOE/CMC) and choose "Servers->Nodes". Right click on "Nodes" and per node select "Placeholders".

Make sure that the following entries are present with the following values:

%NCSInstrumentLevelThreshold% = 10

%SMDAgentHost% = localhost

%SMDAgentPort% = 6404

10. Enable Saposcol process monitoring

-------------------------------------

**This step can be executed and checked by the attached AC tool attachment(for all Windows and UNIX based BO cluster system or BO web application server hosts).

Download and unzip the attachment "SAP_BOE4_procmon.zip". On Windows OS, copy the file "SAP_BOE4_Win_procmon.ini" under the directory <drive>:\usr\sap\PRFCLOG\procmon\ (drive used by SAPOscol). On Unix OS, copy the file "SAP_BOE4_Unix_procmon.ini" under the directory /usr/sap/tmp/procmon/. This file configures the list of processes that must be monitored (cpu & memory) by saposcol (SAP Operating System Collector). Remark: depending on the saposcol configuration, the default folders indicated above might change. More information regarding SAPHOSTAGENT and process monitoring with SAPOSCOL are available from SAP notes 1031096 and 790639. After the files have been properly copied, you must restart saposcol (SAPHOSTAGENT), then the SMD agent.

11. Replace CMS.lst for BOE4

----------------------------------------------------------


Get the latest cms.lst file from the attachment, and replace the old one under the installation path of BOE:

on Windows:<BOE installation directory>\conf\lst

Typical path on Windows:

D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf\lst

12. Edit SapAgentConfig.xml in solman for BOE 4.1 (only for solman lower than SP9)

----------------------------------------------------------

For BI 4.1, the setup activity ‘SAPHotsAgent’ is adding the action bo40.dump_kpis into “SAPAgentConfig.xml” file only starting with SolMan SP9. With a lower SolMan SP you have to add this manually to your file.

Check the content of AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> ‘SAPAgentConfig.xml’-> Scope = SMD Agent of the BOE System -> Download.

command: bo40.dump_kpis -> longsid has to be set to the right value “<LONGSID>” and

prefix must be: “BOBJ ENTERPRISE|<ShortSID>”

Example for <LONGSID> = T45_BOE:

<action prefix="BOBJ ENTERPRISE|T45" name="boe4_kpis_T45" class="com.sap.smd.wily.hostagent.action.RemoteOsCommandAction" period="3600000">

<property name="commandkey" value="bo40.dump_kpis" />

<property name="longsid" value="T45_BOE" />

</action>

13. Update commands.xml for BOE in solman (for solman lower than SP11)

----------------------------------------------------------

please replace commands.xml with the new file attached in the note. Solution Manager -> AgentAdministration -> Applications Config -> com.sap.smd.agent.application.remoteos -> Application resources -> commands.xml.

Upload the new file to each SMD Agent of your BOE system and then restart SMD agent.

If you encounter an issue with commands.xml on UNIX, please refer to note: 1809048 - SolMan scripts failing for BI Platform on UNIX

14. 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.

Further information:

---------------------

For troubleshooting issues with BOE managed system setup also refer to SAP note 1722874.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

Attachments

1849781 Missing RCA Extractor for BOE 4.1 in Solman7.1 before SP13

1809048 SolMan scripts failing for BI Platform on UNIX

1646341 EarlyWatch Alert for SAP BusinessObjects IDD / EIM

1558756 Solution Manager 7.1 - BI Monitoring: Prerequisites

1540591 Wily Introscope Setup for SAP BOE 4.0

File Name File Size (KB) Mime Type

cms_lst.zip 255 application/x-zip-compressed

BOE4_scripts.zip 139 application/x-zip-compressed

SAP_BOE4_procmon.zip 1020 application/x-zip-compressed

commands.zip 14 application/x-zip-compressed

Documents

0001975394