Accessing SMA data in Pega running in Websphere 8.5
Hi, I am trying to access SMA data using a Java application, and Pega is installed in a Websphere Server.
On page 9 in SMA documentation (SMA_Ref_Guide_V63SP1.pdf) there is the following statement:
In a multi-node installation, JMX uses RMI to communicate with the other nodes being monitored. In Java, explicit garbage collection is forced once per minute in any system using RMI, although it is possible to configure the JVM to suppress this by disabling explicit GC calls. If not suppressed, frequent garbage collection can lead to degraded system performance.
If a Process Commander node and SMA are sharing a JVM on such a system, that system will collect garbage once per minute, because of the system’s use of RMI. Again, it will adversely affect Process Commander performance on that node.
This issue can affect all server types except WebSphere, which uses SOAP services for intranode communications, not RMI.
I was trying to connect to SMA using JConnect using the same information I use to configure SMA on Pega running on Websphere (Hostname and port). This info is specific for Websphere according to page 21 on the same documentation (SMA_Ref_Guide_V63SP1.pdf)
Host/Server Name (WebSphere only): Required. The host or Server name in which the WebSphere application server is running.
Hi, I am trying to access SMA data using a Java application, and Pega is installed in a Websphere Server.
On page 9 in SMA documentation (SMA_Ref_Guide_V63SP1.pdf) there is the following statement:
In a multi-node installation, JMX uses RMI to communicate with the other nodes being monitored. In Java, explicit garbage collection is forced once per minute in any system using RMI, although it is possible to configure the JVM to suppress this by disabling explicit GC calls. If not suppressed, frequent garbage collection can lead to degraded system performance.
If a Process Commander node and SMA are sharing a JVM on such a system, that system will collect garbage once per minute, because of the system’s use of RMI. Again, it will adversely affect Process Commander performance on that node.
This issue can affect all server types except WebSphere, which uses SOAP services for intranode communications, not RMI.
I was trying to connect to SMA using JConnect using the same information I use to configure SMA on Pega running on Websphere (Hostname and port). This info is specific for Websphere according to page 21 on the same documentation (SMA_Ref_Guide_V63SP1.pdf)
Host/Server Name (WebSphere only): Required. The host or Server name in which the WebSphere application server is running.
So from this information I believe that when Pega is running on WebSphere, SMA does not use standard RMI protocol to retrieve information, and instead it uses SOAP services. So JConnect and any client that uses RMI will not be able to retrieve SMA data using RMI.
My question is: is my statement above correct? If so, how do I find instructions to implement this SOAP calls to retrieve SMA data when Pega is running on Websphere?
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
***Edited by Moderator Marissa to update SR Details***
Accenture DO Brasil Ltda
BR
Just to complement the configuration required on SMA, the Port was missing on the post.
Host/Server Name (WebSphere only): Required. The host or Server name in which the WebSphere application server is running.
Port (WebSphere only): Required. The SOAP connector port, which is defined in the WebSphere Administrative Console and listed in the WebSphere log: The SOAP connector is available at port 8880.
Pegasystems Inc.
US
You should be able to connect to Pega node and access mbeans by configuring remote JMX on websphere and SOAP connector port isn't needed.
Accenture DO Brasil Ltda
BR
Hi, JMX is configured in Websphere, and I can access it using Jconsole, but Pega MBeans are not listed.
As evidence, I have attached 2 screenshots from Jconsole:
+ Websphere.jpg: it show the MBeans available using JMX in a Pega 7.3 installation in Websphere, notice that "com.pega.PegaRULES" MBean is missing
+ Tomcat.jpg. it shows MBeans available using JMX in a Pega 7.3 installation in Tomcat, notice that "com.pega.PegaRULES" MBean is present
Furthermore, when SMA is configured in a Websphere installation it requires a Hostname AND a SOAP port, and when SMA is configure in Tomcat it requires only the Server URL for the JMX Service.
So it makes me believe that on Websphere SMA is not using standard JMX to access its data, it uses a SOAP connection to access the data