Queue processor state -- invalid state or not running debugging

Issue: Queue processor state is in -- state.

Sometimes the queue processor state will be in invalid state -- neither running nor stopped,  might related to invalid accessgroup.  You don't have the option to restart the queue processor as well.

Solution:
Option 1: Try to start /decommision the queue processor from the node.
Option 2: Restart the data flow by running the OOTB activity
 Data-Decision-DDF-RunOptions.pxStartRunByID  by providing the parameter as the queue name.

Source: SA-89741

Issue:-  Queue processor state is not visible on landing page.

Solution:  Check the access group in async requestor type for the queues.

SMA remote connection on Websphere and Tomcat

SMA remote connection on Websphere.

1. Enable JSR160RMIConnector

• Servers > Server Types > WebSphere Application Servers.
• Click on your server (default is server1) and select the Configuration tab.
• Scroll down to the Server Infrastructure section and expand Administration and select Administration Services
• Enable JSR160 RMI JMX Connector. Select JMX Connectors, then check JSR160RMIConnector and click Enable. When prompted, select Save to Master Configuration:

    Verify the IIOP Port Number

• Click on your server (default is server1) and select the Configuration tab.
• Click ports

• Restart the websphere server.

SMA configuration:

1. Enter PRPC url details

2. Select Remote connection- SMA is Stand alone

3. HostName: only hostname/ip address.

4. Port: Enter Soap Connetcor port address.

If connecting over https, the following SSL certificates settings has to be done. 

RESOLUTION

Make the following change to the operating environment:

1. Log into the administrative console.
2. Expand Security and click SSL certificate and key management. Under Configuration settings, click Manage endpoint security configurations.
3. Select the appropriate outbound configuration to get to the (cell) management scope.
4. Under Related Items, click Key stores and certificates and click the CellDefaultTrustStore key store.
5. Under Additional Properties, click Signer certificates and Retrieve From Port.
6. In the Host field, enter remote server IP in the host name field, enter SOAP PORT in the Port field, and remote server IP _cert in the Alias field.
7. Click Retrieve Signer Information.
8. Verify that the certificate information is for a certificate that you can trust.
9. Click Apply and Save.

https://pdn.pega.com/support-articles/sma-fails-instantiate-wasjmxconnector-due-admcoo16e-error

https://pdn.pega.com/support-articles/system-management-console-generates-soap-connection-error

SMA remote connection on Tomcat.

Set the following entries in setenv.bat of tomcat's bin folder

set CATALINA_OPTS=-Dcom.sun.management.jmxremote = true

set CATALINA_OPTS=-Dcom.sun.management.jmxremote

set CATALINA_OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.port=8686

set CATALINA_OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.authenticate=false

set CATALINA_OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.ssl=false

In SMA configuration:

1. Enter PRPC url details

2. Select Remote connection- SMA is Stand alone

3. service:jmx:rmi:///jndi/rmi://10.225.70.235:8686/jmxrmi

KEYED PAGE ACCESS datapage auto populate

A data page (earlier called as Declare pages ) rule defines the contents of a clipboard page.

KEYED PAGE ACCESS  is a feature which allows the user to retrieve the results faster. This has been introduced in PRPC 7.1.


This feature is supported only for LIST structure READONLY datapages

On definition tab check the Access pages with user defined keys to implement this feature.



 The user can retrieve the results based on single key or by defining multiple keys.

If multiple keys are defined, then the results retrieved/returned is an AND operation of all the keys defined.

Note: The key value applied is case sensitive.

Allow multiple pages per key

Check this checkbox, if the keys are not unique on the list of data (duplicate rows for the same key), the user can retrieve multiple rows/pages for key(s).




How to use/invoke this KEYED PAGE ACCESS datapage:

This can be invoked/referred only through autopopulate properties

The data page retrieves all the records. the keys are applied only through auto populate property.

Ex:

Create a data page with the following.




2. Create an auto populate property refering to a datapage as shown below.



The Keys field can be provided with the following values.
1. Constant value as shown above.
2. Can refer to another property.
3. Can have self reference property(.DemoKeyedPageAccessAutoPop.pyOrgUnit)


3. Refer the above created property in a section. Include a repeating layout and configure as shown below.



4. Now refer the above section in a flow and the result will be as shown below.



Clipboard  structure for the data page. The data page has retrieved all the records.





Clipboard structure for the auto popualte property.



The auto population of the data occurs only when properties of the datapage are refered. In our case we are refering the data page properties pyUserIdentifier, pyOrgUnit, pyOrganization.

The DemoKeyedPageAccessAutoPop property we created is a reference type property. This establishes a reference to the data page, The property shows reference information in the clipboard.