Scenario

A scenario is a document describing the data and behavior of one or more services for the simulation server. The simulation server is embedded into the ApiGear Studio tool. The simulation server can be used using the simulation protocol over HTTP or WebSockets. Support for the simulation protocol does come with most of ApiGear Blueprint Templates.

It can provide simulation to one or more services and their operation endpoints. The format of a scenario is described here.

schema: apigear.scenario/1.0
name: "count scenario"
version: "1.0"
interfaces:
  - name: demo.Counter
    state:
      count: { value: 0 }
    methods:
      - name: increment
        actions:
          - add: [ $state.count, $params.step ]
      - name: decrement
        actions:
          - add: [ $state.count, $params.step ]

Variables

In actions you can reference the state and an operation parameters using the $state and the $params prefix. You can use them to read the value of the variable or to write to the variable.

Action

At several places the scenario uses action sequences. A sequence is a list of actions each action is an object with a key of the action command and a array value as the action arguments.

- command: [ argument list ]

When an action changes the state a state changed notification will automatically be send after all actions of the sequence have been run.

Typical actions are

• set sets a value - set: [$state.count, 5 ] - similar the state.count = 5
• signal emits a signal from the simulation: - signal: [ shutdown, { timeout: 5 }] similar to signal('shutdown', { timeout: 5} )

other actions are add, sub, mult, div. There are more to come.

Playbooks

A playbook is a time based execution of actions. A playbook has a name and can be triggered from an action or can run automatically on simulation start.

playbooks:
  - name: increment counter
    interval: 2000 # 2 seconds  
    loop: true # start over when at end
    steps: # step is called every 2 secs according to interval
      - name: increment
        actions:  # list of actions
        - set: [ $state.count,  1 ]
        - signal: [ shutdown, 10]
      - name: clear
        actions:
        - set: [ $state.count, 0]
        - signal: [ shutdown, 7]    

The interval defined the tick and on each tick a step is running. If loops is true then the playbook will start again after finished.

Schema Data

When a state or return statement defines a value it can be defined as static value using the value notation or it can also be mocked using a schema notation.

For example to create a random count value you can between 0 and 100 you can create a schema.

schema: apigear.scenario/1.0
name: "count scenario"
version: "1.0"
interfaces:
  - name: demo.Counter
    properties:
      count: 
        schema:
            type: integer
            minimum: 0
            maximum: 100

Now on every call to retrieve the service state it will return a number between 0 and 100.