Working with the Business Service Layer

On this page…
About the Business Service Layer About the Examples

Middle-Tier Developer

Middle-tier developer

Little to no MATLAB experience Moderate IT Experience Expert at business logic and services tier Java expert .NET expert Minimal access to IT systems Expert at J2EE Expert at .NET Web frameworks Expert at Web services

Integrates deployed component with the rest of the J2EE system by converting MATLAB data types (MWArrays) to the Java Business logic objects Integrates deployed component with the rest of the .NET system by converting MATLAB data types (MWArrays) to the .NET Business logic objects

About the Business Service Layer

Note   For comprehensive end-to-end implementations of the concepts in this chapter, see Sources for More Information.

Most software contains a business service layer, which is a set of interfaces, business objects (and logic to manipulate them), and mechanisms for data access that run the core business.

A typical business service layer contains the following sublayers:

• Interfaces — Typically the business service layer can implement several different interface types which all interact with common data elements and common business objects, all using the same business logic. Software and related services used to access business data from native or Web clients include:

  • SOAP services

  • Remoting interfaces

  • HTTP services

  • Java servlets

  • JSPs (for Java)

  • ASPX (for .NET)

• Business Objects and Logic — This is business data expressed in the form of objects along with the logic to manipulate the objects. This data is loaded by a combination of inputs from the interfaces and data from the data access layer.

• Data Access — This layer links to all lower-level data such as databases, where access into a deployed application would typically take place. Your generated component fits into this category, as it can be used as a mechanism through which to access the MATLAB Compiler Runtime (MCR).

Elements of the Business Service Layer

Back to Top

About the Examples

Depending on the size and complexity of an implementation some of these elements can overlap. The examples in this documentation assume direct communication from the interfaces into the DAO (data access object or wrapper utility) that you create.

All examples in this document are coded as stateless (with the exception of the MATLAB Builder JA™ WebFigures example) and are scalable. Servers can be added or augmented by a load balancer for performance tuning.

Tip   To scale MATLAB Builder NE WebFigures, use the .NET Distributed Session setting. This enables all machines in your Web farm to use the same session.

Back to Top

Middle-Tier Developer Tasks

Creating a DAO for Deployment

© 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS