Attachment 1485238 Details for Bug 1559622 – Latest server configuration file

Latest server configuration file

rhq-server.properties (text/plain), 18.83 KB, created by Prachi on 2018-09-20 17:18:12 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Prachi

Created: 2018-09-20 17:18:12 UTC

Size: 18.83 KB

patch

obsolete

>#################### RHQ Server Configuration Properties ####################
>
>#############################################################################
># Database Settings
># -----------------
># INSTALLATION ACTION REQUIRED!
>#   All properties must be explicitly set for the desired database vendor.
>#
># These should point to the database that your RHQ Server will use as
># its backend RDBMS storage.
># If you are using Oracle:
>#   - comment out the Postgres settings
>#   - uncomment the Oracle settings below
>#   - adjust the values to match your environment
>#
># For proper URL format and property values, you may need to consult your
># database administrator or database documentation. This is an important
># consideration when using Oracle Real Application Clusters or other data
># replication or fail-over configurations.
>#
># NOTE: rhq.server.database.password is not to be set to the actual password
>#       but instead should be the encoded password value as generated by:
>#          rhq-encode-value.sh(.bat)
>#############################################################################
>
># PostgreSQL database
>rhq.server.database.connection-url=jdbc:postgresql://127.0.0.1:5432/rhq
>rhq.server.database.user-name=rhqadmin
>rhq.server.database.password=1eeb2f255e832171df8592078de921bc
>rhq.server.database.type-mapping=PostgreSQL
>rhq.server.database.server-name=127.0.0.1
>rhq.server.database.port=5432
>rhq.server.database.db-name=rhq
>hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect
>rhq.server.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
>
># Oracle database
>rhq.server.database.connection-url=jdbc:postgresql://127.0.0.1:5432/rhq
>#rhq.server.database.user-name=rhqadmin
>#rhq.server.database.password=1eeb2f255e832171df8592078de921bc
>#rhq.server.database.type-mapping=Oracle10g
>#hibernate.dialect=org.hibernate.dialect.Oracle10gDialect
>#rhq.server.quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
>
>#############################################################################
># Server Settings
># ---------------
># UPGRADE ACTION REQUIRED! The following property must be explicitly set:
>#   rhq.server.high-availability.name
>#
># These are miscellaneous settings that the server will use to customize itself
># to the environment in which it is running. These are settings you usually
># want to change or at least be aware of.
>#############################################################################
>
># Defines what this server's name is to be known as to the RHQ system.
># It doesn't necessarily have to be an IP address or hostname, but it can be.
># If left blank, the RHQ Server will pick a name for itself based on the
># hostname it is running on.
># NOTE! If you are upgrading an existing server, this must be the same name
># as the server being upgraded.
>rhq.server.high-availability.name=
>
># Email settings used to connect to an SMTP server to send alert emails.
>rhq.server.email.smtp-host=smtp.corp.redhat.com
>rhq.server.email.smtp-port=25
>rhq.server.email.from-address=rhqadmin@prachi-jon3311.bc.jonqe.lab.eng.bos.redhat.com
>
>#############################################################################
># Host and Port Bindings
># ----------------------
># INSTALLATION ACTION REQUIRED! The following property must be explicitly set:
>#   jboss.bind.address
>#
># These define the ports the RHQ Server will bind to. Most of the time
># you can leave these alone. You can change these default values to
># conform to your own environment's requirements, such as the IP address
># the RHQ Server will bind to (jboss.bind.address) and the ports
># browsers will use to access the RHQ web application
># (rhq.server.socket.binding.port.http, rhq.server.socket.binding.port.https)
># If you change the binding address, you might also want to change
># "rhq.autoinstall.public-endpoint-address" as well.
>#############################################################################
>
># The bind address for the RHQ server (jboss server).  To bind the server on
># all network interfaces set to 0.0.0.0, otherwise a specific IP address.
># jboss.bind.address=0.0.0.0
>jboss.bind.address=0.0.0.0
>
># By default only local management connections 
>jboss.bind.address.management=127.0.0.1
>
>jboss.socket.binding.port-offset=0
>
>jboss.management.native.port=6999
>jboss.management.http.port=6990
>jboss.management.https.port=6443
>
># This is high availability identifier for each RHQ Server instance. Must be unique, max 28 characters and can not
># include dash character ('-')
>#jboss.tx.node.id=1
>
>rhq.server.socket.binding.port.ajp=7009
>rhq.server.socket.binding.port.http=7080
>rhq.server.socket.binding.port.https=7443
>rhq.server.socket.binding.port.jacorb=2528
>rhq.server.socket.binding.port.jacorb-ssl=2529
>rhq.server.socket.binding.port.messaging=4449
>rhq.server.socket.binding.port.messaging-throughput=4455
>rhq.server.socket.binding.port.osgi-http=7090
>rhq.server.socket.binding.port.remoting=3447
>rhq.server.socket.binding.port.txn-recovery-environment=3712
>rhq.server.socket.binding.port.txn-status-manager=3713
>
>#############################################################################
># Installer Settings
># ------------------
># INSTALLATION ACTION REQUIRED! Review the default settings:
>#
># These enable the installer when starting for the first time. To do so,
># first ensure all values in this properties file are appropriately set
># for your environment. Once you are sure all values are as you want them,
># set rhq.autoinstall.enabled=true and run the server then run the installer.
>#
># rhq.autoinstall.enabled
>#    This must be true to trigger the automatic install.
># rhq.autoinstall.database
>#    Allowed values: auto, overwrite, skip:
>#     auto     : create a new schema if one does not exist, otherwise
>#                upgrade the existing schema as needed (keep  existing data).
>#     overwrite: create a new schema even if one exists (lose existing data).
>#     skip     : leave existing database as is. WARNING! You must ensure your
>#                database schema already exists and is up to date.
># rhq.autoinstall.public-endpoint-address
>#    The public IP/hostname that all agents will use to talk to this server.
>#    If not set, a value to use is determined at auto-install time.
># rhq.autoinstall.public-endpoint-port
># rhq.autoinstall.public-endpoint-secure-port
>#    The public ports that all agents will use to talk to this server.
>#    If not set, values to use will be determined at auto-install time.
>#    You can normally leave these empty unless you have a special setup
>#    where the server's bind ports are exposed differently to remote
>#    clients (e.g. within a Docker container).
># rhq.autoinstall.server.admin.password
>#    The password for the built-in "rhqadmin" superuser. If not set the
>#    password will be prompted for by the "rhqctl install" command.
>#
>#    NOTE: rhq.autoinstall.server.admin.password is not to be set to the
>#          actual password but instead should be the encoded password value
>#          as generated by: rhq-encode-value.sh(.bat)
>#############################################################################
>
>rhq.autoinstall.enabled=true
>rhq.autoinstall.database=auto
>rhq.autoinstall.public-endpoint-address=
>rhq.autoinstall.public-endpoint-port=
>rhq.autoinstall.public-endpoint-secure-port=
>rhq.autoinstall.server.admin.password=x1XwrxKuPvYUILiOnOZTLg==
>
>#############################################################################
># Advanced Settings
># -----------------
># The settings below can usually be left as-is. These are advanced settings
># and should only be changed if you know what you are doing.
>#############################################################################
>
># Enable debug messages from RHQ code
>rhq.server.log-level=INFO
>
># Set this to true to have the server reject agent requests upon startup.
>rhq.server.maintenance-mode-at-startup=false
>
># RHQ Server's remote endpoint for agents to talk to
># bind-address and bind-port are derived from the HA server definition,
># if you set the address/port here, they will override the HA server
># definition found in the database
>rhq.communications.connector.transport=servlet
>rhq.communications.connector.bind-address=
>rhq.communications.connector.bind-port=
>rhq.communications.connector.transport-params=/jboss-remoting-servlet-invoker/ServerInvokerServlet
>
># Multicast detector configuration for auto-discovery
>rhq.communications.multicast-detector.enabled=false
>rhq.communications.multicast-detector.bind-address=
>rhq.communications.multicast-detector.multicast-address=224.16.16.16
>rhq.communications.multicast-detector.port=16162
>
># Server-side SSL Security Configuration for HTTPS thru Tomcat
># These are used for browser https access and
># for incoming messages from agents over sslservlet transport.
># [Due to issue https://issues.jboss.org/browse/WFLY-1177, you cannot change
># rhq.server.tomcat.security.keystore.file or rhq.server.tomcat.security.truststore.file
># after you install RHQ. If you need to change those again, you must manually do so in standalone-full.xml.]
># Note that security algorithm settings are commented out - the defaults will be determined at runtime
># based on the JVM the server is running in (for IBM JVMs, the algorithm will default to "IbmX509",
># for all other JVMs, the algorithm will default to "SunX509"). If you need a specific algorithm value,
># you may hardcode it here in this file by uncommenting the lines and setting the values explicitly.
>rhq.server.tomcat.security.client-auth-mode=false
>rhq.server.tomcat.security.secure-socket-protocol=TLSv1,TLSv1.1,TLSv1.2
>#rhq.server.tomcat.security.algorithm=SunX509
>rhq.server.tomcat.security.keystore.alias=RHQ
>rhq.server.tomcat.security.keystore.file=${jboss.server.config.dir}/rhq.keystore
>rhq.server.tomcat.security.keystore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.server.tomcat.security.keystore.type=JKS
>rhq.server.tomcat.security.truststore.file=${jboss.server.config.dir}/rhq.truststore
>rhq.server.tomcat.security.truststore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.server.tomcat.security.truststore.type=JKS
>
># Server-side SSL Security Configuration (for incoming messages from agents)
># These are used when secure transports other than sslservlet are used
>rhq.communications.connector.security.secure-socket-protocol=TLS
>rhq.communications.connector.security.keystore.file=${jboss.server.config.dir}/rhq.keystore
>#rhq.communications.connector.security.keystore.algorithm=SunX509
>rhq.communications.connector.security.keystore.type=JKS
>rhq.communications.connector.security.keystore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.communications.connector.security.keystore.key-password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.communications.connector.security.keystore.alias=RHQ
>rhq.communications.connector.security.truststore.file=${jboss.server.config.dir}/rhq.truststore
>#rhq.communications.connector.security.truststore.algorithm=SunX509
>rhq.communications.connector.security.truststore.type=JKS
>rhq.communications.connector.security.truststore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.communications.connector.security.client-auth-mode=none
>
># Client-side SSL Security Configuration (for outgoing messages to agents)
>rhq.server.client.security.secure-socket-protocol=TLS
>rhq.server.client.security.keystore.file=${jboss.server.config.dir}/rhq.keystore
>#rhq.server.client.security.keystore.algorithm=SunX509
>rhq.server.client.security.keystore.type=JKS
>rhq.server.client.security.keystore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.server.client.security.keystore.key-password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.server.client.security.keystore.alias=RHQ
>rhq.server.client.security.truststore.file=${jboss.server.config.dir}/rhq.truststore
>#rhq.server.client.security.truststore.algorithm=SunX509
>rhq.server.client.security.truststore.type=JKS
>rhq.server.client.security.truststore.password=RESTRICTED::5fb458952ebdaa86aa0b4e8d3eac5d13
>rhq.server.client.security.server-auth-mode-enabled=false
>
># Operations/controls timeout
># Defines the default timeout for all operations (specified in seconds)
>rhq.server.operation-timeout=600
>
># Additional Quartz settings
>rhq.server.quartz.selectWithLockSQL=SELECT * FROM {0}LOCKS ROWLOCK WHERE LOCK_NAME = ? FOR UPDATE
>rhq.server.quartz.lockHandlerClass=org.quartz.impl.jdbcjobstore.StdRowLockSemaphore
>
># Concurrency limits for incoming UI and agent messages
>rhq.server.startup.web.max-connections=200
>rhq.server.agent-downloads-limit=45
>rhq.server.client-downloads-limit=5
>rhq.communications.global-concurrency-limit=30
>rhq.server.concurrency-limit.inventory-report=5
>rhq.server.concurrency-limit.availability-report=25
>rhq.server.concurrency-limit.inventory-sync=10
>rhq.server.concurrency-limit.content-report=5
>rhq.server.concurrency-limit.content-download=5
>rhq.server.concurrency-limit.measurement-report=10
>rhq.server.concurrency-limit.measurement-schedule-request=10
>rhq.server.concurrency-limit.configuration-update=10
>
># Content Local Filesystem Repository
>rhq.server.content.filesystem=${jboss.server.data.dir}/packagebits
>
># The frequency (in millis) the server checks for updated plugins
>rhq.server.plugin-scan-period-ms=300000
>
># When this is enabled, the server at start up will compare its endpoint
># address to the host name/address found on the host machine. If they differ,
># the server endpoint address will be updated to the value found on the host
># machine. This is targeted for use in cloud deployments where IP addresses
># change frequently, but it can be of use in other deployment settings where
># you have to deal with IP address changes.
>rhq.sync.endpoint-address=false
>
># When this is enabled, the server will request that agents send content for
># for binary files that are being monitored for drift. The content for those
># files will then be persisted on the server. By default, the server does not
># persist content for well known binary file types like .ear, .war, .zip, .so,
># etc. The server does however persist content for text files or any other
># files that are not known binary types.
>#rhq.server.drift.store-binary-content=false
>
># The installer will create a default EAP management user named 'rhqadmin'.
># The password is generated and obfuscated and specified here.  This should
># not be edited.
>rhq.server.management.password=-66d7b663a4d7079f207a6df87216de44
>
>
>#############################################################################
># Storage cluster configuration settings
>#
># IMPORTANT NOTE:
># - Storage Node properties will be stored in the database
>#    after the initial install. The server will use database stored
>#    properties during operation and after restarts.
># - Additional servers in an HA topology will use database stored Storage
>#    Node properties. So properties set in this configuration file will be
>#    overriden on install with the database values.
>#############################################################################
>
># The username RHQ will use to authenticate against the Storage Cluster.
># The value is generated and should not be edited.
>rhq.storage.username=zhjoylqt
>
># The password RHQ will use to authenticate against the Storage Cluster.
># The value is generated and obfuscated and should not be edited.
>rhq.storage.password=-1623a9b18681bc0f207a6df87216de44
>
># A comma-delimited list of storage nodes. Each Storage node uses this list as
># contact points to find other nodes in the cluster and learn the ring
># topology. The RHQ server(s) use this list to connect to the cluster;
># therefore, this property MUST BE SET in order for RHQ to talk to the Storage.
># Cluster. The of an entry is as follows:
>#
>#    hostname1,hostname2
>#
># Note that this is actually an installer setting. Changing the value after
># installation will have no effect.
>rhq.storage.nodes=prachi-jon3311.bc.jonqe.lab.eng.bos.redhat.com
>
># The ports used by storage nodes to communicate with each other
># and used by the RHQ server(s) to communicate with the cluster.
># Both properties are required.
>#
>rhq.storage.cql-port=9142
>rhq.storage.gossip-port=7100
>
>#############################################################################
># Storage client settings
>#
># The following are advanced settings the client (i.e., driver) that
># communicates with the storage cluster
>#############################################################################
>
># The request limit will automatically change by this amount when there is a
># topology change event. The change will be persisted to this file. Topology
># change events include nodes being added/removed and nodes going up/down.
># Defaults 30,000 if undefined.. If specified the value is parsed as a double.
>rhq.storage.request.limit.topology-delta=30000
>
># If a request timeout occurs, there is a good possibility that it could be
># followed by successive timeouts due to read/write patterns. This property
># specifies a dampening period such that the request throughput will only be
># decreased once for all timeouts that occur during said period. Defaults to
># 30 seconds if undefined. The value is specified in milliseconds and is parsed
># as a long.
>rhq.storage.request.limit.timeout-dampening=30000
>
># The warmup time during which the request limit is allowed to grow from
># 50% of the maximum to 100% of the set request limit value. The value is
># in minutes. Defaults to 3 minutes if undefined.
>rhq.storage.request.limit.warmup-period=3
>
># Sets the maximum throttling value for warmup periods. If a timeout occurs,
># the request rate is halved with increased warmup period (as configured above).
># This setting limits the maximum the warmup is allowed to grow to and can be
># counted as warmup-period * max-warmup-counter, which is by default 30 mins.
># This value defaults to 10 if undefined.
>rhq.storage.request.limit.max-warmup-counter=10
>
>##############################################################################
># Metrics aggregation settings
>#
># Note that if you commit the RHQ Server into inventory, these settings can be
># managed through the resource configuration of the Measurement Subsystem.
># Changes made through the Measurement Subsystem resource are applied
># dynamically at runtime whereas directly editing these properties requires a
># a server restart for changes to take effect.
>##############################################################################
>
># Specifies the number of schedules for which data will be fetched per thread.
># A higher value can improve aggregation performance at the cost of greater
># memory utilization.
>rhq.metrics.aggregation.batch-size=5
>
># Specifies the number of batches that can be processed in parallel. A higher
># value can improve aggregation performance at the cost of greater memory
># utilization.
>rhq.metrics.aggregation.parallelism=3
>
># The number of threads to use during aggregation. It defaults to
># ceiling(5, num_cores).
>rhq.metrics.aggregation.workers=4
>
># A limit, specified in days, on the age of raw data that is ingested. If raw
># data has a timestamp that is more than limit days old, then it is not stored.
># This prevents raw data that is for example a year old from being stored.
>rhq.metrics.data.age-limit=3

Actions: View

Attachments on bug 1559622: 1485238