Product versions: BOE XI 3.1 and netweaver 7.x
This article is finished.
This BOpedia page is provided by the RIG team. Don't hesitate to put comments.
Main Contributors : Martha L, Stephane T, Anthony L, Erica L, David F G
With the help of Antonia R, Ferry L , Eliot G
New : If you want to learn about the BI4.0 Integration, please have look to the following article :
Link to the main SP page Introduction, Chapter A and B : Integration of BOE XI3.1 into the SAP Enterprise Portal 7.x
Chapter C : Create BOEXI3.1 Integration Kit IView Template into SAP EP Portal
Chapter D : Create URL iview into the SAP EP portal
Chapter E : Integrate BOEXI3.1 into a KM Navigation into SAP EP portal
Chapter F : Creating Roles in SAP EP Portal and assigned them to Portal Users
Chapter G : Viewing BOEXi3.1 reports into SAP EP Portal
Scenarios and KM and iView possibilities : Scenarios and KM and iView possibilities
Webinar link and QA : Webinar and QA
Appendix : Chapter H, I, J, K, L, M : Appendix of the BOEXI3.1 Integration into the SAP EP
Chapter C ) Create BOE Integration Kit IView Template
SAP Enterprise Portal (SAP EP) uses iViews as the fundamental building blocks to create portal content. EP comes with many predefined iViews (templates) so portal content administrators can easily create content. BusinessObjects Integration Kit for SAP delivers an iView template for integration of Crystal Reports into the Enterprise Portal.You should not use it to integrate Web Intelligence Reports as this iView template was created specifically for Crystal Reports
To implement BOE Integration Kit iView Template solution you need:
The following procedure describes how to integrate a Crystal Report using the BOE Integration Kit iView template.
1) Create a System Landscape in EP
You must have a system landscape in order to specify the details of the BOE Web Application server that will process the iView Template to host the report, and to specify the BW system (logical system name of SAP ABAP system) to be used to validate the logon token generated by EP when the user logs on, so the user can SSO from EP to CMS to BW and view the report.
2) Create a folder
To create the portal system landscape
1. Logon to the Portal
2. Navigate to System Administration > System Configuration
3. Click System Landscape
4. Expand Portal Content folder.
5. Right-click Portal Content folder and Select New > Folder
Enter a Folder Name and Folder id, click Finish, and click OK to close the Folder wizard.
The folder name is the display name that appears in the Portal Content, the Folder ID is a unique identifier for the folder.
6. Click : Close the wizard
7. Right click the folder (in our case _Demo_SDN_System_Landscape)
3) Create a System Landscape in a folder
8. Select New > System (from template)
9. In the System Wizard, select the option SAP system using dedicated application server.
10. Click Next
11. Enter System Name, System ID (optionally you can add a System ID Prefix) and click Next
12. Click Finish
13. Make sure Open the object for editing is selected and click OK
14. From the Property Category list select Crystal Enterprise Server (this category is by default inthe SAP Portal)
15. Specify the information regarding the BOE system that hosts the report and the Web App Server that should be used to redirect the BOE iView requests. In Hostname of Crystal Enterprise Server, enter the fully qualified domain name of the BOE Web Application Server including the port. For example BOEXI31.domain.com:8080
16. In Path of Crystal Enterprise Server, enter the virtual directory where the viewer applications required for BOE iview are located. This is the virtual directory on the Web Application Server that hosts the BOE applications. By default this virtual directory is /SAP.
17. You can confirm the path of this virtual directory, for example in Tomcat by browsing to Tomcat's webapps directory. <Install Dir>/\Business Objects\Tomcat55\webapps there should be SAP directory. In Protocol of Crystal Enterprise Server choose http or https for the protocol to be used by the viewer applications. In this example we are using http.
If you don't specify fully qualified name for BOE App Server, EP may determines that not all the machines are on the same DSN domain, which causes the following error when try to view the report trough the BOE iView "Session Manager will not work§ Please check DSM log for details"
If you get this message, the SSO does not work and you will be prompted for your user ID and password.
18. From the Property Category list choose User Management. Your selections determine authentication method to use. In Authentication Ticket Type select SAP Logon Ticket and in Logon Method select SAPLOGONTICKET
19. From the Property Category list select Connector. Your selections determine the SAP ABAP system that will be validating the users. This is the system that you have defined previously as an entitlement system in CMC. Configure the values for Application Host, Gateway Host, Gateway Service, SAP client, SAP System ID (SID) and SAP System Number according to the SAP system.
To reach the Gateway Service, you need to connect on the SAP NW BI server using SAP Gui and run the transaction SMGW. You then should see a column like TP NAME and the value is the Gateway Service.
You should already have most of this information, as you needed it when configuring the same SAP ABAP system as an entitlement system in CMC.
Make sure that you specify the Application Host and Gateway host names as fully qualified names. This is mandatory for the SSO authentication.
20. Before clicking Save, ensure that you have selected the System Type: SAP_BW
21. Click Save.
22. Now you have to create a System Alias for this System Landscape. This is the name you reference when creating the iViews. From the Display dropdown, select the System Aliases option . In the Alias Name field, enter the desired name (for example BOEXI31_System_Alias) and click the Add button.
23. Close the System Alias you just created.
4) Check the SSO of your System Landscape
24. Right click System, select Open, Connection Tests and Click on Test. If the test connection is passed your SSO between your Netweaver Portal and BW is working correctly.
5) Upload (Importing BusinessObjects Enterprise iView template )
The iView template that comes with BOE Integration Kit for SAP is a portal archive file that needs to be uploaded to EP. The portal iView template delivers a BusinessObjects Enterprise focused iView that allows the content administrator to easily create new content derived from the BusinessObjects Enterprise system by configuring a preconfigured set of properties such as selecting the viewer for the content type from BusinessObjects Enterprise.
The Integration Kit for SAP includes 3 iViews:
This is a sample iview used to display alerts of Crystal Report reports. This is specific to CR reports that are designed with alerts (not described in this document).
This is a sample a iview that displays reports from BusinessObjects Enterprise as thumbnail. (not described in this document).
This iView template allows EP content administrators create new iViews of the type BusinessObjects Enterprise Report. You use the iView template to integrate Crystal Reports into EP. You should not use it to integrate Web Intelligence Reports as this iView template was created specifically for Crystal Reports
To upload the iView template:
1. Log onto the SAP Enterprise Portal.
2. Navigate to System Administration > Support .
3. Click Portal Runtime .
4. Click Administration Console .
5. Click Browse next to the Archive Uploader.
The master iView is installed by default in the following folder:
<Install Dir>/BusinessObjects Enterprise 12.0/Web Content/Enterprise12/sap/iviews/import/ep
The filename is com.businessobjects.pct.masteriview.par.
6. Select the file.
7. Click Upload .
After the successful upload the iView template is available for you to create new iViews based on the template properties.
Uploading the BOE iView template adds the "BusinessObjects Integration Kit -iView template" into the list of templates available for creating a new iView from a template.
6) Creating BusinessObjects Enterprise iViews content
Now that you have done all configuration steps you are ready to create an iView using the BOE iView template.
1. In the SAP Enterprise Portal navigate to Content Administration > Portal Content
2. Open the folder Portal Content
3. Navigate to the folder you created when creating the System Landscape (chapter C - step 2 ) in our case : Demo_SDN_System_Landscape
4. Right click the folder and select New > iView. In the New iView template wizard select iView template and click Next
5. In Template Selection, select the BusinessObjects Enterprise Integration Kit- iView template option and click Next
6. Specify an iView Name and iView id and click Next. The iView name is the display name that appears in the Portal Catalog. The iView ID is a unique identifier registered in the Portal Content Directory; this ID appears within the portal administrator environment.
7. Select the option Standard BusinessObjects Enterprise Report. Click Next
8. Select the SAP system alias (this is the alias specified when creating the System Landscape (chapter C - step 22) - in our case : BOEXI31_System_Alias
9. In the BusinessObjects Enterprise report ID specify the SI_ID of the report. The SI_ID of the report appears in the properties of the object in InfoView or CMC. In this example the SI_ID is : 7016
You can put the ID of a Crystal Document or Webintelligence Document ....
If you specify an SI_ID that does not exist, later when viewing the iView you will just get a blank page without any errors
10. In the Application parameters, specify the cms using the following format:
cms_name=<CMS>:<PORT> For example: cms_name=BOEXI31:6400
11. In the Viewer Application Page, specify reportView.do
12. Select the BusinesObjects Enterprise Viewer and select the option to view the report on demand or the last instance. Click Next
13. In the Summary page, select the option Open for editing when wizard completes. Click Finish
14. Click Preview to test your iView.
15. You can now add this iView template to any page in the portal. (look at the chapter F,G)