Authorization and transaction management handled by the mashup layer

The mashup layer acts as a single point where authorization and transaction management are handled in a consistent way.

If a resource ID is not passed for authorization or if the request is not transactional, the request is not stopped. Instead, it continues through to the mashup and business logic layers.

Each invocation of a mashup is considered to be part of a transaction.

The following graphic illustrates an example of how the mashup layer handles authorization and transaction management.