Skip to end of metadata
Go to start of metadata

Contents

Latest up to date information for SAP BOE 3.x is available in SAP Note 1648370.

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

Create a technical system in Solution Manager 7.1 for BOE 3.x

In Solution Manager 7.1 the technical system will be created by technical system editor, no longer SMSY.

Go to SolMan Admin Workcenter, then click Landscape:

Create Empty Technical System

Press menu System Operations, click Create System in the dropdown list.

Then the technical system will be created in Technical System Editor. In Technical System Type Selection, Select Unspecific Cluster System (UNSPECIFIC).

Push Next and Enter System Name.

The BOE system has following naming convention. The <SID> is a 3 character system ID that is determined by the SID of the connected SAP J2EE system (in case the BO Web Applications are deployed on a SAP J2EE) or in case Tomcat or WebSphere is used can be chosen by the customer.

     - <SID>_BOE for the Business Objects Cluster component  (e.g. B32_BOE) 
     - <SID>_WAS for the Web Application Server (WebAs) component (e.g. B32_WAS)

Enter Technology Type from dropdown list as SBOP Enterprise 3.1.
Host – if the host is already know you get a suggestion, otherwise just enter the host name.

Then Push next.

Enter extended System ID as <SID>_BOE and push save:

Then the steps of “Technical System Editor – Create System” complete.

The UI of “Technical System Editor – Editor” shows up. The first step is to define header data, as the required information has been provided in previous steps, push next. Go to assign Database.

Push Assign Database System: Select the right database system. If the DB is not yet there you can create it.

Push next: Define technical Instances.

Then push Add. The technical instance represents a physical deployment of BOE server. For example, if you have a BOE cluster system which deploys BOE servers on host 1 and host2, then you need to add two technical instances for two hosts.

Enter the instance name as:  BOE_<host>. Note: in below example, we create a technical instance BOE_diagp001, because the host name is diagp001.
Choose the technology type as: “SBOP enterprise 3.1”.
Host = <host> and push ‘OK’

You now have the Instance here:

It is strongly recommended to enter the Installation Path now, otherwise it has to be entered in managed system setup step 5. For this case, it is "c:\Program Files(x86)\Business Objects\BusinessObjects Enterprise 12.0\".

Push save and next.

Maintain assigned Software – Add product instance

Then push Add.

In the pop-up add “BOBJ ENTERPRISE XI 3.1” as Search term and push ‘Search’. This step help you narrow down the Product Instances in a short list where you can easily select proper ones.

Then all Product instances that contain “BOBJ ENTERPRISE XI 3.1” are listed.

Select the Product Instances listed in below table in “Product Instance – Query Result List”. Push ‘CTRL’ button to add more than one at a time.

Product Installed

Product Instance

Diagnostics Relevant

Installed

true

BOBJ ENTERPRISE XI 3.1: ADAPTIVE JOB SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: ADAPTIVE PROCESSING SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: CENTRAL MANAGEMENT SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: CONNECTION SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: CRYSTAL REPORTS SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: DESKTOP INTELLIGENCE SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: EVENT SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: INPUT FILE REPOSITORY SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: JOB SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: MULTIDIMENSIONAL ANALY. SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: OUTPUT FILE REPOSITORY SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: REPORT APPLICATION SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: SERVER INTELLIGENCE AGENT

true

true

true

BOBJ ENTERPRISE XI 3.1: WEB APP CONTAINER SERVER

false

true

true

BOBJ ENTERPRISE XI 3.1: WEB INTELLIGENCE SERVER

true

true

true

BOBJ ENTERPRISE XI 3.1: Enterprise (SMP)

false

true

true

SBOP EXPLORER XI 3.2: Exploration Server

true

true

true

SBOP EXPLORER XI 3.2: Index Server

true

true

true

SBOP EXPLORER XI 3.2: Master Server

true

true

true

SBOP EXPLORER XI 3.2: Search Server

true

true

true

SBOP EXPLORER XI 3.2: Explorer (SMP)

false

true

* In case you install SBOP Explorer with BOBJ Enterprise, you can add product instances for SBOP Explorer.

Note: please select the Product Instances to your technical system based on your deployment landscape. For example, you have a complex deployment landscape, where BOE_PROD1 only contains CMS, Adaptive Job Server, Adaptive Processing Server; BOE_PROD2 contains Crystal Reports Servers; BOE_PROD3 contains Web Intelligence Servers. You can configure specific Product Instances for BOE_PROD1, BOE_PROD2 and BOE_PROD3 respectively.

Push ‘Add’ button to add the selected Product instances.

Check status message in the pop-up. It should be displayed as “Selected Product Instances have been assigned to System” with green check.

Now you have the Product instances as below. Check them and push ‘Save’. Installed flag and Diagnostics flag should be set automatically.

Maintain assigned Software – Add Software Component Versions

Under Product instances tab, click one product instance added in the previous step, you can find its related software components below and their installed checkbox are empty.

 

 Click each checkbox one by one or use "Select All", "Set Flags" functions to set installed flag on for all software components of that product instance.

Then switch to "Software Component Versions", confirm the selected software component are assigned here.

Go back to tab "Product Instances", set installed flag on for all the software components of all the product instances recursively. Now you shall have all Software components added, check them and push "Save".

Below is a table that contains the mapping from Product Instance to Software Component Version. You can check the software component assigned.

Product Instance

Software Component Versions

BOBJ ENTERPRISE XI 3.1: ADAPTIVE JOB SERVER

ADAPTIVE JOB SERVER 3.1

BOBJ ENTERPRISE XI 3.1: ADAPTIVE PROCESSING SERVER

ADAPTIVE PROCESSING SERVER 3.1

BOBJ ENTERPRISE XI 3.1: CENTRAL MANAGEMENT SERVER

CENTRAL MANAGEMENT SERVER 3.1

BOBJ ENTERPRISE XI 3.1: CONNECTION SERVER

CONNECTION SERVER 3.1

BOBJ ENTERPRISE XI 3.1: CRYSTAL REPORTS SERVER

CRYSTAL REPORTS CACHE SERV 3.1
LIST OF VALUES JOB SERVER 3.1
CRYSTAL REPORTS PAGE SERV 3.1
CRYSTAL REPORTS JOB SERVER 3.1

BOBJ ENTERPRISE XI 3.1: DESKTOP INTELLIGENCE SERVER

DESKTOP INTEL.CACHE SERVER 3.1
DESKTOP INTEL.REPORT SERV 3.1
DESKTOP INTEL.JOB SERVER 3.1

BOBJ ENTERPRISE XI 3.1: EVENT SERVER

EVENT SERVER 3.1

BOBJ ENTERPRISE XI 3.1: INPUT FILE REPOSITORY SERVER

INPUT FILE REPOSITORY SER 3.1

BOBJ ENTERPRISE XI 3.1: JOB SERVER

PROGRAM JOB SERVER 3.1
PUBLISHING JOB SERVER 3.1
DESTINATION JOB SERVER 3.1

BOBJ ENTERPRISE XI 3.1: MULTIDIMENSIONAL ANALY. SERVER

MULTIDIMENSIONAL ANAL. SER 3.1

BOBJ ENTERPRISE XI 3.1: OUTPUT FILE REPOSITORY SERVER

OUTPUT FILE REPOSITORY SER 3.1

BOBJ ENTERPRISE XI 3.1: REPORT APPLICATION SERVER

REPORT APPLICATION SERVER 3.1

BOBJ ENTERPRISE XI 3.1: SERVER INTELLIGENCE AGENT

SERVER INTELLIGENCE AGENT 3.1

BOBJ ENTERPRISE XI 3.1: WEB APP CONTAINER SERVER

WEB APP CONTAINER SERVER 3.1

BOBJ ENTERPRISE XI 3.1: WEB INTELLIGENCE SERVER

WEB INTEL. REPORT SERVER 3.1

BOBJ ENTERPRISE XI 3.1: Enterprise (SMP)

BOBJ ENTERPRISE XI 3.1

SBOP EXPLORER XI 3.2: Exploration Server

SBOP EXPLORATION SERVER XI 3.2

SBOP EXPLORER XI 3.2: Index Server

SBOP INDEXING SERVER XI 3.2

SBOP EXPLORER XI 3.2: Master Server

SBOP MASTER SERVER XI 3.2

SBOP EXPLORER XI 3.2: Search Server

SBOP SEARCH SERVER XI 3.2

SBOP EXPLORER XI 3.2: Explorer (SMP)

SBOP EXPLORER XI 3.2

* In case you install SBOP Explorer with BOBJ Enterprise, you can add product instances for SBOP Explorer.
 

Creation of the technical system is finished, push Close:
 

You can find the system now in the list of technical systems if you perform a refresh.

Definition of the technical system is now finished.

Managed System setup for BOE 3.x

Switch to Solution Manager Configuration, find your technical system in Technical Systems tab. Note: You can click filter and input your long system id in “Technical Systems” column to find it quickly.

Select the system and then push ‘Configure System’.

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

In the first step,  column "Assigned Product Systems of the Technical System" is empty means no product system is assigned, click "Edit Technical System Software".

In Technical System Editor, change to "Edit" mode, click "Assign to Product System" to assign the product system.

** "Assign to Product System" button is a new feature from Solution Manager 7.1 SP5. If the SP level lower than SP5, please still use SMSY to create the product system.

In the popup dialog, input product system name with naming convention <SID>_BOE and click "Create" button.
 
Select those "(SMP)" ending product instances, check their "Assign..." box on, then close this dialog.
 

Save and close Technical System Editor.

 

Click "Refresh" button and check the assigned product system is available.

Note: Please make sure product instance and software component version are maintained correctly before step 2.
 
The second step is checking prerequisites.

 
 
Second step is critical. First we need to go to edit mode, then execute all prerequisites checks. Make sure the prerequisites return green result (Especially for the managed system, in this case, the first line in the log, "Managed system B32_BOE~UNSPECIFIC fulfills the Diagnostics prerequisites" must 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 may need to go back to the technical system editor to fix it.

For any error here, push ‘show’ in the Details column to check the log.

e.g.:

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. Make sure the agent is running well.

If the agent is not yet assigned push ‘Agent Admin’. Check if the agent is visible. Otherwise push ‘Agent Candidates Management’.

Select the agent that is known to your SLD and push Attach. Enter the credentials for the user and push ‘Apply’.

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 BOE installation, then the host should be the host where you install your web application server, and the port number should be the http port for your web application server.

Push next.

In Step 5, Enter Landscape Parameters. Check the value for the installation Patch, correct it and push ‘Save’. (If the instance's Installation Path has already been input in the step 3 "Define Technical Instances" in Technical System Editor, it shall be identical here)

Check the log:

Push next.

Step 6 is also critical. Mark Extractor Setup and push Execute Selected.

Wait until the background job is finished and check the result in the log:

Log example:

Select Introscope Host Adapter and push Execute Selected:

Push Next.

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

Push Next.

In step 8, Activity is automatically done when you push next again.

Push Next.

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

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

Report BOE Web Application Server SLD data to SLD

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

Tomcat:

  • Note 1508421 - SAP SLD Data Supplier for Apache Tomcat
  • Note 1608645 - SAP SLD data supplier support for BOE 3.1 Webapp on Tomcat

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

For Tomcat and WebSphere systems, the extended SID can be defined in the SLD DS customization. See Tomcat/WebSphere SLD DS setup documentation (notes: 1508421, 1482727) – by adding the line com.sap.sup.admin.sldsupplier.SYSTEM_ID = <SID>_WAS in the property file sldDataSupplier.properties of the SLD DS web application. Otherwise, you can modify the extended SID in Technical System Editor later.

The naming convention for Web Application Server:

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

Check the Technical System for BOE Web Application in LMDB

As long as Solman sync the landscape data from SLD to LMDB, you can find the auto created technical system for BOE Web Application 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 Web Application. The auto created BOE Web Application technical system will use the first character from host name as the technical system name. Then you can go to technical system editor to check the integrity of technical system data.

In technical system editor, please check the Extended System ID, make sure it applies the naming convention for web application server in the style of <SID>_WAS. The ID "DIA" in the screenshot is not a good one, shall be changed to B32_WAS according to previous case.

Also make sure the product version list here is 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. Make sure the “Diagnostic Related” flags are set properly. And make sure each Produtc Version has corresponding Software Component Versions listed below.

Note: In our environment, we install BOE Explorer within BOE, so the Web Gateway is listed here. If you only install BOE Web Application, you will not see this item.

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 Web Application Server with BOE 3.x Web Application

As the SLD data for Web Application Server has been reported by SLD data supplier, you can find the auto-created technical system for web application servers 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. For SAP J2EE engine, you have to add product instance manually by clicking "Edit Technical System Software".

Then need to assign product system, in "Edit" mode, click "Edit Technical System Software" button.

 

Click "Assign to Product System" button in Technical System Editor.

Input the product system name using naming convention <SID>_WAS, then click "Create" button.
 
 
Click all instances as Assigned.

 
 
Save and close.

 
 
Refresh and check the 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.

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.
 

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.

Enter the configuration extraction properties

There are few manual steps for defining the parameter for the remoteos agent application in agent framework. Go to agent framework from work center, then Solution Manager Administration -> Infrastructure -> Agent Framework.

In Agent Framework, select All Agents.

Select tab Applications Configurations, and then on the left pane select agent application “com.sap.smd.agent.application.remoteos”. Select the scope corresponding to the host where BOE platform is installed, click Edit. Add below properties. Then save.

PROPERTY NAME

Description

ENV_SID_<SID>_BOE_AUTH_TYPE

The authorization type for CMS logon

ENV_SID_<SID>_BOE_CMS

CMS connection string: <CMS host>:<CMS port>

ENV_SID_<SID>_BOE_CMS_USR

CMS user with read access to the CMS

ENV_SID_<SID>_BOE_CMS_PWD

Password for CMS user

ENV_SID_<SID>_BOE_DIR

BOE installation directory
Windows example: c:\Program Files\SAP BusinessObjects
Unix example: /usr/BOE/sap_bobj



Then on the left pane select agent application 'com.sap.smd.agent.application.filesystem". Select the scope corresponding to the host where BOE platform is installed, check whether the install path of BOE and the Web Application Server have been set correctly for variable “smd.file-landscape_root_direxctories”. In case its value not set or incorrect, click Edit and update the value, then save.

  • No labels