Send Command and Listener.

[esantos]

Hi, Oleg.

I have more than one routine sending command to initialize another task.
When a routine sends a command to start a task that has already been started by another task, the second command is lost and the routine is not started a second time.

For you to understand better, this is my structure:


I have one task on one server x and another on server y, these two tasks send command to start a third task z


The question is:


Is there any way to create a command queue sent?


For example, if the tasks of server X sent a command to run the task, and that of the server y sent soon after so that the server x is still running, it has like this server command y wait for the end to restart the server task?

[Oleg]

You solve the problem such:

Lets server Z has main task MainZ
Server X should run the task Z1
Server Y should run the task Z2
by using Send command and Listener

Tasks Z1 and Z2 are similar and both starts the task MainZ by such algorithm

Wait for Task MainZ
Start task MainZ (with required start)

In this case you can avoid such problem.
Also pay attention that Start Task action can pass some parameter too

[esantos]

Thanks Oleg. This will be useful to me.


Can you get me one last doubt? What protocol is used to communicate between the two tasks?

[Oleg]

What protocol is used to communicate between the two tasks?

Maybe between two instances of RoboTask?
This is non-standard protocol. We designed it specifically for RoboTask.

[esantos]

What protocol is used to communicate between the two tasks?

Maybe between two instances of RoboTask?
This is non-standard protocol. We designed it specifically for RoboTask.

In this case, in the communication between the send command and the listener. My question is whether we go through auditing often.

[Oleg]

You can encrypt all traffic between Send Command and Listener.
Go to Listener trigger and click on "Plugin settings".
Turn on the option Encryption Required.
Also you can set the listener password. Read here please: https://robotask.com/help/index.php?net ... ttings.htm

The encryption uses dynamic encryption key for each session.
Listener uses built-in system encryption engine of Windows™
Also pay attention that these settings are global for all Listener triggers in all tasks.

[esantos]

You can encrypt all traffic between Send Command and Listener.
Go to Listener trigger and click on "Plugin settings".
Turn on the option Encryption Required.
Also you can set the listener password. Read here please: https://robotask.com/help/index.php?net ... ttings.htm

The encryption uses dynamic encryption key for each session.
Listener uses built-in system encryption engine of Windows™
Also pay attention that these settings are global for all Listener triggers in all tasks.

Thanks Oleg