If you work with Teamwork Cloud projects, you can simulate them on the server without using a modeling tool. You can execute your models either by using REST API or via Cameo Collaborator for Teamwork Cloud user interface (if there are Cameo Collaborator documents published from those models).
Preparing the environment for server-side simulation
Server-side simulation runs in Teamwork Cloud, therefore you need to have access to a working Teamwork Cloud instance.
To prepare the environment for server-side simulation
- Install Teamwork Cloud if you have not already done that.
- Stop Teamwork Cloud services (No Magic AuthServer, No Magic WebApp)
- Go to <Teamwork_Cloud_installation_directory>\WebAppPlatform\webapps directory and replace the webapp.war file with another webapp.war file provided by your sales executive.
- Go to <Teamwork_Cloud_installation_directory\WebAppPlatform\shared\conf directory and open the webappplatform.properties file.
In the file, make sure the following property is specified: | Code Block |
|---|
flexnet.server.name=<server_ip/server_address> |
- Restart the Web Application Platform.
Preparing projects for server-side simulation
To simulate a project on the web, it has to meet the following criteria: - A project has to be added to Teamwork Cloud.
- For simulation results to be saved, you need to specify the Result Location property of a Simulation Configuration. The value of the Result Location property should be the instance in which you want to save the simulation results.
- The executable model should not require any user input. This means that simulation needs to be performed fully automatically.
- The executable model must end automatically without any user input.
Server-side simulation limitations
There several limitations related to server-side simulation: - Currently, there is no UI in the simulation web application, so UI-based features (like charts, timelines, controls, breakpoints, animation, variables tree, etc.) are not available.
- You can execute only one simulation at a time.
- Max 15min The execution duration cannot exceed 15 min.
- Project options are not cannot be read, defaults so default option values are always used instead of the actual project optionsones.
- Math engine integrations (Matlab, mathematicaMathematica, etc..) are not available.
- Trade Studies with Excel file are files are not available.
- The ExcelHelper API is not available.
- Scripts from the attached JAR files are not available.
- FMI/FMU co-simulation is not available.
- UseCase Execution is not available.
- Executing on Execution of historical project revision is revisions is not available.
- Validating runtime model based on Requirements Requirement-based runtime models is not available.
- Lifelines representing Property Properties with nested paths in InteractionEngine are not available.
- DSL stereotypes are not applied on to created Slot and InstanceSpecification elements
- Finding elements by Name (e.g Signals, Operations with ALH, mapping with ExcelHelper) is not available.
| 