development framework for service-oriented application

Development Framework forDevelopment Framework forService-OrientedService-Oriented

Application InstrumentationApplication Instrumentationand SAP R/3 Modeland SAP R/3 Model

Andreas KöppelUniversity of Karlsruhe, Germany

[email protected]

Application Management Starts at the Application Developer!

DMTF 2001 Developers' Conference June 11-13, 2001

RoadmapRoadmap

• Application Management• Framework

– Model Requirements– Model Design– Provider Implementation

• SAP Model– Systems– Landscapes


ScenarioScenario: SAP R/3 (I): SAP R/3 (I)

Presentation

Internet

Application

Database

Web-clients

Web Server Internet Transaction

Server (ITS)

Database

App-Server

. . .Web-

clientsClient Client

CreateProduction

Orders

ReleaseProduction

Orders

ScheduleProduction

Accept Customer

Order

ConfirmDelivery

BuildProducts

ExplodeBill -of-Material

ReserveMaterial

CustomerService

Rep

PlantPersonnel

ProductionOrder

CustomerOrder

Part Material Task

App-Server App-Server

Layer 3-tier Multi-tier

System


ScenarioScenario: SAP R/3 (II): SAP R/3 (II)

Developer

Company boundary

Computing Center

Operator

SAP Customer

User

Server Client

Software (R/3)

Company boundary(eventually)

R/3 Basis Development

Regional Support


FCAPSFCAPS

• Configuration mgmt incl. software distribution(installation)

• Accounting incl. software asset mgmt and softwarelicense mgmt

• Security mgmt including virus protection

Application

Accounting Performance Security

Fault Configuration


LifecycleLifecycle

Particularly important: Running,Executable= Operation

Deployable Executable RunningInstallable


ServiceService Level LevelManagementManagement

SLM widens the management context of theapplication.

Service

Application

Implementation

Analysis

Control

MeasurementReporting

SLA

defines

influences

AvailabilityPerformance(Throughput,

Response Time)Recoverability


RoadmapRoadmap





Goal (I)Goal (I)

Agent (Provider)

Mgmt ContextOriented

Meldungen

Operationen

Application= Resource

Workflows

Instrumentation

SLA Support

ResourceOriented

Development Framework

• standard-based

• model-based

supports user at the development of


Goal (II)Goal (II)

CIMOM

CIMRepository

access

Provider(s)

state

keys

configuration

performance

events

methods

associations

Application

inter-operate

integrate

Model

instantiate

store

ManagementApplication

access

ModelDocumentation

explain

history


ArchitectureArchitecture

Developer's View

AM starts at the application developer!

Development Framework

Concepts(Req. Eng.)

Integration(SW Design)

ImplementationSupport

CCWorkflows

SLA Support

Instrumen-tation

ProjectsRequirementsAM, SLM

App Models

Tool Kit

Modules


SubSub-Models-Models

initiallife cycle

deployable installable executable runningappstatus

multiplicity

sub-model

1:n 1:n 1:n

transportsetup

installation

runtime model

expectedexpected+

running

expected = configuration-derived: topology, dependencies, keys, status (no contact/lost comm)

availabilitythroughput

response timenumber of users

SLA support


Run-Run-TimeTime Model Model

initiallife cycle

executable runningappstatussub-model

installation

runtime modelfunctionalsystemsstructural

data/dataflow

external systemslandscapes

workflow = default+rollback+exception

best practices (tasks):routine (daily/weekly/...)

configurationanalysis

workflows

registrationconfigurationindications

history

methods


HierarchiesHierarchiesGenerally, top classes are CIM_System.• Structural containment hierarchy (explicit)• Functional containment hierarchy (explicit)• Inheritance hierarchy (explicit)• Status aggregation hierarchy (implicit)• Performance aggregation hierarchy

(implicit)• Event aggregation hierarchy (implicit)• Configuration hierarchy (explicit)


DesignDesign Tasks Tasks

• Create an initial model (implicit:load also)

• Modify the model• Explain the model (description

qualifier, instance models)• Simulate the model (static

instances, queries)• Design GUI of management

application


Supporting ObjectsSupporting Objects

• Generic application model templates• Design patterns• Property patterns• Event templates


Design SupportDesign SupportRepository Editor

Selection

visualrepresentation

textrepresentation

structuredrepresentation

visualisation data

Namespace

modelclasses

inheritedclasses

instances

File

instances

classes

coderepresentation

implementation code

Design PatternBrowser

Description Editor

Event ToolQuery Tool

BrowserNamespace Admin.

providercompilation


Editor Programs

Design SupportDesign SupportImplementationImplementation

Repository

CIMModelread only

read only

SelectionManager Update (XML)

MOFXML

Visio

XSLTHTML

.vsd

MOF-XSLT Parser

LoadXML

SaveXML

CIM Portal(Design Pattern

Browser,Model Browser)

• least dev effort

• built on existing tools

• visual modeling


PortalPortal


ImplementationImplementation Tasks Tasks

• Design provider environment• Integrate the model in the provider code and the

application code• Write additional management code• Test the provider• Revise the GUI• Write additional management application code• Test the management application• Package provider, model, management application


SupportSupport Objects Objects

• Provider data structure templates• Generic provider architecture templates• Code templates for certain classes and

property categories• Provider help classes (configuration file

access, log file access, scoped keysupport)


ProviderProvider• Install/Uninstall with the application• Uptime is independent of the app• Access data instances in the app’s memory

asynchronously (instances of classes andproperties)

• Provide information asynchronously(indications)

• Incite code execution asynchronously(methods)

• Discriminate the context of the app’s data(associations and keys)


App SystemTechnical EnvironmentTechnical Environment

Configuration

Process 1

Runtime Data

Process 2

Runtime Data

ProcessCIMOM

App Code on HD

Module A

Module B

Configuration

App Code on HD

Module C

Obj A1

Obj A2

Obj B1

Obj A3

computer system boundary

Provider(s)

Provider(s)

execute

execute

ProcessCIMOM

Process 1

Runtime Data

Obj C1

Obj C2


RoadmapRoadmap





SAP R/3SAP R/3 Architecture Architecture

Presentation

Internet

Application

Database

Web-clients

Web Server Internet Transaction

Server (ITS)

Database

App-Server

. . .Web-

clientsClient Client

CreateProduction

Orders

ReleaseProduction

Orders

ScheduleProduction

Accept Customer

Order

ConfirmDelivery

BuildProducts

ExplodeBill -of-Material

ReserveMaterial

CustomerService

Rep

PlantPersonnel

ProductionOrder

CustomerOrder

Part Material Task

App-Server App-Server

Layer 3-tier Multi-tier

System


OverviewOverview

• SAP System Component Repository• Future: SAP Landscape Directory• Focus on systems and software features• SAP core model


SystemsSystems

GroupComponent

PartComponent

*

1..*

DA_DSWSystemComponentSystem

GroupComponentPartComponent

11..*

DA_DASystemComponentLocalASystem

CIM_ApplicationSystem

{abstract}

DA_ApplicationSystem

DA_DistributedApplicationSystem


11..*

DA_DASystemComponentLASystem

DA_LogicalApplicationSystemDA_LocalApplicationSystem

{abstract}

DA_DistributedSoftwareSystem

• Systems: main building blocks of the model


{sap_abstract}SAP_ApplicationSystem

11..* SAP_BCSystemClient

{sap_abstract}SAP_DistributedApplicationSystem

*

1..*

SA

P_D

AS

yste

mC

ompo

nent

Sys

tem

SAP_BCClientSAP_BCApplicationServer

11..*

SAP_BCSystemApplicationServer

CIM_ApplicationSystem

SAP_BCMessageServer

11..*

SAP_BCSystemMessageServer

SAP_BCSystem

SAP SystemsSAP Systems

DA_ApplicationSystem

DA_DistributedApplicationSystem

DA_LocalApplicationSystem

DA_LogicalApplicationSystem


ExternalExternal Systems Systems

level 2blevel 2c

level 2a

level 1

CIM_System:ExtSystem

CIM_System:ExtSubSystem

ExtApplSystem

SWFeature

CIM_SWFeature:ExtSoftwareFeature

ExtApplSystem

SWFeatureCIM_Service:

ExtService

CIM_SAP:ExtSAP

ExtHostedAccessPoint

ExtHostedService

CIM_Product:ExtProduct

CIM_SWElement:ExtSWElement

ExtSWFeatureSWElements

ExtProductSoftwareFeatures

[ExternalView] class MyExternalClass: AnyClass {...};[Association, ToExternalView]class ExternalViewDependency: AnyAssociation {...};[Association, ToExternal]class ExternalDependency:CIM_LogicalIdentity {...};

ApplicationModel

ToExternalView

ExternalSystem

ToExternal


SAPSAP External External Systems Systems

• Computer system, database, webserver

SAP_BCApplicationServer

SAP_BCSystem

MachineType: stringOpSys: stringOpSysRelease: stringOpSysValid: stringSAPVersionsSupported: stringIPAddress: string

{ExternalView}SAP_ComputerSystem Antecedent

Dependent1

*SAP_BCApplicationServerHost

DBInstanceName: string

{ExternalView}SAP_DatabaseInstance

GroupComponent

PartComponent 0..11

SAP_BCSystemDB

Antecedent

Dependent *1..* SAP_BCUsingDB

Antecedent

Dependent

1

*

SAP_DBHost

GroupComponent

PartComponent

1

1..*

SAP_DBSystemInstance

Manufacturer: stringOwner: stringRelease: stringDBSID: string

{ExternalView}

SAP_DatabaseSystem

SAP_BCMessageServerAntecedent Dependent1 *SAP_BCMessageServerHost


SAPSAP Application Application Server Server

Number: string {MaxLen=2}AvailabilityMonitoringPolicy: stringInstanceProfileName: stringInstanceProfilePath: stringStartProfileName: stringStartProfilePath: stringHomeDirectory: string

SAP_BCApplicationServer

Release: stringPatchLevel: stringCompilationInfo: stringCompatibleDBSystemReleases[]: stringCompatibleBCSystemReleases[]: stringCompatibleOSReleases[]: stringDBSLVersion: stringDBClientLibVersion: stringABAPLoadVersion: uint16CUALoadVersion: uint16RunMode: string {MaxLen=3}

SAP_BCKernel


11

SAP_BCApplicationServerKernel

Type: string

SAP_BCKernelComponent

GroupComponent

PartComponent

1

*

SAP_BCKernelComponent

• CIM_SWFeature, CIM_SWElement

• Awkward to construct slim designs (OS, HW deps and SWF!)


Service AccessService Access Pts Pts (I) (I)

Host A (server) Host B (client)

:SAP_ApplicationService

ServiceServiceDependency

:SAP_ApplicationServicePort

CIM_ServiceSAPDependency

:SAP_ApplicationServiceReference

SAP_ApplicationServiceAccessByPort

SAP_ReferencePortDependency

optionaladdress and accessinformation that isequal for all clients

optionaladdress and accessinformation that isequal for all clients ona specific host

:CIM_ServiceSAPDependency

optionaladdress and accessinformation that isonly for a single client




Service AccessService Access Pts Pts (II) (II)

System B (client)System A (server)

ApplicationServer X



CIM_ServiceServiceDependency

Application LayerMiddleware

:CIM_ServiceAccessPoint



LoadBalanc:SAP_ApplicationService

:RFCComm:SAP_ApplicationService

CIM_ServiceAccessBySAP

...AccessByPort

ProtocolHostName

:SAP_TCPIPServicePort

Name...

:SAP_RFCDestination

...ReferencePortDep...

CIM_SAPSAPDep...

ProtocolHostName


ProtocolHostName


...AccessByPort

...AccessByPort

...ReferencePortDep...

Name...

:SAP_RFCDestination


SAPSAP Keys Keys (I) (I)• Each class defines an additional set of key

properties, the SAP key, in order to supportexisting SAP naming schemes

• CIM key properties, e.g. CIM_System.Name,are built out of SAP key properties in orderto provide a meaningful name to externaltools at design time


SAPSAP Keys Keys (II) (II)• A property having a SAP_KEY qualifier is part of

the unique name of an object, e.g.:SAP_BCClient

• The property to which the composition appliesis marked with a COMPOSITE qualifier: classSAP_BCClient {

[KEY, COMPOSITE]string Name = “003.SystemName.C11”[SAP_KEY]string SystemName = “C11”

...};


ScopeScope

• Objects are named within the scope of other objects,similar to the CIMs ‘weak’ association and ‘propagated’keys– E.g. a Client ‘001’ is unique within a SAP System

• Enhances flexibility towards classes down theinheritance hierarchy

CreationClassName {KEY}Name {KEY}...

SAP_ApplicationSystem

1* {SCOPE}

SAP_BCSystemClient

CreationClassName {KEY}Name {KEY, COMPOSITE}LicenseNumber {SAP_KEY}...

SAP_BCSystem

CreationClassName {KEY}Name {KEY, COMPOSITE}SystemCreationClassName {SAP_KEY, SCOPED="SAP_BCSystem.CreationClassName"}SystemName {SAP_KEY, SCOPED="SAP_BCSystem.Name"}SystemLicenseNumber {SAP_KEY, SCOPED="SAP_BCSystem.LicenseNumber"}...

SAP_BCClient


LandscapesLandscapes

Level 3

Level 2

Level 1

SystemAspectAnySystemLogicalIdentity

Landscape

AnyClass ClassAspectLogicalIdentity

ModelExtensionClass

Mutual CIMClass

Landscape

Core Model

[Landscape(“MyLandscape”)]class MyModel_MyAspect: MutualBaseClass {…};


InstallationInstallationDependenciesDependencies

• Similar to CIM_Check• Compatibility of a pair of products also

on the level of CIM_Product andCIM_SoftwareFeature.

• Dependencies: OS, hardware, SWcomponents and patchlevel

• Instantiation independent of the actualinstallation (as modeled by the DMTF)


ConclusionConclusion

• Framework: holistic approach toapplication model/provider developmentincluding service level management.

• SAP model: good basis for furtherrefinement of the model

• SAP model future: performance,business applications, events

• CIM has proved to be flexible and simpleenough


QuestionsQuestions??

development framework for service-oriented application

Documents