by Prakash Palani (Prakash.Palani@basisondemand.com)

A BasisOnDemand.com Guide

MANAGED SYSTEM SETUP GUIDE FOR SBOP BI PLATFORM 4.0 Helps you to setup the Managed System Setup for BI Platform

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 2 - P a g e

Table of Contents

Introduction .......................................................................................................................................... 3 1.

Step 1 - Transfer Tomcat Web App details to SLD ................................................................................ 3 2.

3. Step 2 - Transfer BOE Data to SLD ........................................................................................................ 6

4. Managed System Setup ........................................................................................................................ 7

5. Step 3 - Logical component setup ....................................................................................................... 11

6. Step 4 - Solution Creation ................................................................................................................... 14

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 3 - P a g e

Introduction 1.

There are too many blogs available in the web which helps to perform “Managed System Setup for Business Objects BI Platform”, when I attempted to configure the same for the first time, those blogs were really helpful, but I could see many of the most important tips/steps were missed out which made me to write this article for the benefit of the people who are yet to configure root cause analysis setup for SBOP BI. This article describes the step involved in transferring Tomcat and BOE data to SLD and managed system setup for BOE, it does not contain information about SMD Agents/any other pre-configuration steps and the managed system setup for Tomcat Web App server. High Level Steps :

1. Refer OSS Note : 1653689, 1722874, 1508421 2. Transfer Tomcat Web App and Business Objects details to the SLD which is connected to LMDB

of Solution Manager 3. Adjust the Extended SID according to the rules mentioned in 1653689 4. Perform Managed System Setup for BOE 5. Create Logical Components 6. Create Solution

Step 1 - Transfer Tomcat Web App details to SLD 2.

Download the TomcatSLDDataSupplierWEB.zip application from OSS Note 1508421 and extract it to local directory

2.1. Enable Manager Role in TomCat Application if not enabled already

Open tomcat-users.xml from tomcat installation directory (i.e. e:\business objects\tomcat55\conf)

Add roles “manager” and “admin”

Adjust the file like the above one, then restart the tomcat service

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 4 - P a g e

2.2. Deploy the SLDDS Application using Tomcat Manager Page

Open Tomcat Manager Page by calling http://<hostname>:<portusedbytomcat>/manager/html

Use the “WAR file to deploy” option to deploy the downloaded war file downloaded from 1508421 Select the file and press Deploy button. Once deployed, you will see an additional application called TomcatSLDDataSupplierWEB in the manager page (refer the below screenshot).

2.3. Send Data to SLD

Next step is to transfer the data using the SLDDataSupplier application which was deployed in the

previous step, in order to perform the data transfer, create the connect.key file to generate a file with SLD related information such as (user, host, port, pwd, etc.,)

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 5 - P a g e

2.4. Adjust the Tomcat SLDDS control file to send the data to SLD

Open sldDataSupplier.properties (if the file is not found in the below mentioned directory, then copy sldDataSupplier.properties.template to sldDataSupplier)

Below are the important parameters to be entered in the ds supplier properties file.

Once the connect.key and sldds properties files are created start the SLDDS application from Tomcat manager page as mentioned below.

During the application start, the information about the Tomcat server will be sent to SLD (using the connect.key and the XML file generated by the application), the same will also reflect under the LMDB/Managed System Configuration page.

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 6 - P a g e

Tips : If you don’t see the managed system definition in the solution manager even after performing the steps above, you have two options to force the data transfer.

1. Check whether the XML is properly generated by the SLDDS application – by Calling - http://<Host>:<Port>/sap.com~TomcatSLDDataSupplierWEB/sldsupplier

a. Transfer the data manually : http://<Host>:<Port>/sap.com~TomcatSLDDataSupplierWEB/sldsupplier?action=sldSupplier

2. If the XML is generated but not transferred to SLD then a. Transfer the data using manual step by calling - > sldreg -connectfile

<pathtoconnectkeyfile>\connect.key <WORKING_DIR>\<filegname>.xml (generated by SLDDS)

As I already described, as we are done with the data supplier for Tomcat, we need to perform similar steps to transfer the BI Platform Details (such as SIA, Processing Server, Adaptive Server, CMC, etc.,) to SLD.

3. Step 2 - Transfer BOE Data to SLD

Generally the BI Platform specific details will be automatically transferred to SLD destination if the connect.key file is created and stored in the location where hostctrl program is located. (i.e. c:\program files\sap\hostctrl\exe\). If the file does not exist in the location specified, generate it using the command sldreg –configure connect.key. You can verify the logs from the <BOEInstallDirectory>\java\lib\bobj-sld-ds\bobjsldds.log. You must be able to locate the logfile as well as the XML (SIA_<hostname>_bobjslddsoutput.xml) file which is used by the sldreg to transfer the BI Platform specific data. If the data is not automatically transferred by the BI Platform, then you can use the below command to manually transfer the data. But if you use these options, you may have to perform it again whenever there is a change in BOE. (i.e. Additional Job Server, etc.,)

1. Transfer the data using manual step by calling -> sldreg –connectfile <pathtoconnectkeyfile>\connect.key <BOEInstalldirectory>\java\lib\SIA_<hostname>_bobjslddsoutput.xml

2. According to SAP notes, the BOE SID should be named as <SID>_BOE, you may adjust it in the solution manager system, once it is available there.

We are now done with the data transfer to SLD, the next steps are something similar as we do for other products such as ERP, NW, etc.,

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 7 - P a g e

4. Managed System Setup

SOLMAN_SETUP -> Managed System Configuration -> Choose BOE system and Configure System

If you find the system status as red, then open “Display Technical System Software” and adjust the product system definitions (like below screenshot). Mark the relevant software components as Installed and Diagnostics Relevant in Edit Mode.

Make sure you have all the necessary information under Software, Technical Instances and Hosts.

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 8 - P a g e

Check Pre-requisites

This step verifies the minimum requirement for the managed system setup.

Assign Diagnostic Agent installed on the BOE host.

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 9 - P a g e

Enter System Parameters Load Balancer Host (Tomcat App Server Host) Load Balancer Port (Tomcat Port (i.e. 8080) CMS System (i.e. hostname:6400) User : Administrator User Pwd : <password>

ni

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 10 - P a g e

Landscape Parameter You may have to adjust the parameter if needed, but in most of the cases all the required parameters will be automatically captured by the BOE SLD transfer.

Configure Automatic Steps

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 11 - P a g e

Create Logical Components As we are dealing with non-ABAP system, you must create logical component using the SMSY transaction.

5. Step 3 - Logical component setup

To assign logical components, we must have a valid product system defined in SMSY, proceed as mentioned below to configure the product system and the logical component.

5.1. Define the Product System

Verify whether you have a valid technical system under Technical System.

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 12 - P a g e

If the technical system is found, then create a product system manually.

Assign the technical system to the product system that got created in the last step Choose all the relevant product instances by selecting “Relevant” and “Technical System” flags, in addition to that, assign G37_BOE under Technical System and mark the system type as “BO Cluster”

Next step is to create a logical component for the product system G37_BOE.

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 13 - P a g e

Create New Logical Component

Assign the product system under the relevant layer of your landscape.

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 14 - P a g e

6. Step 4 - Solution Creation

SOLMAN_WORKCENTER - > Solution Manager Administration - > Solutions

New

Guide to perform “Managed System Setup for BO BI Platform”

www.basisondemand.com 15 - P a g e

Assign the Landscape Component to newly created solution; this will help to get your EWAs generated for the BOE system. Rather than detailing out in a text form, I have attempted to give the screenshots as much as possible; I hope that this article is informative and useful for the consultants who are yet to play around with the “Managed System Setup for Business Objects BI Platform”.