Hierarchy
⤷ BW (Application Component) SAP Business Information Warehouse
⤷ RS (Package) BW: General Business Information Warehouse
IMG Activity
ID | BW_PORTAL_OVER | Overview: Integration into Portal |
Transaction Code | S_BR8_35000016 | (empty) |
Created on | 20040311 | |
Customizing Attributes | BW_PORTAL_OVER | Integration into the Enterprise Portal |
Customizing Activity | BW_PORTAL_OVER | Integration in the SAP Enterprise Portal |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BW_PORTAL_OVER |
USE
A number of settings need to be made in the BW system for integration of SAP NetWeaver BW and SAP NetWeaver Portal. Some settings are interdependent. For this reason, we recommend that you follow the specified sequence when you maintain the settings in the BW system and the portal. The report Maintain Settings for Integration into SAP Enterprise Portal (report RSPOR_SETUP) provides step-by-step support to administrators of the BW system and the portal in setting up secure connections in both directions. The report first asks you to specify some necessary details and then automatically determines additional specifications, which you enter either manually or automatically when following these steps.
Requirements
Before you start to maintain settings, you should first specify general information. Some of this information is used by various steps. If you specify this mandatory information first, you can perform the steps in a simple, logical sequence.
The report summarizes these specifications on the selection screen. The specifications are saved for the current session so that the transactions for the individual steps can be called separately from the SAP Reference IMG.
BW administrators need authorization for transactions SM59, SMGW, RZ10, STRUSTSSO2, SM30 (table RSPOR_T_PORTAL) and possibly STMS.
The portal roles super_admin_role and com.sap.ip.bi.business_explorer_showcase need to be assigned to the portal administrator. The administrator should also have access to the portal file system.
From an organizational viewpoint, we recommend that BW and portal administrators work closely together.
Connections Between SAP NetWeaver BW and SAP NetWeaver Portal
This report supports you in setting up connections between the BW system and the portal. The portal communicates with the BW system using the Web protocols http or https. The definition is performed on the system object in the portal.
The BW system uses an RFC connection to communicate with the portal. The portal acts as an RFC server and the BW system as an RFC client. The report is used to create an RFC destination.
Single Sign-On Between SAP NetWeaver BW and SAP NetWeaver Portal
With Single Sign-On, you do not have to log on to the BW system and the portal separately. SAP logon tickets facilitate Single Sign-On. SAP logon tickets are generated in the source system and contain the system ID, user, validity, and a digital signature. The digital signature is created using the private certificate key. The signature can be verified in the target system using certificates with a public key. The source system must be entered in the access control list (ACL), since the target system must trust SAP logon tickets from the source system.
To use Single Sign-On successfully, you must specify the complete URL including host name and domain. The host name and domain must be used to call the portal in the Web browser. The portal URL prefix including the domain must therefore be entered in step 3. When BW iViews are called within the portal, the host name of SAP NetWeaver AS from step 7 is used if it is a Web template from the runtime of BEx Web 3.x. For this reason, you are also required to specify the domain there. Refer to the documentation for different domains under SAP Library -> SAP NetWeaver -> Security -> User Authentication and Single Sign-On -> Authentication on the Portal -> Single Sign-On -> Single Sign-On with SAP Logon Tickets -> SAP Logon Tickets for Multiple Domains.
Standard settings
This section describes the individual values on the selection screen. The documentation for the individual steps provides detailed descriptions of the values.
Creating the RFC Destination on Application Server Java
Program ID: The program ID is the name of the registered server program (see step Creating RFC Destinations for the Portal).
Portal Directory: The portal directory is used to start the SAP NetWeaver Administrator tool. The file ./admin/go.bat must exist in this directory. SAP NetWeaver Administrator can also be installed locally on the administrator's PC so that the portal server can be accessed remotely.
BW User and BW Password: The Application Server Java uses the BW user and BW password to query the RFC function module signatures in the BW system. The user can be compared to ALEREMOTE.
Create RFC Destination for Portal
User-Defined RFC Destination, Program ID as RFC Destination and RFC Destination: You can either choose the description of the RFC destination yourself or the system copies the program ID (see above). If you choose a user-defined name, enter the name under RFC Destination.
RFC Description: The RFC description is the text that is displayed in the BEx Web Application Designer and the BEx Query Designer as the description for the connected portal.
Maintain Portal Server Settings for Portal
Default: You can select a portal as the standard portal by setting the Default indicator. A warning is displayed if another portal is already selected as the default portal.
Portal URL Prefix: The portal URL prefix is required for the input help in BEx Information Broadcasting. The report uses the portal URL prefix to list particular iViews for maintaining or testing the settings. The portal roles super_admin_role and com.sap.ip.bi.business_explorer_showcase are necessary for calling these iViews.
RM Prefix for BW Metadata: The RM prefix for BW metadata is required in the step Set Up Repository Manager for BW in Portal and also has to be maintained in the portal server settings. The prefix determines the path in Knowledge Management, using which BW metadata is accessed by the repository manager.
Export BW Certificate to BW System
Export Path and Export File Name: The BW certificate is saved under the specified path and file name and can then be imported to the portal.
Create a BW System in the Portal
Path in Portal Content and Name in Portal Content: The BW system in the portal is created under the specified path and name in the Portal Content Studio.
Template for Defining the BW System in Portal: When you create the BW system in the portal, you can select System with Load Balancing or System with Application Server as template. The necessary information is determined and displayed depending on the template selected.
BW Properties: The following properties are specific to a BW system. If the BW Directory Provider indicator is set, the BW system is displayed in the open dialog when you select queries or InfoProviders. The BW Documents for InfoProvider, Master Data and Metadata properties contain the path for the relevant CM repository manager for storing BW documents in Knowledge Management. These properties are used when the documents are migrated to Knowledge Management.
The BW Master System property means that the BW system is the central persistence store for the portal. The BW master system is used to read and execute Web templates. The executable BW Web runtime requires one BW master system within a portal.
System Alias: Every system in the portal requires a system alias. The logical system name is recommended as the alias. However, you can enter any value.
Create System Alias SAP_BW: For the portal role com.sap.ip.bi.business_explorer_showcase, a BW system with the system alias SAP_BW is required in the portal. Only one system can have the alias SAP_BW.
Configure User Management in the Portal
Logon Ticket Client: The logon ticket client can be any value between 000 and 999. The client is required if multiple portals with identical portal SIDs are connected. This is not normally the case and the default value can usually be accepted. You have to enter the client later when you import the portal certificate to the BW system.
Export Portal Certificate to the Portal
Portal SID: The portal SID is required so that naming conventions are observed. It must be entered when you import to the BW system.
Import Path and Import File Name: The portal certificate should be saved under the specified path and file name and can be imported from there to the BW system.
Maintain User Assignment in the Portal
User-Mapping User and User-Mapping Password: The user-mapping user and its password are used to check user assignments. This information is not mandatory but ensures that all settings have been made to guarantee a secure connection from the BW system to the portal.
Activities
- Specify the required details described above.
- Execute the activity (= the report Maintain Settings for Integration to Portal).
- Enter the required details on the selection screen.
- Choose Execute.
- Choose Previous Step or Next Step to switch between the individual ste
Business Attributes
ASAP Roadmap ID | 262 | Technical and Graphical Settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | BW_PORTAL_OVER | 0 | ARS0000021 | Business Explorer |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMGDUMMY | D - Dummy object | RSPOR_CUST01 |
History
Last changed by/on | SAP | 20050720 |
SAP Release Created in | 400 |