By enabling supportMultiContext session parameter, Adapter processes subscriptions in multi context mode. By enabling OrdersUseMultiContext orders can also be processed in multi context this can be used only after enabling "supportMultiContext". By using multi contexts the performance improvements can be seen in terms of throughput and decreased latency because the wait time will be reduced.

Context mapped to symbol can be done at startup or dynamically. At Startup only user (BA) can map symbol to context by com.apama.mds.MDServerContextRequest event. If the symbol is already mapped to one context, then adapter will reject that request and acknowledge to user with error message by com.apama.mds.MDServerContextResponse event.

If Symbol is not mapped to any context while handling subscriptions, then Adapter will send a request to user(BA) for create a new Context by com.apama.mds.CreateContextRequest event and expects response in com.apama.mds.CreateContextResponse event. If the user doesn't respond to request, then the subscription will be handled in the default context.