SAP Solution Manager Monitoring - BusinessObjects (BOBJ) BI 4

Linh Nguyen ITConductor.com 1

SAP Solution Manager Monitoring Setup

BusinessObjects (BOBJ) BI Platform 4.0Published: 25 August 2015

Linh Nguyen

IntroductionA common SAP technology stack for Business Intelligence that we often come across in the field has been SAP Business Warehouse (BW) backend as the enterprise data warehouse platform, with a BusinessObjects (BOBJ) Business Intelligence (BI) reporting application. Performance testing, monitoring and tuning in such environment requires the setup of tools that will monitor the BOBJ as well as the BW system. This has to be part of any performance and availability management project involving the environment described above. This comprehensive guide originated from our 3-parts blog, which we will detail the setup for monitoring BOBJ in Solman 7.1:• Part 1 documents the various Preparation steps in order to allow the

Solution Manager and the Managed System to communicate with each other via the Diagnostics Agent.

• Part 2 we will look at the Auto-Configure tool for BOBJ.• Part 3 we will perform the Managed System Configuration inside Solman.

Solution Manager Technical Monitoring

SAP BusinessObjects Business Intelligence platform 4.0

Monitoring Setup

Part 1 of 3

Installation of Diagnostics AgentBy OZSoft Consulting for ITConductor.com

Installation of Diagnostics Agent• Download Diagnostic Agent

• In order to install and setup the Diagnostics Agent and the SAP Host Agent, you must first download the required files from the Service Market Place.

• Go to http://service.sap.com/sltoolset → Software Logistics Toolset 1.0

• Go to http://service.sap.com/sltoolset → download Kernelreleases delivered for SL Toolset → Kernel forinstallation/SWPM → SAP KERNEL 7.21 EXT 64-BIT UC

• Please refer to SAP Note 1833501 - Diagnostics Agent Installer Versions.

Installation of Diagnostics Agent

Installation of Diagnostics Agent• After downloading the file, extract the SWPM and Kernel

files using the SAPCAR executable on the BOE server.

• Run with Administrator in extract folder sapinst.exe

Installation of Diagnostics Agent• Choose the installation type «Install – Diagnostic Agent» and

click on "Next".

• Enter a 3-character SID for the Diagnostics Agent (usually SMD or DAA), select the disk drive where the agent will be installed

• Enter the hostname of the BOE server if not show automatic

• Choose a password for SAP System Administrator and SAP System Service User.

• SAP recommended that you choose Local Domain (local installation) for the diagnostics agent users

• A pop up will ask you to add the Diagnostics Agent to the trusted users. Click "Yes" to continue.

• Enter the password for SAP System Administrator again.

• Enter the connection parameters to the SLD. Use the SLD hostname and port of the Solution manager, use SLDDSUSER as username, and enter the password.

• Enter a system number for the Diagnostics Agent. This number must be unique for this installation host.

• Enter the full hostname for Solution Manager, SCS Message Server Port (81<SCS instance number>), SMD_AGT as user (created in System Preparation in SOLMAN_SETUP), and password for SMD_AGT.

• Select "Configureconnection via Java SCS Message Server"

Installation of Diagnostics Agent• Verify the installation

parameters are correct

• Unpack the archive

• You should see a pop up saying the installation has completed.

• Make sure the installation finishes without error.

• Open the management Console and verify the SAP diagnostics instance has a green status.

General Information

• Following documents are most relevant for installing and working with the Diagnostics Agent:

Refer to SAP Note 1365123 for the Diagnostics Agent installation strategy.

Refer to SAP Note 1833501 for information on Diagnostics Agent installer versions, and for an overview of SAP Notes related to Mass Deployment / Unattended Installation.

Refer to SAP Note 1858920 and the latest Installation and Setup Guide

Next – Auto configure using AC tool

• Now that we have established connection between SAP Solution Manager and the Diagnostics Agent, we need performed configuration on SAP BusinessObjects Business Intelligence platform 4.0 for connect to Solution Manager, which is the next section that we’ll examine.

Monitoring Setup

Part 2 of 3Auto configure using AC tool

By OZSoft Consulting for ITConductor.com

• Latest up to date information for SAP BOE 4.0 is available in SAP Note 1653689 - SolMan 7.1: Managed Sys Setup - BI Platform 4.0

• Latest up to date information for SAP BOE 4.1 is available in SAP Note 1975394 - SolMan 7.1: Managed Sys Setup - BI Platform 4.1

• Please go through SAP Note 1653689, and follow the steps in this note to download AC tool

• To download AutoConfigure tool. please refer to AC-Tool central note 2137275.

Download AC Tool

• Unzip download file to BO server

• Download file from SAP.

Run AutoConfigure.exe• Run

AutoConfigure.exe on Windows

• You need to install Java on the server, or to check the environment variables

Run AutoConfigure.exe

• Set System environment variables JAVA_HOME

• Run from console

Started AutoConfigure.exe

• Select the first nine steps and click on "Execute Selected“.

• Select BI Platform 4.x and “Confirm”

Enable SLD support for BO cluster

• Enter sld server info (hostname, port, user, password)

• Select Tomcat Service as BOE WAS

• Click on "No" for the HTTPS usage (In my case, my SLD uses HTTP).

Enable SLD support for BO cluster

• Click on "Yes" when you are asked to trigger SLD transfer.

• Check the status of the task "Enable SLD Support".

Enable Introscope for Java components

• Select the task "Enable Introscope for Java components" and click on "Execute Selected".

• Key in the hostname for the Central Management Server (CMS) host follow by the port number. Enter the username and password for the Central Management Console (CMC). Click "OK" to continue.

• Key in "True" for the "IntroscopeAgentEnableInstrumentation"

• Key in Wily IntroscopeWorkstation hostname andport number for"IntroscopeAgentEnterpriseManagerHost" andIntroscopeAgentEnterpriseManagerPort", and key in theWily Introscope Workstation protocol type for"IntroscopeAgentEnterpriseManagerTransport".

• A message box should show up telling you the BOE Node has been detected and asking to restart the BOE SIA Node manually. DO NOT RESTART THE NODE NOW.

• Check that the "Enable Introscope for Java components" task executed successfully.

Enable Introscope for C++ components

• Select the task "Enable Introscope for C++ components" and click on "Execute Selected".

• Key in the NCS Parameter. Enter 10 for NCSInstrumentLevelThreshold, "localhost" for SMDAgentHost, and 6404 for SMDAgentPort.

Enable Introscope for C++ components

• Check that the "Enable Introscope for C++ components" task executed successfully..

Enable Saposcol process monitoring

• Select the task "Enable Saposcol process monitoring" and click on "Execute Selected".

• Check that the "Enable Saposcol process monitoring" task executed successfully.

Configure step of BOE 4.0(SP level lower than SP3)

• Select the task "Configure step of BOE 4.0(SP level lower than SP3)" and click on "Execute Selected".

• Check that the "Configure step of BOE 4.0(SP level lower than SP3)" task executed successfully.

Replace cms.lst for BOE4

• Select the task "Replace cms.lst for BOE4" and click on "Execute Selected".

• Check that the "Replace cms.lst for BOE4" task executed successfully.

Required Software on Business Intelligence 4.X system

• Select the task "Required Software on Business Intelligance4.X system" and click on "Execute Selected".

• If your Solution Manager is higher than 7.1 sp6, choose "Other"

• Check that the "Required Software on Business Intelligance 4.X system" task executed successfully.

Enable CSJNI

• Select the task “Enable CSJNI – Update configurations of cs.cfg" and click on "Execute Selected".

• Step 8 finished with error, Run in console for determine errors….

Enable CSJNI

• Under <BOE installationpath>\dataAccess\connectionServer

Check the cs.cfg file the content exists like the screen shot show.

Enable CSJNI

• The file cs.cfg has been copied from another server. After that, steps 8 and 9 were completed without error.

Enable TDA Service

• Select the task “Enable TDA service” and click on "Execute Selected".

• Enter the jvmmond port and password.

Enable TDA Service

• Then a pop-up dialog will come out to state some message.

• After the above stepss, the configuration for BOE on host side is done.

• Restart BOE to make the changes take effect.

Enable TDA Service

• Check that the "Enable TDA service" task executed successfully.

Tomcat – pre-check the agent dll file version

• Select the task “Tomcat – pre-check the agent dll file version” and click on "Execute Selected".

• This step was used to judge whether the dll file under the wily agent install path is the right version for tomcat to avoid the workload performance, more details refer to the Note: 1273028

Tomcat – pre-check the agent dll file version

• Enter the wily agent install path where exists the dll file: for example C:\usr\ccms\wily\ext for different wily agent's version. (By the way, this step should be run while have java agent installed on, if not, run the step after 12th step, if yes and in boe.properties file for the option "wily.javaagent.install" the value is set to false which means not to install a new java agent, then this step should be run at first.)

Tomcat – Install Introscope Agent

• Download the latest Intorscope Agent installation files. Download the latest CA Introscope Agent for Javamanual installation package from the SAP ServiceMarketplace. Please refer to the SAP note 797147 formore information.

• Extract Introscope Agent files

• To install the CA Introscope Agent please extract theinstallation .SAR package on the Tomcat host.

cd /usr/sap/ccms

SAPCAR –xvf ISAGENT.9.1.5*.SAR

• SAP recommends the installation into thedirectory /usr/sap/ccms/wily.

• Check that the Agent’s files are properly extracted. Make sure that the /wily sub-directory exists inthespecified folder.

• Add following Java VM parameters to run IntroscopeJava Agent with Tomcat JVM:

• Restart Tomcat. The Introscope Agent will shortly startsending performance data to the configured EnterpriseManager

• Look for the agent log files in the <AGENT_HOME>/logsfolder. Check that a log file for the Introscope Agent exists.

• Check that the "Tomcat – Install Introscope Agent" task executed successfully.

Configure JVM GC log

• Select the task "Configure JVM GC log" and click on "Execute Selected".

• Click on "No" when you are asked to restart Tomcat now.• Check that the "Configure JVM GC log" task executed

successfully.

Check Tomcat logging

• Select the task "Check Tomcat logging" and click on "Execute Selected".

• Click "Yes" to restart Tomcat now.

• Check that the "Check Tomcat logging" task executed successfully.

Install and run SLD Data Supplier

• Select the task "Install and run SLD Data Supplier" and click on "Execute Selected".

• On the "Found SLD War File" message window, click on "Keep it" to continue.

Install and run SLD Data Supplier

• Check that the "Install and run SLD Data Supplier" task executed successfully.

Enable TDA for Tomcat

• Select the task “Enable TDA for Tomcat" and click on "Execute Selected".

• Select a tomcat service

• Enter the jvmmond port and password should be the same with step "Enable TDA for BOE"

Enable TDA for Tomcat

• Two message dialogs come out to state the final status. Click OK.

• After the above steps for tomcat, restart the tomcat server.

Start Jvmmond.exe as OS service

• Select the task “Start Jvmmond.exe as OS service" and click on "Execute Selected".

• Select a folder with JRE installed. Be sure this folder haveJRE installed. e.g. \usr\sap\DAA\SMD98\exe\sapjvm_6\bin

• Enter the jvmmond port and password should be the same with step "Enable TDA for BOE"

• Then an install frame come out, do the install process then a service named " JvmmondByACTool" will show in the services list of windows. For security, this service is not started, and it's Startup Type is Manual. Start it and change the Startup Type into Automatic if needed.

Final status for ACTool

• Final status for ACTool configuration process like the following screen shot

Next – Managed System Setup of BOE 4.0 system in Solman 7.1• Now that we have performed configuration on SAP

BusinessObjects Business Intelligence platform 4.0 for connection to Solution Manager, next we will configure Solution Manager to monitor the scenario

Monitoring Setup

Part 3 of 3Managed System Configuration

By OZSoft Consulting for ITConductor.com

• If all steps are performed in parts 1 and 2 without errors, there should be 2 new BOE systems available

Managed System Configuration BOE 4.0

• SOLMAN_SETUP: Configure the technical system with or without Service Delivery/EWA (EarlyWatch).

1. Assign Product: SBOP BI PLATFORM 4.0

2. Check Prerequisites: Execute All Automatic Activities

3. Assign Diagnostics Agent

4. Enter System Parameters: BOE login details

5. Enter Landscape Parameters

6. Finalize Configuration:

• Automatic Activities – Execute All

• Manual Activities – Set status to Manually Performed for all

7. Check Configuration:

8. Check Complete

• Configuration and System Status should be green

Full Configuration Incl. Service Delivery/EWA (EarlyWatch).

Managed System Configuration BOE_WAS

1. Assign Product

• Assign logical component

1. Assign Product

• Assign logical component

3. Assign Diagnostics Agent

4. Enter System Parameters

5. Enter Landscape Parameters

• Manual Activities – Set status to Manually Performed for all

7. Check Configuration:

8. Check Complete

Technical Monitoring Configuration – BOE, BOE_WAS.

1. Overview: Setup Monitoring, Alerting and reporting

5. Define Scope

6. Setup Monitoring

7. Reporting

8. Complete

Technical Monitoring Demo – BOE, BOE_WAS.

SAP Solution Manager Monitoring Setup

BusinessObjects (BOBJ) BI Platform 4.0

SummaryThe technical monitoring setup is lengthy, yet it only scratches the surface. We are using default thresholds out-of-the-box, so typically in your environment you would need to plan another phase to configure thresholds, notifications and any downstream integration such as service desk functionality. For best practices, we recommend those to be done over a period of time with actual learning from the behavior of actual systems in use, typically with some representative test or production workload. Managing alerts, thresholds and notifications is normally an iterative process, however there must be at least a general service level defined for IT operations to implement the policies and procedures which address overall performance and availability objective of the environment.IMPORTANT: note that Solman 7.1 does not show the details of the alerts in the inbox, and still requires one to navigate to the managed system to troubleshoot the alerts (without time-sensitive context because one still has to find the alert/event, if it still exists in the managed system when one performs the analysis). Alerts in Solmanare a form of aggregation on events or metrics. It is still very hard to find the root-cause or context of the problem or do any kind of correlation!If you have additional environment such as SAP BPC (Business Planning & Consolidation) either with SAP Netweaver or Microsoft platform, there's many more configuration to be done to set up Solution Manager to monitor them.

About IT-ConductorIT-CONDUCTOR HEADQUARTER Email: info@itconductor.com20660 Stevens Creek Blvd., Suite 261 Worldwide: +1 (408) 416-2565Cupertino, CA 95014. USA North America Toll-free: +1 (888) 666-2899

http://www.itconductor.com

Company> Stop Guessing, Start Managing!IT-Conductor is the AMMO you need to:

• Automate

• Monitor• Manage &

• Optimize your SAP Performance & Operations.

IT-Conductor was officially founded in 2014 after more than 10 years of turning a big idea of automating IT into a practical solution. The big idea is to enable customers to "Stop Guessing, and Start Managing" their enterprise IT application environment. It's all about the integrated ability to collect vast amount of application and supporting infrastructure instrumentation data into standardized and time-synchronized intelligence that can be action upon.

> Monitor SAP WITHOUT Installation!The power of IT-Conductor lies in it's ease of access through a cloud platform to simply hook up to your environment via a secured connection and start agentlessly monitor and manage the applications, databases, hosts and related infrastructure components. Templates make application discovery fast and easy to go from monitoring to managing in minutes!

___________________________________________________________________________________________________________________________________________

© 2015 IT-Conductor, Inc. and/or its affiliates. All rights reserved. IT-Conductor is a trademark of IT-Conductor, Inc. or its affiliates. This publication may not be reproduced or distributed in any form without IT-Conductor’s prior written permission. If you are authorized to access this publication, your use of it is subject to the Terms of Service and Copyright and Trademarks posted on itconductor.com. The information contained in this publication has been obtained from sources believed to be reliable or from IT-Conductor’s own experience and research. IT-Conductor disclaims all warranties as to the accuracy, completeness or adequacy of such information and shall have no liability for errors, omissions or inadequacies in such information. This publication consists of the opinions of IT-Conductor organization and should not be construed as statements of fact. The opinions expressed herein are subject to change without notice. Although IT-Conductor may include a discussion of related legal issues, IT-Conductor does not provide legal advice or services and its research should not be construed or used as such.

SAP Solution Manager Monitoring - BusinessObjects (BOBJ) BI 4

Documents

Accenture POV - SAP BI and BOBJ 081408 for Clients

SAP #BOBJ #BI 4.1 Upgrade Webcast Series 12: Monitoring

Mastering SAP Monitoring - BusinessObjects (BOBJ) Monitoring

SAP BusinessObjects BI Platform 4 - BR3 Consultants · SAP BusinessObjects BI Platform 4.2 Supported Platforms ... Analysis edition for OLAP and BI LaunchPad on SAP NW Portal

SAP BusinessObjects Implementation - Visual BI Solutions

Introduzione a BUSINESSOBJECTSintranet.izsler.it/UserFiles/File/Bobj/BusinessObjects...Introduzione a BusinessObjects La riproduzione e la trasmissione, anche solo parziale, del software

SAP BusinessObjects BI Platform for Cloud Vendors

SAP #BOBJ #BI 4.1 Upgrade Webcast Series 7: Upgrade Process: Moving from BusinessObjects XI Release 2/3.1 and 4.0 to BI 4.1

One Strategy for Enterprise BI BusinessObjects BI... · 2013-05-16 · Features by product areas SAP BusinessObjects BI platform yCore BI platform ySelf-service access to SAP BusinessObjects

SAP BusinessObjects BI platform 4.1 Architecture · SAP BusinessObjects BI platform infrastructure SAP BusinessObjects BI platform 4.1 Architecture Information Design Tool (UNX) Business

SAP® BusinessObjects™ EdgE BI cOn IntEgrAcIón dE … BusinessObjects Edge BI with Data... · 4 sap® Businessobjects™ edge Bi es la opción de Business intelligence (Bi) para

Support For BEx Query Elements in BOBJ BI Dec 2012.pdf

SAP BusinessObjects BI Platform11

SAP BusinessObjects BI: новые ... - sapvod.edgesuite.netsapvod.edgesuite.net/rusapforummoscow/2015/pdfs/2_Makoed_BI... · SAP BusinessObjects BI: новые возможности

Rolta SmartMigrate for BI (BOBJ) March 2015

SAP Fiori with SAP BusinessObjects BI Launchpad

BOBJ (SAP BI) APS Spliting Best Pra

SOLUTION SHEET SAP BusinessObjects BI

SAP BusinessObjects BI 4.1 What's New L1

SAP BusinessObjects BI 4.1 Supported Platforms (PAM)