SAP Note

Header Data

Symptom

This note describes how to setup BEx Web in SAP NetWeaver 2004s. All required steps are mentioned. Additionally, this note contains a checklist to check the installation and configuration.

Other Terms

Business Explorer, RSPOR_SETUP, BEx Web, Runtime, J2EE, Web Application, BEx Information Broadcasting, RFC, HTTP, HTTPS, ABAP, Java, Single Sign-On, SSO

Reason and Prerequisites

You configure BEx Web and BEx Information Broadcasting in a system landscape with SAP NetWeaver 2004s.

Solution

Overview

l Other References

Frequently Asked Questions (FAQ)

SDN Forum

Learning Map for Consultants

l Definition of Terminology

Usage Types

l Architecture

l Installation (*)

Types of Installation

l Configuration Overview(*)

l Configuration Tools (*)

Template Installer

Report RSPOR_SETUP

l Configuration Checks (*)

l SAP Support Messages (*)

l Additional Information

Topics marked with (*) should be read by everyone who installs, upgrades and configures a SAP NetWeaver 2004s system with Usage Type BI-Java.

917950 - SAP NetWeaver 2004s: Setting Up BEx Web

Version 27 Validity: 07/18/2007 - active Language English (Master)

Released On 07/18/2007 11:16:50 Release Status Released for Customer Component BW-SYS Basis System and Installation

BW-BEX-ET-BC Broadcasting

BW-BEX-ET-RT Query Run Time

BW-BEX-ET-WEB BEx Web ABAP Runtime

BW-BEX-ET-WEB-EP Enterprise Portal Integration

BW-BEX-ET-WEB-RT WEB Run Time

Priority Correction with high priority Category Installation information

Other Components

This note will be frequently updated.

Other References

l Documentation

You can find a detailed description of all required steps in the BI system under transaction SPRO / SAP Reference IMG / SAP Customizing Implementation Guide / SAP NetWeaver / Business Intelligence / ReportingSettings / Web-Based Settings / Integration into the Portal.

l Frequently Asked Questions (FAQ)

You can access a list of frequently asked questions for BI under http://sdn.sap.com / Home / Developer Areas / SAP NetWeaver / Business Intelligence and than Quick Links / SAP BI FAQs (https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/feb70f5d-0701-0010-68a1-f7d46f2cf274). This list is frequently updated.

l SDN Forum

There is a SDN Forum available during Ramp-Up of SAP NetWeaver 2004s under http://sdn.sap.com / Forums / SAP Business Intelligence / SAP NetWeaver 2004s Ramp-Up (https://forums.sdn.sap.com/thread.jspa?forumID=154). You use this forum to place your question and discuss with experts.

Definition of Terminology

SAP introduced new terms with SAP NetWeaver 2004 like IT practices, IT scenarios and Usage Types. Usage types are a new structuring element for SAP software on a technical level. For more information, see SAP Service Marketplace at http://service.sap.com/instguidesNW2004s Usage Types

l AS-ABAP

Contains all ABAP-based SAP WebAS functionality (software components SAP_ABA, SAP_BASIS and SAP_BW)

Data Warehouse Management, OLAP processor, Existing SAP BW 3.5 Web Runtime, ...

Internet Graphics Service (IGS) comprised

l AS-Java

Contains all Java-based SAP WebAS functionality (J2EE)

Adobe Document Services (ADS), Universal Data Integration (UDI) and Metadata Model Repository (MMR) comprised

Universal Data Integration (UDI) is an independent component that is used for data retrieval and does not require Usage Type BI-Java

See note 853572 for additional information about AS-Java

l EP

Contains Portal

Requires Usage Type AS-Java

l BI

Contains BI Content Add-On (software component BI_CONT)

Requires Usage Type AS-ABAP

l BI-Java

Contains all Java- and WebDynpro-based BI functionality

New NW2004s Web Runtime (incl. Analysis Item, Formatted Reporting, Web Printing, PDF Export, ...), new Planning Modeler for BI Integrated Planning, ...

Requires Usage Type EP and AS-Java

See Release Notes under http://help.sap.com/saphelp_nw04s/helpdata/en/index.htm

l BI accelerator

Standalone engine based on TREX

l Search and Classification

Standalone engine based on TREX

BI accelerator and Search and Classification require two different TREX standalone engines

Architecture

As described above, BEx Web in SAP NetWeaver 2004s (Usage Type BI-Java) requires Usage Types EP and ASPortal on a Java stack is required. This Java stack could be installed on the same server or on another server (see Types of Installation for details). BEx Web Runtime and BI Consumer Services (BICS) are implemented in Java and using Portal Runtime functionality. BEx Web Runtime is responsible to generate output for Web Browser and BICS retrieves data from BI Platform and/or UDI. In SAP NetWeaver 2004s, load is moved from AS-ABAP (BI-ABAP) to AS-Java (BI-Java). BI generates load on Portal (ASJava), therefore BI users generate more load on Portal than normal Enterprise Portal users. See note 927530 for additional information about BI-Java sizing. Which functionalities of BEx Web in SAP NetWeaver 2004s are requiring a Portal?

l New BEx Web Application Designer (Unicode, Command Wizard, ...)

l Exporting to PDF and Printing

l Integrated Planning

l Drag&Drop (Analysis Web Item)

l Web Items (Container Layout, Menu Bar, Tab Pages, Button Group, ...)

l Formatted Reporting with BEx Report Designer

l Document Integration with storage in Knowledge Management

l ...

For details, see Release Notes for Usage Type BI-Java under http://help.sap.com/saphelp_nw04s/helpdata/en/index.htm If you don't want to use the new BEx Web functionality, you can still use BEx Web 3.5 Runtime that is running only with Usage Type AS-ABAP.

Installation

Types of Installation As result of your installation or upgrade process, you can have the following system state:

l Application Server ABAP (AS-ABAP with own system ID and instance number)

l Application Server Java (AS-Java with own system ID and instance number)

l Double-Stack (ABAP and Java combined on one server with identical system ID and instance number)

In case of AS-ABAP and AS-Java the ABAP stack and Java stack are separated by system ID (SID) and instance number. But both stacks could be installed together on one server or separately on two different servers.are like different systems. In case of Double-Stack installation, the ABAP stack and Java stack are running as one system on one server. The term Add-In installation describes an installation process - it is not a system state. The result of an Addinstallation is a Double-Stack system (AS-ABAP and AS-Java with on system ID). An Add-In installation allows to install a Java stack to an existing ABAP stack. An Add-In installation of an ABAP stack to an existing Java stack is not possible. Important In case of Add-In installation, the system ID (SID) of AS-ABAP and AS-Java is identical. This causes problems during import and certificates, if you are using the Template Installer. Please see topic Additional Information for details about these settings. Important In case of Add-In installation, the User Management (see Configuration) is automatically set to client 001.If you want to use another client, you have to adjust a few settings. Please see topic Additional Information for details about these settings. See FAQ for details about possible system landscapes. Types of Upgrade

l From SAP EP 6.0 (SAP NetWeaver 2004)

l From SAP BW 3.5 (SAP NetWeaver 2004)

l From SAP BW 3.x

Upgrade from SAP EP 6.0 (SAP NetWeaver 2004) If you upgrade a SAP EP 6.0 Portal with existing System Objects to BW (now BI) systems in the Portal System Landscape, please ensure to maintain the new properties at the System Object (see Additional Information below for details). See FAQ for details about possible system landscapes. See http://service.sap.com/instguidesnw2004s for general installation and upgrade information about SAP NetWeaver 2004s.

Configuration Overview

You can summarize the configuration in three main topics:

1. Communication

2. Single Sign-On (SSO)

3. User Management

You have to setup both directions for communication:

1. Java to ABAP communication

2. ABAP to Java communication

For communication, the RFC/JCo protocol and HTTP(S) web protocol are used. Communication is used to create and display BI content in the Portal. Communication is also be used to display Portal content in BI (e.g. BEx Information Broadcasting shows Knowledge Management folder). See note 888687 for technical details. For Single Sign-On (SSO), you have to ensure that Java and ABAP trust each other:

1. Java is trusting ABAP

2. ABAP is trusting Java

Single Sign-On (SSO) is working with SAP Logon Tickets. SAP Logon Tickets are created with the help of certificates and could be validated with certificates. Therefore, certificates must be exchanged between Java and ABAP.Certificates consist of a public key and optionally of a private key. The private key of certificate is required for creating and signing SAP Logon Tickets. The public key of certificate is used for validating SAP Logon Tickets.SAP Logon Tickets are digitally signed with the private key of the issuing system's certificate. They contain the user ID, authentication scheme, validity period, issuing system and digital signature but they do not contain any passwords. SAP Logon Tickets are validated with the public key of the issuing system's certificate (the public key is located in System PSE or TicketKeystore). They are only accepted if the issuing system is part of Single SignAccess Control List (ACL) or EvaluateTicketLoginModule in the validating system. See note 888687 for additional technical details. User Management could help you to minimize the effort of administrating your user accounts. Common user storage for ABAP and Java is recommended. Several options are available:

1. LDAP Directory (external)

2. ABAP System (as Central User Administration or single system)

3. Java System Database (J2EE, former Portal User Management Engine; double maintenance of user required)

Option 2 is recommended. For Add-In installation, option 2 is automatically set up. See References for details.

Configuration Tool

To configure BI-Java, you should use the Template Installer (template-based automatic configuration). In order to have the latest corrections for the Template Installer available, please use the latest patch of the SCA LMSupport Package Stack. The latest patch can be downloaded from SAP Service Marketplace. How to use this Configuration Tool? At first, use the Template Installer to perform the automatic configuration. In most cases, this templateautomatic configuration is enough to enable BEx Web in SAP NetWeaver 2004s. In a second step, we recommend to use the Java-based Diagnostics & Support Desk Tool (see note 937697)automatically check your configuration. Important Please remember, especially an automatic configration process has its limits. Your system landscape could differ from the standard case. Therefore, it is important to understand the manual steps as performed with the report RSPOR_SETUP. You can find screenshots and additional information about the configuration in the attached file WDEBU7_Setting_up_BEx_Web.zip. The slides are based on the wprkshop "Upgrading to SAP NetWeaver 2004s BI Technical aspects" (WDEBU7).

Template Installer

The Template Installer is installed with Usage Type EP and used for automatic configuration.

l Prerequisites

l System Upgrade and System Copy

l Required Steps

l Data Entry ABAP (BI system)

l Data Entry Java

l Error Messages

l Result

Prerequisites Before you start the Template Installer, please check note 983156 for required prerequisites. You can check the prerequisites for the Template Installer automatically, if you run the report RSPOS_SETUP. See note 1033320 for details. System Upgrade and System Copy In case of a system upgrade or system copy, you might have to adjust the Template Installer (CTC) settings, because these settings contain the previous values that are not valid anymore. Please have a look at the attachment System_Upgrade_Copy.ZIP of this note. Required Steps You can perform the template-based automatic configuration with the following steps:

1. Start SAP NetWeaver Administrator (NWA) with alias /nwa ://:/nwa

2. Logon with user "Administrator"

(In case of Add-In Installation, logon with user "J2EE_ADMIN")

3. Choose Deploy & ChangeTemplate Installer

4. Choose Template "Complete BI PostInstallation" (or "BIPostInstallProcess"; if template is not visible, see note 964988)

5. Press Execute Template

6. Adjust default value under Data Entry (see below)

7. Press Install

If the template BIPostInstallProcess is not existing, please see topic Additional Information. Data Entry ABAP (BI system)

l ABAP Administration User (ABAP_ADMIN and ABAP_PASSWORD)

Used by RFC Destination in J2EE; ABAP user

l Backend System (BACKEND_SYSTEM)

Hostname of ABAP system

l Backend System Number (BACKEND_SYSNUMBER)

System number of ABAP system

l Backend Client (BACKEND_CLIENT)

Client of ABAP system

l Backend HTTP Port (BACKEND_HTTP_PORT)

See profile parameter ms/http_port on ABAP message server or icm/server_port_... on ABAP application server

l Backend System ID (BACKEND_SID)

System ID of ABAP system With SAP NetWeaver 2004s SP6 the following parameters must be specified:

l Backend Server Port (BACKEND_SERVER_PORT)

Message server port; see profile parameter ms/server_port_... on ABAP message server Data Entry Java

l Java Host (J2EE HOST)

Hostname of J2EE

l Java System ID (J2EE SID)

System ID of J2EE

l Java HTTP Port (J2EE HTTP PORT)

http port, 500, e.g. 51000 for system number 10

l P4 Port (P4PORT)

TCP/IP port of Visual Administrator, +4, e.g. 51004 With SAP NetWeaver 2004s SP6 the following parameters must be specified: Java Administration User and Password (USER and PASSWORD) User used during configuration of the Java stack

l WebDynpro JCo User and Password

Used by WebDynpro for Planning Modeller (BI integrated Planning)

l Logon Group

Used by WebDynpro for Planning Modeller (BI integrated Planning) Error Messages In case of a problem, don't get confused by the long error message. Please read the especially the last sentence of the error message. Normally, this last sentence gives a hint what to do. At first, you should check your input parameters. Press button Install to continue the following steps or correct the problem and restart the Template Installer (by starting the SAP NetWeaver Administrator with /nwa again). In general, you can run the Template Installer as many times as required. But it could happen that retrieve error messages due the fact that objects already exist or steps already performed. In this case, you should stop using the Template Installer and continue with the report RSPOR_SETUP (see below). Step 1 For example, the RFC destination could not be created because it is already existing and locked. If the prerequisites regarding SSO are not fulfilled, the error message "Element 'SAPConfigLib.DEP.Unclassified.createRfcDestination': Error during executing Java Reflection:RFC_DESTINATION_ERROR" will appear in step 1. Step 9 If the error message "Application is not authorized to execute keystore operation" or "java.security.AccessControlException: access denied {EnginePermission: [keystore][view:GET_VIEW:TicketKeystore]}" appears, there is a problem regarding missing access rights. You should be able to add them manually:

1. Start Visual Administration

2. Choose Key Storage/Runtime/Security

3. Select "TicketKeystore"

4. Grant "sap.com/tc~lm~ctc~ccl~template_installer~wd/webdynpro/public/lib/sap.com~tc~lm~ctc~ccl~template_installer~wd.jar" to the following actions:

GET_VIEW, CREATE_ENTRY_AT_VIEW, READ_ENTRY, FIND_ALIAS, LIST_ENTRY,VIEW_ALIASES and SIZE_OF_VIEW

Step 10 For example, the certificate could be updated in step 10 (Import Engine Certificate To ABAP). If the Portal certificate is already existing on the ABAP side (see transaction STRUSTSSO2), this is not a problem and you can continue. See topic Additional Information for details about specific issue with Template Installer and Add-In installation. Result The Template Installer setup the communication and Single Sign-On (SSO) between ABAP and Java. It creates RFC Destinations (on ABAP and Java side), exchanges certificates and create a System Object on Portal side. We recommend to use the Java-based Diagnostics & Support Desk Tool (see note 937697) to automatically check your configuration. Report RSPOR_SETUP

The report RSPOR_SETUP is part of Usage Type AS (software component SAP_BW). It could be used to perform a manual/semi-automatic configuration. But for configuration, the Template Installer is recommended. The report could be used to check the configuration of communication and Single Sign-On (SSO) from ABAP to Java.

l Required Steps

l Data Entry

l Result

l Documentation

Important Before you use the report RSPOR_SETUP, you should apply the following notes:

l 916571 RSPOR_SETUP: Adjustments for Template Installer

l 928332 RSPOR_SETUP: (Part 2) Adjustments for Template Installer

Please see Releated Note of this note for additional notes with correction of the report RSPOR_SETUP. The report RSPOR_SETUP will be frequently updated. Required Steps You can perform an initial check of the automatic configuration with the following steps:

1. Execute the report RSPOR_SETUP with transaction SE38 (or SA38; or you can execute the report from the SAP Reference IMG, see Documentation below)

2. Use value help of entry field Program ID (or RFC Destination) to choose __ as RFC Destination (this destination is created by the Template Installer)

3. Enter Portal SID (required to check step 10)

4. Press button Execute

Placeholder correspond to the field BACKEND_SID of the Template Installer's Data Entry. correspond to the field J2EE HOST and to J2EE SID. Important Please run the report on your productive client. On the ABAP stack, all configuration steps must be perform your productive client. Data Entry All required data entries are described in the documentation (see link below). For checking the automatic configuration done by the Template Installer, you have to specify only the parameter RFC Destination and the Portal SID. The report RSPOR_SETUP can check the ABAP to Java communication and SSO configuration with these two parameters. Result The report RSPOR_SETUP displays each configuration step in three area:

l Status Overview

l Entries (manual steps, parameters and values)

l Checks

Status Overview area gives a short summary of all configuration steps. Entries area enables you to perform a configuration step manually. Checks area is quite helpful to analyze error messages. This area displays detailed information and gives hints how to manually check the configuration. Note 888687 contains a detailed description for analyzing communication and Single Sign-On (SSO) problems. In case of problems, it might be required to perform a configuration step manually with the information displayed in the Entries area. Please use the document Problem_Analysis.doc to analyze problems with the configuration. The document is attached to this note. The document could be used to analysis configuration issues on your own. In addition, this document must be attached to a SAP support message. If you run the report RSPOR_SETUP with the parameters above, step 12 should be green. Step 12 is checking whether a BI user could be mapped to a Portal user. This check requires a succuessful configuration of communication and Single Sign-On (SSO). We recommend to use the Java-based Diagnostics & Support Desk Tool (see note 937697) to automatically check your configuration. Documentation You can find a detailed description of all required steps in the BI system under transaction SPRO / SAP Reference IMG / SAP Customizing Implementation Guide / SAP NetWeaver / Business Intelligence / Reporting-relevant Settings / Web-Based Settings / Integration into the Portal. Configuration Checks

We recommend to use the Java-based Diagnostics & Support Desk Tool (see note 937697) to automatically check your configuration. You can check the configuration manually with the following steps:

1. Test Communication and Single Sign-On (SSO) with report RSPOR_SETUP (ABAP to Java)

2. Test System Object in Portal (Java to ABAP)

3. Test Standard Web Template in BI (both directions)

In addition to these three basic tests, there are more tests described in the document Checklist.doc. This document is attached to this note. Test Communication and Single Sign-On (SSO) with report RSPOR_SETUP (ABAP to Java) As described above, you should ensure that the step 12 of report RSPOR_SETUP is green. This means that communication and SSO from ABAP to Java is working. Test System Object in Portal (Java to ABAP) Please perform the following steps to check the System Object in the Portal:

1. Open iView System Administration / System Configuration / System Landscape

2. Choose System Object with the path portal_content/systemlandscape/SAP_BW

3. Choose Connection Tests

4. Enable WAS Connection Test

5. Enable Connector Connection Test

6. Press Test to perform connection tests

Important If you upgraded your system, please ensure that you configured the new properties in SAP NetWeaver 2004s. See topic Additional Information about details of new properties of System Object. Test Standard Web Template in BI (both directions) This test will check the ABAP to Java and Java to ABAP communication. Additionally, this check will ensure that the new Java-based BEx Web runtime is working.

1. Run Report RS_TEMPLATE_MAINTAIN_70

2. Enter Template ID 0ANALYSIS_PATTERN

3. Choose Program / Execute

4. Choose Analyse / Validate

5. Choose Analyse / Execute in Debug Mode

A Web Browser is opened and you have to logon to the Portal. Finally, an empty Analysis Pattern (without data) should appear. After these tests you can continue your testing by creating and using your own Queries (with BEx Query Designer), Web Templates (BEx Web Application Designer) and Reports (BEx Report Designer). See note 889314 "Using the BI Add-On for SAP NW 2004s" for details about Business Explorer for SAP NetWeaver 2004s.

Error messages during executing Web Template

If only a blank screen or message "Access Denied" appears, see note 872043. If message "Error while loading the Web template "0ANALYSIS_PATTERN" (return value "5")" appears, activate Content (see topic Additional Information below). If message "Parameter HIERARCHY_DATE does not exist" appears, see note 923122. If message "RFC_ERROR_LOGON_FAILURE: The issuer of SSO ticket is not authorized" (Deutsch: "Der Aussteller des SSO-Tickets ist nicht authorisiert") appears, please check step 10 of report RSPOR_SETUP. See note 888687 for additional information (Single Sign-On from Java to ABAP). See note 495911 for details how to analyze this issue. If message "Got null system object for alias SAP_BW check object permissions" (or other system alias instead of SAP_BW) appears, please check the permissions of the system object. All end user must have read access to the system object in the Portal Content (see topic Additional Information below how to set permissions of system objects). If message "More than one mastersystem found: SAP_BW" (or other system alias instead of SAP_BW) appears, please check all System Objects in the Portal System Landscape. Please check which System Object has the property "BI Master System" checked on that should not have it checked on. At first, check all BI System Objects. If you could find a second "BI Master System", check also all other (non BI) System Objects. "BI Master System" is a new property of the System Object for BI systems in the Portal. Only one BI system could be marked as "BI Master System" in one Portal (technical keywords:com.sap.ip.bi.base.portal.connection.PortalConnectorLandscapeService.getMasterSystemAlias). If message "Maximum of ### connections reached" appears, see note 919196 about pop-up blockers. If you get an unexpected language, please see note 780271 about logon language.

SAP Support Messages

In this section you can find all required information that should be part of a SAP Support Message. A SAP Support Messages should contain the following information:

l supportdesk.zip (according to note 937697)

The following information is optional:

l Output of report RSPOR_SETUP (see note 935177 to download easily the output)

l Document Problem_Analysis.doc with replaced screenshot showing the configuration of your system (see attchements of this note)

l Additional logs (details will be provided by SAP; see note 930046 how to make logs better readable)

Additional Information

In this section you can find additional information about specific issue.

l Add-In Installation and importing Certificates with identical system ID (SID)

l Add-In Installation with another client than 001

l Using ABAP system for Portal User Management

l New Properties of System Object

l Set Permissions of System Object

l Activate Web Template of BI Content

l Template BIPostInstallProcess not existing

l Error message "Session Management will not work"

Add-In Installation and importing Certificates with identical system ID (SID)

In case of Add-In installation, the system ID (SID) of AS-ABAP and AS-Java is identical. This causes problems during import and certificates, if you are using the Template Installer. Because the ABAP system does not allow to import a certificate with identical Distinguished Names (DN) (e.g. identical common names (CN), subject names, ...). Also the standard client of the J2EE must be different from the standard client of the ABAP system. If the common names are identical, the report RSPOR_SETUP displays the error message "Portal and BW certificate must be different" (English). If the client of the Portal certificate is existing in the ABAP system, the error message "Add-In Installation: check logon.ticket_client (see note 994785)" is diplayed. This issue could be solved by creating a new Portal certificate with a different Distinguished Name (DN). The steps to create a new Portal certificate are described in the report RSPOR_SETUP documentation of step "Export Portal Certificate to the Portal" (step 9):

1. Delete J2EE certificate (SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert) in Visual Administrator under Services Keystorage

2. Create new J2EE certificate (SAPLogonTicketKeypair with other Distinguished Name) in Visual Administrator under Services Keystorage (as described in documentation of step 9 "Export Portal certificate in Portal", report RSPOR_SETUP)

3. Delete J2EE certificate in certificate list and access control list (ACL) with transaction STRUSTSSO2

4. Import new J2EE certificate to certificate list in transaction STRUSTSSO2

5. Add new J2EE certificate to access control list (ACL) in transaction STRUSTSSO2

See report RSPOR_SETUP documentation of step "Configure User Management in Portal" (step 8) or note 994785 how to change the standard client of the J2EE. You can check the settings with the Java-based Diagnostics & Support Desk Tool (see note 937697)

Add-In Installation with another client than 001

Important In case of Add-In installation, the User Management (see Configuration) is automatically set to client 001.If you want to use another client, please perform the following two steps:

1. Change the property Client under register SAP System in Portal iView UME Configuration first

2. Run the Template Installer (see above)

You can check the settings with the Java-based Diagnostics & Support Desk Tool (see note 937697)

Using ABAP system for Portal User Management

If you use an ABAP system as persistence for Portal User Management, the following users are created during installation in the ABAP system. Important In case of Add-In installation, these users are automatically created on the ABAP side in client 001. If you want to use another client, you have to create these users with their roles in this other client. User Role SAPJSF SAP_BC_JSF_COMMUNICATION J2EE_ADMIN SAP_J2EE_ADMIN J2EE_GUEST SAP_J2EE_GUEST User SAPJSF is used for JCo (RFC) communication from Java to ABAP. User J2EE_ADMIN is the J2EE and Portal Administrator user. User J2EE_GUEST is used for anonymous logon. Users with Role SAP_J2EE_ADMIN are automatically mapped to Portal Group Administrators. Users with Role SAP_J2EE_GUEST are automatically mapped to Portal Group Guests. The passwords of these users are defined by the customer during installation.

New Properties of System Object

If you upgrading your Portal from SAP NetWeaver 2004 to SAP NetWeaver 2004s, the System Object representing the BI system must be extended with the following new properties:

Property (Property ID) Value Authentication Ticket Type SAP Assertion Ticket (AuthenticationTicketType) BI Directory Provider X (com.sap.ip.bi.directory) BI Documents for InfoProvider Data /bi_documents (com.sap.ip.bi.km.doc.folder.infoprovider) BI Documents for Master Data /bi_documents (com.sap.ip.bi.km.doc.folder.master) BI Documents for Metadata /bi_documents (com.sap.ip.bi.km.doc.folder.meta) BI Master System X (com.sap.ip.bi.mastersystem) Especially the property BI Master System is important to maintain. Otherwise, it is not possible to run BEx Web Applications.

Set Permissions of System Object

All end user must have read access to the system object in the Portal Content. Please perform the following steps to set the permissions of a system object:

1. Logon to Portal

2. Choose iView System Administration / Permissions / Portal Permissions

3. Expand folder Portal Content and choose system object

4. Use context menu of system object to open permissions

5. Search for "Everyone" in "Groups" (do not use role "Everyone")

6. Choose Add

7. Set dropdown box Administrator to Read and switch checkbox End User on

Activate Web Template of BI Content

Please perform the following steps to activate a Web Template of BI Content:

1. Logon to BI System

2. Start transaction Data Warehouse Workbench (transaction code RSA1)

3. Choose register Business Content (left pane)

4. Select Object Types

5. Expand BEx Web Template in tree (middle pane)

6. Double click on Select Objects

7. Choose 0ANALYSIS_PATTERN (or any other Web Template of the BI Content)

8. Object will be transferred to right pane

9. Press button Install / Install to activate the Web Template

Now, you can execute the activated Web Template.

Template BIPostInstallProcess not existing

This indicates a wrong installation. Please look into note 964988 for a solution.

Error message "Session Management will not work"

If the error message "Session Management will not work! Please check the DSM log file for details. ...'" appears, please have a look into note 596698. In general, this error message appears, if you are calling the Portal URL without domain. E.g. http://myportal:50000/irj instead of http://myportal.sap.com:50000/irj.

Validity

References

This document refers to:

Software Component From Rel. To Rel. And Subsequent

SAP_BW 700 700

710 710

SAP Notes

This document is referenced by:

SAP Notes (40)

1498753 Variable screen not closed in Bex Broadcaster 1033320 RSPOR_SETUP: (Part 3) Adjustments to the template installer 1032261 RSPOR_SETUP: Comparing Support Packages

994785 RSPOR_SETUP: Add-In Installation: check logon.ticket_client 989525 BI 2004s: Checking Java Connections Web Application Designer 983156 BI configuration w. Template Installer 974818 BEx Web Java: Alternat configuration for RFC with add-in 964988 BIPostInstallProcess not visbile in template installer 953109 RSPOR_SETUP: "Option Unicode flag is not set (ABAP is Unicod 951381 Report Designer cannot embed data provider 948483 Reporting problems in SAP NetWeaver 2004s BI Usage 945055 Transporting Web templates in SAP NetWeaver 2004s 942236 RSPOR_SETUP: "Number of registered processes exceeds... 937697 Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool 935177 RSPOR_SETUP: Overview for support/saving as a local file 934276 Print preview in SAP NetWeaver 2004s BI does not work 930046 NW2004s default trace for BI Web Applications 929603 RSPOR_SETUP:"Profile parameter login/create_sso2_ticket is.. 929602 RSPOR_SETUP: "com.sap.ip.bi Java classes with different vers 929398 RSPOR_SETUP: Error message "Portal certificate not in ACL" 928332 RSPOR_SETUP: (Part 2) Adjustments for the template installer 927788 RSPOR_SETUP: Error message CALL_FUNCTION_REMOTE_ERROR 927530 BI Java sizing 927242 RSPOR_SETUP: Error message USER_OR_PASSWORD_INCORRECT 923359 Collective Note: Configuration Wizard - Template Installer 923122 Parameter HIERARCHY_DATE does not exist 919196 Dialog box blocker and Java/ABAP BEx Web applications 916638 RSPOR_SETUP: Input help is empty 916637 RSPOR_SETUP: Short dump CX_SY_RANGE_OUT_OF_BOUNDS 916571 RSPOR_SETUP: Adjustments for template installer 916090 RFC-error messages in Web Application Designer 2004s 889314 Using the BI Add-On for SAP NW 2004s 888687 BEx Web Java: Analysis of communication/logon problems 872043 BEx Web Applications (Java): Access denied 853572 Release Restr.: Usage Type AS-Java of SAP NetWeaver 2004s 826776 Report RSPOR_SETUP: Error message "error get certificate" 805344 How URLs are generated automatically in BW 780271 UME/ABAP: Use of logon language 596698 Session Release Agent - Typical Problems & Troubleshooting 495911 Trace analysis for logon problems

916638 RSPOR_SETUP: Input help is empty 919196 Dialog box blocker and Java/ABAP BEx Web applications 923122 Parameter HIERARCHY_DATE does not exist 923359 Collective Note: Configuration Wizard - Template Installer 596698 Session Release Agent - Typical Problems & Troubleshooting 927242 RSPOR_SETUP: Error message USER_OR_PASSWORD_INCORRECT 927530 BI Java sizing 927788 RSPOR_SETUP: Error message CALL_FUNCTION_REMOTE_ERROR 928332 RSPOR_SETUP: (Part 2) Adjustments for the template installer 929398 RSPOR_SETUP: Error message "Portal certificate not in ACL" 929602 RSPOR_SETUP: "com.sap.ip.bi Java classes with different vers 929603 RSPOR_SETUP:"Profile parameter login/create_sso2_ticket is.. 1032261 RSPOR_SETUP: Comparing Support Packages 1033320 RSPOR_SETUP: (Part 3) Adjustments to the template installer 853572 Release Restr.: Usage Type AS-Java of SAP NetWeaver 2004s 872043 BEx Web Applications (Java): Access denied 964988 BIPostInstallProcess not visbile in template installer 969503 RSPLAN: Start of Planning Modeler with SSO does not work 1498753 Variable screen not closed in Bex Broadcaster 974818 BEx Web Java: Alternat configuration for RFC with add-in 780271 UME/ABAP: Use of logon language 916637 RSPOR_SETUP: Short dump CX_SY_RANGE_OUT_OF_BOUNDS 495911 Trace analysis for logon problems 934276 Print preview in SAP NetWeaver 2004s BI does not work 935177 RSPOR_SETUP: Overview for support/saving as a local file

Attachments

937697 Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool 942236 RSPOR_SETUP: "Number of registered processes exceeds... 945055 Transporting Web templates in SAP NetWeaver 2004s 948483 Reporting problems in SAP NetWeaver 2004s BI Usage 948487 Customer Message requirements for Web Application Designer 951381 Report Designer cannot embed data provider 953109 RSPOR_SETUP: "Option Unicode flag is not set (ABAP is Unicod 916571 RSPOR_SETUP: Adjustments for template installer 916090 RFC-error messages in Web Application Designer 2004s 889314 Using the BI Add-On for SAP NW 2004s 888687 BEx Web Java: Analysis of communication/logon problems 805344 How URLs are generated automatically in BW 994785 RSPOR_SETUP: Add-In Installation: check logon.ticket_client 989525 BI 2004s: Checking Java Connections Web Application Designer 983156 BI configuration w. Template Installer

File Name File Size (KB) Mime Type

WDEBU7_Setting_up_BEx_Web.zip 1427 application/x-zip-compressed

Checklist.zip 1335 application/x-zip-compressed

System_Upgrade_Copy.zip 64 application/x-zip-compressed

Problem_Analysis.zip 1752 application/x-zip-compressed