Resolution:
How to set up a Multi Tier Submissions environment

DS Engines can also be effective as drivers, and you can create services and submit tasks from the engine. The submitting Engines will then function just as if they were a second tier of a Driver. This option is called 'Multi Tier Submissions' (or 'Dual Tier Submission').

First, let us define the two tiers:

    * You will need to have at least 2 Engines, say engine A and engine B.
          o Driver A will submit to Engine A.
          o Engine A will operate as Driver B and will submit to Engine B.
    * You will also need to two Services: Service A and Service B.
          o Service A will be created and submitted from Driver A. You can use a Task of this Service to call the submission method on Service A code. This method should be implemented to create and submit Service B.
          o Service B will be created and submitted from Engine A.

Note: The attachment illustrates this architecture.

Now, all that is left to do is to define two groups of Engines.
You can do so by creating two Discriminators. The first discriminator will force Service A to run on Engine A and the second will ensure Service B will be running on Engine B.
Alternatively, you can set max number of Engines that each Service will utilise. This field sets the maximum number of Engines that can concurrently execute Service invocations on every instance. This can be done via the Service Type Registry. However, theoretically, the same Engine could be used by both Services.

How to set up a Multi Tier Submissions environment