chef\config\chef-evn-stack\env-scms.yaml

This env-scms.yaml file is an example of setting variables that will be used by Chef recipes to dynamically update ColdFusion files

tf_splunk:
  client_enabled: true
  monitors:
      - source: scms-error
         source_type: log4j
         path: C:\ColdFusion\cfusion\logs\coldfusion-error.log
        app_index: commerce
      - source: scms-out
         source_type: log4j
        path: C:\ColdFusion\cfusion\logs\coldfusion-out.log
        app_index: commerce
      - source: scms-exception
        source_type: log4j
        path: C:\ColdFusion\cfusion\logs\exception.log
        app_index: commerce

Configure environment to enable Splunk

  tf_datadog:
    agent_enabled: true
    handler_enabled: true
  datadog:
  iis:
    instances:
        - host: localhost

Configure environment to enable Datadog

tf_scms:
  max_jvm: Xmx1024m
  min_jvm: Xms1024m
  server_environment: 'env'
  server_hostname: 'env.thermofisher.com'

Setting variables which will be used to update jvm.config

  dsName1:
    primary_db: databaseName01
    secondary_db: databaseName02
    service: serviceName
    user_name: userName
    user_password: encryptedPWD
  dsName2:
    primary_db: databaseName
    service: serviceName
    user_name: userName
    user_password: encryptedPWD
  dsName3:
    primary_db: databaseName01
    secondary_db: databaseName02
    service: serviceName
    user_name: scms_user
    user_password: encryptedPWD
  dsName4:
    db_server: 10.53.02.25
    db_name: databaseName
    user_name: userName
    user_password: encryptedPWD
  dsName5:
    db_server: 10.50.20.255
    db_name: databaseName
    user_name: userName
    user_password: encryptedPWD

Setting variables which will be used to update neo-datsource.xml



COLDFUSION INTERFACING WITH AWS