What are the different parts of an analytic composite application?

SAP xApp Analytics combine business know-how, process know-how, and software know-how into a form that amplifies the power of existing data and functionality. In practice, this means this work is accomplished by knitting a composite application out of five parts: the user interface (UI), process logic, and services from transactional enterprise applications and those for analytics and collaboration.

Everything starts with the needs of the enterprise, department, team, and organization. What are the critical metrics or success indicators? Where does this data reside, and would enterprise services, web services, APIs, or periodic data "dumps" be the appropriate way to go?

The business logic comes next. What information needs to be presented to the actual user at what time, what action options are appropriate, and would these interactions be with backend SAP processes, third-party applications, or homegrown tools? Will this process span intradepartmental efforts or cross over partner, supplier, and customer boundaries? This business logic, available options, and analytic guidance are developed, customized, simulated, and deployed using SAP NetWeaver Visual Composer, a model-driven development environment that enables and accelerates development. The powerful, simple, model-driven nature of SAP NetWeaver Visual Composer means that the population of people who can create or modify an analytic composite application can grow ...

Get Enterprise SOA now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.