Setting Up BEx in SAP-BI70

Created by Sumit Kothiyal Web BeX BI

SAP NetWeaver 2004s: Setting up BEx Web and Problem Analysis

Author: Sumit Kothiyal

Date Written: 20/03/2009

Declaration:

I hereby declare that this document is based on my personal experiences and / or experiences of my project members. To the best of my knowledge, this document does not contain any material that infringes the copyrights of any other individual or organization including the customers of Infosys.

Sumit Kothiyal

Project Details

Project code: NHRBWSEZ S/W Environment: Windows, Unix. Appln. Type: SAP BI BeX Analyzer Project Type : Production Support, SAP BI Upgrade

Target Readers:

SAP Basis Support, SAP BW Administrator.

Keywords: SAP BeX Analyzer.

This short document contains all screenshots required for the setting up BEx Web and steps to perform for the BeX setup.

Status Overview

Report RSPOR_SETUP (transaction SE38) or through SPRO as below:


Click on execute and you will see the below screen:


Make sure check configuration is checked and then press execute:


Apply the following two notes before you check the configuration with report RSPOR_SETUP:

• 916571 RSPOR_SETUP: Adjustments for Template Installer • 928332 RSPOR_SETUP: (Part 2) Adjustments for Template

Installer


Press button Overview and click on the marked third line to download the complete output of report RSPOR_SETUP to a text file

(If the third line is not marked, please apply note 935177)

If there any failed step (marked red). Search for notes with error message.

Step 1 Create RFC Destination in J2EE Engine

SAP J2EE Visual Administrator (\usr\sap\<PORTAL_SID>\JC<SYSTEM_NUMBER>\j2ee\admin\go.bat)

<SID> / Server<#> / Services / Jco RFC Provider / RFC Destination

Program ID: Gateway host:

SAP Router string might be required for Gateway host

Gateway service: (3300; sapgw is defined in :\windows\system32\drivers\etc\services or /etc/services)

Number of processes (1..20):

Application server host:

SAP Router string might be required for Application server host

System number: Client: Language: User: Password:

The icon “Running man” must be visible in the list of “Available RFC Destinations” next to the name of Program ID


Checks for Step 1 - Create RFC Destination in J2EE Engine

Check existence of RFC Destination on J2EE-EngineThe existence of the RFC Destination on J2EE-Engine could not be checked directly.

It could be checked, if the RFC connection in step 2 could be established.

Validation check for SAP BI User and Password

No check with password <...>.

Step 2 Create RFC Destination for Portal

Transaction in BI System Display and Maintenance of RFC Destinations (SM59) / TCP/IP

Connection

Screenshot of register Technical Settings (Gateway Host and Gateway service must be visible on screenshot)

Screenshot of Logon & Security Program ID, Gateway Host and Gateway Service must be identical

to Step 1 Send SAP Logon Ticket must be checked on

Name of RFC destination: Connection type:


Description of RFC destination:

Technical settingsActivation type: Program ID: Gateway host: Gateway service:

Logon/securitySend SAP Logon Ticket : active

Checks for Step 2 - Create RFC Destination for Portal

Check existence of RFC destination Check RFC destination with RFC Call Check Number of registered Processes Check existence of com.sap.ip.bi Java classes Check version information of com.sap.ip.bi Java classes Compare version information of Java support package

(com.sap.ip.bi classes) with ABAP support package (SAP BI)



Step 3 - Maintain Portal Server Settings for Portal

BI Transaction Table View Maintenance (SM30)

Table RSPOR_T_PORTAL / Maintain / New Entries

RFC destination:

System name:

Default: X

URL Prefix:

KM RM Prefix:

KM Service URL:

Checks for Step 3 - Maintain Portal Server Settings for Portal

Compare Domains of URL Prefixes (ABAP and Portal)

Domain of URL Prefix (ABAP):

Domain of URL Prefix (Portal):

Check content of table RSPOR_T_PORTAL

RFC Destination:

Systemname:

Default Portal:

URL Prefix:

KM RM Prefix:

KM Service URL:

Step 4 - Maintain Single Sign-On in BI

Maintain BI Transaction Profile (RZ10)

Select Profile (Not START or DEFAULT) / Enhanced Maintenance / Change

login/create_sso2_ticket: 2

login/accept_sso2_ticket: 1

Checks for Step 4 - Maintain Single Sign-On in BI


Check Profile parameters

Profile parameters are checked automatically.

Step 5 Export BI Certificate into Portal

Trust Manager for Single Sign-On with Logon Ticket (STRUSTSSO2) Select Own Certificate / Menu Certificate / Export

Checks for Step 5 - Export BI Certificate to BI

Check Step 5 with Step 12

Step 5 could implicitly tested with Step 12.


Step 6 Import BI Certificate to Portal

Step 6.1 Import BI Certificate into Portal


<SID> / Server<#> / Services / Key Storage / TicketKeystore / Views / Load

Detailed information of the CERTIFICATE must be identical with screenshot of step 5:Step 6.1 Step 5[DN] Owner[issuerDN] Issuer[validNotBefore] Valid From[validNotAfter] to[fingerprint] Check Sum


Step 6.2 Enter BI Certificate into Evaluate Ticket Login Module


<SID> / Server<#> / Services / Security Provider / Components / ticket / Authentification /com.sap.security.core.server.jaas.EvaluateTicketLoginModule

Name of Login Module must be com.sap.security.core.server.jaas.EvaluateTicketLoginModule

trustedsys1 must be ABAP system ID and client (see status line of screenshot in step 5; (2) indicates only the number of open SAP GUI windows connected to the system)

trustediss1 must be identical with Owner in step 5 trusteddn1 must be identical with Issuer in step 5

Number behind trustedsys, trustediss and trusteddn must be identical

Number must be identical with number in step 6.3 First number must start with 1, than 2, 3 and so on


Step 6.3 Enter BI Certificate into Evaluate Assertion Ticket Login Module


<SID> / Server<#> / Services / Security Provider / Components / ticket / Authentification / com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule

Name of Login Module must be EvaluateAssertionTicketLoginModule See step 6.2 for other checks


Checks for Step 6 - Import BI Certificate to Portal



Step 7 Create BI System in Portal iView in Portal

Portal iView System Administration / System Configuration / System LandscapeContext Menu New / System

Property Category: BI / Business Intelligence Property Category: BI KM / Business Intelligence KM Integration Property Category: Connector Property Category: User Management

Property BI Master System must be selected Property Authentication Ticket Type must be SAP Assertion Ticket Property Logon Method must be SAPLOGONTICKET


Checks for Step 7 - Create BI System in Portal

Check System with Connection Tests Portal iView System Administration / System Configuration / System Landscape Context Menu Object / Connection Test

Note: Connection Test for Connectors requires Step 9 and 10. Otherwise you will retrieve the following message in dev_jrfc.trc: "The system is unable to interpret the SSO ticket received".

Step 8 Configure User Management in Portal

Portal iView System Administration / System Configuration / Configuration for User ManagementTab Page Security Settings

Screenshot of register DataSources Screenshot of register ABAP System Screenshot of register Security Policy settings

(property SAP Reference System must be visible)

Property SAP Reference System (under register Security Settings) must be set (to BI system or to any other SAP system with same users as BI system)


Checks for Step 8 - Configure User Management in Portal

Check Step 8 with Step 12 Step 8 could implicitly tested with Step 12.

Step 9 Export Portal Certificate to Portal



<SID> / Server<#> / Services / Key Storage / Views / TicketKeystore / SAPLogonTicketKeypair-cert / Export

Select SAPLogonTicketKeypair-cert(This allows us to see the values of the certificate, CN=…)

See step 6 for check

Checks for Step 9 - Export Portal Certificate to Portal




Step 10 Import Portal Certificate to BI

Transaction in BI SystemTrust Manager for Single Sign-On with Logon Ticket (STRUSTSSO2)

Double-click on Portal certificate in Certificate List (This allows us to see the values of the certificate, CN=…)

Select Portal SID in Certificate List Select Portal SID in Access Control List (ACL) Portal certificate must be part of Certificate List Double-click on Portal certificate in Certificate List and compare

fields with the detailed information of the CERTIFICATE of certificate SAPLogonTicketKeypair-cert (see step 7):Step 8 Step 7Owner [DN]Issuer [issuerDN]Valid From [validNotBefore]to [validNotAfter]

Portal certificate must be in Access Control List (ACL) Compare fields with

System Portal System ID (default value, if login.ticket_issuer is not existing; see second screenshot below)Cl. (Client) 000 (default value if login.ticket_client is

not changed)Certificate Owner [DN]

For verification of the correct parameters (System ID and Client) in the Access Control List (ACL), please perform the following steps.

Config Tool (see folder \usr\sap\...\JC…\j2ee\configtool; start configtool.bat)

Use default DB settingsCluster-data / Global server configuration / Services / com.sap.security.core.ume.service

• Select key login.ticket_client (if key login.ticket_issuer is existing, please ensure that this key is visible)


Checks for Step 10 - Import Portal Certificate to BI

Check SSO from SAP EP to SAP BI by calling BI iView Use Portal Role Business Explorer to call BI iView BEx Web Analyzer (System Alias SAP_BW is required for Portal Role Business Explorer). You can also call any other BI iView with System Alias SAP_BW.

Step 11 - Set Up Repository Manager for BI in Portal

Portal iView System Administration / System Configuration / Knowledge Management / Content ManagementConfiguration / Content Management / Repository Managers

BI Document RepositoryPrefix (must start with /): /bi_documents (recommended value)Active: XRepository Services: PropertiesSecurity Manager: BWDocumentSecurityManagerShow empty Folder: (off)Show technical Names: (off)Life time Security Cache: 7200Alias of BW System: SAP_BWPrefix of BW Metadata Repository: /bw_metadata

BI Metadata RepositoryPrefix (must start with /): /bw_metadataActive: XRepository Services: PropertiesSecurity Manager: BWMetadataSecurityManagerShow Objects data is received from (off) Show Objects data is sent to: (off


Show usage: (off)Life time Security Cache: 7200 Alias of BI System: SAP_BW

Checks for Step 11 - Set Up Repository Manager for BI in Portal

Check BI Document Repository Manager by viewing document in SAP EP iView KM Content

Call SAP EP iView Content Administration / KM Content.Expand one of the subfolder Documents on InfoProvider Data, Master Data Metadata under folder /bi_documents.If you expand the second level folder, the third level is read dynamically from SAP BI via RFC.

Check BI Metadata Repository Manager by viewing document in SAP EP iView KM Content

Call SAP EP iView Content Administration / KM Content. Expand folder Active Version under folder /bw_metadata. Expand one of the subfolder on the third level. If you expand the third level folder, the fourth level is read dynamically from SAP BI Via RFC

Step 12: Maintain User Assignment in Portal Step

Portal iView User Administration / User Assignment

Checks for Step 12 - Maintain User Assignment in Portal

Check SAP BI and EP UserCheck if SAP EP User is the expected user, i.e. either the identical user id (ignore case) or the mapped user (User Mapping).SAP BI User contains only capital letters. SAP EP User could contain lower and/or upper case letters.

RSWR_RFC_SERVICE_TESTSAP BI User: SAP EP User:

RSWR_RFC_SERVICE_TEST: RSRD_MAP_TO_PORTAL_USERSSAP BI User: SAP EP User:

Compare SAP BI and EP Server TimeDifferent Server Times could be a reason for retrieving always an invalid SAP Logon Ticket.

SAP BI Server Time: SAP EP Server Time:

Check assigned Portal Roles of SAP EP User

Step 13 Security Settings for BEx Web Applications (Java)


iView in PortalSystem Administration / Permissions / Portal PermissionsPortal Content / Content Provided by SAP / Platform Add-Ons / Business Intelligence / iViews / BEx Analyzer

pcd:portal_content/com.sap.pct/platform

• In row Everyone, the column Administrator must be Read and column End User must be checked on

• Icon of Everyone must be the Group icon; column Description must be Built-in Group Everyone

Step 14 - Import SAP NetWeaver Plug-In into BI

http://service.sap.com/swdc / SAP Software Distribution Center / Support Packages and PatchesEntry by Application Group / SAP NetWeaver / SAP NetWeaver '04

Basis Plug-In: 2005_1_700 0016

Checks for Step 14 - Import SAP NetWeaver Plug-In into BI

Check SAP NetWeaver Plug-In Existence and version of SAP NetWeaver Plug-In is checked

automatically.

For general questions, please read note 917950.

For specific communication and Single Sign-On (SSO) problems, please read note 888687.
