Compound applications

What is compound applications?
Composite applications are applications built from a combination of several existing functions using business sources of information. Composite applications are collections of software assets that are put together to provide business functionality. These assets are generally artifacts that are provided independently of one another to enable specific platform functions to be assembled and used.

Using a composite application can relieve a user of switching between applications. It provides instant access to multiple applications in the same place, with the added benefit of being able to add and remove functions manually. Compound applications can be compared to mashups. However, composite applications use business information sources, while mashups use web-based, mostly free, resources.

The four levels of compound applications are data, application, productivity, and presentation. A solution architect must deal with components, a composition stack, and composite application specifications. To select a composition stack, one or more containers must be selected from each layer. A number of component types must be able to be provided in the containers. Components are selected by defining a repository of assets to be built from component types based on business needs. Methods for connecting the assets must also be defined to provide a cross-functional process. These connections are loosely coupled.

An application is considered a well-adapted composite application if it conforms to a standard architectural design and has the following characteristics:

A complete user experience to bring many types of applications together in a single client view

Consistent and uniform GUI

Full authentication and data confidentiality

Flexibility to implement service-oriented architecture functions such as reusability and loose coupling to use

Behave as a unique application for heterogeneous applications

Intercommunication of the components

Reuse of computer assets

Composition of the parts

Aggregate multiple applications into a single client view

Providing access anytime, anywhere in a semi-connected environment

The client composite application infrastructure is a composite application runtime environment that is required to install and run applications that are specifically built in a WebSphere Portal Server environment. Compound applications also have a specific structure. Information workers form the highest level of the structure. You access documents and business information via portals. They also create documents during business activities that are part of larger business processes and coordinate the activities of systems and people. The activities are controlled by process-specific business rules that call up resources within a service interface. Business rules are ultimately applied to the contents of these documents in order to extract, transform and transfer information to the next stage of the process.

Assets for composition include workflows, documents, business activities and rules, schemas, UI screens, reports, metrics, etc.

Was the explanation to "Compound applications"Helpful? Rate now:

Further explanations for the initial letter C