Learn more about MATLAB Compiler

Lifecycle of a Deployed MATLAB Web Application

On this page…
Introduction MATLAB Programmer Business Service Developer Front-End Developer Server Administrator Internal Analyst End-To-End Developer

Introduction

How does a single piece of M-code become a deployable, portable, robust, scalable Web application? Through skillful deployment by a number of people in an organization, each playing distinct and significant roles.

The following diagrams depict the supported implementation and architectures available when using MATLAB application deployment products.

Deployed Application Tier Interactions

Back to Top

MATLAB Programmer

The first phase in a deployed application's life begins when code is written in MATLAB by a MATLAB programmer, whose objective is sharing it with other people either within or outside of the organization. To accomplish this objective, the programmer uses MATLAB Compiler. MATLAB Compiler makes M-code usable by people in vastly different environments who may not have knowledge of MATLAB or the M language.

When MATLAB Builder JA (for Java language) or MATLAB Builder NE (for Microsoft .NET Framework) is installed along with MATLAB Compiler, M-functions can be encrypted and wrapped in Java or .NET interfaces. The MATLAB programmer takes these deployable components and gives them to the business service developer.

Back to Top

Business Service Developer

At this point in the deployment lifecycle, integration is usually required in order to make the deployed application work with the existing applications in the organization. The Business Services Developer installs these deployable applications along with the proper version of the MCR, and converts MATLAB data types to native language data types so they can be used without any coupling to MATLAB in other tiers of the installation architecture. When the Java or .NET component is called, it will instantiate the MCR to execute the underlying MATLAB code. Once these services are exposed (either as Web services or through an API) Front End Developers can connect to them and use them.

Back to Top

Front-End Developer

Front-end developers are typically responsible for user-visible functionality and know little about under-the-covers implementation. Their primary concern is the stability and security of the organization's data within the confines of a firewall. Once the front-end developers create some mechanism for exposing the application functionality to the end user, it is up to the end user to complete the lifecycle by interacting with the application to perform some task or solve some business problem. External users typically achieve this through a Web browser.

Back to Top

Server Administrator

Server administrators are responsible for keeping the servers up and running, meeting the IT department's commitments to the rest of the organization as outlined in SLA agreements. They are not MATLAB experts and may or may not know much about integrating deployed applications in various computing environments. However, they are expert in understanding which versions of which computing environments (JREs and .NET frameworks, for example) can co-exist and run stably in order to achieve the end-user's desired results.

Back to Top

Internal Analyst

Internal analysts may use the Web site or may interact with the business tier directly. In this case, an example of a common activity would be when a financial analyst accesses a business tier Web service and a complex Microsoft^® Excel^® model. Or, they access an internal Web site, performing specific tasks not available to their customers.

Back to Top

End-To-End Developer

The end-to-end developers are virtual "one-stop shops." They are MATLAB experts, but are also skilled in many of the areas of expertise as the business service developer and front-end developer, though their level of expertise may vary over their many areas of responsibility. To this end, this guide presents examples of comprehensive deployment tasks scoped specifically to the time and resource constraints typically faced by end-to-end developers.

Back to Top

MATLAB Web Application Environment

MATLAB Programmer Tasks

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