In the implementation guide for Pega Marketing 7.22, I encounter the following:
Updating the marketing agents access group
After you create a new application, update the marketing agents access group to reference your new
application. This access group is necessary for the correct functioning of Pega Marketing agents. For
more information on agents, see Pega Marketing agents.
Does this imply, I cannot have more than one application building on Pega Marketing in the same PRPC environment? Or should I copy the agents? Or is there some other logic I am missing?
Hi, as you point out, it's all about the marketing agents being able to see the appropriate rulesets that contain your marketing assets. I've not tried creating an application that's built on more than one application but the same thinking could apply to the idea of having a top level application that has all the rulesets assoicated with your other applications and use this as the target application for the PegaNBAM:Agents access group.
There's one other point that might influence your thinking, we use a node level page to make the main application configuration details available, that's where we hold the customer class ( and prospect class ). Consequently, there can only be one of these pages ( and hence customer class ) in the system.
Would it be a possible and valid solution to specialize the Declare Page Declare_MKTSystemSetting per application and have it as a Thread Level page? Is this the page you are revering to?
Especially regarding perfomance. Is it a correct assumption that performance will not be hit, because it is a hardcoded XML, which is read in?
edit: investigating this, it would at least need a copy of the set of agents, else you do not have a application specific thread at runtime (the access group of the agents is pointing to both applications in the possible alternative approach) So remaining question seems to be, if it is possible to run more versions of the agents. I will address this question seperately in this topic
Hi, I always seem to be answering in the negative.
I don't believe this will work, the reason being that, to queue an item for an agent you have to provide the ruleset and the agent name.
In our case, when a campaign is about to initiate a new program run, it queues the work for the program run agent and hence would qualify the request by the ruleset ( pegaMKT-engine) and the agent name ProcessProgramRun.