How to externalize configuration properties outside of RMS.
Article ID: KB0084359
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
Description
We can externalize configuration properties outside of the RMS.cdd file by specifying a property file at command-line during the RMS engine startup. Create a customized property file containing all environment specific RMS cdd properties (LDAP properties, Common Properties, SCS properties, WS properties, Studio Properties, RMS Approval and other properties).
Example:
created a sample rms.properties
-----rms.properties------
ws.scs.rootURL=F:/tmp/webstudio
ws.scs.impl.type=file
ws.scs.repo.dir=F:/BE530GA/be/5.3/rms/repo
ws.scs.command.path=""
ws.scs.default.username=""
ws.scs.default.password=""
tibco.clientVar.Webstudio/port=9090
tibco.clientVar.Webstudio/DB/driverName=oracle.jdbc.OracleDriver
tibco.clientVar.Webstudio/DB/url=jdbc:oracle:thin:@localhost:1521:orcl
tibco.clientVar.Webstudio/DB/maxConnections=5
tibco.clientVar.Webstudio/DB/userName=WS_USER
--------------------------
Environment
Resolution
Example:
./be-rms -p <FileLocation of rms.properties>
Another option is to override the RMS.cdd properties at the be-rms.tra level. This helps to externalize configuration properties outside of RMS.CDD
Issue/Introduction
Feedback
