Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Shaun Arman (ShaunA70)
Cahaba GBA
US
ShaunA70 Member since 2015 5 posts
Posted: Oct 29, 2015
Last activity: Nov 10, 2015
Posted: 29 Oct 2015 9:12 EDT
Last activity: 10 Nov 2015 11:19 EST
Closed

[SOLVED] Class PATH variabls

We are currently upgradeing both PEGA and WebSphere (PEGA 7.1, WAS Proprietary information hidden) and had a issue with some settings.

I know WAS uses variables such as: {WAS_INSTALL_ROOT}, {USER_INSTALL_ROOT}, {LOG_ROOT}, etc....

We have several claspaths we need to manually configure in PEGA, and some config files for PEGA. Is is possible to use these WAS variables so when we upgrade in the feature we do not have to keep manually changeing all these entries throughout PEGA and WAS?

As an example, in this location

 

What I would like to use is something like this:

{JAVA_HOME}/lib/com.ibm.mq.jar

 

Is PEGA capable of knowing what this variable is if it is defined in WebSphere?

To see attachments, please log in.
Installation and Deployment

Posted: 9 years ago
Posted: 9 Nov 2015 10:59 EST
Abhisek Ganguly (Abhisek_Ganguly)
Rabobank

Rabobank
NL

I don't think Pega would understand the variable if you put it like the way you are saying. But, remember these are complie time classpaths, it does not have any connections with the runtime environment path.

https://pdn.pega.com/java-and-activities/about-the-process-commander-51-class-paths

To see attachments, please log in.
Posted: 9 years ago
Posted: 10 Nov 2015 8:55 EST
Andy Werden (WERDA)
PEGA
Senior Fellow Technology Architect
Pegasystems Inc.
US
Keep in mind that you can import external JAR's into the PRPC database and make the compile time / runtime classpath issue irrelevant. I notice that you have listed the MQ JAR's -- I always import MQ Jars into database to simplify MQ integratoin
To see attachments, please log in.

Related content:

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

Pega Collaboration Center 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