When you have multiple interior BC engines in load balance and/or fault tolerant mode:
1). The first interior BC engine started becomes the scheduler and all others will become workers.
2). If all interior BC engines are started at the same time, then all engines will go into a standby state. In this standby state, there would be an election process to see what are the scheduler and worker weights. If all are the same, then the BC engine that started first will become a scheduler and others will become workers.
3). If you want to designate a specific interior BC engine as a scheduler, then uncomment and tune the following values in the deployed interior server BusinessConnect .tra file. The higher scheduler weight (compared to the comparable value in the other deployed engine .tra files) will insure that the respective engine will become the scheduler. The other engines will become workers.
Private Process to BC Queue Configuration
#tibco.clientVar.gatewayProperties/transports/backoffice/RVCMQ/scheduler/weight=10
Note that the parameter above only affects the BC engine when it is used in an RV environment. This parameter has no effect if EMS is used.
DMZ to Interior Queue Configuration
#tibco.clientVar.gatewayProperties/transports/Intercomponent/msh/sweight=10
4). If the BC-1 engine is having a scheduler weight 10 and BC-2 engine is having a scheduler weight 6, then the BC-1 engine will become the scheduler, due to higher weight, and BC-2 will become a worker, due to a lower weight.