Understanding the internal mechanism and configuration parameters of SMS Builder may help you tune the processing engine for optimal performance.
The processing engine powers mobile-commerce solutions, and lets you scale your services. The processing engine is designed to serve the continued growth of mobile traffic, which demands instant interactions with mobile applications.
The processing engine processes interactive applications somewhat differently than it processes event applications, as shown below.
Interactive Application Processing
Event Application Processing
Processing Engine Configuration File
# Configuration for Incoming Queue – Interactive Application # Number of threads to handle the dispatch of the incoming queue. # Note that this should not exceed the messageReceiverThreads incomingThreads=2 # Configuration for Incoming Queue – Interactive Application # Maximum number of messages allowed in the incoming queue. This is a global queue # that handles all incoming messages before dispatching to a specific message # receiver. incomingBackLog=1000 # Configuration for Message Receiver – Interactive Application # A message receiver is created for each active Brand Mobiliser application # Configure the number of threads to handle the message queue for each message # receiver. messageReceiverThreads=2 # Configuration for Message Receiver – Interactive Application # Maximum number of messages allowed in each message receiver queue # There is one queue for each message receiver. messageReceiverBackLog=500 # Configuration for Event Application, used in Campaign # Maximum number of dispatching thread to process the event queue maxDispatchThreads=12 # Configuration for Event Application, used in Campaign # Number of Processor per event application maxEventWorkers=1 # Batch size in processing the subscriber file batchLoadSize=100