Schedule tasks for load to datawarehouse

[dgudkov]

@reynsnivea

Is it possible to clarify the difference between the server connection that we can establish via the button on the home page (first picture) and the second one that we can create via de add connectors button (second picture) ?

The first picture shows Server Link configuration. See this post for more details: Server Link explained

@reynsnivea

Do I understand it correctly that if we want to use the server command that we have to create 1 connector for each space in which we want to run tasks using that server command action ?

Yes, the "Server command" action requires a connector to EM Server. Each connector can connect to 1 space only.

@reynsnivea

Can we call other easyMorph projects using “call another project” action that reside in other spaces ?

The "Call another module/project" action doesn't "know" about spaces. It refers a project by project path (absolute or relative). If you need a project to run a space task, use the "EM Command" action.

Alternatively, you can use a parameter to provide a project with a path to another project that may happen to be in another space. But that can be inconvenient, because by default the file picker in Server UI doesn't allow picking files from public folders of other spaces. You can enable picking files from the whole disk drive, but that can be undesirable from a security perspective if untrusted people can run the task.

@reynsnivea

The EasyMorph server command does not allow to add a parameter for the name of the task that EM-server has to run. So if we want to deploy or master flow that orchestrates all tasks in another space or server, we have to name the tasks exactly the same. Is that correct (same task name and description) ?

The "Run task" command in the "EM Server command" action identifies a task by an internal ID rather than a name. That's why it doesn't support parameters. Two tasks may have the same name but different IDs. So that won't work.