"Admin Portal" separate from Default Server Group

[delawless]

Question for the community regarding setting up an what I call an "Admin Portal".

Our setup is as follows: A group of 3 servers that run the application and content manager tiers for Cognos, which respond to the activities in a set of 2 servers in our DMZ with the gateways installed (with webserver).  This group of 5 servers is the "default group" of servers that performs the customer related actions that is normal for Cognos.  There is an additional server that is in our internal network that has the application/gateway tiers (with webserver), and connects to the content manager in the default group.  There are no current custom routing sets, or anything truely unique about this setup.

What I would like to do is ensure that my "Administration Portal" stays out of the normal load balancing of the regular cognos activities (running jobs, reports, etc that come from the customer facing gateways), but is able to perform (potentially) the same activities if the request is coming from the internal "Admin" gateways.

Does anyone know how configure the cognos dispatcher so that our admin portal is isolated from the other default group, but can also potentially perform any actions needed?

Thanks.