prsysmgmt deployment on multinode environment
Hi,
We deployed prsysmgmt in a multinode environment and created the SMA node. Since node.xml is getting generated on jVM home directory for only one node we are unable to see the configured node when the request goes to other JVM in prsysmgmt.As a work around we have created a directory in shared path where all jvm has access and created the jvm property -Dcom.pega.sma.tempdir with shared directory path with full write access in WAS7.But after configuring SMA nodes node.xml is not writing on to shared directory and still it is getting writing on to jvm home directory. Please let us know the approach to deploy prsysmgmt in a multinode environment.
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Pegasystems Inc.
US
Hi,
There is no problem with the approach followed by you. But the prsysmgmt application looks for the JVM arg -Dcom.pega.sma.tmpdir instead of -Dcom.pega.sma.tempdir
Remove the existing Nodes.xml file from JVM home directory, configure the valid JVM arg with the shared directory path and restart all the JVM's to apply the changes. And later you can proceed with adding node details which should update the Nodes.xml in the specified shared path.