I am extending the interaction schema to add a new attribute called ccAgentId to store the call center agent id. While making SOAP call, the call center application will send the string agent Id.
So I started following the instructions as mentioned into the document Extension example
After making the changes in interaction and proposition schema, I updated the offer space as below to store the ccAgentId sent via the propose method
I am making the call and passing the attribute as below. But the extension value is not getting saved into the proposition schema (proposition is saved but the extension column is blank).
<!--You may enter ANY elements at this point-->
<interaction ccAgentId="TarunG" />
I have the interactiond process running on the instance. I really don't know what this process actually does other than some very high level info I saw in the documentation. A side question, is this even required to run if I have just one instance (control instance) running? Also if I have multiple servers, do I need to run it on all the servers? I don't have any separate execution instance as of now.
After further debugging the interaction.js and the code generated by offer space, I got the option variable NmsInteraction_UseDaemon
When you keep the variable = 1 (default), the "if" part is executed and when =0, then else part (below code)
Now the confusing part is, when the option variable is set to 0 (default one), the ccAgentId is not saved where as when option var = 1, it is saved properly.
That means, with the direct SQL, it is working fine whereas the asynchronous processing is not saving the data. I fear, if I do the synchronous insert statement, I will have trouble when Millions of calls will come in an hour as everyone will try to lock the table for insert/update [Same details I notices for Update method as well].
Can someone please help me to understand what is happening inside and how can I have it working with default value for the option variable.
Hard to say, looks like what you have is correct here. This part is a bit off-script:
<interaction ccAgentId="TarunG" />
Documentation says use <empty/> for the child node of <context/>, though really should be fine either way.
For perf tuning, I haven't messed with any of those params; never could figure out what they did or how they'd have an impact.
The Inbound Interaction module is cleverly designed for horizontal scaling: in that queries are run in js on the app servers, not the db, which is only consulted once for a single recipient row to process all the non-anonymous offers against. If your app servers are showing high load in benchmarks, just add more of them. If the db is overloaded, make sure join keys have indexes etc, and in a worst-case scenario look to replication strategies such as Power Cluster(tm).
Nothing confusing. The interactiond daemon's entire purpose is to record interaction logs, asynchronously, and needs to be active on all servers you want to record logs from. Interactiond's performance is tuned via its buffer allocation.
Can you please let me know why the value of the additional data (ccAgentId in my case) is not saving with the daemon enabled? I have interactiond process running on the servers. Also can you please share more details how it works? When you make the update status, does it store the data into any queue or memory buffer and then every second it is processes?
Also for the configuration "callDataSize : Max. number of characters stored in the shared memory for call data Default: 0", can you provide more details.
Any suggestion for optimum values below parameters with customers having 25M members and 200 live offers
maxProcessMemoryWarningMb --> Probably 75% of above