onestoppega

  Split For Each shape in pega Parallel processing in Pega We can allow users to perform multiple tasks independently to complete the work, in pega we can this as parallel processing. In a stage or flow rule, we can add smart shapes to achieve this parallel processing. Smart shapes in pega Pega has defined some smart shapes like  Split Join ,  Split-For-Each,  and  Spin-Off . We have to use these smart shapes in sub-process shape. Each shape can call one or more processes to proceed in parallel. Split For Each shape in pega Split for each allows us to run a single process multiple times by looping through a Page List or Page Group. The main flow continues when processes on the PageList/PageGroup processed. I Will explain with an example:  In a Service Request case type when the user submits a request it should be going for the inspection process. Used Split Join shape to fulfill this requirement with two sub-processes. When all sub-processes are complete, t...

  Spin Off in pega Parallel processing in Pega We can allow users to perform multiple tasks independently to complete the work, in pega we can this as parallel processing. In a stage or flow rule, we can add smart shapes to achieve this parallel processing. Smart shapes in pega Pega has defined some smart shapes like  Split Join ,  Split-For-Each,  and  Spin-Off . We have to use these smart shapes in sub-process shape. Each shape can call one or more processes to proceed in parallel. Spin-Off in pega The spinoff is not a shape, it is an option in the sub-process shape. Which allows running the sub-process independent and in parallel to the main process. The main flow will not wait for the sub-process and no join options available for SpinOff processes. How to configure Spin-Off option in a subprocess I Will explain with an example:  In a Service Request case type when the user submits a request it should be going for the inspection process. Used Split Join ...

  Tracing a listener   You can trace a listener that is available in the cluster or on a specific node to debug its activity. To view and manage listeners on the Listener Management landing page, you must have the following privileges: pzSystemOperationsObserver   privilege to view the list of listeners and view more details about a listener. pzSystemOperationsAdministrator   privilege to view the list of listeners and perform all available actions on listeners. Click   Designer Studio   > System > Operations > Listener Management . Select a node from the list at the top left corner of the page to manage listeners in the cluster (all nodes) or on a specific node (either the current node or a remote node). Optional: Filter the list of listeners. In the   Actions   column, click the   Actions   link that corresponds to the listener that you want to trace, and select one of the following options. Trace service on node   - Sele...

 securing SMA on Websphere     Refer to following PDN article for more details:              https://pdn.pega.com/security/implementing-authentication-for-prsysmgmt-and-prdbutil           Add the following security contraint entry in your web.xml and repackage the EAR:            <security-constraint> <web-resource-collection> <web-resource-name>System Management Application - DB utility Application </web-resource-name> <description>secure all urls for this application</description> <url-pattern>/*</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>PegaDiagnosticUser</role-name> </auth-constraint> </security-constraint> <login-config...