Simflofy's Global Properties
Simflofy's Global Properties file can be used to configure specific parts of your Simflofy environment to tailor it to your exact specification needs.
Initial Run Properties
| Property | Description |
|---|---|
simflofy.initialize.mongo | Will generate the collections required for Simflofy and create indexes for fast searches. Set this to false after your initial run, as it will cause long startup times for more heavily used systems. |
simflofy.initialize.bootstrap | Will load some default configurations into the database. Set to false after the first run. |
simflofy.initialize.update | Mostly needed for a 2.X to 3.X upgrade. Will run patches which remove deprecated connectors, add the new ones, transform out of date configurations to be used for 3.X. Set to false after the first run. |
simflofy.initialize.runallpatches | If this and simflofy.initialize.update is set to true, all patches will be run, regardless of whether they have been previously run. |
simflofy.initialize.demoview | Will use widget instances from the bootstrap to generate a sample Content View with some pre-loaded content. All of the connectors generated by this option are overwritten on startup,so they are not appropriate for reuse. |
simflofy.encrypt.db.passwords | If true , mongo.db.password will be encrypted on startup. |
General Configuration
| Property | Description |
|---|---|
simflofy.multi.tenant | Set to true to put Simflofy Admin in multi-tenant mode. This will allow the creation of new tenants (orgs) and also the creation of users for the orgs. |
simflofy.global.org | The name of the global organization. Still needed for single tenant mode. |
simflofy.global.dbname | The name of the global organizations database in MongoDB. |
simflofy.aes256.encryption | If true , passwords will be encrypted using AES256 when stored in the database. |
simflofy.tsearch.location | The full URL of a TSearch instance associated with Simflofy Admin. This will be used to provide "Go To" links for Content Views |
simflofy.max.upload.size | The maximum upload size, in bytes, that Content Services will accept. This does not bypass any API restrictions for connectors. |
simflofy.context.path | sed in email notifications to link back to your instance. Takes the format http://myhost:8080/simflofy-admin |
simflofy.report.dir | If auditing using the CSV option for job auditing, this will be location where the file is stored. If left empty, tomcat/temp will be used. |
simflofy.threads.corePoolSize | Initial size of the pool of threads used to run Jobs. Limits the number of simultaneous jobs that run at once. |
simflofy.threads.maxPoolSize | Max size of the thread pool used to run jobs. |
simflofy.default.logo | Image file placed in simflofy-admin/WEB-INF/classes/logo |
simflofy.default.favicon | .ico file placed in simflofy-admin/WEB-INF/classes/favicon |
Email Server Configuration
| Property | Description |
|---|---|
email.active | Set to true to allow emails to be sent, false to turn off all emails. |
email.smtp.port | SMTP Port for sending email notifications. |
email.smtp.host | SMTP Host for sending email notifications. |
email.smtp.username | Username for SMTP authentication. |
email.smtp.password | Password for SMTP authentication. |
email.smtp.auth | true if needing to authenticate with SMTP. |
email.smtp.starttls.enable | Some SMTP servers need this to true. |
email.bcc | Comma delimited list of email addresses to copy emails to. |
email.from.address | The from address in the email notifications. |
Distributed Mode
| Property | Description |
|---|---|
simflofy.server.mode | SINGLETON or DISTRIBUTED. Singleton means that jobs are run by the same instance of Simflofy in which they were called. DISTRIBUTED means you have clustered instances of Simflofy, with one of them acting as the "Job Runner" |
simflofy.server.job.runner | In DISTRIBUTED mode, one or more nodes must be set to true or jobs will not run. |
Job History Cleanup
| Property | Description |
|---|---|
simflofy.job.cleanup.interval | How often Simflofy will check for jobs that require history cleanup. Format: [integer][time unit],so 1d is 1 Day. Also supports M(Month), and w(Week). |
simflofy.job.cleanup.time | The hour the history cleanup check will be performed. 0 is midnight, 23 is 11PM |
Event Processing
| Property | Description |
|---|---|
simflofy.event.queue | All Content Service events will be added to a queue for processing. These events trigger event jobs. |
simflofy.server.event.rule.processor | When events are queued they need to be processed (matched) to any Event Configurations. You must have at least one event rule processor if you queue events |
simflofy.event.queue.retain | How many days to retain unprocessed events in the queue. |
Internal Auditing
| Property | Description |
|---|---|
simflofy.internal.audit.audit | true or false. Whether internal audit data will be collected |
simflofy.interlal.audit.all | true or false. Whether all audit types should be collected |
simflofy.interlal.audit.list | A comma delimited list of internal audit types. |
Discovery
| Property | Description |
|---|---|
simflofy.discovery.collect | true or false. Initialize the Discovery Data Collection service on startup |
simflofy.discovery.report | true or false. Initialize the Discovery Report Generation service on startup |
simflofy.discovery.job.check | How often to check if a data collection jobs or report generation has completed. Format: [integer][time unit],so 20s is 20 seconds. Also supports m for Minutes. |
simflofy.discovery.delay | How long to wait after startup to begin data collections or report generation. Format: [integer][time unit],so 20s is 20 seconds. Also supports m for Minutes. |
simflofy.discovery.schedule.check | How often Monitor threads will check for changes in schedule/report configurations. Format: [integer][time unit],so 5m is 5 minutes. Also supports m for Minutes. |
Related Articles: