Deploy and Run SOA Applications
R2026bMultiple approaches are available for build, package, deploy, and run service-oriented architecture (SOA) applications. The approach you should choose depends on your development and target environment and on available or preferred tooling.
Once an application is running in the target environment, tools are available for tuning parameters, monitoring signal data, and logging signal and output data to an Association for Standardization of Automation and Measuring (ASAM) Measurement Data Format (MDF) file that you can then import into the Simulation Data Inspector for analysis.
Choose a Deployment Approach
Use this table as a guide for choosing a deployment approach.
| Deployment Approach | Reasons to Choose |
|---|---|
| Linux Runtime Manager app |
|
| Run on Custom Hardware app |
|
packNGo function |
|
Deploy By Using Linux Runtime Manager App
You can use the Linux Runtime Manager to deploy a system of applications if the Embedded Coder Support Package for Service-Oriented Applications on Linux is installed on your development computer. Using the Linux Runtime Manager, you can build, package, deploy, and run SOA application code on an ARM 64 Linux target computer.
For information on how to set up a target computer for use with the Linux Runtime Manager and how to build software component models and deploy applications, see Set Up Linux Target Computer and Build Simulink Model and Deploy Application, respectively.
Deploy By Using Run on Custom Hardware App
The Run on Custom Hardware app enables you to:
Build, deploy, and run the SOA application code on your development computer or a target computer by using external mode and XCP communication.
Perform the steps to build, deploy, connect, and run separately or with one click.
Use an external mode simulation for parameter tuning and signal monitoring.
To establish an external mode connection, instead of setting model configuration parameters, use the Run on Custom Hardware app to specify connection settings.
In the Software Component Designer app, open a software component model that you want to connect to a target computer.
Open the Run on Custom Hardware app.
Specify a hardware board. In the toolstrip, on the Hardware tab, from the Hardware menu, select the board setting for your development or target computer.
Specify a TCP/IP connection. From the Connection menu, select TCP - IP Address: "localhost" - Port:17725", the default connection settings, or Change Connection. If you select Change Connection, the app displays a TCP/IP connection parameters dialog box. In the dialog box, enter the target computer IP address and TCP port number, and click OK.
In the toolstrip, in the Run on Hardware section, specify a stop time (in minutes) and click Monitor and Tune and choose between using one-click or step-by-step commands for performing these actions:
Build the target application on your development computer.
Deploy the application to the target computer.
Connect Simulink to the application that runs on the target computer.
Start execution of the application on the target computer.
This table shows the workflow support that the app provides for your target hardware.
| Workflow Feature or Task | Target Computer | ||
|---|---|---|---|
| Development Computer | Custom Target Hardware | ||
One-click | Yes | Yes, if you set up connectivity between Simulink and your target hardware. | |
| Step-by-step | Build for Monitoring
| Yes | Yes. Software builds target application on development computer by using the toolchain that you specify. |
Deploy
| Yes | Yes, if you set up connectivity between Simulink and your target hardware. | |
Connect
| Yes | Yes | |
Start
| Yes | Yes | |
For information on how to set up external mode connectivity programmatically, see Set Up External Mode Connectivity Between Simulink and Target Hardware.
Relocate Application Code to a Development Environment By Using
packNGo Function
If your development environment does not provide MATLAB or Simulink, use the packNGo function to package generated
application code files in a ZIP file so that you can relocate, unpack, and build or rebuild
them in another development environment.
For information, see Relocate or Share Generated Code and Compile Code in Another Development Environment.
Tune Parameters and Monitor Signals
If you need to calibrate a software component model, set up the model so you can tune parameters and monitor signal data as the code runs on the target computer.
To enable parameter tuning and signal monitoring for a component model, before you build the model and deploy the application to the target computer, identify parameters that you want to tune and signals that you want to monitor. Then, see the topic in this table that aligns with your deployment approach:
| Deployment Approach | More Information |
|---|---|
| Linux Runtime Manager app | Tune Parameters and Measure Signal Data for Deployed Applications |
| Run on Custom Hardware app | External Mode Simulation by Using XCP Communication |
packNGo function | Relocate or Share Generated Code |
Log Application Execution Results to an MDF File
You can generate application code from a component model that logs signal and output data to an Association for Standardization of Automation and Measuring (ASAM) Measurement Data Format (MDF) file for analysis.
In the component model, specify signals and output data that you want the generated code to log.
Configure the component model for data logging. Select these model configuration parameters:
Signal logging or Output, or both to specify the type of data to log
Build the application.
Deploy and run the application on the target computer.
View the time series of generated code variables by doing one of the following
Import the MDF file into the Simulation Data Inspector.
Use Vehicle Network Toolbox™ MDF file functions.
For more detail and an example, see Log signals to MDF file.
See Also
Linux Runtime
Manager | Run on Custom
Hardware | packNGo | Log signals to MDF
file
