SAP Netweaver Capabilities

SAP Jave AS supports J2EE standard, version 1.3 and 1.4


SAP Web Application Server


ABAP WorkBench
- ABAP Editor
- ABAP Dictionary
- Screen Painter
- Menu Painter
- Function Builder
- Class Builder

ABAP Categories
- Screens (With ABAP Dictionary integrated inthe system, automatic consistency checks for screen input fields (type, foreign key, fixed value checks).
- Lists (display data using minimum programming effort)
- Classes (similar to a function group but multiple instances. contains data objects (attributes) and functions (methods))
- Function modules (actively integrated modularization units with an interface. They can be called primarily from within programs or other function modules. elements are: import paramenters, Export parameters, Changing parameters, Exceptions)



Features of SAP Web AS Platform
- Server-based and Client-based Web Applications
- ABAP
- Java
- Business Communication Services
- Connectivity
- Database and Operating Systems
- SAP Knowledghe Warehouse

SAP Exchange Infrastructure (XI)

SAP Integration Builder

- Central development environment for the development of all design objects for theintegration Repository at design time.

- Defines all configuration objects for the integration Directory at configuration time

Prerequisites to Design

Business Process Components

Business processes are initially designed in the Integration Builder and only utilize abstract messages. The processes are finalized and configured in the Integration Directory. At the execution time, the processes are executed within the Business Process Engine (BPE)

Cross-Component Business Process Management

- Provides integrated capability to design, model, and execute complex distributed interfacing scenarios involving homogenous and heterogeneous systems

Components of BW

- Enterprise-wide data warehousing

- Business intelligence platform

- Business Intelligence Tools

Technical Components of SAP NetWeaver Master Data Management

- SAP EP

- SAP MDME Console

- SAP MDME Client

- SAP MDME Importy Manager

- SAP MDME Syndicator

- SAP Exchange Infrastructure

- SAP Business Warehouse

Architecture of SAP NetWeaver MDM

Master Data Management

Core Components of SAP NW MDM

- Master-data consolidation

- Master-data harmonization

- Central master-data management

Developing Portal Content

-SAP EP Portal Content Studio

- SAP NetWeaver Visual iComposer

- SAP NetWeaver Developer Studio (Web Dynpro)

- SAP NetWaver Developer Studio (Java + PDK Perspective)

SOA Principles

Design Fundamentals
- Design Characteristic (Te-Zhen)
- Design Principle (Yuan-Zhe)
- Design Paradigm (Si-Lu)
- Design Pattern (Mo-Shi)
- Design Pattern Language (Mo-Shi-Yu-Yan)
- Design Standard (Bia0-Zhun)
- Best Practice (Jin-Yan-Zhong-Jie)

Fundamental Design Framework
Design Principles Centered


Design Patterns Centered

Service-Oriented Computing
- Service-Oriented Architecture
- Service-Oriented Design Paradigm
- Service-Oriented Solution Logic
- Service Compositions
- Services
- Service Inventory

Web Service Architecture
- Service Contract
- Core Service Logic (Business Logic)
- Message Processing Logic


Service -Oriented as a Design Paradigm
- Standardized Service Contract
- Service Loose Coupling
- Service Abstraction
- Service Reusability
- Service Autonomy
- Service Statelessness
- Service Discoverability
- Service Composability

Design Principles




Principles and Design Granularity
- Service Granularity
- Capability Granularity
- Data Granularity
- Constraint Granularity

Impacts of Standardized Service Contract
- Service Loose Cupling (affects the quality of attainable)
- Service Abstractio (affects the extent of attainable)
- Service Reusability (establishes conventions that affect the potential of attainable)
- Service Discoverability (Introduces contract design conventions that can enhance or constrain)
- Service Composability (may introduce contract content requirements that support)

Service Contract Coupling Types
- Logic-to-Contract Coupling (contract drives logic)
- Contract-to-Logic Coupling (logic drives contract)
- Contract-to-Technology Coupling underlying technology)
- Contract-to-Implementation Coupling (implementation environment)
- Contract-to-Functional Coupling (external logic)

Service Consumer Coupling Types
- Consumer-to-Implementation Coupling
- Consumer-to-Contract Coupling

Coupling and Service Models
- Entity Services
- Utility Services
- Task Services
- Orchestrated Task Services

Impacts of Service Loose Coupling
- Standardized Service Contract (can influence the design standards for)
- Service Abstraction (emphasizes some forms of)
- Service Reusability (establishes a complementary form of centralization that maximizes opportunities for)
- Service Autonomy (Increases levels of attainable)
- Service Discoverability (regulates published meta information used for)
- Service Composability (helps prevent dependencies that inhibit)

Type of Meta Abstraction
- Technology Information Abstraction
- Functional Abstraction
- Programmatic Logic Abstraction
- Quality of Service Abstraction

Contract Content Abstraction Levels
- Detailed Contract
- Concise Contract
- Optimized Contract
- Mixed Detailed Contract

Access Control Levels
- Open Access
- Controlled Access
- No Access

Impacts of Service Abstraction
- Standardized Servie Contract (can influence the design standards used for)
- Service Reusability (regulates the quantity and nature of meta information published in support of)
- Service Composability (regulates the quantity and nature of meta information published in support of)
- Service Discoverability (regulates the quantity and nature of meta information published in support of)
- Service Lossse Coupling (can influence the extent of attainable)

Measures of Planned Reuse
- Tactical Reusability
- Targeted Reusability
- Complete Reusaqbility

Impacts of Service Reusability
- Standardized Service Contract (encourages the design of highly generic)
- Service Abstraction (challenges)
- Service Loose Coupling (emphasizes)
- Service Discoverability (emphasizes)
- Service Autonomy (emphasizes)
- Service Statelessness (emphasizes)
- Service Composability (forms the basis of)

Risk Associated with Service Reusability and Commercial Design
- Cultural Concerns
- Governance Concerns
-Reliability Concerns
- Security Concerns
- Commercial Design Requirement Concerns
- Agile Delivery Concerns

Type of Service Autonomy
- Runtime Autonomy (execution)
- Design-Time Autonomy (governance)

Measuring Service Autonomy
- Service Contract Autonomy
- Shared Autonomy
- Service Lgic Autonomy
- Pure Autonomy

Impacts of Service Autonomy
- Standardized Service Contract (encourages the normalization of)
- Service Loose Coupling (directly supports)
- Service Abstraction (can influence the level of)
- Service Reusability (increases the potential of)
- Service Statelessness (increases the potential of)
- Service Composability (increases the potential of)

Types of State
- Active and Passive
- Stateless and Stateful
- Session and Context Data

Measuring service Statelessness
- Non-Deferred State Management (low-to-no istatelessness)
- Partially Deferred Memory (reduced statefulness)
- Partial Architectural State Management Deferral (moderate statelessness)
- Full Architectural State Management Deferral (high statelessness)
- Internally Deferred State Management (high statelessness)

Impacts of Service Statelessness
- Service Reusability (increases service scalability and availability in support of)
- Service Autonomy (can establish design characteristics that can both support and hinder)

Type of Discovery
- Design-Time Discovery
- Runtime Discovery

Discoverability Meta Information
- Functional Meta Data
- Quality of Service Meta Data

Impacts of Service Discoverability
- Standardized Service Contract (influences the content and design standards for)
- Service Abstraction (needs to be balanced against)
- Service Reusability (supports enterprise-wide)
- Service Composability (supports the creation and evolution of)

Impacts of Service Composability
- Standardized ServiceContract (supports)
- Service Loose Coupling (supports)
- Service Abstraction (supports)
-Service Reusability (supports)
-Service Autonomy (supports)
-Service Statelessness (supports)
-Service Discoverability (supports)

Evolutionary Cycle States of a Composition
- Composition Design Assessment
- Composition Runtime Assessment
- Composition Governance Assessment

Impacts of Service Composability
- Standardized Service Contract (Influences design standards for)
- Service Abstraction (introduces the "hidden composition members" consideration which requres careful positioning of)
- Service Loose Couping (emphasizes decreased)
- Service Reusability (introduces special considerations because it is a sophisticated form of)
- Service Autonomy (amplifies the need for high levels of)
- Service Statelessness (requires highly standardized)
- Service Discoverability (encourages composition-centric meta data in support of)

Zachman Enterprise Architecture Framework

Rows:
Row 1 – Scope (Planner's View0
External Requirements and Drivers
Business Function Modeling

Motivation/Why
Business goals, objectives and performance
measures related to each function
Function/How
High-level business functions
Data/What
High-level data classes related to each
function
People/Who
Stakeholders related to each function
Network/Where
Organization locations related to each function
Time/When
Cycles and events related to each function

Row 2 – Enterprise Model (Owner's View)
Business Process Models
Business Function Allocation
Elimination of Function Overlap and Ambiguity

Motivation/Why
Policies, procedures and standards for each process
Function/How
Business processes
Data/What
Business data
People/Who
Organization roles and responsibilities in each process
Network/Where
Organization locations related to each process
Time/When
Events for each process and sequencing of integration and process improvements

Row 3 – System Model (Designer's View)
Logical Models
Project Management
Requirements Definition

Motivation/Why
Organization policies, standards and procedures associated with a business rule model
Function/How
Logical representation of information systems and their relationships
Data/What
Logical data models of data and data relationships underlying organization information
People/Who
Logical representation of access privileges constrained by roles and responsibilities
Network/Where
Logical representation of the distributed system architecture for organization locations
Time/When
Logical events and their triggered responses constrained by business events and their responses


Row 4 – Technology Model (Builder's View)
Physical Models
Technology Management
Solution Definition and Development

Motivation/Why
Organization rules constrained by information systems standards
Function/How
Specifications of applications that operate on particular technology platforms
Data/What
Database management system (DBMS) type requirements constrained by logical data models
People/Who
Specification of access privileges to specific platforms and technologies
Network/Where
Specification of network devices and their relationships within physical boundaries
Time/When
Specification of triggers to respond to system events on specific platforms and technologies

Row 5 – As Built (Integrator's View)
As Built
Configuration Management
Deployment

Motivation/Why
Organization rules constrained by specific
technology standards
Function/How
Programs coded to operate on specific technology platforms
Data/What
Data definitions constrained by physical data models
Data/What
Data definitions constrained by physical data models
Network/Where
Network devices configured to conform to node specifications
Time/When
Timing definitions coded to sequence activities on specific platforms and technologies

Row 6 – Functioning Enterprise (User's View)
Functioning Enterprise
Operations Management
Evaluation

Motivation/Why
Operating characteristics of specific
technologies constrained by standards
Function/How
Functioning computer instructions
Data/What
Data values stored in actual databases
People/Who
Organization personnel and key stakeholders working within their roles and responsibilities
Network/Where
Sending and receiving messages
Time/When
Timing definitions operating to sequence activities


Rules:
Rule 1: Columns have no order
Rule 2: Each column has a simple, basic model
Rule 3: Basic model of each column is unique
Rule 4: Each row represents a distinct view
Rule 5: Each cell is unique
Rule 6: Combining the cells in one row forms a complete description from that view

Federal Enterprise Architecture Framework V1.1

National Institute of Standards and Technology (NIST) model
The NIST model has been promoted within the Federal Government as a management tool that illustrates the interrelationship of enterprise business, information, and technology environments. The five-layered model allows for organizing, planning, and building an integrated set of information and information technology architectures.

Purpose
. Organize Federal information on a Federalwide scale
. Promote information sharing among Federal organizations
. Help Federal organizations develop their architectures
. Help Federal organizations quickly develop their IT investment processes
. Serve customer needs better, faster, and cost effectively

Value
. Promote Federal interoperability
. Promote Agency resource sharing
. Provide potential for Federal and Agency reduced costs
. Improve ability to share information
. Support Federal and Agency

Framework Components

1. Architecture Drivers

2. Strategic Driection

3. Current Architecture

4. Target Architecture

5. Transitional Processes

6. Architectural Segments

7. Architectural Models

8. Standards

Pinnciples
1. Standards: Establish Federal interoperability standards.

2. Investments: Coordinate technology investments with the Federal business and architecture.

3. Data Collection: Minimize the data collection burden.

4. Security: Secure Federal information against unauthorized access.

5. Functionality: Take advantage of standardization based on common functions and customers.

6. Information Access: Provide access to information.

7. Proven Technologies: Select and implement proven market technologies.

8. Privacy: Comply with the Privacy Act of 1974.

Federal Enterprise Architecture Framework, Level I

(the view from 20,000 feet)

Federal Enterprise Architecture Framework, Level II

(the view from 10,000 feet)

Federal Enterprise Architecture Framework, Level III
(the view from 5,000 feet)

Federal Enterprise Architecture Framework, Level IV

(the view from 1,000 to 500 feet)

The Zachman Framework

Enterprise Architecture Planning (EAP)

is a "how to" approach for creating the top two rows of the Zachman Framework, Planner and Owner

Design Architectures

Remote Access using NetMeeting

1. Setup Remote Desktop Sharing on Windows Server
1.1. Launch NetMeeting: “Start” button->Programs->Accessories->Communications->NetMeeting
1.2. Click on menu “Tools”->”Remote Desktop sharing…’
1.3. Check the box “Enable Remote Desktop Sharing on this computer”
1.4. Click “Wizard…”, follow through wizard steps, enable a password-protected screen saver, and click “Finish”
1.5. Click “OK” to close “Remote Desktop Sharing Settings”
1.6. Close NetMeeting Application
1.7. An icon of NetMeeting Remote Desktop Sharing is displayed on the status bar at the bottom
1.8. Right-Click on the icon and click on menu “Activate Remote Desktop Sharing”
1.9. Now the NetMeeting Remote Desktop Sharing is activated. It should stay activated after every restart


2. Remote Access Windows Server Computer
2.1. Following steps are on Windows Server Computer
2.2. Find Windows Server Computer Name: On Desktop->My Computer icon->Right-Click->Properties->”Computer Name” Tab
2.3. Capture the text in “Full computer name:”. For example, current server has the text “computer1.yourcompany.com”
2.4. End of steps on Windows Server Computer
2.5. Following steps are on client computer
2.6. Launch NetMeeting: “Start” button->Programs->Accessories->Communications->NetMeeting
2.7. Click menu “Call” -> “New Call…”
2.8. In “To:” box, type or paste the full computer name of the Windows Server Computer. For example, current server full computer name is “computer1.yourcompany.com”
2.9. In “Using:” box, leave the option “Network”
2.10. Ensure “Require security for this call (data only)” checkbox is checked
2.11. Click “Call” button
2.12. The “Remote Desktop Sharing Password” window pops up. It asks credentials (User, Password and Domain) on Windows Server Computer.
Note: The User and Password are not for local client computer, they are for remote Windows Server Computer which has GEMS database installed
2.13. Enter User and Password that can login to Windows Server Computer
2.14. In “Domain:” box, enter “nam” (this is three letter word without quotes, see example)
2.15. Click “OK” button
2.16. The Remote Windows Server Computer screen is displayed and can be controlled on local client computer

TOGAF

TOGAF = The Open Group Architecture Framework

What kind of architecture does TOGAF deal with?
– Business Architecture - this defines the business strategy, governance, organization, and key business processes
– Data Architecture - this describes the structure of an organization's logical and physical data assets and data management resources
– Applications Architecture - this provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization
– Technology Architecture - this describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services

What it is

(TOGAF)
• Generic
• Process Driven
• “One size fits all organizations”
• Flexible
• Set of Conceptual Tools
• Providing generic deliverables

(ADM)
• A step-by-step approach to developing an enterprise architecture
• Method - a way, technique, or process of or for doing something
• Process - a series of actions or operations towards an “end”

What it is Not

(TOGAF)
• Prescriptive and HOW to Customize the Framework
• Prescriptive and Artifact driven
• Specific to company size or to an industry
• Ontology Driven
• Tool
• Prescribing a specific set of deliverables
(ADM)

• The whole TOGAF
• Framework
• Chair in an ivory tower
• Quick & easy

TOGAF

Architecture Development Method

Enterprise Continuum
A virtual repository of all architecture assets
– Models, patterns, architecture descriptions
– Deliverables produced in this iteration of the ADM
– Deliverables produced in other iterations of the ADM
– Assets from the industry at large

• TOGAF provides two reference models for possible inclusion in an organization’s Enterprise Continuum
– The TOGAF Foundation Architecture
– The Integrated Information Infrastructure Reference Model

Resource Base

A set of resources, guidelines, templates, background information etc..
• For reference during application of the ADM
• Covers a broad range of topics used to develop an architectur

Enterprise Architecture Life Cycle (EALC)

The Strategic Alignment Model (Enterprise Value)

Preliminary Phase: Framework & Principles

Phase A: Architecture Vision

Phase B: Business Architecture

Phase C: Information Systems Architectures

Phase D: Technology Architecture

Phase E: Opportunities & Solutions

Phase F: Migration Planning

Phase G: Implementation Governance

Phase H: Architecture hange Management

Requirements Mnagement