-
Notifications
You must be signed in to change notification settings - Fork 8
Launcher
The launcher is the main component that starts the overall MMI environment. In particular, the component can optionally start all services and the available adapters using the MExecutableDescription file. Moreover, the component serves as central registry and provides information regarding the available adapters, services and MMUs. Especially, the target engine uses the Launcher to access the available Motion Model Units. It can be therefore considered as logical communication layer.
| <<interface>> MMIRegisterService |
|---|
| +GetRegisteredAdapters(sessionID: string): list +GetRegisteredServices(sessionID: string): list +GetAvailableMMUs(sessionID: string): map<MMUDescription,list> +RegisterAdapter(description: MAdapterDescription): MBoolResponse +UnregisterAdapter(description: MAdapterDescription): MBoolResponse |
| +RegisterService(description: MServiceDescription): MBoolResponse +UnregisterService(description: MServiceDescription): MBoolResponse +CreateSessionID(properties: map<string, string>): string |
Detailed description of available parameters/functions:
| Function Name | Description |
|---|---|
| GetRegisteredAdapters | Returns all registered Adapters in the current MMI environment. |
| GetRegisteredServices | Returns all registered Services in the current MMI environment. |
| GetAvailableMMUs | Returns all available MMus in the current MMI environment with the respective addresses at which the MMU is accessible. |
| RegisterAdapter | Allows registering an adapter in the current environment. |
| UnregisterAdapter | Allows unregistering an adapter in the current environment. |
| RegisterService | Allows registering a service in the current environment. |
| UnregisterService | Allows unregistering an adapter in the current environment. |
| CreateSessionID | Returns a unique session ID |
In general, the proposed launcher is provided with the released version of the framework. The launcher is able to start executables applications such as adapters or services. For this purpose a description file is required.
| MExecutableDescription |
|---|
| +Name: string +ID: string +Language: string +ExecutableName: string +Author: string +Version: string +Dependencies: list +Vendor: string +VendorDomain: string +ServiceURL: string +UpdateUrl: string |
Detailed description of available parameters/functions:
| Parameter | Required | Description |
|---|---|---|
| Name | x | The name of the application. |
| ID | x | Unique id of the application. |
| Language | x | |
| ExecutableName | x | The name of the executable file (e.g., adapter.exe or service.bat) |
| Author | x | |
| Version | x | |
| Dependencies | Optional dependencies to start the application. | |
| Vendor | Optional properties. | |
| VendorDomain | ||
| ServiceUrl | ||
| UpdateUrl |
- What is the MOSIM Framework?
- Components of the Framework
- Repository Structure
- RPCs with Apache Thrift
- Setting up the MMI-Environment
- MMU Development
- Target Engine Integration
- Integration in Unity
- Integration in UE4
- Integration in 3rd Party Engines
- Service Development
-
Intermediate Skeleton & Retargeting
- Concept of the Intermediate Skeleton
- Retargeting Service and Configurator
- Retargeting in Unity
- Retargeting in UE4
- Constraints