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: Nov 2, 2015
Last activity: Nov 2, 2015
Posted: 2 Nov 2015 9:01 EST
Last activity: 2 Nov 2015 9:01 EST
Closed

useing WebSphere variables in PEGA

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.

Related content:

Related content has not currently been identified for this post.

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