Title: Introduction to Visual Composer
1Introduction to Visual Composer
2Visual Composer
- SAP Visual Composer (VC) provides a development
environment for rapidly creating and adopting
model-based transactional and analytical
applications.
3Enterprise Portal Design Tools
4VC Design Criteria
- Simplicity
- Fast development model-based applications no
coding - Small set of highly-reusable easy concepts
- Graphical interface is user friendly
- Browser based
- Reusable components
- Reuse functionality from model to model
5VC Design Criteria
- Tightly integrated to SAP NetWeaver 2004
- Connectivity to SAP and third party systems
- Using portals, ERP, BW, JDBC and web services
- Different runtime environments
- Web Dynpro and Adobe Flex
- Test-and-Redo
- Quick modeling
6Modeling in VC
7Model Creation Workflow
- Define your application needs
- What are your data sources
- What UI components do you need
- Layout, controls and etc.
8Model Creation Workflow
- Create your page and iView
- Dragging the icons from the elements task panel
- Naming accordingly
9Model Creation Workflow
- Find system, then locate data service
- BAPIs from SAP systems
- Tables from SQL databases
- Queries, tables, cubes from BI
- Web services
10Model Creation Workflow
- Design the iView logic
- Dragging forms, operators and UI elements onto
the workspace - Connect them for proper flow
- Format the design in layout mode
11Model Creation Workflow
- Deploy model and view it in runtime
- Check iView in both design time and runtime
12Overview - Application Modeling
- Design Time
- Visual Composer is a design-time software tool
- Define all runtime attributes and properties
- Runtime Environments
- Implements in XML-based Visual Composer language
- Model once run anywhere
- Web Dynpro Flex
13Overview - Application Modeling
- Creating and Adapting Applications
- Create from scratch
- Or adapt an existing application
- Data Services
- SAP RFCs remote function call
- SAP BAPIs business APIs
- Business warehouse info cubes, BI queries
- JDBC relational databases
- Web services
14Overview - Application Modeling
- Storyboard
- GUI called work desk, work space, drawing
board - Three different boards
- Graphical modeling elements
- Screen layout actual look and feel
- View source code
15Overview - Application Modeling
- Workflow
- Drill down from upper-level model entities down
to the lowest-level elements and controls - Events
- An event is a signal that an action has occurred
(like click a submit button) - Modeling elements (such as data flow lines) are
modeled to respond to these events
16Overview VC Architecture
- The Visual Composer is installed on the
development server, running on the J2EE engine
which also runs the portal - The storyboard is accessed from the client using
a browser - At runtime, the user deploys the model to the
portal and views the application on the portal - The deployed content is also stored in the Portal
Content Directory (PCD)
17Overview VC Architecture
18Working with VC
- Prerequisites
- Enterprise Portal installed (2004s)
- End user computer accessing storyboard
- Microsoft IE 6.0 or higher
- Adobe SVG Viewer 3.0 (view storyboard)
- Microsoft XML parser 4.0 or higher
- Flash environment (view resulting application)
19Working with VC
- Prerequisites (cont)
- Portal connected to back end systems
- Permission to access portal and have VC role
- Mapped as a user to backend systems on portal
- For BI, BW, JDBC
- Install required connectors
- Define systems and aliases in portal
20Working with VC
Menu
Task Panel
Navigation
Tool Bar
Work Space
Tool Box
21Working with VC
- Main Menu
- Main Toolbar
- Navigation Toolbars
22Working with VC
- Tabbed Workspace
- Board Toolbox
23Working with VC
- Task Panel
- Task Panel Toolbar
24Working with VC
25Using VC Log On
- Logging On
- http//sbasap09.sba.uwm.edu50000/VC
- Note VC is case sensitive
- Enter userid and password
- The same as you use for portals
- Note The logon screen looks the same as the one
you use for portals - Click Log on
26Using VC - Logon
27Using VC - Logon
28Demonstration
- Look up sales orders for a customerusing a R/3
BAPI
29Demo Customer Search
Results Table
Search Form
Search
Search Data
Customers List
30Demo Create a New Model
A. New Model
B. Name the model
31Demo Create an iView
A. Compose ? iView
B. Double click on iView
32Demo Find IDES System
A. Find Data ? IDES_Fall07
33Demo Browse for Service
A. Look For Browse Service Catalog ? Reload
34Demo Select BAPI
- BAPI_SALESORDER_GETLIST
- Drag onto work area
35Demo Select Search Fields
A. Select Customer Number and Sales Organization
36Demo Select Report Fields
37Demo Add Input Form
A. Drag input port onto work space, add Input Form
38Demo Add Table Form
A. Drag Sales Orders output port onto work space,
add Table View
39Demo - Model
40Demo View Layout
A. Click on Layout Tab
41Demo View Code
A. Click on Source Tab
42Demo Deploy Model
A. Deploy ? Deploy entire model ? Deploy
43Demo Run Model
A. Click on Run, Portal will appear
44Demo - Output