sapnote_0000917950

04.09.2012 of 19

SAP Note 917950 - SAP NetWeaver 2004s: Setting Up BEx Web

Note Language: English Version: 27 Validity: Valid Since 18.07.2007

Summary

SymptomThis note describes how to setup BEx Web in SAP NetWeaver 2004s. Allrequired steps are mentioned. Additionally, this note contains a checklistto check the installation and configuration.

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

Reason and PrerequisitesYou configure BEx Web and BEx Information Broadcasting in a systemlandscape with SAP NetWeaver 2004s.

Solution

Overview

o Other References

- Frequently Asked Questions (FAQ)

- SDN Forum

- Learning Map for Consultants

o Definition of Terminology

- Usage Types

o Architecture

o Installation (*)

- Types of Installation

o Configuration Overview(*)

o Configuration Tools (*)

- Template Installer

- Report RSPOR_SETUP

o Configuration Checks (*)

o SAP Support Messages (*)

o Additional Information

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

04.09.2012 of 19


This note will be frequently updated.

Other References

o Documentation

You can find a detailed description of all required steps in the BIsystem under transaction SPRO / SAP Reference IMG / SAP CustomizingImplementation Guide / SAP NetWeaver / Business Intelligence /Reporting-relevant Settings / Web-Based Settings / Integration intothe Portal.

o Frequently Asked Questions (FAQ)

You can access a list of frequently asked questions for BI underhttp://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.

o SDN Forum

There is a SDN Forum available during Ramp-Up of SAP NetWeaver2004s 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 thisforum to place your question and discuss with experts.

Definition of TerminologySAP introduced new terms with SAP NetWeaver 2004 like IT practices, ITscenarios and Usage Types. Usage types are a new structuring element forSAP software on a technical level.

For more information, see SAP Service Marketplace athttp://service.sap.com/instguidesNW2004s

Usage Types

o AS-ABAP

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

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

- Internet Graphics Service (IGS) comprised

o AS-Java

- Contains all Java-based SAP WebAS functionality (J2EE)

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

04.09.2012 of 19


- Universal Data Integration (UDI) is an independent componentthat is used for data retrieval and does not require Usage TypeBI-Java

- See note 853572 for additional information about AS-Java

o EP

- Contains Portal

- Requires Usage Type AS-Java

o BI

- Contains BI Content Add-On (software component BI_CONT)

- Requires Usage Type AS-ABAP

o BI-Java

- Contains all Java- and WebDynpro-based BI functionality

New NW2004s Web Runtime (incl. Analysis Item, FormattedReporting, Web Printing, PDF Export, ...), new Planning Modelerfor BI Integrated Planning, ...

- Requires Usage Type EP and AS-Java

- See Release Notes underhttp://help.sap.com/saphelp_nw04s/helpdata/en/index.htm

o BI accelerator

- Standalone engine based on TREX

o Search and Classification

- Standalone engine based on TREX

BI accelerator and Search and Classification require two differentTREX standalone engines

ArchitectureAs described above, BEx Web in SAP NetWeaver 2004s (Usage Type BI-Java)requires Usage Types EP and AS-Java, i.e. a Portal on a Java stack isrequired. This Java stack could be installed on the same server or onanother server (see Types of Installation for details).BEx Web Runtime and BI Consumer Services (BICS) are implemented in Java andusing Portal Runtime functionality. BEx Web Runtime is responsible togenerate output for Web Browser and BICS retrieves data from BI Platformand/or UDI.

In SAP NetWeaver 2004s, load is moved from AS-ABAP (BI-ABAP) to AS-Java(BI-Java). BI generates load on Portal (AS-Java), therefore BI usersgenerate more load on Portal than normal Enterprise Portal users. See note927530 for additional information about BI-Java sizing.

04.09.2012 of 19


Which functionalities of BEx Web in SAP NetWeaver 2004s are requiring aPortal?

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

o Exporting to PDF and Printing

o Integrated Planning

o Drag&Drop (Analysis Web Item)

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

o Formatted Reporting with BEx Report Designer

o Document Integration with storage in Knowledge Management

o ...

For details, see Release Notes for Usage Type BI-Java underhttp://help.sap.com/saphelp_nw04s/helpdata/en/index.htm

If you don't want to use the new BEx Web functionality, you can still useBEx Web 3.5 Runtime that is running only with Usage Type AS-ABAP.

InstallationTypes of InstallationAs result of your installation or upgrade process, you can have thefollowing system state:

o Application Server ABAP (AS-ABAP with own system ID andinstance number)

o Application Server Java (AS-Java with own system ID andinstance number)

o Double-Stack (ABAP and Java combined on one server withidentical system ID and instance number)

In case of AS-ABAP and AS-Java the ABAP stack and Java stack are separatedby system ID (SID) and instance number. But both stacks could beinstalled together on one server or separately on twodifferent servers. Both stacks are like different systems.

In case of Double-Stack installation, the ABAP stack and Java stack arerunning as one system on one server.

The term Add-In installation describes an installation process - it isnot a system state. The result of an Add-In installation is a Double-Stacksystem (AS-ABAP and AS-Java with on system ID). An Add-In installationallows to install a Java stack to an existing ABAP stack. An Add-Ininstallation of an ABAP stack to an existing Java stack is not possible.

ImportantIn case of Add-In installation, the system ID (SID) of AS-ABAP

04.09.2012 of 19


and AS-Java is identical. This causes problems during import andcertificates, if you are using the Template Installer. Please see topicAdditional Information for details about these settings.

ImportantIn case of Add-In installation, the User Management (seeConfiguration) is automatically set to client 001. If you want touse another client, you have to adjust a few settings. Please see topicAdditional Information for details about these settings.

See FAQ for details about possible system landscapes.

Types of Upgrade

o From SAP EP 6.0 (SAP NetWeaver 2004)

o From SAP BW 3.5 (SAP NetWeaver 2004)

o 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 (nowBI) systems in the Portal System Landscape, please ensure to maintain thenew properties at the System Object (see Additional Information below fordetails).

See FAQ for details about possible system landscapes.

See http://service.sap.com/instguidesnw2004s for general installation andupgrade information about SAP NetWeaver 2004s.

Configuration OverviewYou 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. BExInformation Broadcasting shows Knowledge Management folder). See note888687 for technical details.

For Single Sign-On (SSO), you have to ensure that Java and ABAP trusteach other:

04.09.2012 of 19


1. Java is trusting ABAP

2. ABAP is trusting Java

Single Sign-On (SSO) is working with SAP Logon Tickets. SAP Logon Ticketsare created with the help of certificates and could be validated withcertificates. Therefore, certificates must be exchanged between Java andABAP.Certificates consist of a public key and optionally of a private key. Theprivate key of certificate is required for creating and signing SAP LogonTickets. The public key of certificate is used for validating SAP LogonTickets.SAP Logon Tickets are digitally signed with the private key of theissuing system's certificate. They contain the user ID, authenticationscheme, validity period, issuing system and digital signature but they donot contain any passwords. SAP Logon Tickets are validated with the publickey of the issuing system's certificate (the public key is located inSystem PSE or TicketKeystore). They are only accepted if the issuing systemis part of Single Sign-On Access Control List (ACL) orEvaluateTicketLoginModule in the validating system.See note 888687 for additional technical details.

User Management could help you to minimize the effort of administratingyour 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 automaticallyset up. See References for details.

Configuration ToolTo configure BI-Java, you should use the Template Installer (template-basedautomatic configuration). In order to have the latest corrections for theTemplate Installer available, please use the latest patch of the SCALM-TOOLS for your Support Package Stack. The latest patch can be downloadedfrom SAP Service Marketplace.

How to use this Configuration Tool?At first, use the Template Installer to perform the automaticconfiguration. In most cases, this template-based automaticconfiguration 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) to automatically check yourconfiguration.

ImportantPlease remember, especially an automatic configration processhas its limits. Your system landscape could differ from thestandard case. Therefore, it is important to understand the

04.09.2012 of 19


manual steps as performed with the report RSPOR_SETUP.

You can find screenshots and additional information about theconfiguration in the attached fileWDEBU7_Setting_up_BEx_Web.zip. The slides are based on thewprkshop "Upgrading to SAP NetWeaver 2004s BI - Technicalaspects" (WDEBU7).

Template InstallerThe Template Installer is installed with Usage Type EP and used forautomatic configuration.

o Prerequisites

o System Upgrade and System Copy

o Required Steps

o Data Entry ABAP (BI system)

o Data Entry Java

o Error Messages

o Result

PrerequisitesBefore you start the Template Installer, please check note 983156 forrequired 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 CopyIn case of a system upgrade or system copy, you might have to adjust theTemplate Installer (CTC) settings, because these settings contain theprevious values that are not valid anymore.Please have a look at the attachment System_Upgrade_Copy.ZIP of this note.

Required StepsYou can perform the template-based automatic configuration with thefollowing steps:

1. Start SAP NetWeaver Administrator (NWA) with alias /nwa<PORTAL_PROTOCOL>://<PORTAL_SERVER>:<PORTAL_PORT>/nwa

2. Logon with user "Administrator"

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

3. Choose Deploy & Change Template Installer

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

5. Press Execute Template

04.09.2012 of 19


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

7. Press Install

If the template BIPostInstallProcess is not existing, please see topicAdditional Information.

Data Entry ABAP (BI system)

o ABAP Administration User (ABAP_ADMIN and ABAP_PASSWORD)

Used by RFC Destination in J2EE; ABAP user

o Backend System (BACKEND_SYSTEM)

Hostname of ABAP system

o Backend System Number (BACKEND_SYSNUMBER)

System number of ABAP system

o Backend Client (BACKEND_CLIENT)

Client of ABAP system

o Backend HTTP Port (BACKEND_HTTP_PORT)

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

o Backend System ID (BACKEND_SID)

System ID of ABAP system

With SAP NetWeaver 2004s SP6 the following parameters must be specified:

o Backend Server Port (BACKEND_SERVER_PORT)

Message server port; see profile parameter ms/server_port_... onABAP message server

Data Entry Java

o Java Host (J2EE HOST)

Hostname of J2EE

o Java System ID (J2EE SID)

System ID of J2EE

o Java HTTP Port (J2EE HTTP PORT)

http port, 5<J2EE_SYSNUMBER>00, e.g. 51000 for system number 10

o P4 Port (P4PORT)

04.09.2012 of 19


TCP/IP port of Visual Administrator, <J2EE_HTTP_PORT>+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

o WebDynpro JCo User and Password

Used by WebDynpro for Planning Modeller (BI integrated Planning)

o Logon Group

Used by WebDynpro for Planning Modeller (BI integrated Planning)

Error MessagesIn case of a problem, don't get confused by the long error message. Pleaseread the especially the last sentence of the error message. Normally, thislast 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 problemand restart the Template Installer (by starting the SAP NetWeaverAdministrator 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 objectsalready exist or steps already performed. In this case, you should stopusing the Template Installer and continue with the report RSPOR_SETUP (seebelow).

Step 1For example, the RFC destination could not be created because it is alreadyexisting and locked.

If the prerequisites regarding SSO are not fulfilled, the error message"Element 'SAPConfigLib.DEP.Unclassified.createRfcDestination': Error duringexecuting Java Reflection:RFC_DESTINATION_ERROR" will appear in step 1.

Step 9If the error message "Application is not authorized to execute keystoreoperation" 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 toadd 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.

04.09.2012 of 19


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 10For example, the certificate could be updated in step 10 (Import EngineCertificate To ABAP). If the Portal certificate is already existing on theABAP side (see transaction STRUSTSSO2), this is not a problem and you cancontinue.

See topic Additional Information for details about specific issue withTemplate Installer and Add-In installation.

ResultThe 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_SETUPThe report RSPOR_SETUP is part of Usage Type AS (software componentSAP_BW). It could be used to perform a manual/semi-automatic configuration.But for configuration, the Template Installer is recommended. The reportcould be used to check the configuration of communication and SingleSign-On (SSO) from ABAP to Java.

o Required Steps

o Data Entry

o Result

o Documentation

ImportantBefore you use the report RSPOR_SETUP, you should apply thefollowing notes:

o 916571 RSPOR_SETUP: Adjustments for Template Installer

o 928332 RSPOR_SETUP: (Part 2) Adjustments for TemplateInstaller

Please see Releated Note of this note for additional notes with correctionof the report RSPOR_SETUP. The report RSPOR_SETUP will be frequentlyupdated.

Required StepsYou can perform an initial check of the automatic configuration with thefollowing steps:

04.09.2012 of 19


1. Execute the report RSPOR_SETUP with transaction SE38 (or SA38; or youcan execute the report from the SAP Reference IMG, see Documentationbelow)

2. Use value help of entry field Program ID (or RFC Destination) tochoose <BI_SID>_<J2EE_HOSTNAME>_<J2EE_SID> as RFC Destination (thisdestination is created by the Template Installer)

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

4. Press button Execute

Placeholder <BI_SID> correspond to the field BACKEND_SID of the TemplateInstaller's Data Entry. <J2EE_HOSTNAME> correspond to the field J2EE HOSTand <J2EE_SID> to J2EE SID.

ImportantPlease run the report on your productive client. On the ABAPstack, all configuration steps must be perform your productiveclient.

Data EntryAll required data entries are described in the documentation (see linkbelow). For checking the automatic configuration done by the TemplateInstaller, you have to specify only the parameter RFC Destination and thePortal SID. The report RSPOR_SETUP can check the ABAP to Java communicationand SSO configuration with these two parameters.

ResultThe report RSPOR_SETUP displays each configuration step in three area:

o Status Overview

o Entries (manual steps, parameters and values)

o 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 displaysdetailed information and gives hints how to manually check theconfiguration. Note 888687 contains a detailed description for analyzingcommunication and Single Sign-On (SSO) problems.

In case of problems, it might be required to perform a configuration stepmanually with the information displayed in the Entries area.

Please use the document Problem_Analysis.doc to analyzeproblems with the configuration. The document is attached tothis note. The document could be used to analysisconfiguration issues on your own. In addition, this documentmust be attached to a SAP support message.

If you run the report RSPOR_SETUP with the parameters above, step 12 shouldbe green. Step 12 is checking whether a BI user could be mapped to a Portaluser. This check requires a succuessful configuration of communication andSingle Sign-On (SSO).

04.09.2012 of 19


We recommend to use the Java-based Diagnostics & Support Desk Tool(see note 937697) to automatically check your configuration.

DocumentationYou can find a detailed description of all required steps in the BI systemunder transaction SPRO / SAP Reference IMG / SAP Customizing ImplementationGuide / SAP NetWeaver / Business Intelligence / Reporting-relevant Settings/ Web-Based Settings / Integration into the Portal.

Configuration ChecksWe 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 testsdescribed in the document Checklist.doc. This document isattached to this note.

Test Communication and Single Sign-On (SSO) with reportRSPOR_SETUP (ABAP to Java)As described above, you should ensure that the step 12 of reportRSPOR_SETUP is green. This means that communication and SSO from ABAP toJava is working.

Test System Object in Portal (Java to ABAP)Please perform the following steps to check the System Object in thePortal:

1. Open iView System Administration / System Configuration / SystemLandscape

2. Choose System Object with the pathportal_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

ImportantIf you upgraded your system, please ensure that you configured the new

04.09.2012 of 19


properties in SAP NetWeaver 2004s. See topic Additional Information aboutdetails 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 Webruntime 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, anempty Analysis Pattern (without data) should appear.

After these tests you can continue your testing by creating and using yourown Queries (with BEx Query Designer), Web Templates (BEx Web ApplicationDesigner) and Reports (BEx Report Designer).

See note 889314 "Using the BI Add-On for SAP NW 2004s" for details aboutBusiness Explorer for SAP NetWeaver 2004s.

Error messages during executing Web TemplateIf only a blank screen or message "Access Denied" appears, see note872043.

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, seenote 923122.

If message "RFC_ERROR_LOGON_FAILURE: The issuer of SSO ticket isnot authorized" (Deutsch: "Der Aussteller des SSO-Tickets ist nichtauthorisiert") appears, please check step 10 of report RSPOR_SETUP. Seenote 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 objectpermissions" (or other system alias instead of SAP_BW) appears, pleasecheck the permissions of the system object. All end user must have readaccess to the system object in the Portal Content (see topic AdditionalInformation below how to set permissions of system objects).

If message "More than one mastersystem found: SAP_BW" (or othersystem alias instead of SAP_BW) appears, please check all System Objects inthe Portal System Landscape. Please check which System Object has theproperty "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

04.09.2012 of 19


Master System", check also all other (non BI) System Objects."BI Master System" is a new property of the System Object for BI systems inthe Portal. Only one BI system could be marked as "BI Master System" in onePortal (technical keywords:com.sap.ip.bi.base.portal.connection.PortalConnectorLandscapeService.getMasterSystemAlias).

If message "Maximum of ### connections reached" appears, see note919196 about pop-up blockers.

If you get an unexpected language, please see note 780271 about logonlanguage.

SAP Support MessagesIn this section you can find all required information that should be partof a SAP Support Message.

A SAP Support Messages should contain the following information:

o supportdesk.zip (according to note 937697)

The following information is optional:

o Output of report RSPOR_SETUP (see note 935177 to download easilythe output)

o Document Problem_Analysis.doc with replaced screenshot showing theconfiguration of your system (see attchements of this note)

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

Additional InformationIn this section you can find additional information about specific issue.

o Add-In Installation and importing Certificates with identicalsystem ID (SID)

o Add-In Installation with another client than 001

o Using ABAP system for Portal User Management

o New Properties of System Object

o Set Permissions of System Object

o Activate Web Template of BI Content

o Template BIPostInstallProcess not existing

o Error message "Session Management will not work"

04.09.2012 of 19


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

In case of Add-In installation, the system ID (SID) of AS-ABAPand AS-Java is identical. This causes problems during import andcertificates, if you are using the Template Installer. Because the ABAPsystem does not allow to import a certificate with identical DistinguishedNames (DN) (e.g. identical common names (CN), subject names, ...). Also thestandard client of the J2EE must be different from the standard client ofthe ABAP system.

If the common names are identical, the report RSPOR_SETUP displays theerror message "Portal and BW certificate must be different" (English).

If the client of the Portal certificate is existing in the ABAP system, theerror message "Add-In Installation: check logon.ticket_client (see note994785)" is diplayed.

This issue could be solved by creating a new Portal certificate with adifferent Distinguished Name (DN). The steps to create a new Portalcertificate are described in the report RSPOR_SETUP documentation of step"Export Portal Certificate to the Portal" (step 9):

1. Delete J2EE certificate (SAPLogonTicketKeypair andSAPLogonTicketKeypair-cert) in Visual Administrator under ServicesKeystorage

2. Create new J2EE certificate (SAPLogonTicketKeypair with otherDistinguished Name) in Visual Administrator under Services Keystorage(as described in documentation of step 9 "Export Portal certificate inPortal", 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 transactionSTRUSTSSO2

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

See report RSPOR_SETUP documentation of step "Configure User Management inPortal" (step 8) or note 994785 how to change the standard client of theJ2EE.

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

Add-In Installation with another client than 001

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

04.09.2012 of 19


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

2. Run the Template Installer (see above)

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

Using ABAP system for Portal User ManagementIf you use an ABAP system as persistence for Portal User Management, thefollowing users are created during installation in the ABAP system.

ImportantIn case of Add-In installation, these users are automaticallycreated on the ABAP side in client 001. If you want to useanother client, you have to create these users with theirroles in this other client.

User RoleSAPJSF SAP_BC_JSF_COMMUNICATIONJ2EE_ADMIN SAP_J2EE_ADMINJ2EE_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 GroupAdministrators.Users with Role SAP_J2EE_GUEST are automatically mapped to Portal GroupGuests.

The passwords of these users are defined by the customer duringinstallation.

New Properties of System ObjectIf you upgrading your Portal from SAP NetWeaver 2004 to SAP NetWeaver2004s, the System Object representing the BI system must be extended withthe following new properties:

Property (Property ID) ValueAuthentication 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.

04.09.2012 of 19


Otherwise, it is not possible to run BEx Web Applications.

Set Permissions of System ObjectAll end user must have read access to the system object in the PortalContent. Please perform the following steps to set the permissions of asystem 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 ContentPlease perform the following steps to activate a Web Template of BIContent:

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 existingThis indicates a wrong installation. Please look into note 964988 for asolution.

Error message "Session Management will not work"If the error message "Session Management will not work! Please check theDSM log file for details. ...'" appears, please have a look into note

04.09.2012 of 19


596698. In general, this error message appears, if you are calling thePortal URL without domain. E.g. http://myportal:50000/irj instead ofhttp://myportal.sap.com:50000/irj.

Header Data

Release Status: Released for CustomerReleased on: 18.07.2007 09:16:50Master Language: EnglishPriority: Correction with high priorityCategory: Installation informationPrimary Component: BW-SYS Basis System and Installation

Secondary Components:BW-BEX-ET-RT Query Run Time

BW-BEX-ET-WEB BEx Web ABAP Runtime

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

BW-BEX-ET-BC Broadcasting

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

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_BW 70 700 700

SAP_BW 71 710 710

Related Notes

Number Short Text

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

929603 RSPOR_SETUP:"Profile parameter login/create_sso2_ticket is..

04.09.2012 of 19


Number Short Text

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"

780271 UME/ABAP: Use of logon language

596698 Session Release Agent - Typical Problems & Troubleshooting

495911 Trace analysis for logon problems

Attachments

FileType

File Name Language Size

ZIP Problem_Analysis.zip E 1.752 KB

ZIP WDEBU7_Setting_up_BEx_Web.zip E 1.427 KB

ZIP System_Upgrade_Copy.zip E 64 KB

ZIP Checklist.zip E 1.335 KB

sapnote_0000917950

Documents

based diagnostics

universal data integration

frequently asked questions

sap service marketplace

sap netweaver 2004s

bi integrated planning

topic additional information

usage type bi