Question
Allianz
DE
Last activity: 23 May 2017 1:08 EDT
SMA add nodes automatically
Hi,
We plan to use docker infrastructure in the near future, and it's possible that, for some stage, we would docker containers containing PRPC scale automatically.
But we need to configure SMA manually. Is it possible to configure SMA nodes automatically? For example, with JMX?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
I believe you now do not have to configure SMA nodes one by one (from 7.2.1+), we have added auto-discovery feature for the sake of cloud deployment (all running docker containers including production envs).
Allianz
DE
Ok, I will check it, that's really nice to have.
Allianz
DE
Hi,
I could not verify if this is fixed on 7.2.1+. I downloaded 7.2.2 Personal Edition, but SMA is not deployed with it. I commented on the post: https://collaborate.pega.com/question/personal-edition-722-not-able-access-sma-getting-404-resource-not-available-error
I still have no access to a 7.2.1+ to verify this.
Allianz
DE
Hi,
I have tested this on PRPC 7.2.1, and i still had to add nodes manually. How would use this new auto-discovery feature in SMA?
Capgemini
FR
Hi,
Have you followed this article ?
Regards
Allianz
DE
Hi,
Thanks for your reply, I will test it
Regards
Allianz
DE
Hi,
i tried to use your suggestion, on Personal Edition 7.2.2, with SMA from normal PRPC 7.2.2.
But it did not work, when i enabled auto-discovery, it fails to connect through JMX.
When i configure manually, it works (same JVM, no credentials required).
Pegasystems Inc.
IN
Hi
What is the error message saying ? Can you paste the full error message here ?
Allianz
DE
com.pega.jmx.ui.util.JMXClientException: Exception getting MBean Server connection. Cannot connect to the server with specified settings
Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: Proprietary information hidden; nested exception is: java.net.ConnectException: Connection refused: connect]
Do you want the entire stack trace message? I have added if on an attachment
Pegasystems Inc.
IN
Hi
I am sorry I overlooked one point. Are you on Personal Edition ?
If yes, I would encourage you to try it with full version and share the outcome.
Allianz
DE
On which PRPC Version did this Feature start? Can i test this with 7.2?
We don't have PRPC 7.2.2 yet. We only have 7.2 or 7.2.1. But I have more operational support to try this on 7.2 node. On 7.2.1, it will take me more time until i can have this tested. I do not have access to these nodes myself. I have to ask for help from someone else.
Pegasystems Inc.
IN
As Kevin mentioned in his earlier reply , this feature started from 7.2.1 onwards
SMS Management and Technology
AU
Hi All
As per this article https://pdn.pega.com/managing-nodes-automatically-system-management-application-cluster/managing-nodes-automatically
There are ports that need to be configured for SMA auto node discovery
SMAAutoNodeDiscoveryPort=<PRPCport>
Hi All
As per this article https://pdn.pega.com/managing-nodes-automatically-system-management-application-cluster/managing-nodes-automatically
There are ports that need to be configured for SMA auto node discovery
SMAAutoNodeDiscoveryPort=<PRPCport>
SMAAutoNodeDiscoveryJMXPort=<JMXPort>
How do we configure auto node discovery if we have two pega instances running on the same host?
Ie Tomcat1 8080, Tomcat 2 8090
And we want sysmgmt to automatically see both nodes.