Settings for the File ConfigValues.xml
Configure the following settings for the ConfigValues.xml file:
- Set all the log levels to ERROR.
- Set
com.tibco.cim.jmxmonitor.details.enable
tofalse
. - Set
com.tibco.cim.init.AsyncCallQueueSenderManager.poolSize
to12
(can be increased if the CPU usage of the application server and the database server results in a bottleneck). - Set
com.tibco.cim.init.AsyncCallQueueReceiverManager.poolSize
to12
(can be increased if the CPU usage of the application server and the database server results in a bottleneck). - Set
com.tibco.cim.optimization.import.cyclictest
tofalse
. - Set
com.tibco.cim.optimization.import.mutationtest
tofalse
. - Set
com.tibco.cim.jmxmonitor.copytoas.enable
tofalse
. - Set
com.tibco.cim.cache.debug
tofalse
. - Set
com.tibco.fc.importcatalog.chunksize
to500000
.Note: The property setting is purely based on the maximum number of records in a CSV and database configuration. If your database can process high numbers in a single transaction, then you can set the parameter value as high as possible. - Set
com.tibco.fc.importcatalog.delay
to30
.Note: The property defines the amount of wait time (in seconds) before the next ping for the event status is triggered. If number of records are few in every CSV, you can set the parameter to smaller values like 5. - Set
com.tibco.fc.retry.count
to600
.Note:The property defines the maximum number of pings for event status before the import on the next repository or relationship is triggered. This parameter works along with
com.tibco.fc.importcatalog.delay
to define the maximum wait time before the next import is triggered.If the value of
com.tibco.fc.retry.count
is set to600
then the maximum wait time is 600 * 30 = 18,000 seconds, which is 300 minutes or five hours.