Post-installation Task 2: Updating the ConfigValues_OMS.xml File
Update the following OMS configuration values in the ConfigValues_OMS.xml file:
Procedure
-
In the
Offline Catalog >
Common Configuration subcategory, add the following OMS configuration values:
<ConfValue description="Flag to enable or disable the publishing of model loading notification message. If set to false then notification will not sent" name="Enable model loading success Notification" propname="com.tibco.fom.oms.model.loading.notification.enabled" sinceVersion="4.0" visibility="Basic"> <ConfBool default="false" value="false"/> </ConfValue>
-
In the
Catalog Publishing JMS Destinations Configuration category, add the following OMS configuration values:
<ConfValue description="Model loading success notification publish topic" name="Model loading success notification publish topic" propname="com.tibco.fom.oms.model.loading.notification.publish.topic" sinceVersion="4.0" visibility="Advanced"> <ConfString default="tibco.aff.oms.modelloading.success.notification.publish" value="tibco.aff.oms.modelloading.success.notification.publish"/> </ConfValue> <ConfValue description="OPE Rule model receiver queue" name="OPE Rule model receiver queue" propname="com.tibco.fom.oms.afi.operulemodel.receiver.queue" sinceVersion="3.0" visibility="Advanced"> <ConfString default="tibco.aff.catalog.operulemodel.request" value="tibco.aff.catalog.operulemodel.request"/> </ConfValue> <ConfValue description="OPE Rule model receiver count" name="OPE Rule model receiver count" propname="com.tibco.fom.oms.afi.operulemodel.receiver.count" sinceVersion="3.0" visibility="Advanced"> <ConfNum default="3" value="3"/> </ConfValue> <ConfValue description="OPE Rule model publish topic" name="OPE Rule model publish topic" propname="com.tibco.fom.oms.afi.operulemodel.publish.topic" sinceVersion="3.0" visibility="Advanced"> <ConfString default="tibco.aff.ope.events.operulemodel.publish" value="tibco.aff.ope.events.operulemodel.publish"/> </ConfValue>
-
In the
Data Interfaces Configuration >
Data Interface Flags subcategory, add the following OMS values:
<ConfValue description="JMS QoS Enabled for RPC get operations" name="JMS QoS Enabled for RPC get operations" propname="com.tibco.fom.oms.tds.get.jms.qosEnabled" sinceVersion="3.0.2" visibility="Basic"> <ConfBool default="false" value="false"/> </ConfValue> <ConfValue description="replyToDeliveryPersistent flag for RPC get operations" name="replyToDeliveryPersistent flag for RPC get operations" propname="com.tibco.fom.oms.tds.get.jms.replyToDeliveryPersistent" sinceVersion="3.0.2" visibility="Basic"> <ConfBool default="true" value="true"/> </ConfValue> <ConfValue description="deliveryPersistent flag for NON-RPC get operations" name="deliveryPersistent flag for RPC get operations" propname="com.tibco.fom.oms.tds.get.jms.deliveryPersistent" sinceVersion="3.0.2" visibility="Basic"> <ConfBool default="true" value="true"/> </ConfValue> <ConfValue description="JMS QoS Enabled for RPC set operations" name="JMS QoS Enabled for RPC set operations" propname="com.tibco.fom.oms.tds.set.jms.qosEnabled" sinceVersion="3.0.2" visibility="Basic"> <ConfBool default="false" value="false"/> </ConfValue> <ConfValue description="replyToDeliveryPersistent flag for RPC set operations" name="replyToDeliveryPersistent flag for RPC set operations" propname="com.tibco.fom.oms.tds.set.jms.replyToDeliveryPersistent" sinceVersion="3.0.2" visibility="Basic"> <ConfBool default="true" value="true"/> </ConfValue> <ConfValue description="deliveryPersistent flag for NON-RPC set operations" name="deliveryPersistent flag for RPC set operations" propname="com.tibco.fom.oms.tds.set.jms.deliveryPersistent" sinceVersion="3.0.2" visibility="Basic"> <ConfBool default="true" value="true"/> </ConfValue>
-
In the
Data Interfaces Configuration >
Data Interface Flags subcategory, add the following OMS values:
<ConfValue description="DB row lock wait timeout for postgresql in miliseconds" name="DB Row Lock Wait TimeOut" propname="com.tibco.af.oms.lock.wait.timeout" sinceVersion="4.0" visibility="Advanced"> <ConfNum default="1" value="1"/> </ConfValue>
- In the Web Service Configuration category, set the default value of the com.tibco.af.oms.http.port property to 9091.
-
In the
Offline Catalog > Common Configuration subcategory, add the following subcategory:
<Category description="OPE Rule Catalog Configuration" name="OPE Rule Catalog Configuration" visibility="Advanced"> <ConfValue description="Use offline ope rule" name="Use offline ope rule" propname="com.tibco.fom.oms.afi.offline.operule.use" sinceVersion="3.0" visibility="Advanced"> <ConfBool default="false" value="false"/> </ConfValue> <ConfValue description="OPE Rule catalog poller and WS directory" name="OPE Rule catalog poller and WS directory" propname="com.tibco.fom.oms.afi.offline.operule.directory" sinceVersion="3.0" visibility="Advanced"> <ConfString default="/home/tibuser/tibco/af/operule" value="/home/tibuser/tibco/af/operule"/> </ConfValue> <ConfValue description="OPE Rule catalog import success poller and WS directory" name="OPE Rule catalog import success poller and WS directory" propname="com.tibco.fom.oms.afi.offline.operule.importsuccess.directory" sinceVersion="3.0" visibility="Advanced"> <ConfString default="/home/tibuser/tibco/af/operule-success" value="/home/tibuser/tibco/af/operule-success"/> </ConfValue> <ConfValue description="OPE Rule catalog import failure poller and WS directory" name="OPE Rule catalog import failure poller and WS directory" propname="com.tibco.fom.oms.afi.offline.operule.importfailure.directory" sinceVersion="3.0" visibility="Advanced"> <ConfString default="/home/tibuser/tibco/af/operule-failure" value="/home/tibuser/tibco/af/operule-failure"/> </ConfValue> </Category>
Copyright © Cloud Software Group, Inc. All rights reserved.