![]() A usage type can be run separately in different systems (so interfaces between usage types must work locally as well as remotely).A usage type can share a system with other usage types.The relationship between components and Usage Types is illustrated in the following table: Former component name But, since Usage Types are a pre-determined and configured collection of software components, they encompass more than components provided by themselves. Usage Types are where there is the biggest relationship to the former components. Dough can be used to make both cookies and pizza. It is the way they combine the ingredients that create unique dishes. The vendors in the food court all use the same ingredients and hardware (ovens, grills, etc.). ![]() Usage Types may also be built on and/or leverage other Usage Types. Usage Types are realized by installing and configuring a collection of software components. A Usage Type determines the role which a SAP NetWeaver system plays in a landscape and the intended purpose of a system. A Usage Type represents a logical view of the SAP NetWeaver Technology platform. The different vendors in the food court provide menus according to the demands of the users.īut something has to be installed somewhere.Įnter Usage Types. The lunch cashew chicken and a chocolate chip cookie is a composite business process made up of individual services ordered and combined to make the process. The overall business process is the meal lunch eaten by a user. The cookie and the chicken are services ordered off of the menu of service providers. Lets say the meal, then, is cashew chicken and a chocolate chip cookie. Or (back to food), you get your entrée from the Chinese restaurant in the food court and dessert at the cookie place at the end its still a meal. In this case, the definition of system is very blurry and intentionally abstract does it really matter what systems the engines reside on if the processes are eventually combined (and abstracted) into a higher level composite application? The ultimate service architecture throughout a landscape, for example, can be a set of process engines that are waiting around to be put to use (kind of like a food court at a mall). Components, however, do not really describe what a service architecture can provide. In fact key capabilities, as seen in The Refrigerator view, are the most understandable groupings of technologies that most resembles the former product/component view. Components are a historical term that imply a monolithic structure of a system and are not entirely compatible with the actual integrated platform of SAP NetWeaver. This used to be components, but as I mentioned in Part III, the component view of SAP NetWeaver is being replaced. In other words, at some point IT Scenarios actually require software on hosts. Now that an IT Scenario Variant has been selected, we are getting very close to what the IT personnel actually need to install. Here, in the final installment, we will see how that helps out the IT department who has to implement SAP NetWeaver Part IV Usage Types In Building the Bridge – Part III, I talked about selecting business processes off of the IT menu with IT Scenario Variants.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |