Tools and Best Practices to Integrate Content Into Your Portal

7/30/2019 Tools and Best Practices to Integrate Content Into Your Portal

1/69

2005 Wellesley Information Services. All rights reserved.

LOGO WILL GO HERE

Tools and BestPractices to

Integrate Contentinto Your Portal

Payal JainDeloitte Consulting LLP


2/69

2

In This Session We Will ...

Consider various types of content to be integrated

on a Portal

Examine some of the challenges, including:! How to integrate content

! What is the best solution to integrate content?

! Easy ways to maintain content

Describe various types of content

Discuss various ways to integrate content on your

SAP Enterprise Portal


3/69

3

Key Elements and Phases of a Portal Project Roadmap

G

O

V

E

RN

A

N

C

E

S

T

A

FF

I

N

G

ContinuousImprovement Monitoring

Update/Test/

Upgrade

FutureConsider-

ations

SupportPacks

ChangeMgmt.

Strategy

Define

Build

Key

Decisions

Test and

Deploy

KM Folder

Structures

Branding

and Design

Transport

Strategy

Development

Standards

Design

Ready

Your

Platform

Landscape Ext. AccessHardware

SizingLDAPSSO

Procure

Hardware

Install

Hardware

Install SAP

Ent. Portal

PCD

Structure

SAP

Content

Non-SAP

Content

Custom

Content

Business

Packages

Build

Integrating

Content

Build

DeliveringContent

Naming

Conventions

Knowledge

Mgmt.

User

Mgmt. Security Roles

User

Adoption

Performance

Mgmt.

Trouble-

shootingRoll-out Training

Identify

Types of

Applications

Define

Technical

Reqs

Define

Accessibility

Needs

Define

Availability

Needs

Define

Security

Reqs


4/69

4

What Well Cover

Content Integration overview

Integrating SAP content into your portal

Integrating non-SAP content Other topics: Knowledge Management and Unification

Content integration best practices and summaries

Wrap-up


5/69

5

What Well Cover





Wrap-up


6/69

6

What is the Enterprise Portal Vision?

A typical vision for Enterprise Portal is to provide a single point of access

to all the information assets of the enterprise, specific to the needs of the

targeted audience

Data Sources and Targets

ERP

Enterprise Portal

Applicationsand Files

CRM

Legacy

Others

Information

Other KM applications

Internet servicesServices

e-business services

Security

Administration

InformationDatabases

Email

Metadata Directory

Portal Constituents

Customers

Employees

Suppliers

Partners

App

licationIntegration

Search

Publishing&Distribution

Collaboration

Personalization

Bu

sinessIntelligence

Process

Delivery

Channels

External Internet ContentEnterprise Content

The enterprise portal provides common services and a common presentation layer to

internal and external sources of content or systems of record. Such systems can reside

internal or external to the enterprise portal.


7/69

7

Various Types of Portals

News Portals

! News information aggregated from various sources

! Authoring and publishing articles

Entertainment Portals

! Specialized UI catered to the user

! Presentation of high volume/resolution videos

Educational Portals

! Knowledge bases

!

Powerful search integration


8/69

8

Various Types of Portals (cont.)

Transactional Portals

! Real-time information exchange

! Time-sensitive data access

Collaboration Portals

! Synchronous and asynchronous information exchange

! People connection

Hybrid Portals

! Multi-portal integration


9/69

9

Content Integration Challenges

Integrating business processes across an organization

! Multiple locations/multiple businesses but similar

business processes

Hybrid portal scenarios

! Existing corporate portal product and SAP ERP system the

best way to integrate SAP content seamlessly

Planning for future functionality

! Document management, content host ing, search and retrieval


10/69

10

Why SAP Enterprise Portal?

Unparalleled/tight integration of SAP R/3 content

on the Portal

Low cost solution to integrate data and content fromSAP R/3 onto the Web without spending a lot of money

on middleware products

! System integration can be the most expensive solution to

develop, implement, and maintain in an organization

Easiest way to get your SAP data on the Web it is the

future direction of SAP


11/69

11

Various Tools to Integrate Content on the Portal

SAP Enterprise Portal consists of

three major components

!

Portal Server! Knowledge Management (KM)

! Unification

Well discuss integration elements ofall of these in this presentation!

1 - Portal Server

2 - KM

3 - Unification

WebServer


12/69

12

Integrating Content on EP

Portal Server! Content from SAP R/3, BW, CRM, etc.

! Content from Web

! Custom content from legacy applications (.Net, ASP, Java,Visual Composer, Web Dynpro based content integration)

Knowledge Management!

Collaboration content (collaboration rooms, discussiongroups, chat rooms, email integration)

! TREX search capabilit ies

! Document management

Unification! Drag & Relate content

! Content integration from various content databases

(e.g., SQL, Oracle, etc.)


13/69

13

What Well Cover





Wrap-up


14/69

14

Developing and Integrating SAP Content

There are multiple ways to integrate SAP content into your portal

! 1 Transactional content (content developed utilizing standard EP

templates EP Content Studio)

! 2 Business Package content

! 3 Custom developed content

!Web Dynpro (NWDS)

!

PDK (NWDS)!PDK for .Net

!Visual Composer

! 4 Evented content

Complexity of Application

RequiredSkillLevel

Business

Packages

Content

Studio

Visual

Composer

Developer

Studio

Development

Kit


15/69

15

1. Transactional Content

SAP Enterprise Portal provides an iView wizardframework and various default iView templates forcreating iViews over most SAP R/3-based systems:

e.g., Core R/3, BW, CRM, and HR! iViews can be created based on:

!SAP transactions

"

Web GUI" WIN GUI

" JAVA GUI

!BSP pages

!BW queries and reports

!URL iViews

! ITS-based IAC iViews


16/69

16

iView Creation Wizards

SAP Enterprise Portal offers a number of iView wizards,

each one specific to the type of iView you want to create

! The wizards provide a step-by-step, making sure you provide

all of the necessary pieces of information that are required to

generate the iView

At the end of the creation process, the wizard takes the

information you provided and generates an iView! You can then edit the iView properties to modify your

specifications


17/69

17

Steps for Using the iView Creation Wizard

You can use the iView creation wizard to create iViews

based on existing iView templates or portal

components

To use the wizard to create an iView based on an

iView template:

1. Within the Portal Content Studio, right-click the folder in

which you want to create the iView, and then in the context

menu that appears, choose New > iView

2. In the first step of the wizard, choose the iView template you

wish to use as the basis for your new iView


18/69

18

Steps for Using the iView Creation Wizard (cont.)

To create an iView based on a portal component:

1. Within the Portal Content Studio, right-click the folder in

which you want to create the new iView, and then in the menu

that appears, choose New from Portal Archive > iView

2. Next, choose the portal archive that contains the portal

component on which you wish to base the new iView

3. Now, a list of portal components that exist in the portalarchive is shown. Choose a portal component to use and

fol low the wizard to create your iView.


19/69

19

iView Wizard Example


20/69

20

iView Creation Wizard Using an iView Template


21/69

21

iView Creation Wizard


22/69

22

iView Creation Wizard (cont.)


23/69

23

iView Creation Wizard (cont.)


24/69

24

SAP Transactions GUI comparison

WIN GUI

! SAPGUI client needs to be installed on Windows

! Seamless integration and great performance

! Fully-integrated SAPGUI features

WEB GUI

! Zero application footprint on Client browser-based

! Required component ITS server (integrated ITS on WAS 6.40

or Standalone ITS 6.20)

! Performance screen repainted each time

JAVA GUI

! Client installation for Java GUI downloaded at Runtime

! Performance better than WEB GUI


25/69

25

GUI Comparison in Detail

Low Integration:

Colors/Display can be

changed based on pre-

defined combinations in

SAPGUI, but not follow

same look and feel asPortal themes

Low Integration:

Colors/Display can be

changed based on pre-

defined combinations in

SAPGUI, but not follow

same look and feel asPortal themes

High Integration: Style

sheets can be modified

based on Portal themes

Presentation

Some ConfigurationNone

Internet Transaction

Server Required -

Standalone 6.20 or

Integrated ITS - 6.40

Server Side

Requirements

Installation of Java GUIclient software (10MB)

Installation of SAPGUIclient software on client

Zero Installation on Client Browser-based

Interface

ApplicationFootprint

SAPGUI for Java

provides platform

independent support for

Mac OS, OS/2, Linux,and other UNIX

platforms, both within

and outside a Web

browser

SAP GUI for Windows

provides native support

on Windows platformsand is the most

robust of all the GUIs

offered by SAP

The SAPGUI for HTML

runs in place in the

browser. The contents

are generated by theInternet Transaction

Server (ITS). The SAP

GUI for HTML need not

be installed separately on

the client computers.

Overview

Java GUIWin GUIWeb GUIComponent


26/69

26

GUI Comparison in Detail (cont.)

Since this method also is

involved in maintaining

client and server

configuration,

maintenance becomes a

huge task. In addition, itis not widely used in the

SAP community.

This is a huge and

impractical effort to

maintain workstations in

an environment of more

than few hundredworkstations

The scope of theSAPGUI for HTML is

restricted by the inherent

limitations of HTML and

Web browsers. Although

you can map most

screen elements andcontrols used on SAP

screens to HTML, some

controls have restrictions.

Limitations

High: Performance is

good (content is

rendered at runtime)

High: Performance is

same as SAP GUI

client software

Low-Medium: HTML

screen is re-painted with

each click

Performance

Web-based access via

Java GUI iViews on the

Portal (client software

needs to be installed to

access functionalityotherwise)

Web-based access via

WIN GUI iViews on the

Portal (client software

needs to be installed to

access functionalityotherwise)

Web-based access to all

SAP Transactions via ITS

server (No Portal

required; however iViews

can be created to accessfunctionality - content is

rendered at runtime)

Functionality

Java GUIWin GUIWeb GUIComponent


27/69

27

SAP BW Content Integration

You can use Visual Composer to integrate BW content

Standard iView templates exist for creating iViews for

BW reports and BW queries

BI Java SDK is one development option

! Access to SAP and non-SAP data warehouse sources

! Provides interoperability between various BI sources

BW report access on Portal two options:

! Security control led in BW standard landing page with

report tree

! Security controlled in Portal integrated role-based reporting


28/69

28

SAP CRM Content Integration

CRM PCUI content integration! Best practice

! Instead of customizing existing BSP PCUI applications,

create a new Web Dynpro iView!Modifying/customizing PCUI blueprint tables is complex

CRM queries integration!

BW dril ldown queries for detailed sales, marketing, andbusiness partner data

Solution database integration! Provides tight integration of the solution database on the

portal. For example, customer interaction center and solut iondatabase integration on the same page provide fastercustomer service and response time.


29/69

29

2. Business Package Content

SAP Portals Business Packages (BPs) are portal-based

solutions that rapidly empower anyone to collaborate

and operate more efficiently through bringing relevant

applications, information, and services to users roleand responsibil ity

! Key components of Business Packages include:

!Role-based enterprise portal

!Collection of reports and queries

!Pre-defined integration to applications

!Taxonomy of content and documents! Integration of Internet content


30/69

30

2. Business Package Content (cont.)

! Key benefits of Business Packages include:

!Build portal applications quickly and easily

!Make users productive, fast!

!Fully pre-configured packages with task-related worksets!Download packages easily

! Get integrated business processes

!Get built-in business processes

!Pick packages that meet business needs

!Benefit from SAPs extensive business experience

! Get maximum flexibility

!Expand business capabil ities as needed with packages!Expand back-end access as needed


31/69

31

Business Package Content Information via SDN

SDN content portfol io:

! https://www.sdn.sap.com/sdn/contentportfolio.sdn

! Over 8,000 iViews

! Lots of Business Packages

!Employee Self-Service

!CRM

!Manager Self-Service

!Procurement

!Sales

! Industry-based solutions

!Third-party integration


32/69

32

Business Package Content Tips and Gotchas

Gotcha!! Make sure all pre-requisites are satisfied prior to

installing a BP

! Installing a Business Package does not mean content isreadily available some configuration and setup isalways required

New features! Business Packages can now be UN-DEPLOYED with

SDM (NW04)

Tip!

! Always gather business requirements first and then analyzewhat business package fits your need instead of analyzingwhat business packages f its your businessTip


33/69

33

3. Methods/Tools for Integrating Custom-Developed Content

Application Integrator

NWDS Netweaver Developer Studio

Netweaver Visual Composer Java iViews PDK for Java JCo and JCa connector

.NET iViews PDK for .NET


34/69

34

Application Integrator

Used to integrate (Web) applications flexibly

! For example, passing parameters or providing credentials

! These applications could be SAP applications or any

application that comes with a Web (HTTP/HTTPS) front end.Parameters could be static or retrieved dynamically.

Application Integrator is integrated with NW04 Portal

(.PAR can be downloaded for EP 6 SP2 and below)


35/69

35

NWDS for Web Dynpro

Model-based UI development

! Separation between UI logic and business logic

Independent of client technology

Model-View-Controller based architecture

Can build re-usable components

Open platform


36/69

36

NWDS Web Dynpro Application View

View Editor

Data ModelerOutline View

Perspective


37/69

37

NWDS Web Dynpro Application View Components

Perspective

Displays the Web Dynpro application and all i ts components

View Editor

Displays view contents

Consists of seven tabs for properties, context, layout, plugs,

actions, methods, and implementation

Previous screen shows the layout of View EmailFormView

Outline View

Outl ines all the elements that view contains

Data Modeler

Displays how the data is flowing and how it is mapped

between model (BAPI) and view


38/69

38

For the above Screen:

Email Model: Model imported from R/3 system. It will contain the structure of

the BAPI.

Component Controller: Its l ike a mediator between model and the different

views that a component contains

We have to map the data from model to component controller and then from

component controller to the view. Once mapping is done data will

flow automatically.

NWDS Web Dynpro Application Description


39/69

39

Easy Integration of Web Dynpro iViews


40/69

40

Visual Composer

Visual Modeling tool

! iView creation without any development/coding required

! Sophisticated User Interface design and development using

visual modeling tool

! Creates code automatically JSP, Java, and HTMLB code

Reduced total cost of ownership (TCO)

! Increased ROI

! Minimal effort to create content

Content integration via BAPIs and function modules

! Point-and-click interface to add input and output parametersto the iView

With the new Visual Composer tool you can easily

create Evented iViews

Vi l C Fl E l


41/69

41

Visual Composer Flow Example

iView Input

Fields

BAPI/Function

Module Bank Get

List to which

fields are input

Bank List is

returned based

on input

The Bank List Selected is

submitted to

BAPI/Function Module for

Bank Details

Bank Address isreturned

PDK f J


42/69

42

PDK for Java

PDK for Java can be downloaded from SAP Service

Marketplace as a business package for EP 6.0

Allows to create and execute portal components and

services locally

! Based on IDE workbench

! Consists of APIs to develop custom content on the portal

! Provides plug-ins to simplify programming to create

Web services

! Provides a platform to develop your own connectors

PDK f NET


43/69

43

PDK for .NET

.NET platform is adopted by many organizations

PDK for .NET enables SAP EP content development with

Visual Studio .NET

.Net connector enables you to integrate SAP content via

function modules, BAPIs RFCs

Integrated PDK development environment enables you

to create iViews with the same look and feel as

your portal

4 Eventing


44/69

44

4. Eventing

What is Eventing? Communicating changes in data orconditions as they occur to portal users across applications

and organizations

! Eventing on SAP Portal is a framework that enables iViews to

communicate with each another on the client side

! For example, update one iView and reflect changes based on your

selection on the other

Eventing enables you to provide very visual user interfaces! Portal provides access to multiple systems instead of making the user

hunt for information on a particular topic

Use evented iViews in dashboard-type scenarios to provide morebang for the buck and in scenarios where users will have to

navigate multiple iViews/Systems to retrieve a piece of

informationTip

Eventing Example


45/69

45

Eventing Example

Eventing

User Enters

Material

Number

Details forMaterial 100

are populated

in evented

iViews

What Well Cover


46/69

46

What We ll Cover



Integrating non-SAP content

Other topics: Knowledge Management and Unification


Wrap-up

Integrating Non SAP Content


47/69

47

Integrating Non-SAP Content

What is non-SAP content?

! Web-based content easy to integrate via URL iViews or

Application Integrator to pass parameters

! Other applications e.g., Peoplesoft , JDEdwards, mainframeapplications, Oracle, etc.

!Create custom applications Web Dynpro, Java, .NET, etc.

Integrating Non-SAP Content (cont )


48/69

48

Integrating Non-SAP Content (cont.)

Email content

! Groupware: MS Exchange, Lotus Notes

Structured and non-structured data in other systems

and file servers

! Structured data like transactional content, reports, etc.

! Unstructured content l ike email, documents, etc.

RDBMS data SQL, Oracle

! Database content accessed via varied appl ications, forms, etc.

What Well Cover


49/69

49

What We ll Cover






Wrap-up

Portal Knowledge Management


50/69

50

Portal Knowledge Management

Applications around unstructured information

People-centric collaboration

! Threaded discussion

! Collaboration rooms

!

Real-time chat! Ad hoc Web meetings

! Ad hoc workflow

Enterprise content management

! Create portal repositor ies

! Integrate external repositories

Federated search

Open framework

! Plugable repository managers

!

Plugable services! Standard Interfaces WebDAV, ICE

Connectors to d ifferent platforms

! HTTP, FTP, FILE, WebDAV, LDAP

! JDBC, IMAP, UDDI

KM Applications

Repository Services

Repository Framework

Repository

Manager

Repository

Manager

Enterprise Portal

Repository

Manager

Collaboration Publishing

Retrieval &

Text MiningSubscription

KM and TREX


51/69

51

KM and TREX

Document Management solution

! Integrated repositories for data/content

Powerful search and retrieval system

! Searching unstructured information

Ability to build trained taxonomy to allow classification

of content

Custom crawlers

! Crawl KM repositories

! File management systems

! Web

Unification


52/69

52

Unification

Unification provides drag & relate capabil ities onyour portal

Achieved via utilizing content unifiers

! UI components that interact with the system

The unification server provides universal administrative

tools to set up and manage drag & relate relationships

! Separate installation/server

Types of Unifiers


53/69

53

Types of Unif iers

R/3 Unifier! Enables drag & relate between SAP R/3 appl ications

B/W Unifier

! Enables drag & relate between BW appl ications

SQL DB Unifier

! Enables drag & relate between SQL DB objects

Enterprise Application Unifier

! Enables integration of other third-party applications

Unification Drag & Relate to Integrate Content


54/69

54

g g

Easily find related data across applications

Drag & relate is an easy to use navigation tool

To get more information about the highest value sales

order that has not been delivered, the user:

!Drags the Customer ID

!Relates it to the Sales Order component

!The Sales Order is displayed

What Well Cover


55/69

55






Wrap-up

Best Practices to Integrate Any Content on Your Portal


56/69

56

g y

Start small! Implement your portal in phases small steps

! Integrating simple content is the best to start your

EP implementation Use page layouts smartly

! Adjust height, width properties

! Use them to provide pertinent information to users

(example: Alerts, headlines, etc.)

Spend time on usability! Try not to integrate multiple types of iViews on a single

page to improve performance! Pay attention to user needs

Best Practices to Integrate SAP Content


57/69

57

g

Analyze Business Package content, if applicable, perbusiness requirements to jumpstart SAP content

delivery on your portal

Avoid translating portal as a front-end to all SAPtransactions

! High maintenance

! High TCO

! Low value proposition

Instead, analyze content, user groups, user

demographics, and usabil ity of the portal to design andintegrate content

Best Practices to Integrate SAP Content (cont.)


58/69

58

Avoid implementing various types of iViews on asingle page

! e.g., WEB GUI iView, Visual Composer iView, Web Dynpro

iView, and Evented iView

Test WEB GUI applications thoroughly

! Warning! Not all WEB GUI applications work as designed

Spend time on desktop environment! Make sure the SAPGUI version is correct and that the

required/recommended version for functionality is

implemented to avoid getting an error during processing

Best Practices for Integrating Non-SAP Content


59/69

59

Analyze the best way to integrate non-SAP content! Various factors influencing the decision

! In-house skills and capabil ity to develop custom iViews

!Easiest solution to maintain

Target applications that are easy to build

! URL iViews

! VC iViews

! Simple Java iViews

Best Practices to Handle Usability Issues


60/69

60

Common issues with usability

Issues Resolutions

Critical Success Factors

User Acceptance

Process Change

Organizational Change

Usable

Functional

Accessible

Well-Managed

Addressing all barriers to success

Integration into Service Delivery Model

Directed and Aggregated ContentIntegrated Information and Transactions

Organized and Task-directed Taxonomy

Portal Management Structure

Spend Some Time on Usability


61/69

61

! Human Factors

! User Needs/Usefulness! Motivations

! Subjective Satisfaction

! Cultural Expectations

People

! Work Flow

! Inputs and Outputs! External Processing

! Tasks

! Business Satisfaction

Process

! Appl ication Flow

! Error Handling! Exception Handling

! Technology Capability

! Data Integration

Technology

! Navigation/Taxonomy

! Content Relationships

! Labeling and Language

! Functionality

! Branding/Recognition

! Colors and Fonts

! User Flows

! System Flows

Examples of what is

measured

! Whats the effectiveness, efficiency, and satisfaction with which users canachieve tasks required by the business and end deliverable product or system?

Remember! The Portal Evolves and Matures


62/69

62

ROIPotential

Information

Publishing

Database

Inquiry

Simple

Transactions

Complex HR

Transactions

Workflow

Over the Web

Broad and blendedfunctionality from multipleservice providers

Seamless access to otherapplication systems

Workflow automation intoWeb-based transactions

Strategic planning,knowledge management,and planning tools

Database

Inquiry

Complex

Transactions

Level 5Level 4Level 3Level 2Level 1

Broader self services someof which move beyondtraditional HR services

Personalized anddynamic content

Some tools such as benefitscollaboration and search

Portal Maturity

Content Integration Summary


63/69

63

Modifying CRM business package

iViews via BSP may take a lot moreeffort, especially modifying the

blueprint tables for the PCUI

transactions, and you may want to

explore building custom Web

Dynpro iViews

A lot of CRM content is available as a

Business Package. When integratingWebIC, transactions launched from within

CIC, are executed utilizing the ITS server

and may not be as performance effective

as executing the WebIC client or

WIN GUI transactionsCRM Content

Although you can integrate BW

reports/queries into the Portal via

iViews (an iView per report/query),BW data quickly expands,

increasing the maintenance on the

Portal for roles, iViews, etc.

Maintain roles and security in BW system,

and publish the report tree on the WAS to

integrate the same in an iViewBW Content

Modifying business package iView

can be challenging and take a lot of

time and effort (simple layout

changes are possible without mucheffort). Opt instead of creating a

new Web Dynpro iView for

required functionality

Pre-delivered SAP content should be used

to integrate content whenever available for

required functionalityBusiness Packages

Things to RememberBest Practice

Content Integration

Method

Content Integration Summary (cont.)


64/69

64

KM content can be stored/retrieved from

various kinds of repositories including

existing document storage applications

and file servers

Knowledge

Management

Content

Web Dynpro iViews are developed

in the NWDS environment using

visual tools and modelers, and cansave you a lot of time and effort vs.

creating custom Java applications

Web Dynpro content is developed in the

Netweaver Developer Studio environment

and can be used to develop most custom

content in your organization. You can

even build Web Dynpro iViews to connectto your legacy applications and mainframe

applications.

Web Dynpro-Based

Content

Visual Composer is a good tool for

business users, but complexscenarios cannot be built using VC

Visual Composer is a WYSIWYG

development environment, specifically

targeted for business users without

programming knowledge who can produce

front-end screen for SAP function modulesand also customize BW report interfaces

Visual ComposerBased Content

Based on the complexity of iViews

you may want to explore building

Web Dynpro iViews as it may be

less effort to develop a complex

iView using the Web Dynpro dataview modeler

Utilizing the Jco and Jca connectors, you

can create custom iViews to connect to

your back-end systems to build evenevented iViewsJava Based Content

Things to RememberBest PracticeContent Integration

Method

What Well Cover


65/69

65






Wrap-up

Resources


66/69

66

SAP Developer Network! How-to-Guide Web Dynpro

!https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/l

ibrary/uuid/7bfea990-0201-0010-44a7-84a74971b795 SAP Library

! Platform Availability Matrix for EP 6.0

SDN Weblog! Content Integration Robert Chu

7 Key Points to Take Home


67/69

67

Assess the business requirement to choose the bestmethod of integrating content on EP

EP is not designed to externally face all SAP

transactions. Although this can be done, it may not bethe best practice.

Integration of business packages is not as simple as

installing the software; it takes a lot of integration toenable a business package. Research requirements and

pre-requisites before installing/integrating a BP.

External databases/content sources can be configuredas KM repositories to integrate structures and

unstructured information on EP

7 Key Points to Take Home (cont.)


68/69

68

More often than not, it is easier to write a custom iViewthan trying to modify standard BSP transactions. This

holds very true especially in the case of CRM.

Standard out-of-box SQL server connector is deliveredwith Unification easy way to integrate database content

Start small integrate content in phases/releases to

ensure user adoption and success of your portal

Your Turn!


69/69

69

How to contact me:Payal Jain

[email protected]

Questions?

Documents

Tools and Best Practices to Integrate Content Into Your Portal