====== SDK Job Management ======

==== General ====

The SDK Job Management consists of a script, a trigger and a job.\\ The script performs a specific function such as sending an SMS, mounting a USB stick or listening to a serial interface.

​

The trigger triggers the script. The trigger can be based on an event or on a time. Events can be based on all sorts of features of the router. \\ Example: incoming call, successful/failed SMS, interfaces are powered up/off, VPN functions are enabled/disabled and many more. A script can also be triggered manually via the CLI.

​

When the job is created, a trigger can be assigned to a script.

​

​

==== Script ==== 

To do this, navigate to Services -> Job Management -> Scripts -> Add on the web interface.

{{ :configuration:jobmanegement_scripts.png?nolink |}}

Here a name(regex), a description and the arguments of the script can be passed. Furthermore, the script is created here by writing(edit), uploading(uploading) or selecting it from memory(select).

{{ :configuration:jobmanagement_scripts_edit.png?nolink |}}

​

For the script we're using, [[https://wiki.netmodule.com/sdk/reference|the Arena language and the API Manual]].

​

==== Trigger ==== 

==Events:==

It is triggered whenever the event occurs.

​

{{ :configuration:jobmanagement_trigger.png?nolink |}}

​

Here sdk-startup was chosen as the trigger. This means that the script is triggered every time sdk starts, including when booting up. If system-startup is selected, only the system-startup of the router is triggered. If you select cliphp as the trigger, you can trigger the trigger manually via a browser. The command is: nmevent -e "cliphp" -m "TRIG". "cliphp" is the event and "TRIG" is the name of the trigger.

==Date&time:==

If you use a time-based trigger, the following menu is displayed.

{{ :configuration:jobmanagement_trigger_time.png?nolink |}}

​