Currently Being Moderated

Sharing the Accumulated Wisdom of Building Composites

Mark your calendar  for Tuesday, Sept 7, 2PM Pacific / 23:00 CET for a special SAP Mentor Webinar hosted by me, and featuring Harald Schubert and Ulf Fildebrandt, architects with SAP Development talking about their recently released document "Composite Development Architecture Guidelines".  Replay links:

Webinar Chat log: Guidelines for Composition Application Architecture 

Webinar Replay: https://sap.na.pgiconnect.com/p91966188 

 

Join us for an informative session where Harald and Ulf discuss the guidelines they recommend for building applications with SAP NetWeaver CE and BPM and the reasoning and customer experience behind them.   Hear other experienced SAP Mentors share their stories about implementing composite applications as they comment on the guidelines.

 

Here's an example of a guideline you'll hear about in this upcoming webinar:

 Guideline:  "Select a leading artifact within your composition that will dictate storage of composite context" - Page 10

This guideline resulted from customer projects where customers were trying to maintain a large "context view" of related data that was being passed step-to-step and even between process instances that were operating on the same data objects.  As a result, this continual serialization of duplicate business objects understandably led to performance problems.

The guideline goes on to state that the lead artifact designates the scope of data within  the lifcycle in the following manner:

  • If process definition is the most important entity, then context persistence only lasts until the end of the process instance
  • If data is the most important entity, then the key business objects need their own lifecycle, and CAF is a good choice. In the above example, data migration and governance was the application, so the specific business objects being governed needed a lifecycle beyond specific process steps or process instances.
  • If data is only relevant in one UI task, then data can be stored within a Web Dynpro context.

 

Implications of leading artifact for your project management

While this guideline specifically deals with architecting your application for optimal performance of data serialization, you can see how the above guideline actually has implications for managing the entire project. 

Composite applications are a multidisciplinary approach.  And, when incorporating BPM, they even include a management philosophy.  Selecting your lead artifact is in a sense selecting your foremost layer in the composite architecture: presentation, business logic, backend services & persistence, and integration.  If maintaining and improving data quality are the primary goals of the process, then it makes sense for business objects and persistence to be a key architectural component.

Hear more at the upcoming SAP Mentors Webinar

Webinar Chat log: Guidelines for Composition Application Architecture 
Webinar Replay: https://sap.na.pgiconnect.com/p91966188

Related sessions at SAP TechEd Las Vegas

One of our guests, Harald Schubert will be presenting a couple of related sessions at SAP TechEd Las Vegas.  If you would like to more detail, then be sure to book Harald's sessions:

Comments

Actions

Filter Blog

By date: