multi-threading agent call to ServiceLevelEvent
Right now, we're probably limiting ourselves to only five agents running at any one time as we have not modified/overridden the "threadpoolsize" parameter. We have sufficient horsepower to bump this up to 15, but is it also possible to multi-thread the call to ServiceLevelEvent in the agent?
try { tools.getDatabase().executeRDB(strGoalSQL.toString(), pgGoalTime); }
catch (DatabaseException e) { throw new PRAppRuntimeException("Pega-ProCom", 0, e.getMessage()); }
java.util.Iterator enum = pgGoalTime.getProperty("pxResults").iterator();
while (enum.hasNext())
{
ClipboardProperty aResultsProperty = (ClipboardProperty) enum.next();
ClipboardPage aResultsPage = aResultsProperty.getPageValue();
String strAssignHandle = aResultsPage.getString("pxInsHandle");
pega_procom_pegaprocomutilities.ServiceLevelEvent("Goal", strAssignHandle, strAssignmentClass, tools);
}
Message was edited by: Marissa Rogers Added Category
Accepted Solution
Wells Fargo
US
We're on 6.2 sp1 and receive thousands of cases each morning. I have 10 case entry queues, but even split up between the 10, case entry processing takes a while. Rather than adding additional agents, I wanted the existing ones to work more efficiently, so changed the code to:
while (enum.hasNext())
{
ClipboardProperty aResultsProperty = (ClipboardProperty) enum.next();
ClipboardPage aResultsPage = aResultsProperty.getPageValue();
String strAssignHandle = aResultsPage.getString("pxInsHandle");
//pega_procom_pegaprocomutilities.ServiceLevelEvent("Goal", strAssignHandle, strAssignmentClass, tools);
// child object
ClipboardPage childPage = tools.createPage("Code-Pega-Child", "");
ClipboardPage assignPage = tools.createPage("Assign-", "");
childPage.putObject("pyObject", assignPage);
// create parameter page and copy input parameters
ParameterPage paramsPage = new ParameterPage();
paramsPage.putString("Event", "Goal");
paramsPage.putString("Handle", strAssignHandle);
paramsPage.putString("AssignClass", strAssignmentClass);
Object o = tools.getRequestor().queueBatchActivity("Assign-","WFCProcessSLA", paramsPage, childPage);
if (o == null)
{
oLog.infoForced("Fail: child requestor not created");
}
}
tools.getRequestor().waitOnAllBatchActivities();
Pegasystems Inc.
US
Hi Michael.
Having a bit more context would be helpful here. (What version of pega) What is motivating you to consider this approach in the first place?
Since the Agent is the primary way to get multi-hreaded background processing, I would suggest you consider creating another copy of the agent to get additional threads if needed.
Can you clarify where this Java code is from?
Is your goal to create a separate thread for each iteration of the while loop above?
Accepted Solution
Wells Fargo
US
We're on 6.2 sp1 and receive thousands of cases each morning. I have 10 case entry queues, but even split up between the 10, case entry processing takes a while. Rather than adding additional agents, I wanted the existing ones to work more efficiently, so changed the code to:
while (enum.hasNext())
{
ClipboardProperty aResultsProperty = (ClipboardProperty) enum.next();
ClipboardPage aResultsPage = aResultsProperty.getPageValue();
String strAssignHandle = aResultsPage.getString("pxInsHandle");
//pega_procom_pegaprocomutilities.ServiceLevelEvent("Goal", strAssignHandle, strAssignmentClass, tools);
// child object
ClipboardPage childPage = tools.createPage("Code-Pega-Child", "");
ClipboardPage assignPage = tools.createPage("Assign-", "");
childPage.putObject("pyObject", assignPage);
// create parameter page and copy input parameters
ParameterPage paramsPage = new ParameterPage();
paramsPage.putString("Event", "Goal");
paramsPage.putString("Handle", strAssignHandle);
paramsPage.putString("AssignClass", strAssignmentClass);
Object o = tools.getRequestor().queueBatchActivity("Assign-","WFCProcessSLA", paramsPage, childPage);
if (o == null)
{
oLog.infoForced("Fail: child requestor not created");
}
}
tools.getRequestor().waitOnAllBatchActivities();