I want to use object spawner (on machine A) to start workspace server sessions on other machines (machine B, C etc.) based on work load on other machines.
I do not want to have any workspace servers on machine A.
You need an object spawner on every machine which hosts a workspace server (or stored process server or pooled workspace server). That means machines B and C will need one. You'll use load balancing in order to distribute requests from a parent object spawner to a child object spawner. There's a description of this in the Application Server Administration Guide at:
Yes, I understand machine B & C need an object spawner too. Can we limit the object spawner(on machine A) to not start any workspace server sessions on machine A & always distribute workload to machine B, C etc?
If you're using the cost algorithm for load balancing, I believe you could set the maximum cost on machine A to 0, which should effectively eliminate it from consideration in launching workspace servers. See:
Yes. From my understanding If there is no workspace server defined to machine A then it would not start one. The object spawner would only communicate with the object spawner on Machine B or C.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.