"java.extended.properties" are not picked up from TRA when a BusinessWorks application is started as an NT Service.
Article ID: KB0089552
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
Description:
========
When a BW application is deployed as an NT Service and "java.extended.properties" are added after deployment to the TRA file, they are not picked up by Engine.
Environment:
=========
TIBCO BusinessWorks : All
Windows family OS
Cause:
=====
When a BW application is deployed as an NT Service, a key in the Windows Registry is created with different Engine properties. Some of these properties will take precedence over those manually added to TRA.
Resolution:
=======
To ensure our "java.extended.properties" will be added to the Windows registry key for NT Service and picked up at runtime, add it to the bwengine.xml custom engine properties file.
Description:
========
When a BW application is deployed as an NT Service and "java.extended.properties" are added after deployment to the TRA file, they are not picked up by Engine.
Environment:
=========
TIBCO BusinessWorks : All
Windows family OS
Cause:
=====
When a BW application is deployed as an NT Service, a key in the Windows Registry is created with different Engine properties. Some of these properties will take precedence over those manually added to TRA.
Resolution:
=======
To ensure our "java.extended.properties" will be added to the Windows registry key for NT Service and picked up at runtime, add it to the bwengine.xml custom engine properties file.
Issue/Introduction
"java.extended.properties" are not picked up from TRA when a BusinessWorks application is started as an NT Service.
Additional Information
o TIBCO ActiveMatrix BusinessWorks™ Administration document, Custom
Engine Properties : Setting Custom Engine Properties in Deployed
Projects
Feedback
Yes
No
Powered by
