You are on page 1of 19

Unit 12

Integrating with SAP Enterprise Portal


Unit Overview

Unit Objectives
After completing this unit, you will be able to:

Understand the most important functionalities for creating portal content


like iViews, Pages, their layout, etc.
Tasks necessary to be realized for creating new roles and content for end users
Understand the procedure to follow in order to integrate SAP Business
Objects in an Enterprise Portal Installation.
Enable you to configure the templates for proper working within a Enterprise
Portal

Unit Contents
Lesson: Integrating BI Platform Content into SAP Enterprise Portal.....492
Lesson: Integration of SAP Business Objects with Enterprise Portal ....500
Lesson: Comparing Document Viewer and Document List Portal
Component ......................................................................507

2012

2012 SAP AG. All rights reserved.

491

Unit 12: Integrating with SAP Enterprise Portal

TBI30

Lesson: Integrating BI Platform Content into SAP


Enterprise Portal
Lesson Overview
The Enterprise Portal of SAP Netweaver allows to unify the access to resources
and functionality of different systems in one single point. This lesson will
introduce you to the most important objects and concepts of the Enterprise Portal
for integrating objects from the SAP BI Platform into SAP EP.

Lesson Objectives
After completing this lesson, you will be able to:

Understand the most important functionalities for creating portal content


like iViews, Pages, their layout, etc.
Tasks necessary to be realized for creating new roles and content for end users

Business Example
It is your task to setup roles composed of different iViews, pages and worksets
in order to give the user an access to BOE reporting objects via the SAP NW
Enterprise Portal in order to use the existing EP infrastructure as a unifying access
to different functionalities, including BOE reporting objects like Webi Reports,
Crystal Reports or Dashboard designed with the Dashboard Designer.

Basic Concepts of SAP EP

Figure 178: Basic Concepts of SAP EP

492

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Integrating BI Platform Content into SAP Enterprise Portal

Using SAP NetWeaver Portal, organizations can give their employees, customers,
partners, and suppliers a single point of access to the company applications,
services, and information needed for conducting daily work. In addition, the portal
offers business users the capability to easily create and manage portal pages and
to generate their own portal content.
Two usage types are associated with SAP NetWeaver Portal:

EP Core Application Portal (EPC) is a lean portal installation, applicable


when full enterprise portal capabilities are not required.
Enterprise Portal (EP) includes the Collaboration and Knowledge
Management add-on capabilities. The prerequisite for EP is EPC.

The following use cases are available with SAP NetWeaver Portal:

Providing Unified Access to Applications and Processes

SAP NetWeaver Portal (usage types EPC and EP) provides the core
portal capabilities required to standard content to both internal and
external portal users. The portal offers a single point of access through
a Web front end to both SAP and non-SAP information sources,
enterprise applications, information repositories, databases and services
across organizational and technical boundaries.
Managing and Mashing up Portal Pages with Web Page Composer

Web Page Composer is an integral part of SAP NetWeaver Portal. It


enables business users to easily create and manage enriched portal pages
that blend business applications and user-generated content. Web Page
Composer also allows professionals to create interactive portal pages.
Building Communities with Wikis and Forums

Portal users can create and build communities by establishing wikis


and forums as the means to easily share and contribute knowledge
and information. Forums provide the ability to share knowledge by
communicating and delivering information to people with similar
interests. Wikis provides a framework for collaborative writing and
posting ideas and feedback, in order to share and manage knowledge
and information.

Running Content Management Scenarios

2012

Knowledge Management (KM) is one of the basic content services provided


by SAP NetWeaver portal It enables customers to run basic KM scenarios
and to use an extension framework for customizing implementations.

2012 SAP AG. All rights reserved.

493

Unit 12: Integrating with SAP Enterprise Portal

TBI30

SAP Netweaver Portal Desktop

Figure 179: SAP Netweaver Portal Desktop

For portal users, a portal desktop defines the structural layout and design of the
portal workspace displayed on the screen. It is a structured collection of iViews,
pages, themes, and layouts, which can be personalized at runtime.
In the design time environment, a portal desktop is a collection of framework
pages and portal themes, which is defined and customized by content and system
administrators, and ultimately assigned to portal users through portal display rules.
Framework page: Defines the layout of navigational and structural elements in
the portal desktop.
A portal desktop may contain more than one framework page. The administrator
responsible for configuring the portal desktop object sets the active framework
page.
Portal theme Defines the overall look-and-feel of user interface elements in a
portal desktop, such as color, contrast, and font usage.
A portal desktop may contain more than one portal theme. The administrator
responsible for configuring the portal desktop object sets the default portal theme.
Portal desktops combine personalization and scenario-based options for portal
users at runtime:

494

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Integrating BI Platform Content into SAP Enterprise Portal

The flexibility of framework pages enables administrators to design custom-made


navigation layouts that suit various portal user experiences. For example, thin
desktops can support dial-up connections, while customized framework pages
support different navigational needs for a company's employee intranet and
customer-based extranet.
Portal users automatically receive the appropriate framework page based on
transparent display rules, which are predefined by the portal administrator.
Administrators assign multiple themes to a desktop to provide portal users with
the freedom to choose a portal theme to personalize the look and feel of their
portal desktop.

The System Landscape Directory

Figure 180: The System Landscape Directory

The System Landscape Overview appears upon navigation to System


Administration System Configuration. It is a multipurpose system management
tool encompassing two primary purposes:

Displaying all the systems comprising the system landscape.


Associating systems with system aliases to provide back-end connectivity.
The System Landscape Overview also provides alternative access to the
system editors and utilities available from the Portal Catalog context menu.

Activities to be realized in the System Landscape Directory (SLD)

2012

2012 SAP AG. All rights reserved.

495

Unit 12: Integrating with SAP Enterprise Portal

TBI30

The System Landscape Overview is a table listing all the systems in the system
landscape. The overview also provides the following capabilities:

Associate system aliases and systems

Systems appear by their system aliases. Since a system can have


multiple aliases, the same system can appear in multiple records.

You can assign unassigned system aliases to systems by choosing an


alias from the dropdown list in the System Name field.

You can assign unassigned systems to system aliases by choosing an


alias from a system from the dropdown list in the System Alias field.
Full sorting and filtering

You can filter the system landscape list by using the dropdown lists or
free text for any column and for multiple columns. You can sort the
columns as well by clicking the column headings.
Checking system connections

Selecting a system, or multiple systems, and choosing Test Connection


verifies the system connection to its back end.
The system landscape overview provides information about the
previous connection test, including details in the event of failure.

Locating a system in the Portal Catalog


Selecting a system and choosing Locate in Portal Catalog highlights
the selected system in its location under in the Portal Catalog.

Selecting a system and choosing Edit System displays the Properties


editor of the selected system.
Identifying the user management type

The system landscape overview shows the user management type


configured for the system, such use of a logon ticket or user ID and
password; this indicates how the system is authorized to access data.

Since systems typically access data from a back-end source, the


connector to the back end may require user mapping. For more
information, see Editing System Properties. The user mapping type is
defined in the system properties.
From the Properties editor, you can access the System Alias editor.

496

Viewing and checking the connectivity of roles uploaded to the portal


from SAP Business Suite packages

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Integrating BI Platform Content into SAP Enterprise Portal

The Portal Content Administration

Figure 181: The Portal Content Administration

The content administrator is responsible for all tasks that are relevant to the
creation and management of content objects in the portal.
Portal users can gain access to portal content that resides in document repositories,
internal and external services, reports and analytics, and business transactions
in enterprise applications. Content should be developed in a way that enables
members of the organization to connect to their information repositories from the
portal, retrieve data, and interact with this data through a usable interface.
Portal Content Objects
Portal content consists primarily of iViews. Each iView brings specified data to
the portal desktop from an information resource such as a relational database, ERP
system, CRM system, enterprise application, collaboration tool, e-mail exchange
system, intranet, or the Internet. iViews return up-to-the-minute information each
time they are launched.
You can import ready-made iViews into your portal environment from the Portal
Content Portfolio on SAP Developer Network, you can create iViews from
templates provided with the portal, or you can develop custom-made iViews using
the content-creation tools in the portal or other content development kits.
iViews are generally displayed through portal pages. You can import predefined
pages or you can create your own pages. The page definition includes a list of
associated iViews and layout specifications. Also available for import from the
Portal Content Portfolio on SAP Developer Network are worksets and business
packages. Worksets bundle related pages, iViews, and roles, while business
packages are generally groups of related worksets.

2012

2012 SAP AG. All rights reserved.

497

Unit 12: Integrating with SAP Enterprise Portal

TBI30

User access to content is determined by role definitions. A portal role is a


collection of task-oriented content. While portal content is developed to enable
access to information relevant to the organization in which the portal is deployed,
roles define the subset of content available to each function within the organization.
Users are assigned to the role or roles that provide content relevant to them. A
user has access to the content that has been assigned to all of his or her roles.
The role definition determines the navigation structure within the portal. The
navigation structure consists of the top-level navigation bar, and the detailed
navigation tree. A user navigates portal content by clicking tabs in the top-level
navigation and detailed navigation.
Portal Content Studio
The Portal Content Studio is the content administrators main environment for
developing and managing portal content. The range of functionality that you have
in managing portal content depends on the configuration of your portal.

498

2012 SAP AG. All rights reserved.

2012

Unit 12: Integrating with SAP Enterprise Portal

TBI30

Lesson: Integration of SAP Business Objects with


Enterprise Portal
Lesson Overview
This lessen explains the files and objects that are necessary to integrate SAP
Business Objects with the Enterprise Portal as well as the procedures necessary
to follow.

Lesson Objectives
After completing this lesson, you will be able to:

Understand the procedure to follow in order to integrate SAP Business


Objects in an Enterprise Portal Installation.

Business Example
Procedure of Integrating SAP BI Platform Objects
1.

Install the files of the portal integration kit which you can find in the
installation directory of the SAP BI platform installation.

2.
3.

500

First install the com.sap.businessobjects.iviews.par file via the JSPM or


NWDI.

Transport the com.sap.businessobjects.iviews.templates.epa files


Configure the source system in the SLD
Create your role with the corresponding pages and iViews that reference the
objects in the BOE repository

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Integration of SAP Business Objects with Enterprise Portal

Transporting the EPA File to the Portal

Figure 182: Transporting the EPA File to the Portal

In order to transport an .EPA file into the portal please proceed as follows:
1.
2.
3.
4.

2012

Navigate to System Administration Transport Transport packages


Import.
Select the EPA file from the directory where you put the file before, well
from the server or from the workstation/client.
Upload the file. A summary of the objects contained in the transport will
appear.
Import the objects to the portal.

2012 SAP AG. All rights reserved.

501

Unit 12: Integrating with SAP Enterprise Portal

TBI30

Figure 183: Confirming the Correct Transport and Finding the Templates in
the Portal Content Directory

You can find two iView templates after the import in the Portal Content Directory
(PCD):

SAP Business Objects Document List Template: The document list


iView will provide users with many of the same features BI launch pad
provides. Users can navigate all reports they have permissions to view, view
personal folders, and browse categories. They can also edit reports, schedule
report refreshes or manually refresh reports, search BI content, and set user
preferences (if they have appropriate permissions).

SAP Business Objects Document Viewer Template: This is the simplest type of
portal component you can create. This iView displays a single report selected by
the portal administrator at the time they deploy it. Users will see the report when
the iView portal page is displayed. They can navigate within the report normally,
but cannot navigate to any other reports unless the default report contains linked
reports. The portal page designer or administrator configures the content that is
displayed in the iView.

502

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Integration of SAP Business Objects with Enterprise Portal

Configuring a Source System in the System Landscape


Directory

Figure 184: Configuring a Source System in the System Landscape Directory

2012

2012 SAP AG. All rights reserved.

503

Unit 12: Integrating with SAP Enterprise Portal

TBI30

Procedure to configure a source system connection, to be realized in the System


Landscape Directory:
1.

2.
3.
4.

Create a source system using the source system template SAP Business
Objects System which can be found in Portal Content Content provided
by SAP SAP Business Objects iViews.
Fill in the values of the fields System Name, System ID and IDPrefix (e.g.
Training BIP Default System, BIP_DEF_SYS, com.sap).
In the next screen, type in an system alias (e.g. BIP_DEF_SYS_ALIAS).
Finish the creation and open the source system properties via right click on
the newly created entry for the source system. Click on All and then Modify
properties. You will need to provide the following information for this step:

504

Under the SAP BusinessObjects property category, enter the fully


qualified URL for the SAP BusinessObjects BI platform, for example
http://<Server_Name>.wdf.sap.corp:8080/BOE/.
Under the User Management property category, set the
Authentication Ticket Type to SAP Assertion Ticket, and the Logon
Method to SAPLOGONTICKET.
Under the Connector property category, configure Group, Logical
System Name, Message Server, Remote Host Type, SAP Client,
SAP System ID (SID), System Type, and any other applicable fields
with the appropriate information for your system. Configure the fields
SNC Library Path, SNC Mode and SNCName if you use Secure
Network Communication.
Save the settings and test the connection.

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Integration of SAP Business Objects with Enterprise Portal

Connector Properties for a BI platform Source System


in Enterprise Portal

Figure 185: Connector Properties for a BI platform Source System in


Enterprise Portal

In the above slide you can see sample settings for a successful connection to a
server using the BW system for authentication.

2012

2012 SAP AG. All rights reserved.

505

TBI30

Lesson: Comparing Document Viewer and Document List Portal Component

Lesson: Comparing Document Viewer and Document


List Portal Component
Lesson Overview
The two main templates for iViews that come with the Portal Integration Kit
are the document viewer and the document list portal component. This lessen
describes how to configure the templates.

Lesson Objectives
After completing this lesson, you will be able to:

Enable you to configure the templates for proper working within a Enterprise
Portal

Business Example
Comparing Document Viewer and Document list Portal
Component
Two main iView Templates are Available:
1.

SAP BO Document Viewer

2.

For visualizing single BO Reporting objects in the Enterprise Portal.


Both CUIDs (Unique character String) or IDs (unique numeric value)
can be used to identify the object.
SAP BO Document List

Encapsulates most of the functionality of the BI Launchpad within


a single iView.
The navigation to the requested object is realized via the navigation
offered by the BI Launchpad.

SAP Business Objects Document List Template: The document list iView will
provide users with many of the same features BI launch pad provides. Users
can navigate all reports they have permissions to view, view personal folders,
and browse categories. They can also edit reports, schedule report refreshes or
manually refresh reports, search BI content, and set user preferences (if they have
appropriate permissions).
SAP Business Objects Document Viewer Template: This is the simplest type of
portal component you can create. This iView displays a single report selected by
the portal administrator at the time they deploy it. Users will see the report when

2012

2012 SAP AG. All rights reserved.

507

Unit 12: Integrating with SAP Enterprise Portal

TBI30

the iView portal page is displayed. They can navigate within the report normally,
but cannot navigate to any other reports unless the default report contains linked
reports. The portal page designer or administrator configures the content that is
displayed in the iView.
SAP Business Objects KM Integration: SAP NetWeaver provides Knowledge
Management & Collaboration (KMC) capabilities via the SAP Netweaver Portal
(SAP EP). While this feature is currently available, it is no longer being actively
developed, meaning that no new features or upgrades are planned for the future.
Users currently using this solution are recommended to consider moving to the
SAP BusinessObjects Enterprise XI iViews Document List portal component. For
more information check the Portal Integration Kit Installation Guide.

Figure 186: The SAP Business Objects Document Viewer Setup Step 1

In order to configure the iView Template SAP Business Objects Document Viewer,
start by creating a new iView based on the template SAP Business Objects
Document Viewer. You can start this process by right-clicking on the PCD Folder
where you want to store the iView. Choose New iView iView based on
template. Later on choose the template SAP Business Objects Document viewer.
Give the iView a name, ID and a ID prefix. Afterwards open the properties for
further configuration (see next slide).

508

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Comparing Document Viewer and Document List Portal Component

Figure 187: The SAP Business Objects Document Viewer Setup Step 2

Set the source system and the type of document ID. Choose then the BOE object
to be called when opening the iView.

Figure 188: The SAP Business Objects Document Viewer Setup Step 3

2012

2012 SAP AG. All rights reserved.

509

Unit 12: Integrating with SAP Enterprise Portal

TBI30

Figure 189: The SAP Business Objects List Component Setup Step 1

Setting up the document list viewer iView is very easy. Define the system to
connect to and specify the BI Launch Pad path (default = BI). Preview your
access to the BI Launchpad.

510

2012 SAP AG. All rights reserved.

2012

TBI30

Lesson: Comparing Document Viewer and Document List Portal Component

Lesson Summary
You should now be able to:

Enable you to configure the templates for proper working within a Enterprise
Portal

2012

2012 SAP AG. All rights reserved.

511