Overview of SAP NetWeaver Overview of Enterprise Portals

1
Overview of SAP NetWeaverOverview of Enterprise
Portals
2
SAP NetWeaverTM
3
SAP NetWeaver

• SAP NetWeaver is a single integration platform
• Leverages core SAPs strengths
• Proven, mission critical
• Integrated out of the box
• Low TCO
• Delivers the foundations for all application
  needs
• Complete
• Built to extend SAP and to integrate non-SAP
• Open, standards-based

4
NetWeaver Components
6
5
4
3
2
1
7
8
5
1. SAP Web Application Server (WAS)

• Application Platform
• Provides a way to develop JAVA applications and
  ABAP applications that can easily reach back into
  the world of ABAP code
• Provide the premier interactive development for
  the J2EE platform

6
WAS Features

• SAP NetWeaver Developer Studio
• Eclipse-based IDE (JAVA based)
• Environment is enhanced with plug-ins that
  provide specific functions for developers
• A PDK which plugs into Visual Studio for .NET
  developers
• J2EE 1.3 Support
• Release 6.40 provides full support for the J2EE
  1.3 platform
• ABAP Engine
• Allows you to develop and run ABAP applications
  within the server

7
WAS Features

• Web Dynpro
• Creates professional user interfaces while
  minimizing manual coding
• Uses visual design tools and reuses UI components
• Users Model-View-Controller architecture, clear
  separation between UI and backend services
• Open SQL
• An abstraction of the database that allows more
  platform independence than JDBC
• Allows a direct relational interface or an
  object-based interface to access data with little
  work on the part of the developer

8
WAS Features

• Java Dictionary
• Incarnation of the ABAP dictionary in the J2EE
  world
• Java Development Infrastructure
• Overcomes the limitations of file-based control
  systems
• Uses design time repository and component build
  services to eliminate complete recompiles for
  small code changes

9
2. Exchange Infrastructure (XI)

• A platform for process integration based upon the
  exchange of XML messages
• Provides a technical infrastructure for XML-based
  messages exchanges in order to connect SAP
  components with each other, as well as non-SAP
  components
• Delivers business-process and integration
  knowledge to the customer, in the form of SAP
  predefined business scenarios
• Provides a tool set for building new scenarios

10
3. Master Data Management (MDM)

• Is designed to provide a unified view of data
  from a distributed and heterogeneous environment
• It is a tool kit to do any or all of these
• Have a central repository that is a master copy
  of all the data
• Have a virtual master or central copy of all the
  data in a unified schema

11
MDM
12
4. BI - The Solution at a Glance
13
Key Capabilities

• Data Warehousing BW Administrative Workbench
• Extraction, transformation and loading
• Data warehouse management
• Business modeling
• BI Platform
• Online analytical processing (OLAP)
• Data mining
• Alerting
• Meta data repository
• Planning framework

14
Key Capabilities

• BI Suite of Tools BW Business Explorer
• Query design
• Managed reporting and analysis
• Visualization web application design
• Collaboration
• Pre-configured Business Content

15
5. SAP Enterprise Portal (EP)

• Provides an integrated, single point of access to
  heterogeneous IT systems
• Role-based content and collaboration tools
• Integrates people with information - knowledge
  management of unstructured data and unification
  of structured data
• Provides window to data both inside and outside
  their organization and provides tools for
  managing it
• Provides predefined content (Business Packages)
  and building blocks (templates)

16
EP Components

• iView technology
• For creating and administering iViews
• Customers can used iViews delivered by SAP or
  create their own graphically or using JAVA, JSP,
  .NET, ASP languages
• Role technology
• Portal pages (made of iViews) of a particular
  task or area are bundled as roles
• Individuals can be assigned one or more roles,
  gaining access to those pages that are
  appropriate

17
EP Components

• Unification technology
• Facilitates unified access to enterprise
  applications to enable Drag and Relate operations
• Page builder
• Renders HTML pages which allows user interaction
• User management
• Single sign on to all systems
• Use role management
• Create users and assign then roles

18
Example iViews
19
EP Screen
20
Enterprise Portal Design Tools
21
Portal Content Studio
22
Visual Composer
23
Developer Studio (Web Dynpro)
24
Developer Studio (JAVA/PDK)
25
Visual Studio (.NET PDK)
26
Knowledge Management

• To tap the contents of text documents by
  structuring and classifying them so relevant
  information is available
• Content management functions for authoring and
  publishing information in portals uses WevDAV
  and XML
• TREX information retrieval solution finds
  text quickly and builds taxonomy tree
• Collaboration Room and Real-time collaboration
  (RTC) supports teams

27
Different Users Need Different Information
28
SAP EP is that Central Point
29
SAP NetWeaver KM

• It is impossible to centralize all the
  information in a single repository
• Knowledge Management provides
• One search capability
• One unified navigation scheme
• One look and feel
• One access to KM services on top of distributed
  repositories
• KM consists of
• Content Management
• Search and Classification (TREX)

30
6. Solutions for Mobile Business
31
7. CAF

• Composite Application Framework
• A model-driven development environment that
  allows applications to be assisted by the use of
  modeling to describe the structure of the
  application so that code and interfaces of
  various sorts can be generated.

32
8. SAP Life Cycle Management

• Standard off-the shelf process
• Code is written
• Code is documented
• Code is tested
• Bugs are found, new versions may be published
• Code needs installation scripts
• Need the ability to apply patches

33
Overview of Enterprise Portals
34
Portal Content Objects

• iView
• Program that retrieves data and displays it in
  the content area
• Page
• Contains layout and content (iViews)
• Workset
• Collection of tasks, services and information
  that is part of a role
• Role
• Collection of tasks, services and information
  available for a group of users, determines what
  can be accessed, provides visualization and
  navigation

35
Portal Content Objects
Role
User
Workset
Page
iView
36
Typical Object Assignments

• Pages include iViews
• Worksets include iViews and pages
• Roles include worksets
• Groups include users
• Roles are assigned to users or groups

37
Portal Content Directory (PCD)

• All content objects are stored in the PCD
• Delta links object reuse
• Creation of relationships between objects
• Generic transport mechanism
• Personalization
• Object notification
• Versioning
• Permissions to use access control lists (ACLs)
• Filter mechanism and search

38
Hierarchical PCD Structure
iView
39
Portal Content Studio

• Content ? Content Administration
• Navigation panel (left)
• Tabs Browse or search
• Portal content tree shows PCD
• Quick info describes properties of object
  selected

40
Portal Content Studio

• Editing area is displayed
• Object tabs select one of multiple objects you
  are editing
• Object editor tools changing actions and
  operations
• Object editor allows editing the object
• Child object editor edit child objects
• Property editor customize the properties

41
Reusing Objects

• Copy an object
• In the portal catalog, you can create a new
  object by copying an existing object and pasting
  it elsewhere as an object
• You can insert one content object into another
  object as a copy
• Once the copy is made, there is no future
  relationship between the two objects

42
Reusing Objects

• Create Delta Links
• Create an object based on a template new object
  inherits all the properties of the original and
  is delta linked
• In the portal catalog, you can create a new
  object by copying and existing one and pasting
  them as a delta link
• You can insert one content object into another
  object as a delta link

43
Delta Link

• Properties are object parameters that permit the
  configuration and personalization of content in
  the portal
• These properties get set in the property editor
• When a new object (target) is delta linked to
  another (source), it inherits its properties
• If the properties of the source is changed, the
  properties of the target will also change
• If you change the targets properties, those
  properties will no longer be delta linked

44
iViews For SAP Applications

• You can integrate the following SAP applications
  in SAP EP iViews
• SAP Transactions
• Internet Application Components (IACs)
• Business Server Pages (BSP) applications
• WebDynPro and Visual Composer applications
• SAP BW reports
• Generic databases
• RSS Feeds
• URLs

45
R/3 Transaction
46
Integrated SAP Systems

• SAP Transaction R/3 Transaction Codes
• SAP GUI for HTML
• SAP GUI for Java
• SAP GUI for Windows
• SAP IAC Internet Application Components
• ITS
• SAP BSP BSPs with Web WAS 6.1
• SAP WEB Web Dynpro with WAS 6.3
• SAP BW Report SAP BW

47
Naming Conventions

• Each PCD object has a unique name made up of the
  following
• Complete path to the object
• pcdpottal_content/BusAdm746/S903000/.
• Optimal namespace prefix (do not use in this
  course)
• Base name of the ID
• iView001

48
Demonstration

• Browse portal catalog
• Create folder in the portal catalog
• Working with iViews
• Use existing iViews
• Copy
• Delta link
• Create iViews (templates)
• Web-based URL iViews
• R/3 Transaction

49
Working with Pages

• A portal page holds iViews and pages organized in
  a layout
• User can arrange content on the page by moving
  iViews (and pages) from one container to another
  (they can not alter arrangement of containers)
• They can select a different layout, with a
  different arrangement of containers

50
Out of the Box Layouts

• Predefined layouts
• 1 column (full width)
• 2 columns (equal width)
• 2 columns (narrowwide)
• 2 columns (widenarrow)
• 3 columns (narrowwidenarrow)
• You can create new layouts based upon these

51
Demonstration

• Creating a portal page

52
Roles

• Role
• A role is defined to provide access to a set of
  common tasks
• A user or group of users are then assigned to
  that role
• Role is the largest semantic unit within content
  objects
• A user can only access content for which they
  have been assigned a role
• Role structure defines the navigation structure

53
Worksets

• Lets you bundle iViews and pages in folder
  hierarchies
• A workset is always part of a role
• A workset can belong to more than one role
• You can not assign worksets to users

54
Roles and Worksets

• Role can contain the following objects
• Roles
• Worksets
• Pages
• iViews
• Templates for pages and iViews
• Worksets can contain the following objects
• Worksets
• Pages
• iViews
• Templates for pages and iViews

55
Creating a System

• A system definition provides the connector or
  middleware that allows that system to talk to
  EP
• Methods for creating a system
• Existing template
• System Landscape wizard
• Copy and paste an existing system
• Content developers reference a system through an
  alias

56
View a System in Landscape
57
System Property Editor