SMSETUP ManagedSystemSetupofBOE4.0systeminSolman7.1 251115 0909 1450

7/23/2019 SMSETUP ManagedSystemSetupofBOE4.0systeminSolman7.1 251115 0909 1450

http://slidepdf.com/reader/full/smsetup-managedsystemsetupofboe40systeminsolman71-251115-0909-1450 1/38

Managed System Setup of BOE 4.0 system in Solman 7.1

Contents

Installation of Diagnostics Agent on all hostsAuto configure using AC tool*Report BOE SLD data to SLD

*Report BOE Web Application Server SLD data to SLDCheck the Technical System for BOE in LMDBManaged System setup for BOE 4.0Managed System setup for Web Application Server with BOE 4.0 Web Application

Apache TomcatIBM WebSphereOracle WebLogicSAP J2EE Server

Setup of the BOE Database systemWily Introscope setup for BOE 4.0Thread Dump Analysis Supportability

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

**if you want to set up the configuration for Explorer servers, just follow the steps as BOE. You may meet some issues like "Explorer Servers are

not showing up correctly in Solution Manager managed systems configuration"

Please check note 2040930 - SAP BusinesObjects Business Intlligence 4.1 Explorer Services do not show up correctly in Solution Manager.managed system configuration

this issue is fixed in: ( )not including the Explorer installation standalone scenario

BI_4.1_Patch2.9BI_4.1_Patch4.2BI_4.1_SP05BI_4.1_Patch3.5

For troubleshooting on RCA for BOE, please refer to SAP Note 1722874- Troubleshooting Solution Manager Root Cause Analysis for BOE

Installation of Diagnostics Agent on all hosts

If not already done so, SAP Host Control and a Diagnostics Agent needs to be installed on all hosts where BOE is installed.

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

Auto configure using AC tool

Please go through SAP Note , and follow the steps in this note to download the latest version of AC tool1653689

Before executing the run_actool.bat file. We need to maintain the properties file in the conf file.

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1653689

https://service.sap.com/sap/support/notes/1975394

https://css.wdf.sap.corp/sap/support/notes/2040930


https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?iv_language=E&param=69765F6D6F64653D3030312669765F7361706E6F7465735F6B65793D303132303033313436393030303030333037373932303132267361702D6C616E67756167653D452669765F6C616E67756167653D45

http://service.sap.com/sap/support/notes/1833501

https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3136353336383926

https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3136353336383926

http://service.sap.com/sap/support/notes/1833501

https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?iv_language=E&param=69765F6D6F64653D3030312669765F7361706E6F7465735F6B65793D303132303033313436393030303030333037373932303132267361702D6C616E67756167653D452669765F6C616E67756167653D45



https://service.sap.com/sap/support/notes/1975394




Enter the conf file and choose the boe.properties file.I choose sublime 3 as the editor of the boe.properties.

"boe.home" is the root installation of Boe system.Eg. UNIX: /usr/sap/<SID>adm/sap_bobj ; Windows C:\programFiles(x86)\SAPBusinessObjectsPlease pay attention to use the different separators in different operation system.You can leave it empty when you are in Windows, the value would be found by Actool from registry.

"boe.system" is the CMS host name of target BOE nodeEg. Localhost, cmshost:7400,@clustername.

"boe.user" is the CMS user account(Need Administrator Role)

"boe.password" the password of the account you entered

"boe.os.user"# On UNUX, as user to restart boe and/or tomcat and also for setting any added/touched configuration file owner.# On Windows, for JMX jmxremote.password file read-only for this user.

Following picture is an example for how to finish it.

"unix.shell"ou should manually check whether this sh shell path or link exists in your running UNIX system or you should provide a valid sh or bash shell path



or link.

"download.folder"The folder is under the AC root folder <AC_APP_DIR>/downloads and it is default set with value empty.If you keep it empty, it would be set automatically by ACTool.

These parameters are about SLD Server information.

"sld.connectkey.replace"If the parameter "sld.connectkey.replace" is true, it will overwirte the existing connect.keyfile with the information you provide.For these four parameters host,port,user,password what you should do is just enter your own sld server 's information.Pay attention that the sld.server.port shall be range [80,443,1024…65535] and the parameter sld.server.https is a boolean value, type y or n forusing https or not.

This is a sample and you need to provide your own information.

"boe.sld.manualtransfer"This parameter is default true.And this parameter is for manually triggering to transfer BOE xml to sld server once or not.

You can see detail information in Note 1653689 Step 6.1 - Enable SLD support.h

This parameter is for enable introscope for Java components.And thease settings will apply to all SIA node. If you have different settings for different nodes, you should change them manually in CMC.And here is a sample.

These two parameters are both about tomcat.Tomcat service name is used as BOE web application server. And the default BOE installed value is always set as "BOEXI40Tomcat" the port isalways set as "8080".

"tomcat.home" is tomcat install path and it only used for linux operation system.<INSTALL_DIR>/tomcat or <INSTALL_DIR> both works for the parameter tomcat.home.



"tomcat.running.mode.WindowService" is a parameter with boolean value.If you choose true tomcat will run as a windows service.

Choose http or https for this parameter depends on your own system.

These two parameters are paths for the tomcat startup/shutdown shell script.Make sure that your user boe.os.user which defined by JAVA_HOME can run these scripts.If tomcat is default one, you should leave these parameters empty. Otherwise, Manually change the path where scripts exists.

"wily.javaagent.install"If you choose wily.javaagent.install true, it will install a new wily agent in the install folder no matter it is installed or not, else it will try to find ainstalled agent in it.

"wily.javaagent.installfolder"

Recommend use /usr/sap/ccms as wily install folder in UNIX and c:\usr\sap\ccms for windows. Meanwhile, keep wily.javaagent.folder empty asthe setup package of agent is already embedded in actool package.

Provide host and port information of your enterprise manager.6001 is a default number of EM port and you can change it to meet your demands.This is an example for these two parameters.

Set your JMX user and password.

"solman.version"This is the version of the solution manager you used.It should be one of "sp3" "sp4" "sp5" "sp6" "others".

This is the install path of smdagent.If you have multiple SMDAgent, use comma to split the paths.

Eg. /usr/sap/<$DASID>/SMDA<$Instance Number>,/usr/sap/<$DASID>/SMDA<$Instance Number>

This is long SID name for Tomcat technical system. Recommended value is <$SID>_WAS, where <$SID> is the first three character of ATCtechnical system.

This parameter is for option to trigger manual transfer tomcat xml to sld server once or not.You 'd better not touch this.



These parameters are used to monitor the managed system for solution manager.Once Thread dump analysis is enabled, these information is needed."jvmond.install.path" is install path for jre and the port is default set 1099 if there is no other application use this port.

"console.verbose"When silent mode is set, if this parameter is set false, all console output will be disable. However, you can still find all the same log in log files.

"boe.node.restart"Default no to touch this parameter.If you would like to restart your boe after setting up, make sure you has already specify the parameter boe.os.user as boe node running user.

"virtualHostName"

If you don't specify this parameter, it will automatically get physic/logic host name.

" "boe.service.nameIf you are using linux operating system, keep it as default or empty.When you are in Windows operating system, find your service in your Windows service list.As usual, the default Boe 's service is set like BOEXI40SIA<HostName>.

"smdagent.windows.servicename"This parameter is only used in Windows operating system.You should find smdagent.windows .servicename in the service list.This parameter is usually set as SAP${INSTANCE}_${Number} like SAPDAA_98.

"smdagent.restart"If you set false here then you should restart smdagent manually.

When you finished maintaining all the parameters, you can execute Actool to finish the set up session.

Just following the steps and then everything would be done in few seconds.

http://boe.service.name/

http://boe.service.name/



Then Please restart tomcat server.

*Report BOE SLD data to SLD

this step can be done by AC tool

In order to setup managed system for BOE 4.0 system in Solution Manager 7.1, you need to report BOE 4.0 SLD data through SLD data supplierto SLD. You can find detailed introduction step by step in the “Post Installation” section in BOE 4.0 installation guide.

*Report BOE Web Application Server SLD data to SLD

this step can be done by AC tool if the web application server is tomcat

You also need to configure the Web Application Server where your BOE Web Applications are deployed as managed system in SolutionManager. For different Web Application server, please refer to below notes.

Tomcat: Note 1508421 - SAP SLD Data Supplier for Apache Tomcat

WebSPhere: Note 1482727 - SAP SLD Data Supplier for IBM WebSPhere Application Server

Extended SID for Web Application System which is connected to the BOBJ System shall has following naming convention:

<SID>_WAS (e.g. BOP_WAS)

(<SID> must be identical to the SID chosen for the BOBJ system. If there are multiple Web Application Server systems connected to the sameBOBJ system (e.g. for load balancing, scale out) then they shall be numbered like <SID>_WAS, <SID>_WAS1, <SID>_WAS2, … The extenedSID has only 8 chars, so there is only one char for the “numbering”.)

1) For Tomcat and WebSphere systems the extended SID can be defined in the SLD DS customization. See the Tomcat/WebSphere SLD DSsetup documenation (notes: 1508421, 1482727) – by adding the line in thecom.sap.sup.admin.sldsupplier.SYSTEM_ID = <SID>_WASproperty file sldDataSupplier.properties of the SLD DS web application.

Another choice is to modify the extended SID in technical system editor.

2) For SAP J2EE Systems the SID and extended SID are defined by the SLD DS of the SAP J2EE automatically and should not be changed.That means that for the BOBJ System that same SID needs to be taken in order to get both systems consolidated in one EWA report.

Check the Technical System for BOE in LMDB

As long as Solman sync the landscape data from SLD to LMDB, you can find the auto created technical system for BOE in Solman.

In Solution Manager Work Center, go to SAP Solution Manager: Configuration. In the Technical System list, find out the technical system for BOE.The auto created BOE technical system will use the first character from BOE cluster name as the technical system name. Then you can go totechnical system editor to check the integrity of technical system data.



In technical system editor, you are able to set the extended SID. Please make sure it applies the following naming convention pattern:

<SID>_BOE (e.g. BOP_BOE) – The <SID> is a 3 character system ID that is determined by the SID of the connected SAP J2EE system (in casethe BO Web Applications are deployed on a SAP J2EE) or in case Tomcat or WebSphere is used can be chosen by the customer(and setidentical in the Tomcat/WebShere SLD DS customizing).

The default extended SID is from the SLD data supplier which is the first 3 chars of the BO cluster name (which itself by default is built like <fullqualified hostname>:<port>). The extended SID is then built in Solution Manager (LMDB) from the SID by either taking the same name or makingit unique by adding a number filling to 8 chars (e.g. SID=BOP, extended SID=BOP if no other BOP already exists or BOP00001 if already a BOPextended SID exists). This name is typically not very meaningfull why we recommend to change it in the Technical System Editor. This has to bedone only once and the customer shall follow the naming convention above and can choose a SID that is meaningful for him.

Make sure the product version list here are set with diagnostic flag.



Go to the software node in the tree left hand, check whether the product instances are listed according to your BOE system installation. Makesure the “Diagnostic Relevant” flags are set properly and make sure each Product Version has the corresponding Software Component Versionslisted below. If you recieve an error stating that there is no diagnostic template, make sure you have only selected those product instances thatare diagnostics relevant. For a list of diagnostic relevant product instances for SBOP BI PLATFORM 4.0, refer to Maintenance of Product in the

.System Landscape#SAPBusinessObjectsEnterprise

Go to Technical Instance node, check the application servers name, host, type and pathes. Make sure each Server has corresponding SoftwareComponent Version listed below.

http://wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape#MaintenanceofProductintheSystemLandscape-SAPBusinessObjectsEnterprise






Then switch to Central Management Servers, check the CMS server name, host and pathes.

Then go to Host node, make sure proper host info has been listed here. Missing host data can cause managed system setup failure.



Managed System setup for BOE 4.0

Select the Technical System for BOE, and then click Configure System.



There are 10 steps for setting up the managed system for BOE 4.0. Just some steps are critical for us.



In the first step, we should configure the for this technical system. You can find the assigned productProduct System and logical component

system is empty, click "Display Technical System Software" to jump to Technical System Editor.

** in newer solman SPs, you can use the "create automatically" option for product system creation.



In the Technical System Editor, change to "Edit" mode first then click "Assign to Product System" button.

If you are using SAP Solution Manager 7.1 , the button "Assign to Product System" is not availableAttention! lower than support package 5

because the technical system editor does not include product system maintenance. In SP4 and lower, product systems have to be

. So in that case, define the product system there and continue .maintained in transaction SMSY here



In the popup dialog, input the Product System name with naming convention <SID>_BOE, for this example, VMW_BOE. Click "Create" to createthis product system.



Then installed product instances are listed, click those with (SMP) ending instances, in this example, check "Enterprise Servers(SMP)" box asassigned and then close the dialog.

Click the root node of Navigation Tree, select Product Systems Tab and check the created product system is there. If it is correct, save and close



to leave the Technical System Editor.

Then create logical component for your BOE system.

** For solman lower than sp9, logical compoent is created in SMSY rather than LMDB.

** If product version of " is not available in SMSY when you create loigcal component, implement SAP Note 1891049.SBOP BI Platform 4."

"Specifically the following steps need to be implemented:Step A - Download SBOP_BI_PLATFORM_41.zip attached to SAP Note 1603103. The archives contain the required XML files.Step B - Call the report RS_SMSY_PPMS_XML_UP_DOWNLOAD with the option Upload = 'X'. Select the XML file that you just downloaded from

the note, and load the required data into your system.Go to transaction SE38, enter the report name “RS_SMSY_PPMS_XML_UP_DOWNLOAD” and choose to execute the program. On the nextscreen enter “X” for upload, and then select “All Products”, “Download All Components” and hit Execute. Select the downloaded xml file“SBOP_BI_PLATFORM_41.xml” and then you should find the products / components uploaded successfully – check details in the logs. Return toSMSY and create the Logical Component – you should now find the appropriate product in SMSY and Logical Component creation will be asuccess. If the data is still not there immediately after the upload, please wait some time to get the data synchronized to SMSY internally in thesystem."

For solman from sp9, logical component is created in LDMB as the following screenshot.



Choose the system role. choose the product instance that the logical component is assigned. (in our case, SMP)

In our case, we use a logical component that is already created before. if you don't have one, create a new logical component.



After creating the product system and logical component in step1, this step is green.



Second step is critical. First we need to go to edit mode, then execute all prerequisites checks. Make sure the prerequisites return green result.The errors here may mostly related to missing diagnostic flag setting for the technical system or other technical system setup issue, you mayneed to go back to the technical system editor to fix it.

Push next.

In step three, you need to assign a Diagnostic Agent to the managed system. In most case it will assign an Agent to you automatically, otherwiseyou can switch to SLD Agent Candidates and choose an agent from SLD. Make sure the agent is running well.



Push next.

In step 4, at least you need to input the Common Parameters. Select an Introscope EM. If you do not have a Load Balancer for your BOEinstallation, then the host should be the host where you install your web application server, and the port number should be the http port for yourweb application server.

And you need to enter the boe credentials as below. make sure the boe user has the admin access.

Push next.

In Step 5, LMDB already enters the parameter for you. You need to make sure the Install Path and Log Path are correct configured by LMDB.



Push next.

Step 6 is also critical, you click the Execute All. In our case, the status for Extractor Setup and Introscope Host Adapter are interested for us.

Make sure the results for them are green.



Push next.

In step 7, nothing to do, go ahead to next step.

Push next. the step 8 in the screenshot is no longer available in newer solman SPs

In step 9, mark configuration check and push Execute All. Check the log. Make sure you can pass the Configuration Check.



Push next.

In last step 10, check the Status of the different setup steps you performed. The managed system setup complete.

Managed System setup for Web Application Server with BOE 4.0 Web

Application

Apache Tomcat

For detail please refer to wiki: Managed System Setup of Apache Tomcat System in Solman 7.1

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Apache+Tomcat+System+in+Solman+7.1

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Apache+Tomcat+System+in+Solman+7.1



As the SLD data for Tomcat Server has been reported by SLD data supplier, you can find the auto-created technical system for web applicationservers in Solution Manager.

There are also 10 steps for managed system setup. Some of them are critical for us.

The first step is to select product. If "Assigned Product System" is empty, click "Display Technical System Software" goto Technical SystemEditor.

In the Technical System Editor, change to "Edit" mode first, then click "Assign to Product System" button.

Input the Product system name with naming convention <SID>_WAS, for this example VMW_WAS and then click "Create" button.



Check all product instances as assigned.



Save the changes and close the Technical System Editor.



Click "Refresh" button to see product system is assigned.Push next.



The second step is critical for us. In this step, we check the prerequisites by switch to edit mode and execute all.



Check the log if there is any error message.



Click the show to see the detail error info and then fix the problem, make sure you the check result are green.

Push next.

In step 3, we assign the Diagnostic Agent to technical system.



Push next.

In step4, we enter system parameter.

Push next.

In step 5, we enter landscape parameters by switch to edit mode. Here is a parameter “BOWA Log Path” which always has to be set manually. Itis the directory where BOE web application logs are written to and by default is the home directory of the user that runs the web application server(on Windows and with Tomcat this typically c:).

On Windows:



On Unix:



Push next.

In step 6, switch to edit mode, and then execute all automatic activities. Make sure the status of Extractor Setup and Introscope Host

.Adapter are green



Push next.

In step 7, go ahead to next step.

Push next.

In step 8, go ahead to next step.



Push next.

In step 9, click Execute All. Make sure you can pass the Configuration Check.

Push next.

In last step 10, the status of all steps is displayed for you. The managed system setup completed.



IBM WebSphere

For detail please refer to wiki: Managed System Setup of IBM WebSphere in Solman 7.1

Oracle WebLogic

For detail please refer to wiki: Managed System Setup of Oracle WebLogic in Solman 7.1

SAP J2EE Server

TBD.

Setup of the BOE Database system

For detail refer to wiki: How to perform the Database configuration for BOE 4.0 and 4.1 in Solman 7.10

Wily Introscope setup for BOE 4.0

Please refer to Note 1540591 - Wily Introscope Setup for SAP BOE 4.0

Make sure the Agent profile is configured correctly when you setup Wily Agent for the Web Application Server where BOE Web App is deployed.

Find the line of directive file configuration in the <IntroscopeAgent>.profile. This file is in Wily Agent folder, default it is /usr/sap/ccms/wily :introscope.autoprobe.directivesFile=…Append the “sap_boe_webapp.jar” in this line if it hasn't beed appended, and .make sure no "sap_bo_enterprise.jar" in this lineintroscope.autoprobe.directivesFile=…,sap_boe_webapp.jar

Note:1. You should remove the pre-configured sap_bo_enterprise.jar in directives file configuration "introscope.autoprobe.directivesFile". It can notcoexist with sap_boe_webapp.jar here. That file is for BOE 3.x version.2. Starting with release 8.2.4.x and all 9.x releases of the EM, the Management Module for BOBJ (SAP_BOBJ.jar) get installed to folder <EMfolder>/sap/extra_modules.You need to copy the jar files to the deployment folder of the EM <EM folder>/deploy. More detail can be found in SAPNote 1579474.

3.If you are using the edition after solution manager 4.1 sp05. Metrics in Wily Introscope might incomplete because the edition of you ISagent(Java agent) is not proper.

To solve this problem, you should to update your IS agent upper than 9.5.6.1 including 9.5.6.1(eg. 9.5.6.1 & 9.7.1). You can download the latestversion of Isagent from SMP or you can use ACtool to re-setup your IS Agent. Please refer Note 2209163 for detail information about thisproblem.

If you want to download the latest IS agent you can refer Note 1438005.

Thread Dump Analysis Supportability

Thread Dump Analysis for Java instances of BOE Server is supported.Please refer to Note 1608714 for the configuration details.

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+IBM+WebSphere+in+Solman+7.1

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Oracle+WebLogic+in+Solman+7.1

http://wiki.scn.sap.com/wiki/x/z5BsGQ



http://wiki.scn.sap.com/wiki/x/z5BsGQ

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Oracle+WebLogic+in+Solman+7.1

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+IBM+WebSphere+in+Solman+7.1

SMSETUP ManagedSystemSetupofBOE4.0systeminSolman7.1 251115 0909 1450

Documents

Transcript of SMSETUP ManagedSystemSetupofBOE4.0systeminSolman7.1 251115 0909 1450