Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Apache Ignite script not reading external configuration files

SA-44037

Summary



Users followed the installation document to run Apache Ignite clustering JVM in client-server mode.

The engine comes up, but users do not know how to externalize configuration files such as prconfig.xml, prlogj2.xml, and the PegaTemp directory.

Error Messages



WARNING:- prlogging.xml is no longer supported in this version of prpc
INFO: Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup
INFO: Could not find prconfig in the local JNDI context, skipping prconfig setting lookup

Steps to Reproduce



Run clusterService.sh script from the media.


Root Cause



The installation/upgrade/migration fails with error messages about reading configuration files from the wrong folder.

Resolution



Perform the following local-change:
  1. Change the script clusterService.sh manually to add the “-D”, for example:
    “$JAVA_BIN $JVM_OPTS -cp "$classpath" "$PROP_FLAG" -Dpegarules.config=/your_path/prconfig.xml com.pega.pegarules.pub.PegaRULES com.pega.platform.module s.services.ClusterServiceLauncher $ARGS”
    With this change, the script output console shows the following information:
    Found spec for PegaRULES configuration using System property: /your_path/prconfig.xml
    Located PegaRULES configuration: file:/your_path/prconfig.xml
    Sep 13, 2017 4:55:12 PM com.pega.pegarules.internal.bootstrap.SettingReaderJNDI
  2. Repeat Step 1 for pegarules.logging.configuration env variable.
The database user password in clusterService.properties can be encrypted using runPega.bat PassGen.
With Pega 7.3.1, the Apache Ignite engine can be run inside a webcontainer, and -D JVM arguments can be added to the JVM instead of modifying the clusterService.sh script.

The Apache Ignite engine uses the JVM temp directory where it creates the extractedFiles folder, which is different from the Pega engine PegaTemp folder.

Published October 3, 2017 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us