BI-Portal

Configuration of BI and Portal

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 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 Sign-On Access Control List (ACL) or EvaluateTicketLoginModule in the validating system. Reports to Run:

1. RSPOR_SETUP

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

2. RS_TEMPLATE_MAINTAIN_70

Run Report RS_TEMPLATE_MAINTAIN_70 and Enter Template ID 0ANALYSIS_PATTERN > Choose Program / Execute
Choose Analyse / Validate , 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).