SAP BusinessObjects Integration Option for Microsoft SharePoint · PDF fileThe integration...

SAP Integration Option for Microsoft SharePoint SoftwareDocument Version: 4.0 Support Package 9 - 2014-02-17

SAP BusinessObjects Integration Option for Microsoft SharePoint Software Administrator Guide

Table of Contents1 Welcome to the Integration Option for Microsoft SharePoint software. . . . . . . . . . . . . . . . . . . . . .41.1 About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1.1 Document history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Who Should Read this Guide?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 What is the Integration Option for Microsoft SharePoint Software?. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Configuring the Integration Option for Microsoft SharePoint software. . . . . . . . . . . . . . . . . . . . . .62.1 Understanding the Template Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Configuring the web.config Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 Enabling Logging and Tracing in the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Creating Sites Enabled for Accessing SAP BusinessObjects Content Within SharePoint . . . . . . . . . . . . .13

2.4.1 Creating sites using the SAP BusinessObjects Site Definition template. . . . . . . . . . . . . . . . . . 132.4.2 Creating sites using a SharePoint site template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4.3 Configuring site collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

2.5 Configuring Web Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5.1 Adding Web Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.5.2 Connecting Web Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.5.3 Adding the IOMS-Display Search Results web part to a blank site. . . . . . . . . . . . . . . . . . . . . . 16

2.6 Enabling anonymous access on IIS for AnalyticalReporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.7 Installing a host header for SharePoint 2010. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.8 Installing a server farm for SharePoint 2010. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

3 Deploying the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2 Configuring the SAP BusinessObjects Business Intelligence platform. . . . . . . . . . . . . . . . . . . . . . . . . .22

3.2.1 Configuring the software for LDAP Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.2 Windows AD authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.3 Security and Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293.2.4 User and Group Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.2.5 Configuring SSL on IIS 6.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.2.6 Configuring SSL on IIS 7.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.7 Configuring ISA 2006 for Reverse Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.3 Configuring the Optional BI Platform Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.3.1 Specifying a Server for Processing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.3.2 Specifying Parameter Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.4 Scheduling and Scaling Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.4.1 Exporting Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.4.2 Data Source Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.4.3 Report Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2 © 2014 SAP AG or an SAP affiliate company. All rights reserved.SAP BusinessObjects Integration Option for Microsoft SharePoint Software Administrator Guide

Table of Contents

3.4.4 Performance Improvement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.5 Crystal Report Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

SAP BusinessObjects Integration Option for Microsoft SharePoint Software Administrator GuideTable of Contents © 2014 SAP AG or an SAP affiliate company. All rights reserved. 3

1 Welcome to the Integration Option for Microsoft SharePoint software

1.1 About this Guide

This guide details configuration, deployment, and troubleshooting information for the integration Option for Microsoft SharePoint software.

1.1.1 Document history

The following table provides an overview of the recent history of this document:

Version Date Description

SAP BusinessObjects integration option for Microsoft SharePoint software 4.0 Support Package 2

August 3, 2011 First release of this guide

SAP BusinessObjects integration option for Microsoft SharePoint software 4.0 Feature Package 3

March 16, 2012 The following topics were added to this guide:

● "Enabling Logging and Tracing in the Software"

● "Enabling anonymous access on IIS for AnalyticalReporting"

● "Configuring the web.config Tags"

SAP BusinessObjects Integration Option for Microsoft SharePoint Software 4.0 Support Package 9

January 17, 2014 The following topics were added to this guide:

● "Installing a host header for SharePoint 2010"

● "Installing a server farm for SharePoint 2010"

● "Configuring site collection"

A note was added to the following topics:

● "Creating sites using a SharePoint site template"

● "Configuring SSL on IIS 6.0"● "Configuring SSL on IIS 7.5"● "Adding the IOMS-Display Search

Results web part to a blank site"● "Modifying the web.config file of the

extended web application for LDAP"


Welcome to the Integration Option for Microsoft SharePoint software

1.2 Who Should Read this Guide?

This guide is intended for the following audiences:

● Administrators who want to know how to configure the SAP BusinessObjects Business Intelligence (BI) platform to work with the integration option for Microsoft SharePoint software

● Portlet developers who want to know how to create customized portlets

Familiarity with the Microsoft SharePoint portal server is essential, as is a good working knowledge of both Crystal Reports and the SAP BusinessObjects BI platform.

1.3 What is the Integration Option for Microsoft SharePoint Software?

The integration option for Microsoft SharePoint software provides state-of-the-art integration of Business Intelligence content with Microsoft SharePoint portal. This software runs in your Web Browser and allows you to access the SAP BusinessObjects BI Platform content through the Microsoft SharePoint environment.

The main objective of this software is to eliminate the need for a separate platform or portal for accessing Business Intelligence data, for users of Microsoft SharePoint.

The software accomplishes the above objective in the following ways:

● It provides you with an out-of-the-box site template having the look,feel and behavior similar to that of Microsoft SharePoint. After deploying the software on your system, if you have the administrative rights, you can readily use this template to create a dedicated site for accessing the SAP BusinessObjects Business Intelligence(BI) platform content from within the Microsoft SharePoint environment.

● It gives you access to a Web Part gallery consisting of modular units of functionality called Web Parts. As a user holding administrative rights, you can configure these SAP BusinessObjects Web Parts to any site created within Microsoft SharePoint. This way, a SharePoint site can also be enabled for accessing or managing the SAP Businessobjects BI platform content based on the extent of requirements.

● It provides you with end-to-end capabilities such that you can perform all actions required to interact with the BI platform content conveniently and exhaustively while remaining within the SharePoint environment.

The different types of Business Intelligence objects include Crystal Reports documents, Web Intelligence documents, Publications, Xcelsius reports, Advanced Analysis Documents, Portable Data Format documents, Microsoft Excel spreadsheets, Microsoft Word files, program files, object packages and other reports.

For more information about SAP BusinessObjects Business Intelligence (BI) Platform , refer to the SAP BusinessObjects Business Intelligence Platform Administrator Guide, which is included with the BI platform. For more information about Crystal Reports, see the Crystal Reports User' Guide, which is included with Crystal Reports.

SAP BusinessObjects Integration Option for Microsoft SharePoint Software Administrator GuideWelcome to the Integration Option for Microsoft SharePoint software © 2014 SAP AG or an SAP affiliate company. All rights reserved. 5

2 Configuring the Integration Option for Microsoft SharePoint softwareThis chapter describes how to configure the integration option for Microsoft SharePoint software for specific SharePoint deployments. For more information on general administrative tasks, refer to the documentation of Microsoft Office SharePoint server (2007 or 2010 based on your deployment).

2.1 Understanding the Template Configuration File

Every time a website is created by using the SharePoint solution, SharePoint uses an XML configuration template file to generate the <web.config> file entries.

This template also specifies the SAP BusinessObjects BI platform system information that you entered during installation. Hence, if you change the system on which the BI platform Central Management Server (CMS) is located, you need to update this XML file. In particular, you need to update the value for the BusinessObjects Enterprise Central Management Server key to ensure that the value matches the name of the CMS.

During installation, the integration option for Microsoft SharePoint software installation program updates the web.config file that is located in the standard root space of the SharePoint web server(..\InetPub\wwwroot\wss\VirtualDirectories\<portnumber>). The installation program also creates a backup of the original web.config file, known as backup web.config.This file is stored in the installation directory.

By default the SharePoint site is hosted on Port 80 and web.config file is located in the path (C:\inetpub\wwwroot\wss\VirtualDirectories\80).

NoteThe web.config file for Microsoft SharePoint 2007 and SharePoint 2010 are maintained separately on the individual servers but the tags added by the integration option software during installation are almost common to both.

2.2 Configuring the web.config Tags

As an administrator, you can configure some specific tags in the web.config file to define behaviour of features provided by the integration option software.

These configurable tags are mentioned below:

Document Viewer




Configuring the Integration Option for Microsoft SharePoint software

<add key="BusinessObjects Enterprise SharePoint InfoView Voyager Viewer Url" value="http//<IP address of the CMS>/BOE/BI/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=%id%&token=%token%&lang=%lang%" />

<add key="BusinessObjects Enterprise SharePoint InfoView Document Viewer Url" value="/_layouts/OpenDocument/opendoc/openDocument.aspx?sKind=%type%&sIDType=CUID&iDocID=%id%&token=%token%&lang=%lang%" />

<add key="boe.trustguard.enable" value="true" /> </appSettings>

Crystal Viewer

<CrystalReports><add key="path.dhtmlViewer" value="/crystalreportviewers" /></CrystalReports>

Infoview App Settings

<InfoViewAppSettings><add key="cms.default" value="localhost" /><add key="cms.visible" value="false" /<add key="authentication.default" value="secEnterprise" /><add key="authentication.visible" value="false" /><add key="homepage.default" value="/listing/Home.aspx" /><add key="disable.locale.preference" value="false" /><add key="siteminder.enabled" value="false" /><add key="siteminder.authentication" value="secLDAP" /><add key="vintela.enabled" value="false" /><add key="sso.enabled" value="false" />

<add key="logontoken.enabled" value="true" /><add key="persistentcookies.enabled" value="true" /><add key="trusted.auth.user.retrieval"value="" />

<add key="trusted.auth.user.param" value="" />

<add key="trusted.auth.shared.secret" value="" />

<add key="config.logon.service.context" value="" /><add key="config.logon.service.url" value="" />

<add key="config.timeout.service.context" value="" /><add key="config.timeout.service.url" value="" />



<add key="proxy.contextpaths" value=""/><add key="window.properties.default" value="fullscreen=yes,location=no,scrollbars=yes,menubars=no,toolbars=no,resizable=yes"/><add key="customized.help.location" value="" /><add key="SMTPFrom" value="true" /><add key="app.name" value="BusinessObjects InfoView" /><add key="app.name.short" value="InfoView"/><add key="app.name.greeting" value="BusinessObjects" /><add key="app.supportmygroups" value="false"/><add key="app.supportlocreports" value="false" /><add key="app.ondemandlink" value="http://information.ondemand.com/istore/" />

<add key="app.ondemand.toolbar.button.enabled" value="false" /><add key="app.ondemand.textlink.enabled" value="true" /><add key="max.tree.children.threshold" value="200" /><add key="url.exit" value="" /><add key="url.error" value="common/error.aspx" />




<add key="schema.global.prefix" value="NONE" /><add key="schema.prefix" value="*" />

<add key="schema.global" value="/res/general" /><add key="schema.default" value="/res/schema.blue" /><add key="img.obj.default" value="ce_generic_object.gif" /><add key="img.list.heading.separator" value="separator_grey_title_bar.gif" /><add key="img.list.plus" value="collapse.gif" /><add key="img.list.minus" value="expand.gif" /><add key="img.banner.left" value="*IV_left_topbanner.gif" /><add key="img.banner.right" value="*IV_right_topbanner.gif" /><add key="img.banner.logo" value="*login_banner_center.gif" />

<add key="img.sort.arrowdown" value="sort_desc.gif" /><add key="img.sort.arrowup" value="sort_asc.gif" />

<add key="img.panel.titlebar" value="*panel_title_bar_fill.gif" /><add key="img.panel.footerbar" value="*panel_footer_bar_fill.gif" /><add key="img.panel.new.window" value="*new_window.gif" /><add key="img.panel.new.window.hover" value="*new_window_hover.gif" /><add key="img.panel.arrowdown" value="*arrow_down.gif" /><add key="img.panel.arrowdown.hover" value="*arrow_down_hover.gif" /><add key="img.panel.arrowleft" value="*arrow_left.gif" /><add key="img.panel.arrowleft.hover" value="*arrow_left_hover.gif" /><add key="img.panel.arrowright" value="*arrow_right.gif" /><add key="img.panel.arrowright.hover" value="*arrow_right_hover.gif" />

<add key="img.panel.arrowup" value="*arrow_up.gif" /><add key="img.panel.arrowup.hover" value="*arrow_up_hover.gif" /><add key="img.panel.close" value="*close_panel.gif" /><add key="img.panel.close.hover" value="*close_panel_hover.gif" /><add key="img.panel.maximize" value="*maximize.gif" /><add key="img.panel.maximize.hover" value="*maximize_hover.gif" /><add key="img.panel.minimize" value="*minimize.gif" /><add key="img.panel.minimize.hover" value="*minimize_hover.gif" /><add key="img.panel.restore" value="*restore_down.gif" /><add key="img.panel.restore.hover" value="*restore_down_hover.gif" /><add key="img.panel.tearoff" value="*tear_off.gif" /><add key="img.panel.tearoff.hover" value="*tear_off_hover.gif" />

<add key="img.toolbar.calendar" value="toolbar/calendar.gif" /><add key="img.toolbar.home" value="toolbar/home.gif" /><add key="img.toolbar.refresh" value="toolbar/refresh.gif" />

<add key="img.error" value="infoview_error.gif" />

<add key="img.home.myinfoview" value="MyInfoView.gif" /><add key="img.home.favefolder" value="favfolder.gif" /><add key="img.home.folder" value="folder.gif" /><add key="img.home.help" value="help.gif" /><add key="img.home.inbox" value="inbox.gif" />



<add key="img.home.preferences" value="preferences_infoview.gif" /><add key="img.home.ondemand" value="ondemand.gif" />

<add key="localizationContext" value="com.businessobjects.infoview.ApplicationResources"/>

<add key="distributable" value="true" />



<add key="path.rightFrame" value="1" /></InfoViewAppSettings><InfoViewAppActionMapping><add key="logon" value="/logon/logon.aspx" /><add key="logonForm" value="/logon/logon.aspx" /><add key="logonService" value="/logon/logon.aspx" /><add key="timeout" value="/logon/logon.aspx" />

<add key="logoff" value="/logon/logoff.aspx" /><add key="main" value="/listing/main.aspx" /><add key="appService" value="/common/appService.aspx" /><add key="help" value="/help/helpredir.aspx" /></InfoViewAppActionMapping></configuration>

Exclusions

There are certain object types in the BI platform (BOE) repository that are not supported by the integration option for Microsoft SharePoint software. However, once users logon to SharePoint and connect to the CMS, all object types may appear on their sites. If you do not want the unsupported object types to appear on the BusinessObjects site, update the following tag in the web.config file:

<add key="BusinessObjects Enterprise Object Exclusions" value="<exc_Obj1>,<exc_Obj2>,<exc_Obj3>" />

where {exc_Obj1, exc_Obj2...} are the objects you want to exclude. For example,

<add key="BusinessObjects Enterprise Object Exclusions" value="MON.Probe,DFS.Parameters,PlatformSearchScheduling,Analytic" />


2.3 Enabling Logging and Tracing in the Software

To enable logging and tracing for security and monitoring reasons, you need to perform certain configuration settings by making updates to the web.config file.

Perform the following steps:

1. Add the following tag and attribute values in the <configSections> of web.config:

<section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

2. Add the following tag and attributes in the <appSettings> of web.config.

<add key="bobj.logging" value="True"/><add key="bobj.logging.log4net.override" value="[Physical path]\\Logs\\[FileName].xml"/>

3. Create an XML file with the same name as the one that you have specified in FileName above. Add the below content in this file:

<?xml version="1.0" encoding="utf-8" ?><log4net> <root> <appender name="LogAppender" type="log4net.Appender.FileAppender" > <file value="E:\Logs\iPointLog.log"/>  <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date[%thread] %-5level %logger %class - %m%n" /> </layout> </appender> <level value="FATAL"/> <level value="WARN"/> <appender-ref ref="LogAppender"/> </root> </log4net>

1. For a developer trace file, the <value> attribute of <level> tag can have the following possible values:

INFODEBUGERROR

2. For an admin log file, the <value> attribute of <level> tag can have the following possible values:

FATALWARN

3. If you want the <value> attribute of <level> tag to have all possible values (including those for the developer trace and admin log), then you can set <level value="ALL"/>. If you want only specific values for the attribute, then you can add them individually as illustrated in the above example.

4. As of now, the logging feature is only implemented in the Universal Repository Explorer(URE) of the software. (URE is a custom control that is used in implementing certain views of the User actions web page of an SAP BusinessObjects site).Essentially, this means that logging will occur only when you perform certain actions, such as setting scheduling options for an object (for example Enterprise Recipients, Dynamic Recipients for a publication),



viewing History of an object, assigning Categories to an object, sending an object to Inbox etc.). All these actions involve the URE in different views of the User actions web page.Logging will be implemented for all the Web Parts in future.

2.4 Creating Sites Enabled for Accessing SAP BusinessObjects Content Within SharePoint

Based on your requirement, you can create additional SharePoint sites that have access to the SAP BusinessObjects Business Intelligence(BI) platform content. You can do so in one of the following ways:

● By creating a site using any of the SharePoint templates and adding the BusinessObjects Web Parts to the sites pages.

● By creating a site using the <SAP BusinessObjects Site Definition > template that directly enables you to access and manage the BI platform data.

2.4.1 Creating sites using the SAP BusinessObjects Site Definition template

Use the SAP BusinessObjects Site Definition template to create a ready-to-use site. The template handles all basic activities required to view, manage, and interact with Business Intelligence (BI) content from a SharePoint environment.

Web parts are essential to working with objects in BI platform from SharePoint. The Site Definition template consists of the following web parts:

● IOMS-Advertisement● IOMS-Content Explorer● IOMS-Recent Searches● IOMS-Recently Viewed● IOMS-Display Search Results

The Site Definition template appears in the “SAP BusinessObjects” category of templates available for creating a new SharePoint site. After selecting the template, you can specify a unique URL for the site.


Figure 1: SharePoint 2010

2.4.2 Creating sites using a SharePoint site template

After using a SharePoint template to create a site on a SharePoint portal, you can add SAP BusinessObjects web parts to the site.

After adding web parts, before you can work with Business Intelligence platform content, you must activate the SAP BusinessObjects site features of the integration option for Microsoft SharePoint software.

NoteDo not configure multiple SharePoint sites with the same name (even with different protocols) on the same machine. It is possible to enter the names, but the integration option for SharePoint software installation will fail. For example, do not create one SharePoint site called http://my_site and another site called https://my_site (same name but encrypted) on one machine.

2.4.2.1 Activating the BusinessObjects Features of a Site

To activate the BusinessObjects features of your site, perform the following steps:

1. On the Home page of the site, access Site Actions>Site Settings>Site Features . On the Site Features page, you will see a couple of BusinessObjects features.

2. Click the Active button against the feature you want to activate. To deactive the feature, click Deactivate . The following table summarizes the site features and their purpose:



Feature Significance

SAP BusinessObjects Logon Activate this feature to connect to the Central Management Server(CMS). This feature is mandatory to activate as you need to connect to the CMS for working with the BI platform content.

SAP BusinessObjects Log Off Activate this feature to log off from the CMS. This disconnects you from access to the BI platform content.

SAP BusinessObjects Platform Action Pages Activate this feature to perform various actions on the reports or objects like setting object properties, scheduling, viewing history, assigning a category, sending etc.

SAP BusinessObjects Preferences Settings Enable this feature to be able to set preferences like password, timezone and locale, date and time settings, Web Intelligence and Crystal Report preferences etc.

Having activated the mandatory and chosen features, you can now access and work with the BI platform content through the Web Parts added to your SharePoint site.

NoteThese features are already activated if you use the out-of-the-box solution called SAP BusinessObjects Site Definition template provided by the integration option, to create your site in SharePoint.

2.4.3 Configuring site collection

You must configure site collection for each SharePoint site you create. Use the Team Site template to configure site collection.

1. On the Create Site Collection page, enter a title in the Title box and a description in the Description box.2. Beside Web Site Address, select / in the URL list.3. Beside Template Selection, select Team Site on the Collaboration tab.4. Beside Primary Site Collection Administrator, enter <SharePointMachine>\administrator in the User

name box, and click OK.<SharePointMachine> is the name of the machine where SharePoint is installed.A Top-Level Site Successfully Created box appears, confirming that the new site was created successfully.

You must configure the DNS server before you can access the site.

2.5 Configuring Web Parts

This section describes how to add various Web Parts to a SharePoint site page and connect them to the IOMS-Content Explorer Web Part.


2.5.1 Adding Web Parts

You can modify the appearance and functionality of a web page in the SharePoint system by adding Web Parts.

To add a Web Part, complete the following steps:

1. Open the web browser and navigate to the page in the SharePoint portal where you want to add the Web Part.Select Edit Page from the Site Actions drop-down list. The page reloads in the Edit mode.

2. Click Add a Web Part.The Add Web Parts -- Web Page Dialog window appears.

3. From the list of galleries, select the predefined Web Part that you want to add, and click Add.The Web Part is added to the SharePoint portal.

NoteThe Web Parts provided by the integration option can be found within the <SAP BusinessObjects >section of the Add Web Parts -- Web Page Dialog.

2.5.2 Connecting Web Parts

When you configure SAP BusinessObjects Web Parts on any page of a SharePoint site, you might need to connect them with other Web Parts to conveniently view and interact with Business Intelligence(BI) platform data.

To connect any Web Part to the IOMS-Content Explorer, complete the following steps:

NoteYou can connect to Web Parts only in the Edit mode.

1. In the IOMS-Content Explorer Web Part, click edit.2. Select Connections > Send RepositoryExplorer To.

All the Web Parts that have been added to the SharePoint page get listed.3. Click the Web Part you want to connect to the IOMS-Content Explorer Web Part.

The selected Web Part is connected to the IOMS-Content Explorer Web Part.For example, you can connect various Viewer Web Parts like IOMS-Xcelsius Viewer, IOMS-Crystal Report Viewer, IOMS-Analytical Report Viewer to the IOMS-Content Explorer Web Part.

2.5.3 Adding the IOMS-Display Search Results web part to a blank site

You can view SAP BusinessObjects content search results and SharePoint search results on a site that was created using the SharePoint Team Site template..

Before you add IOMS-Display Search Results to a blank site, the following tools must be installed:

● Microsoft .NET Framework 3.5



● Microsoft Internet Information Services (IIS) 7

In addition, site collection must be configure for the blank site.

Before you can view SAP BusinessObjects content search results and SharePoint search results in a site created using the blank site template, you must add the IOMS-Display Search Results web part to the site.

1. Create a blank SharePoint site page.For example, create a page called Bobjsrch.aspx

2. Add the IOMS-Display Search Results web part and the Microsoft Search Core Results web part to the new page.

3. Select Site Actions Site Settings , and click Search settings under Site Collection Administration.The Site Collection Search Results Page box appears on the page that appears.

4. In the Site Collection Search Results Page box, enter /SitePages/Bobjsrch.aspx5. Perform a search on any web page on the site.

The page appears, showing all search results retrieved from the BusinessObjects repository and the SharePoint repository.

2.6 Enabling anonymous access on IIS for AnalyticalReporting

To create or edit a Web Intelligence document from the Microsoft SharePoint portal, you need to enable the anonymous access on Internet Information Services (IIS) for AnalyticalReporting.

1. Go to Start > Control Panel > Administrative Tools > IIS Manager or in the command prompt, type inetmgr to open IIS manager.

2. Navigate to Sites > SharePoint Site <port> > _layouts > AnalyticalReporting.3. In Features view, double-click Authentication.4. In the Authentication page, select Anonymous Authentication.5. In Actions pane, click Enable.

2.7 Installing a host header for SharePoint 2010

Before you install a host header for SharePoint 2010, all SharePoint 2010 prerequisites must be met, and the following tools must be installed:

● Microsoft .NET Framework 3.5● Microsoft Internet Information Services (IIS) 7● Microsoft SQL Server 2008● SharePoint Server 2010


1. In Server Manager, click Roles, click Add Roles, and select the DNS Server check box in the Select Server Roles window of the Add Roles Wizard.


2. Using the SharePoint Team Site template, create a top-level site for the default SharePoint web application on port 80.

3. In SharePoint 2010 Central Administration, create a web application for NT LAN Manager (NTLM) claim-based authentication:a) On the Create New Web Application page, beside Authentication, select Classic Mode Authentication.b) Beside IIS Web Site, select Create a new IIS web site, and enter sharepoint -<<port>> in the Name

box.For example, enter sharepoint -19369<<port>> is the port where you are creating the web application.

c) In the Port box, enter the port number that you entered in step 3b.For example, enter 19369

d) In the Host Header box, enter the host header name for the web application.For example, enter ioms.<<HostHeader>>.comThe Path box displays C:\inetpub\wwwroot\wss\VirtualDirectories\<<HostHeader>>:<<port>>.

e) If necessary, modify the path to the web application in the Path box.f) Beside Security Configuration, select NTLM under Authentication provider.

Beside Public URL, the URL box displays http://<<HostHeader>>:<<port>>.g) If necessary, modify the URL to the web application in the URL box, but leave other options under

Authentication provider set to the default values.h) Beside Application Pool, select Create new application pool.

The Application pool name box displays SharePoint - <<HostHeader>>:<<port>>.i) If necessary, modify the name of the application pool in the Application pool name box.j) Under Select a security account for this application pool, select Predefined, select Network Service in the

list, and click OK.4. Using the Team Site template, create site collection:

a) On the Create Site Collection page, enter a title in the Title box and a description in the Description box.b) Beside Web Site Address, select / in the URL list.c) Beside Template Selection, select Team Site on the Collaboration tab.d) Beside Primary Site Collection Administrator, enter <<SharePointMachine>>\administrator in the

User name box, and click OK.<<SharePointMachine>> is the name of the machine where SharePoint is installed.

A Top-Level Site Successfully Created box appears, confirming that the new site was created successfully. You must configure the DNS server before you can access the site.

5. Configure the DNS server:a) In DNS Manager, under <<SharePointMachine>>, right-click Forward Lookup Zones and select [new

zone].<<SharePointMachine>> is the name of the machine where SharePoint is installed.

b) Select [primary zone], enter the host header name you entered for the web application in the Zone name box, and click Next until finished.

c) In a text editor, open the hosts file on the SharePoint machine, and map the SharePoint machine's Internet Protocol (IP) address to the host header you entered for the web application.

d) In the Windows Registry Editor, locate and open HKLM\System\CurrentControlSet\Con trol\Lsa, add DWORD (32-bit) value for DisableLoopbackCheck and set the value to 1.



e) In Internet Information Servers (IIS) Manager, right-click Sharepoint - <<HostHeader>>:<<port>> and select Bindings.

f) In the Site Bindings dialog box, click Edit.g) In the Edit Site Binding dialog box, enter the SharePoint machine's IP version 4 (IPv4) address in the IP

address box.h) Restart the SharePoint machine.i) Because an Internet site exists for http://<<HostHeader>>:<<port>>, disable the proxy server in the

Microsoft Internet Explorer Local Area Network (Settings) dialog box.6. Go to the http://<<HostHeader>>:<<port>> URL.

The new site home page appears. SharePoint 2010 is ready for the integration option for SharePoint software installation.

7. Install the SAP BusinessObjects integration option for SharePoint software on the SharePoint web application:a) In the SAP Integration for Microsoft SharePoint 4.1 setup dialog box, select the http://

<<SharePointMachine>>:<<port>> [SharePoint - <<HostHeader>>:<<port>>] check box.b) In a text editor, open the hosts file on the SharePoint machine, and add IP-host mapping for the BI

platform machine.This ensures that the integration option for SharePoint installation will set the Central Management Server (CMS) name and the OpenDocument base URL from the hosts file.

8. After installing the integration option for SharePoint software on the http://<<SharePointMachine>>:<<port>> IIS site, set up the SharePoint web application using the host header:

a) In SharePoint Central Administration, select System Settings Farm Management Manage farm solutions , and click infoview.wsp.The Solutions Properties page appears. Note that the integration option for SharePoint is not deployed to the http://<<HostHeader>>:<<port>> web application.

b) Click Deploy Solution to deploy infoview.wsp to http://<<HostHeader>>:<<port>>.c) On the Deploy Solution page, beside Deploy To, select http://<<HostHeader>>:<<port>> in the

Choose a Web application to deploy this solution list.The Solutions Properties page appears, showing that the integration option for SharePoint is deployed to the http://<<HostHeader>>:<<port>>/; http://<<SharePointMachine>>:<<port>>/; http:<<SharePointMachine>>/ web application.

9. Open a command window, and enter the following command:

call "C:\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\14\BIN\stsadm.exe" -o deploysolution -name "InfoView.wsp" -allowgacdeployment -immediate -force -url http://<HostHeader>:<port>

10. Go to http://<<HostHeader>>:<<port>>, and create a new SharePoint site:

a) On the New SharePoint site page, enter a title in the Title box and a description in the Description box.b) Beside Web Site Address, enter the URL to the new site in the URL name box.c) Beside Template Selection, select SAP BusinessObjects Site Definition on the SAP BusinessObjects tab,

and click Create.The new site home page is created.

11. On the client machine, open the host file, and add the following text: [<SHAREPOINT machine IPv4 ip> <<HostHeader>>]


When opening the http://<<HostHeader>> site in a browser, you will be prompted to enter SharePoint-site administrator credentials.

2.8 Installing a server farm for SharePoint 2010

Before you install a server farm for SharePoint 2010, make a note of the physical architecture, logical architecture, specifications, account user names and passwords, license keys, and so on that you will need. In addition, the following tools must be installed:

● Microsoft .NET Framework 3.5● Microsoft Internet Information Services (IIS) 7


1. Run the setup file for the integration option for SharePoint.2. In the SharePoint installation wizard, under Install, click Install software prerequisites.

The Microsoft SharePoint 2010 Products Preparation Tool Welcome window appears, listing the prerequisites that will be installed.

3. Review the list of the prerequisites, and remove any previously installed items before continuing with prerequisite installation.For example, if you do not uninstall Windows Identity Foundation before installing prerequisites, the installation wizard automatically terminates.

4. In the Welcome window, click Next to start installing prerequisites.

NoteIf any prerequisites fail to install, you must correct the issue before continuing the installation, even if the wizard allows you to continue.

5. In the License Terms for software products window, accept the terms of the license agreement, and click Next.A status bar appears, showing the progress of prerequisite installation. When all prerequisites are installed, the Installation Complete window appears. Prerequisites not installed have "(no action taken)" appended to the name.

6. Click Finish to close the Microsoft SharePoint 2010 Products Preparation Tool wizard and to start the Microsoft SharePoint Server 2010 installation wizard.

7. In the Enter your Product Key window, type your license key in the box, and click Continue.8. In the Read the Microsoft Software License Terms window, select the check box to accept the terms, and click

Continue.9. In the Choose the installation you want window, click Server Farm.10. In the Server Type window, select Complete - Install all components. Can add servers to form a SharePoint

farm, and click Install Now.An Installation Progress window appears, showing the progress of the installation.

11. If the server farm includes more than one server, perform steps 1 to 10 on the remaining servers.12. On the server that will handle SharePoint Central Administration, start the SharePoint Products Configuration

Wizard.13. In the Run Configuration Wizard window, select the check box, and click Close.



14. In the Welcome to SharePoint Products window, click Next.As part of server farm configuration, some services may need to be stopped or reset and restarted.

15. If a message about stopping and restarting services appears, click Yes to continue with the configuration wizard.

16. In the Connect to a server farm window, perform one of the following actions:

○ If this is the first server in the farm, select Create a new server farm, and click Next.○ If one server is already in farm, select Connect to an existing server farm, and click Next.

17. In the Specify Configuration Database Settings window, perform the following actions:a) In the Database server box, type the database server name.b) In the Database name box, type the database name.c) In the Username box, type the database-access-account user name.d) In the Password box, type the database-access-account password, and click Next.

18. In the Specify Farm Security Settings window, type the passphrase in the Passphrase box and in the Confirm passphrase box, and click Next.The SharePoint passphrase secures farm configuration data and is required for adding servers to the farm.

19. In the Configure SharePoint Central Administration Web Application window, type a port number in the Specify port number box, or accept the random number assigned by the wizard.

20. Under Configure Security Settings, select NTLM or Negotiate (Kerberos), and click Next.21. In the Completing the SharePoint Products Configuration Wizard window, review the configuration settings

that will be applied, make corrections as needed, and click Next.The Configuring SharePoint Products window appears, showing the progress of the configuration. When the configuration is complete, a Configuration Successful window appears.

22. Click Finish.23. In SharePoint Central Administration, on the Configure your SharePoint farm page, click Start the Wizard to

open the Farm Configuration Wizard.The wizard configuration uses the farm account for all service applications. To change the application pool and service accounts under which specific service applications run, create managed accounts, and then use the Services on Server or Service Applications window to make the changes.When the configuration is complete, a completion window appears.

24. Click Finish.


3 Deploying the Software

3.1 Overview

This chapter describes how to configure the SAP BusinessObjects Business Intelligence(BI) Platform to work with the integration option for Microsoft SharePoint software. It also discusses recommendations for scheduling reports and setting properties to improve the effectiveness of reports for users. To perform these activities, you must be familiar with administering and using the BI platform.

For more information about the BI platform, see the SAP BusinessObjects Business Intelligence Platform Administrator' Guide.

3.2 Configuring the SAP BusinessObjects Business Intelligence platform

When you first install the integration option for Microsoft SharePoint, you must configure or update certain settings within the SAP BusinessObjects BI platform to optimize your deployment.

3.2.1 Configuring the software for LDAP Authentication

You must install MOSS 2007 and LDAP Server. You must also create groups and users in LDAP.

A SharePoint web application must be created on MOSS 2007. If MOSS 2007 and LDAP are on different systems, then you must ensure that these two systems can communicate with each other.

To configure the integration option software for Windows LDAP, complete the following steps:

1. Log into the SharePoint 3.0 Central Administration site.2. Click the Application Management tab.3. Under SharePoint Web Application Management, click the Create or extend Web Application link.4. Click extend web application.5. Specify the port name, host name, and so on.6. From the Zone drop-down list, select Custom, and click Create.

The extended application is created.7. Click Application Management.8. Under Application Security, click the Authentication Providers link.9. In the Authentication Providers page, click the Zone link.10. In the Edit Authentication page, select Forms as the authentication type.11. Enter the membership provider name in the Membership Provider Name field.

The LDAP membership name refers to the name of LDAP membership provider that you specify in the <web.config> file.


Deploying the Software

12. Enter the role manager name in the Role Manager Name field.13. Select No for the Enable Client Integration? option.14. Click Save.

The <Authentication mode> in the <web.config> file of the extended web application is modified to Forms.

3.2.1.1 Modifying the web.config file of the extended web application for LDAP

Before you modify the web.config file of the extended web application, the following tools must be installed:

● Microsoft .NET Framework 3.5● Microsoft Internet Information Services (IIS) 7

In addition, site collection must be configured for the site.

1. In SharePoint Central Administration, from Internet Information Server (IIS), open the web.config file.

2. In the web.config file, add the following lines between the </system.web> tag and the <runtime> tag:

<connectionStrings><add name="LDAPConnectionString"connectionString="ldap://bo-test.product.businessobjects.com:35020/dc=product,dc=businessobjects, dc=com"/></connectionStrings>

3. In the web.config file, add the following membership provider details between the </authorization> tag and the <httpModules> tag:

<membership defaultProvider="LDAPMembership"><providers><add name="LDAPMembership"type="Microsoft.Office.Server.Security.LDAPMembershipProvider,Microsoft.Office.Server,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c"server="bo-test"port="35020"useSSL="false"userDNAttribute="dn"userNameAttribute="uid"userContainer="dc=product,dc=businessobjects,dc=com"userObjectClass="top"useDNAttribute="false"userFilter="(ObjectClass=top)"scope="Subtree"otherRequiredUserAttributes="sn,givenname,cn"/></providers></membership>

NoteValues specified may differ, depending on how users were created in LDAP.

4. Open the web.config file of the extended web application, and add the following lines:

<roleManager defaultProvider="LDAPRoleProvider"enabled="true" cacheRolesInCookie="true"

SAP BusinessObjects Integration Option for Microsoft SharePoint Software Administrator GuideDeploying the Software © 2014 SAP AG or an SAP affiliate company. All rights reserved. 23

cookieName=".PeopleDCRole"><providers><add name="LDAPRoleProvider"type="Microsoft.Office.Server.Security.LDAPRoleProvider,Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,PublicKeyToken=71E9BCE111E9429C" server="bo-test" port="35020"useSSL="false"groupContainer="dc=product,dc=businessobjects,dc=com"groupNameAttribute="cn"groupMemberAttribute="uniquemember"userNameAttribute="uid"dnAttribute="dn"useUserDNAttribute= "false"groupFilter="(ObjectClass=top)"scope="Subtree" /></providers></roleManager>

5. Open the web.config file of the SharePoint Central Administration site, add the following role manager details between the </authorization> tag and the <httpModules> tag:

<roleManagerdefaultProvider="AspNetWindowsTokenRoleProvider"enabled="true" cacheRolesInCookie="true"cookieName=".PeopleDCRole"><providers><add name="LDAPRoleProvider"type="Microsoft.Office.Server.Security.LDAPRoleProvider,Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,PublicKeyToken=71E9BCE111E9429C"server="bo-test"port="35020"useSSL="false"groupContainer="dc=product,dc=businessobjects,dc=com"groupNameAttribute="cn"groupMemberAttribute="uniquemember"userNameAttribute="uid"dnAttribute="dn"useUserDNAttribute= "false"groupFilter="(ObjectClass=top)"scope="Subtree" /></providers></roleManager>

6. Restart IIS.7. Log on to SharePoint Central Administration.8. On the Application Management tab, click Site Collection Administrators.9. Add any LDAP user as the primary administrator, and confirm that the user is identified.10. Log on to the SharePoint site as the site administrator with LDAP user rights.

3.2.1.2 Adding Users and Groups to the Web Applications

A user who logs into the web application as the site administrator can perform all administrative tasks, including creating and deleting users and user groups. However, other LDAP users can log in only if they have already been added to the web application.

To add users and user groups to the web application, complete the following steps:



1. Log into the web application as the site administrator.

2. Select Site Settings People and Groups , and add the LDAP groups or users in the Add the LDAP Groups or Users field, as follows:

○ To add a group, use the following syntax: ldaproleprovidername: groupname○ To add a user, specify the user name.

3.2.1.3 Logging into the Extended Application as an LDAP User

To log into the extended application as an LDAP user, complete the following steps:

NoteAll the steps must be performed manually in IIS.

1. Enable Integrated Authentication, and disable Anonymous logon.

NoteEnsure that you have enabled LDAP authentication in CMS, and test whether the LDAP user can log into InfoView.

2. Compare the base application's <web.config> file with the extended application's <web.config> file, and modify the extended application's <web.config> file to include the missing entries.

3. Convert the InfoviewApp, InfoviewAppActions, PlatformServices, and AnalyticalReporting folders to virtual directories. Ensure that these virtual directories in the extended application point to the same application pool in the base application.

4. Copy the contents of the base application's <"<Sharepoint:port\bin>"> folder to the extended application's <<"ExtendedApplication:Port\bin>> folder.

5. Create a virtual directory called <crystalreportviewers12> and point it to C:\Program Files\BusinessObjects\common\4.0\crystalreportviewers12

3.2.2 Windows AD authentication

Business Intelligence (BI) platform supports Active Directory (AD) authentication with the Windows security plug-in, which is included by default when BI platform is installed on Windows.

Business Intelligence (BI) platform supports Active Directory (AD) authentication with the Windows security plug-in, which is included by default when BI platform is installed on Windows.

You use the Windows AD security plug-in to configure the following types of authentication:

● Windows AD with Kerberos● Windows AD with NTLM

Windows AD authentication requires the following general steps:


1. Configure the required domain controller resources.2. Prepare the host for Windows Active Directory (AD) authentication.3. Ensure the AD security plug-in and map AD groups.4. Choose an authentication method:

○ Windows AD with Kerberos○ Windows AD with NT LAN Manager (NTLM)

5. (Optional) Set-up single sign-on (SSO), using one of the following methods:

○ Kerberos SSO for Windows AD○ NTLM SSO for Windows AD

3.2.2.1 Configuring the Software for Windows AD with Kerberos

Before you configure Windows AD with Kerberos, the following tools must be installed:

● Microsoft .NET framework 3.5● Microsoft Internet Information Services (IIS) 7

1. On the SharePoint portal, configure Windows Active Directory (AD) authentication.See the SharePoint documentation.

2. In the SharePoint software, create a web application, and select Classic Mode Authentication.3. In the Authentication provider section, select Negotiate (Kerberos).4. In the Central Management Console (CMC) in Business Intelligence (BI) platform, configure Windows AD

authentication for Kerberos.See the Authentication section of the SAP BusinessObjects Business Intelligence(BI) platform Administrator Guide.

5. In BI launch pad, confirm that Windows AD authentication is correctly configured for BI platform by logging on with the credentials of an authorized Windows AD user.

6. In the Windows AD domain controller for SharePoint server and Client machines, select Trust this computer for delegation to any service (Kerberos only) .

7. On the SharePoint server open the Internet Information Server (IIS) manager.8. In IIS manager select the site on which integration software is installed and deselect Enable Kernel Mode

Authentication. For example, go to SharePoint site Authentication Windows Authentication Advanced Settings and clear the Enable Kernel Mode Authentication checkbox under Advanced Settings.

9. In the following integration option for SharePoint files, set the value of the authentication.visible flag to true:

○ web.config template configuration file at C:\inetpub\wwwroot\wss\VirtualDirectories\80(where 80 the port where SharePoint is deployed.

○ InfoViewApp at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\InfoViewApp

○ SharePoint platform services at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\PlatformServices



○ OpenDocument files at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\OpenDocument

10. In the integration option for SharePoint software, confirm that Windows AD Kerberos authentication is correctly configured by logging on with the credentials of an authorized Windows AD user.

11. In the Client Browser trusted site, select Add SharePoint Fully Qualified Domain Name URL.For example, if the browser is Internet Explorer, select Tools Internet Options Security Sites .

12. Select SharePoint FQDN, and click Add.13. Select SharePoint FQDN, and Click Add.

3.2.2.2 Configuring the Software for Windows AD Kerberos SSO (Single Sign On)

To configure the integration option for Microsoft SharePoint for Windows AD single sign on (SSO), perform the following steps:

1. Make sure that a Windows AD user is able to logon to the integration option for Microsoft SharePoint software.

2. Enable SSO (Single Sign On) in the Central Managment Console. For understanding how to do so, refer to the Authentication section of the SAP BusinessObjects Business Intelligence(BI) platform Administrator Guide.

3. Set the value of the sso.enabled flag to true, authentication.default to secWinAD and identity impersonate flag to true in the following files of the integration option for Microsoft SharePoint software:a) The InfoViewapp at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects

Enterprise XI 4.0\Web Content\SharepointApp\InfoViewAppb) The SharePoint platform services at C:\Program Files (x86)\SAP BusinessObjects\SAP

BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\PlatformServicesc) The OpenDocument file at C:\Program Files (x86)\SAP BusinessObjects\SAP

BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\OpenDocument4. Restart the IIS server.5. Logon to the client machine with the credentials of a Windows AD authorized user.

6. If the browser is Internet Explorer, go to Internet Options Security Custom Level User AuthenticationLogon and select the <Automatic logon with current user name & password> option.

7. From the client, access the URL of the machine hosting the integration option for Microsoft SharePoint software. The user should be able to login to the software automatically using his Windows AD account credentials.

If the SSO logon fails, take the following steps for troubleshooting:

● Clear the browser cookies, launch a new browser window and access the URL of the machine having the integration option software deployed on it.

● Refer to the CMS (Central Management Server) logs.● Make sure that the Windows AD authentication types of SharePoint & the SAP BusinessObjects BI platform

(Enterprise) are the same (AD Kerberos).● For more information regarding SharePoint software configuration troubleshooting see http://

blogs.technet.com/b/mbiswas/archive/2009/07/10/configure-kerberos-authentication-office-sharepoint-server.aspx


3.2.2.3 Configuring the Software for Windows AD NTLM Authentication

To configure the integration option for Microsoft SharePoint software for Windows AD NTLM authentication, perform the following steps:

1. Configure the SharePoint portal with Windows AD authentications. You can refer to the documentation of Microsoft SharePoint for this.

2. In SharePoint software, Create new web application, and select Classic Mode Authentication.3. In Authentication provider section, select NTLM.4. Configure Windows AD NTLM authentications for the SAP BusinessObjects Business Intelligence platform

(Enterprise). For this, refer to the Authentication section of the SAP BusinessObjects Business Intelligence(BI) platform Administrator Guide.

5. To verify if the Windows AD authentication is configured successfully on the BI platform, logon to the CCM (Central Configuration Manager) using the credentials of a Windows AD authorized user.

6. Set the value of the authentication.visible flag to true in the following files of the integration option for Microsoft SharePoint software:a) The InfoViewapp at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects

Enterprise XI 4.0\Web Content\SharepointApp\InfoViewApp7. To verify if Windows AD NTLM authentication has been configured correctly for the integration option for

Microsoft SharePoint software, logon to integration option using the credentials of a Windows AD authorized user.

3.2.2.4 Configuring the software for Windows AD NTLM SSO (Single Sign On)

To configure the integration option for Microsoft SharePoint for Windows AD single sign on (SSO), perform the following steps:

1. Make sure that a Windows AD user is able to logon to the integration option for Microsoft SharePoint software.

2. Enable SSO (Single Sign On) in the Central Managment Console. For understanding how to do so, refer to the Authentication section of the SAP BusinessObjects Business Intelligence(BI) platform Administrator Guide.

3. Set the value of the sso.enabled flag to true, authentication.default to secWinAD and identity impersonate flag to true in the following files of the integration option for Microsoft SharePoint software:a) The InfoViewapp at C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects

Enterprise XI 4.0\Web Content\SharepointApp\InfoViewAppb) The SharePoint platform services at C:\Program Files (x86)\SAP BusinessObjects\SAP

BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\PlatformServicesc) The OpenDocument file at C:\Program Files (x86)\SAP BusinessObjects\SAP

BusinessObjects Enterprise XI 4.0\Web Content\SharepointApp\OpenDocument4. Restart the IIS server.5. Logon to the client machine with the credentials of a Windows AD authorized user.



6. If the browser is Internet Explorer, go to Internet Options Security Custom Level User AuthenticationLogon and select the <Automatic logon with current user name & password> option.

7. From the client, access the URL of the machine hosting the integration option for Microsoft SharePoint software. The user should be able to login to the software automatically using his Windows AD account credentials.

If the SSO logon fails, take the following steps for troubleshooting:

● Clear the browser cookies, launch a new browser window and access the URL of the machine having the integration option software deployed on it.

● Refer to the CMS (Central Management Server) logs.● Make sure that the Windows AD authentication types of SharePoint & the SAP BusinessObjects BI platform

(Enterprise) are the same (AD NTLM).

3.2.3 Security and Single Sign-On

Users can log on directly to Business Intelligence (BI) platform from SharePoint, using the following types of authentication. Single sign-on workflows can be supported using Kerberos or CA SiteMinder.

Table 1:Authentication mode Description

Claims-based authentication for SharePoint 2010 and SharePoint 2013

When a user logs on to SharePoint Server, a security token is validated and used to log on to SharePoint. The token is issued by a claims provider.

BusinessObjects Enterprise credentials

Lightweight Directory Access Protocol (LDAP) authentication

● The LDAP deployment must be set up properly.● Portal user names must match the aliases in the

authentication system.

Windows Active Directory (AD) authentication ● The AD deployment must be set up properly.● Portal user names must match the aliases in the

authentication system.

NoteBeginning with Microsoft SharePoint 2013, claims-based authentication will be the default SharePoint method.

For information about configuring authentication modes in the Central Management Console (CMC) in BI platform, see the SAP BusinessObjects Business Intelligence Platform Administrator Guide.

Single sign-on Single sign-on (SSO) is enabled when you set the value of sso.enabled to true in the web.config template configuration file. For example:

<add key="sso.enabled"value="true" />


3.2.3.1 Configuring claims-based authentication for SharePoint 2010

This task uses the TrustedPrinciple.conf file pass the shared secret to the client machine when configuring NTLM claims-based authentication for SharePoint 2010.

Before configuring claims-based authentication for SharePoint 2010:

● You must be a member of the SharePoint Administrators group and a member of the Windows Administrators group on the server that is running Central Administration.

● All SharePoint 2010 prerequisites must be met.● The following tools must be installed:

○ Microsoft .NET Framework 3.5○ Microsoft Internet Information Services (IIS) 7○ Microsoft SQL Server 2008○ SharePoint Server 2010

1. Create a SharePoint 2010 site that uses NT LAN Manager (NTLM) claims-based authentication.2. Confirm that users can access the SharePoint site.3. In the Central Management Console (CMC) in BI platform, enable the Windows Active Directory (AD) plug-in,

and import users. See the SAP BusinessObjects Business Intelligence Platform Administrator Guide.4. Confirm that users can manually log on to BI platform.5. Install the Integration option for Microsoft SharePoint (IOMS) software on the site you created in step 1.6. Install the IOMS software on the SharePoint machine.7. In the web.config file for the InfoViewApp web part, perform the following actions:

a) Set authentication.default to secWinAD.b) Set authentication.visible to true.

InfoViewApp is located at <InstallDir>:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Web Content\SharePointApp\InfoViewApp.

8. At a command prompt, enter iisreset /noforce to restart IIS.9. Confirm that Windows AD users can manually log on to the IOMS site that you created in step 1.10. In the CMC in BI platform, perform the following actions:

a) Enable trusted authentication and use the web.config file to generate a shared secret.b) Assign aliases to map Windows AD user names to Enterprise user names.

See the SAP BusinessObjects Business Intelligence Platform Administrator Guide.11. Confirm that Windows AD users can log on to BI launch pad using single sign-on (SSO) with trusted

authentication.12. Copy the shared secret (TrustedPrinciple.conf file) from the BI platform machine to the <InstallDir>:

\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64 directory on the SharePoint 2010 server.

13. In the web.config file for the InfoViewApp web part, set isTrusted to true.14. At a command prompt, enter iisreset /noforce to restart IIS.

From client machines, users can automatically log on, via SSO, to the IOMS site you created.



3.2.3.2 Creating a web application on port 1250

To configure claims-based authentication, the first step is creating and configuring a web application.

Before configuring claims-based authentication, you must be a member of the SharePoint Farm Administrators group and a member of the Windows Administrators group on the server that is running Central Administration. In addition, all SharePoint 2010 prerequisites must be met, and the following tools must be installed:

● Microsoft .NET Framework 3.5 SP1● Microsoft Internet Information Services (IIS) 7● Microsoft SQL Server 2008 R2● SharePoint Server 2010

1. In SharePoint 2010 Central Administration, on the Application Management tab, click Manage web applications, and then click New on the toolbar.The Create New Web Application window appears.

2. Beside Authentication, select Claims Based Authentication.3. Beside IIS Web Site, perform the following actions:

a) Select Create a new IIS web site.b) In the Name box, enter SharePoint - 1250c) In the Port box, enter 1250.d) In the Host Header box, enter the host name to use to access the web application.e) In the Path box, enter the path to the IIS web site root directory on the server.

4. Beside Security Configuration, perform the following actions:a) Under Allow Anonymous, select No.b) Under Use Secure Sockets Layer (SSL), select No.

5. Beside Claims Authentication Types, perform the following actions:a) Select the Enable Windows Authentication check box.b) Select the Integrated Windows authentication check box, and select NTLM in the list.

6. Beside Sign In Page URL, select Default Sign In Page.7. Beside Public URL, in the URL box, http://SP:12508. Beside Application Pool, perform the following actions:

a) Select Create a new application pool.b) In the Application pool name box, enter SharePoint - 1250c) Under Select a security account for this application pool, select Predefined, and select Network Service in

the list.9. Beside Database Name and Authentication, perform the following actions:

a) In the Database Server box, enter SP\SharePoint.b) In the Database Name box, enter a database name for the new web application.c) Under Database authentication, select Windows Authentication (recommended).

10. Click OK to create the web application, and click OK again.The web application is created and appears on the Web Applications Management page in Central Administration.


3.2.4 User and Group Rights

Users need View rights to view the scheduled reports and the instances that have already been triggered. However, they need View On Demand rights to access reports real-time.

To ensure that all users have view rights, in the BI platform CMC, add the users to the group “Everyone” and then assign view rights to this group. The view rights enable all users who belong to the group “Everyone” to view reports from within the SharePoint environment.

For more information about setting user rights, see the SAP BusinessObjects Business Intelligence Platform Administrator Guide.

3.2.5 Configuring SSL on IIS 6.0

Before you configure Secure Sockets Layer (SSL) on Microsoft Internet Information Server (IIS), the following tools must be installed:

● Microsoft .NET Framework 3.5● IIS 6.0


1. Log on to the SharePoint 3.0 Central Administration site.2. Click the Application Management tab, and click Create or Extend Web Application.3. In the Web Application list, select Extend an Existing Web Application, and select the web application for which

to configure a Secure Socket Layer (SSL).4. In the Create New IIS website box, enter an appropriate value.5. In the Port box, enter the default SSL port number.6. Select the Use SSL check box, and enter the SSL URL in the URL box.7. In the Zone list, select Custom, and click OK.8. Go to the Internet Information Services (IIS) site, select the new site you created, and click Properties.

The site should be on port 80. However, if another web site already exists on port 80, change the new web site's port to another number. (Only one web site can run on a single port.)

9. On the Properties page, click the Directory Security tab, and click Server certificates.10. Perform one of the following actions:

○ If a server certificate already exists on the system, select Assign an existing certificate, and follow the wizard instructions.

○ If no certificates exists, create a certificate by downloading and installing the certificate creation utility.11. In the Secure Communications area on the Directory Security tab, click Edit.12. To enable site access with "http" or "https," select Require SSL and 128 bit encryption.



13. If there are no client certificates, select Ignore client certificates.14. Click OK, and click Apply.15. Go to the SharePoint 3.0 Central Administration page, and click the Operations tab.16. Click Alternate Access Mappings.17. In the Alternate Access Mapping Collection list, select the collection for which to map SSL.

A public URL must be specified in the custom zone. If a public URL is not specified, add it.18. Open a browser, and enter the SSL URL.

NoteYou can navigate through all pages or web parts of the site. However, ensure that the URL does not change from https to http while you navigate.

3.2.6 Configuring SSL on IIS 7.5

IIS 7.5 is the web-application server that supports Microsoft Office SharePoint Server (MOSS) 2010.

Before you configure Secure Sockets Layer (SSL) on IIS, the following tools must be installed:

● Microsoft .NET Framework 3.5 44 2013-09-19 SharePoint configuration● IIS 7.5


1. Log on to the machine where Internet Information Services (IIS) 7.5 is running, and enter inetmgr at the command line.

2. In the Internet Information Services (IIS) Manager window, under Connections, select the root server node.The features list appears under Actions, in the right pane of the window. If the list does not appear, right-click the root server node and select Switch to Features View.

3. To create a self-signed certificate, double-click Server Certificates, and then click Create Self-Signed Certificate under Actions.


4. In the Create Self-Signed Certificate dialog box, enter the name of the machine name where IIS is running, and click OK.The certificate is created.



5. Under Connections, expand Sites, right-click the SharePoint site for which to enable the Secure Sockets Layer (SSL), and select Edit Bindings.

6. In the Site Bindings window, click Add.7. In the Add Site Binding dialog box, perform the following actions:

○ In the Type box, select https.○ In the Default port box, enter 443○ In the SSL Certificate box, select the certificate that you created, and click OK.

The site binding is added to the Site Bindings dialog box.

8. Click Close.When you select the site under Connections and then select Actions Manage Web Site Browse Web Site , the new binding value appears as Browse *:443 (https).


9. Double-click the SSL Settings icon in the center pane of the Internet Information Services (IIS) Manager window.

10. In the view that appears, select the Require SSL check box, and then click Apply under Actions.The SharePoint site's SSL URL and the default port are configured.

11. Enter the site's URL (for example, https://lidt50794936) in a browser to open the site, click Continue to this website (not recommended), and enter logon credentials to log on to the SharePoint site.A You may be trying to access this site from a secured browser on the server. Please enable scripts and re-load this page message appears.



12. To prevent the message from appearing, add the site's https URL to the trusted sites list for the browser.In the browser, select Internet Options, click the Security tab, double-click Trusted Sites, click Add, enter the site's https URL, and click OK.The next time you access the SSL-enabled site, the warning message will not appear.

If you will access the SharePoint SSL URL from a remote client machine, you must export the certificate to the server and then import it to the remote client machine.

3.2.7 Configuring ISA 2006 for Reverse ProxyInstall ISA 2006 by using your Windows credentials.

To configure ISA 2006, complete the following steps:

1. Launch ISA 2006.

2. Right-click Firewall Policy New SharePoint Site Publishing Rule .The Welcome to the SharePoint Publishing Rule Wizard screen appears.

3. Enter the publishing rule name in the SharePoint publishing rule name field, and click Next.The Publishing Type screen appears.

4. Select Publish a single Web site or load balancer, and click Next.The Server Connection Security screen appears.

5. Select Use non-secured connections to connect the published Web server or server farm, and click Next.The Internal Publishing Details screen appears.

6. In the Internal Site name field, enter the internal site name. The internal site name refers to the system on which MOSS is running.


7. Select Use a computer name or IP address to connect to the published server, specify the system name or IP address in the Computer name or IP address field, and click Next.The Public Name Details screen appears.

8. From the Accept Request for drop-down list, select Any domain name, and click Next.The Select Web Listener screen appears.

9. Click New.The Welcome to the New Web Listener Wizard screen appears.

10. Specify the web listener name, and click Next.The Client Connection Security screen appears.

11. Select Do not require SSL secured connections with clients, and click Next.The Web Listener IP Addresses screen appears.

12. Select External, Internal, and Local Host, and click Next.The Authentication Settings screen appears.

13. Select No Authentication, and click Finish.

14. Select the newly created listener, and click Properties Authentication .15. Click the Advanced button, and select Require all users to authenticate and Allow Client Connections over Http.

The Authentication Delegation screen appears.16. From the drop-down list, select No delegation, and client cannot authenticate directly.

The Alternate Access Mapping Configuration screen appears.17. Select one of the following options based on your requirements:

○ SharePoint AAM is already configured on the SharePoint server○ SharePoint AAM is not yet configured. Also select this option if you are unsure if AAM is configured.

18. Click Next.The Completing the New SharePoint Publishing Rule Wizard screen appears.

19. Click Finish.The publishing rule is created.

20. Select the publishing rule, and click Apply.21. Right-click the rule, and select Properties.

The Properties screen appears.22. Select the Listener tab, and verify the port and protocol.

NoteBy default, port 80 is used. To change the port number, use the Connections tab.

23. Select the Public Name tab.24. From the This rule applies to drop-down list, select Requests for the following Web sites, and specify the

reverse proxy system.In Path Names, map the client path to the server path.

25. Select the To tab, and verify the name and IP address of the destination system.26. Select the Bridging tab.27. Select Redirect requests to HTTP port, and specify the port in which the extended SharePoint website is

running.



NoteIf you want the reverse proxy to point to the extended application, then you must specify the port number of the extended application. If you want the reverse proxy to point to the base application, then you must specify the base application's port.

28. Select the rule, and click Apply.

3.2.7.1 Configuring Reverse Proxy for the Base SharePoint Application

Ensure that ISA 2006 is configured on the Integration Option software.

To configure reverse proxy for the base SharePoint application, complete the following steps:

1. Log into the Central Administration site.2. Click Operations, and click the AlternateAccessmapping link.3. From the drop-down list, select the web application.4. Click the Add Internal URL link, and add the reverse proxy URL.5. From the Zone drop-down list, select the Default zone.6. In IIS, change Authentication type to Basic.

3.2.7.2 Creating an Extended Website for the Web Application

To create an extended website for the web application, complete the following steps:

1. Log into the SharePoint 3.0 Central Administration site.2. Click the Application Management tab, and click the create or extend web application link.3. From the Web Application drop-down list, select Extend an Existing Web Application. 4. Select the web application for which you want to configure a reverse proxy application.5. Specify the description, port, URL and so on in the appropriate fields.6. Select a zone (for example, Internet), and click OK.7. Navigate to the Central Administration site, click the Operations tab, and click the AlternateAccessMapping

link.8. From the drop-down list, select the web application.9. Click Add Internal URL link, and add the reverse proxy URL.10. From the Zone drop-down list, select the zone for the extended application.11. Click OK.

An extended website is created for the web application.


3.2.7.3 Modifying the <web.config> File of the Extended Web Application for Reverse Proxy

To modify the <web.config> file of the extended web application for reverse proxy, complete the following steps:

1. Copy all the dlls and folders from the bin folder of the base application to the bin folder of the extended applications.

2. In the <web.config> file of the base application, ensure that only one sessionState entry exists, that is, <"sessionState mode = Inproc"/>. Comment any other entries.

3. In the extended application, create a virtual directory called crystalreports12 and point it to C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\dotnet\crystalreportviewers12

4. Convert the following folders to virtual directories:

○ Infoviewapp○ InfoviewAppActions○ PlatformServices○ Analytical Reporting○ CrystalReports○ Xcelsius

NoteEnsure that the virtual directories in the extended application point to the same application pool in the base application.

5. Compare the base application's <web.config> file with the extended application's <web.config> file, and modify the extended application's <web.config> file to include the entries that are missing.

3.3 Configuring the Optional BI Platform Settings

This section describes how to configure the optional BI platform settings for your SharePoint deployment.

3.3.1 Specifying a Server for Processing Reports

By default, the reports that users view are processed by the SAP BusinessObejcts BI platform page server. If the page server is not available, then the Report Application Server (RAS) is used.

If you want to configure the system to use the RAS to process reports, create a new Server Group for your RAS in the BI platform, specify this server group in all the reports, and then stop the platform page server.

To specify a server for report processing, complete the following steps:

1. Log into the CMC.



2. In the Object Management area of the Central Management Console (CMC), select an object by clicking its link.

3. Click the Process tab.4. In the Default Servers To Use For Viewing area, select any of the following options:

○ Use the first available server - If you select this option, then the BI platform uses the server that has the maximum number of free resources when you view a report.

○ Give preference to servers belonging to the selected group - If you select this option, then the BI platform attempts to process the object by using the servers in the server group that you select from the list. If the specified servers are not available, then the object is processed by using the next available server, which may not belong to the selected group.

○ Only use servers belonging to the selected group - If you select this option, then the BI platform uses only the servers in the server group that you select from the associated drop-down list. If none of the servers in the server group are available, then the object is not processed.

5. Click Update.

3.3.2 Specifying Parameter Settings

Parameter prompts are enabled only when you view reports real-time (unless the parameter is a stored procedure). In the Central Management Console (CMC), you must ensure that the Prompt when viewing check box is selected; otherwise, the prompts are disabled, and the users cannot modify the values of the prompts in the report.

You must ensure the following to enable users to work with reports that contain parameters:

● Ensure that users are given View On Demand rights to enable them to view reports that include parameters.● To allow users to modify parameter values, you must ensure that the reports they view are real-time reports.

However, real-time reports can be resource-intensive; therefore, to reduce the processing load on the BI platform services, you must ensure that users work with scheduled reports whenever possible.

● If you want users to work with a report for two different purposes (for example, real-time filtering and general viewing by date), then you must create two copies of the report. Allow users to view the report on demand for real-time filtering. To facilitate general viewing by date, you can schedule the report to run as often as required. Creating two copies of the report reduces the processing load on the system resources, because only the real-time filtering report needs to be viewed on demand.

To specify parameter settings, complete the following steps:

1. Log into the CMC.2. In the Objects Management area of the CMC, select a report by clicking its link.3. In the report, click the Process tab, and then click the Parameters link.4. Under the Value column, select the value that is associated with the parameter that you want to modify.5. Select Prompt when viewing to ensure that users are prompted when they view the report instance in the

corresponding web part.6. Click Submit.


3.4 Scheduling and Scaling Recommendations

The Business Intelligence (BI) platform schedules, processes, and runs reports. The general scheduling and scaling recommendations for the BI platform also apply to the integration option for Microsoft SharePoint. Use the Central Management Console (CMC) to specify the different scheduling properties for reports. For information about additional scheduling recommendations, see the SAP BusinessObjects Business Intelligence Platform Administrator Guide.

When setting scheduling properties for reports, consider the following recommendations:

● If you have reports that need to be updated regularly, and if users are going to access the same set of data, then you must schedule the reports to run per your requirements.

● If you want to view a report, you must schedule and run the report instead of viewing it on demand. Scheduled reports are less resource-intensive.

● If you grant View on Demand rights to users, the reports access the data source whenever users attempt to refresh them.

● When designing your portal, you must exercise caution while combining the web parts of integration option software, which contain real-time views, with third-party web parts that are page refresh intensive. When a user refreshes a page, all the reports in the web page are refreshed. For example, if a web page contains a stock ticker that is refreshed every ten seconds, all the reports in this web page are also refreshed every ten seconds.

3.4.1 Exporting Reports

For reasons related to the performance of the integration option software, you must set the export options (Microsoft Excel, Adobe Acrobat, and so on) at schedule time. When users export reports dynamically by selecting the alternative format viewing options on the toolbar, the requests become process and resource intensive.

3.4.2 Data Source Information

Set your database logon information for your reports through the CMC; otherwise, users need to log into the database each time they refresh or view a report.

3.4.3 Report Rights

If the report contains parameters, users who view the report require View On Demand rights.

If you are using the Page Server to view the summaries of different reports, you must grant Edit rights to users.



3.4.4 Performance Improvement

To improve the performance of the integration option for Microsoft Office SharePoint if you are not using a web farm, the session state on the web application server is enabled by default.

3.5 Crystal Report Considerations

When you create a Crystal report, consider the following recommendations:

● Ensure that the background of your report is transparent.● Ensure that you have the Adobe Flash Player installed on your machine.● Make maximum use of your screen resolution and space for your report parts.● Ensure that parameter names are short and that parameter descriptions are meaningful and useful, because

users can view the parameter names and descriptions in the toolbar.

For information about creating Crystal reports, see the Crystal Reports User' Guide.


www.sap.com/contactsap

© 2014 SAP AG or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Date post:	17-Mar-2018
Category:	Documents
Upload:	tranhanh
View:	241 times
Download:	3 times