PREREQUISTES:
Following prerequisites should be meet before the execution of BI Template.
1.Check that the BI (ABAP) system is SSO enabled.
the following parameters should have the required values:
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
See it in t-code RZ11 or Use report RSPARAM to check the values of these parameters.
if the parameters are not set to the specified value do the settings in RZ10 ,save and activate the profile.Restart the system.
2.Check that the logon group of your BI (ABAP) system is set up (use transaction smlg)
3. Ensure that both the administrator user and the SAPJSF user already exist
in your BI (ABAP) system and have been both at least assigned role SAP_BC_JSF_COMMUNICATION ( but not RO) and profile S_BW_RFC and S_BI-WX_RFCA.
4.Create PSE in ABAP (Transaction strustsso2)
When exporting certificate from the AS-ABAP (BI) system, the system PSE must be
Properly configured Start transaction STRUSTSSO2, if the System PSE does not have a
Green status, right mouse-click on System PSE, clicks on Create, and accept
Initial values. Save the changes.
Execution of BI template will perform all of the below steps .Many times the template may not completely perform all the steps, So its always suggested to cross check all the steps manually.
Following prerequisites should be meet before the execution of BI Template.
1.Check that the BI (ABAP) system is SSO enabled.
the following parameters should have the required values:
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
See it in t-code RZ11 or Use report RSPARAM to check the values of these parameters.
if the parameters are not set to the specified value do the settings in RZ10 ,save and activate the profile.Restart the system.
2.Check that the logon group of your BI (ABAP) system is set up (use transaction smlg)
3. Ensure that both the administrator user and the SAPJSF user already exist
in your BI (ABAP) system and have been both at least assigned role SAP_BC_JSF_COMMUNICATION ( but not RO) and profile S_BW_RFC and S_BI-WX_RFCA.
4.Create PSE in ABAP (Transaction strustsso2)
When exporting certificate from the AS-ABAP (BI) system, the system PSE must be
Properly configured Start transaction STRUSTSSO2, if the System PSE does not have a
Green status, right mouse-click on System PSE, clicks on Create, and accept
Initial values. Save the changes.
Execution of BI template will perform all of the below steps .Many times the template may not completely perform all the steps, So its always suggested to cross check all the steps manually.
Creating BI System in the Portal
1)Logon to the portal.
2)Go to System Administration -> system configuration->Portal content ->External systems ->New ->select "systems(from template)".
3) Select the system as “SAP System using dedicated Application Server”
4) Enter the system name as “
5.)now the syetem is created
6) Enter the properties for the newly created system as follows: a)Application Host : XXX(name of Application host)
b)Authentication Ticket Type: SAP Assertion Ticket
c)BI Directory Provider: Yes
d)BI documents for InfoProvider Data: Root Folder of KM Repository:/bi_documents.
e)BI documents for Master Data: Root Folder of KM Repository:/bi_documents.
f)BI documents for Meta Data: Root Folder of KM Repository:/bi_documents.
g)BI Master System: Yes
h)Codelink :-
i)Gateway Host
j)Gateway service: sapgw00 (Where 00 is the instance no :)
k) ITS description: ITS Server on your server(here TP6).
l)ITS Host name: XXX:8001
m) ITS path: /sap/bc/gui/sap/its/webgui
n)ITS Protocol: http
o)Logical System name: TP6CLNT800
p)Logon Method: SAPLOGONTICKET
q)Remote Host Type:3
r) SAP Client: 800
s)SAP system ID (SID): TP6
t) SAP system No: 00
u)Server Port: 3600
v) SNC partner name: SAP_BW
w) SNC QOP (Security Level): 0
x) System Name: TP6CLNT800
System Type: SAP_BW
User Mapping Type: admin, user
Validate Connection: Yes
Web AS Description: WAS for viewing reports.
Web AS Path: /sap/bw/BEx
Web AS Protocol: http
*to get WAS Host name, WAS Path and WAS protocol settings using the function Module RSBB_URL_PREFIX_GET (Transaction SE37)
* The property BI Master System means that the BI system is the central Persistence storage for the portal. The BI Master system is used to read and execute Web templates. The Running BI Web Runtime requires exactly one BI Master System within the portal.
* Information about the R3 ABAP system can be obtained through transaction smms
* Select “Permissions” for the newly created system and ADD “Everyone: group and set “Read” access to the Administrator and select: End User” checkbox.
8) Create 2 System Alias: PW3CLNT800 and SAP_BW and choose the former one as the default.
Export BI certificate from the BI system.
1) Goto Transaction “strtustsso2” in BW system and double click on Own certificate
2) Click on the Export Certificate button as shown.
3) Give the name to the certificate as “
Import the portal Certificate to the BI system.
1) In the portal navigate to System administration-> System configuration-> KeyStore Administration.
2) Save the certificate at the desired location.Choose the format as Binary
3) To include the certificate in the SSO Access Control list (ACL)Click on “Add to Certificate List”
4) Click on “Add to ACL”
5) Now the Certificate gets included in BI system.
Create RFC Destination in the BW system.
The BI system uses the RFC destination to communicate with the portal.
1) Start Transaction SM59
2) Type: T for TCP/IP connection.
Create RFC Destination in J2EE Engine.
1) Open the Visual administrator in portal system. Go to Server -> services ->JCo RFC Provider->select the existing connection and edit the properties as below.
** Program Id should be the same as the program Id specified in the RFC destination.
2) Select Security Provider-> Evaluate Assertion Ticket -> Click on Edit ->Click on Modify-> Enter the properties as shown below.
Import the BW certificate into the J2EE Engine
1) Start the Visual Administrator Tool.
2) Select the
Create the JCO connection in portal system.
1) Logon to the portal.
2) Navigate to Content Management ->Web Dynpro -> Maintain JCo Destinations-> Create JCo destination for BI-METADATA, BI_MODELDATA, and WD_ALV_MEATADATA_DEST AND WD_ALV_MODERDATA_DEST
3)Click on create.
4)Enter the Name: BI_METADATA
Client: 800
5) Select “Use Local J2EE engine “JEE on XXX\j2e””. Click Next.
6) Select Data Type: Dictionary Meta Data
7) Maintain the details of the Message Server: TP6 XXXX
Logon Group : Public
8) Specify the ABAP user id and Password
Adding permissions to the IViews.
1) Go to Content Administration->Portal Content->Content provided by SAP-> platform Add ons-> Business Intelligence -> Iviews -> select each of the IViews and add “Everyone “ group to all the iviews.
Connected Portal Details
Use transaction “SM30”; enter the Table name “RSPOR_T_PORTAL”.
Click display. Select the RFC Destination created Earlier . click on New Entries.
Configure User Management in the portal.
1) Go to System Administration->System Configuration->UME configuration
Make the following Entries:
Under Data Sources tab.
Under ABAP system tab.
Under User Mapping Tab.
Set up Repository Manager for BI Documents and BI Metadata.
In this activity you can set up the BI document and BI Metadata Repository manager.
Execute the following steps to set up a Repository manager for BI in the portal.
1) Logon to the portal
2) Start iview System administration -> System Configuration ->Knowledge management –>Content Management .
3) Choose Content Management->Repository managers.
4) Under Classes, choose BI document Repository.
5) Create a new instance of the BI Document Repository.
6) Enter the following entries.
Name: unique name of Repository Manager.
Alias of BW system:
Prefix: < BI_DOCUMENTS_PREFIX>(eg: /bi_documents)
Active: X
Security Manager: BWDocumentSecurityManager.
8)Choose OK to save the settings.
Repeat the last 4 steps for BI Metadata Repository.
Maintain User assignment in the portal:
In this activity you assign a user in the BI System to a user in the portal.
Execute the following steps to maintain user mapping in the portal.
1) Logon to the portal
2) Start the iview User Management -> User mapping.
3) Choose User from the dropdown box.
4) Search the user (Administrator)
5) Choose modify
6) Choose the tab User Mapping for system Access.
7) From The system dropdown select the BI system Created.
8) Under the Mapping Data enter the userid (ABAP user) and its Password.
9) Save the entries.
Possible Problems that might arise and its solution:
1) If connection to BI system could not be established because the message server port was not known on the system.
To make this port known, there must be an entry in the file C:\WINDOWS\system32\drivers\etc\services.
2) Any Changes that you make in the config tool should be made under the Global Configuration Settings and not under Instance specific settings.
3) After Unistallation of SAP System, check the registries, as some of the entries might not have been removed by the uninstaller.
So during reinstallation, the installation process may fail due to this.
4) In case of JMSSecurityException, refer to the following note: 971249.
